Support and troubleshooting for migration

Migration problem

If you have a problem and the migration is unsuccessful, you should check the details and assessments in the Confluence Cloud Migration Assistant and rerun the migration.

If you can’t resolve a migration problem using the Confluence Cloud Migration Assistant, Appfire support can review the data on your Comala Document Management app usage in your hosted instance.

To help our team help you, use the support console in the Comala Document Management Server or Data Center app to download a Support package file and attach it to the support ticket.

Create a support package for a support request

For help in analyzing the use of your server instance in Comala Document Management, you can use the server app support console to capture helpful information on your current usage of the Comala Document Management app.

Create an Appfire Comala support package for each space using the document management support console option in space tools.

Add the Usage data and the Support package to a related support request.

Page restrictions

Restricted pages can block migration of Comala workflow data. A pre-migration check in the Atlassian CCMA identifies these pages. You can then remove these page restrictions before the migration, either

Remove all restrictions from pages within each space, or
Delete only the restrictions for pages with an applied workflow, then restore them in the cloud.

You can find all the pages with restrictions and with an applied workflow:

Manually - Run the Content Restrictions report in the Workflows Usage screen to generate and download a CSV file listing the affected documents
Scripted: Using the following SQL query:

SQL Query Find all restricted pages with an applied workflow

-- Explicit permissions
SELECT 
  c.CONTENTID AS content_id,
  c.TITLE AS title,
  s.SPACEKEY AS space_key,
  cps.CONT_PERM_TYPE AS permission_type,
  cp.USERNAME AS username,
  cp.GROUPNAME AS groupname,
  'explicit' AS restriction_source,
  NULL AS ancestor_id
FROM BANDANA b
JOIN SPACES s ON b.BANDANACONTEXT = s.SPACEKEY
JOIN CONTENT c ON c.SPACEID = s.SPACEID
JOIN CONTENT_PERM_SET cps ON c.CONTENTID = cps.CONTENT_ID
JOIN CONTENT_PERM cp ON cps.ID = cp.CPS_ID
JOIN OS_PROPERTYENTRY pe ON pe.entity_id = c.CONTENTID
WHERE 
  b.BANDANAKEY LIKE '%com.comalatech.workflow.production.template%'
  AND c.CONTENT_STATUS = 'current'
  AND b.BANDANAVALUE NOT LIKE '%disabled=true%'
  AND pe.entity_key = 'metadata.awpState'
  AND (pe.string_val IS NOT NULL or pe.text_val IS NOT NULL)
  AND s.SPACEKEY IN ('ADD THE SPACE KEY HERE')
  
  
UNION ALL 
  
  -- Inherited permissions
SELECT 
  c.CONTENTID AS content_id,
  c.TITLE AS title,
  s.SPACEKEY AS space_key,
  cps.CONT_PERM_TYPE AS permission_type,
  cp.USERNAME AS username,
  cp.GROUPNAME AS groupname,
  'inherited' AS restriction_source,
  ca.ANCESTORID AS ancestor_id
FROM BANDANA b
JOIN SPACES s ON b.BANDANACONTEXT = s.SPACEKEY
JOIN CONTENT c ON c.SPACEID = s.SPACEID
JOIN CONFANCESTORS ca ON c.CONTENTID = ca.DESCENDENTID
JOIN CONTENT ancestor ON ancestor.CONTENTID = ca.ANCESTORID
JOIN CONTENT_PERM_SET cps ON ancestor.CONTENTID = cps.CONTENT_ID
JOIN CONTENT_PERM cp ON cps.ID = cp.CPS_ID
JOIN OS_PROPERTYENTRY pe ON pe.entity_id = c.CONTENTID
WHERE 
  b.BANDANAKEY LIKE '%com.comalatech.workflow.production.template%'
  AND c.CONTENT_STATUS = 'current'
  AND b.BANDANAVALUE NOT LIKE '%disabled=true%'
  AND pe.entity_key = 'metadata.awpState'
  AND (pe.string_val IS NOT NULL or pe.text_val IS NOT NULL)
  AND s.SPACEKEY IN ('ADD THE SPACE KEY HERE')

The Atlassian CCMA includes a pre-migration app vendor check for page restrictions. If page restrictions are identified on a document with an active workflow, the check displays a warning and a link to the hosted app’s Workflow Usage screen, where you can run the Content Restrictions report.

Moving your page workflows

Page workflows are not migrated to the cloud. If required, you can consolidate these as space workflows in two ways:

Manually - Consolidating the page workflow in each space
Scripted - Bulk consolidation using the following script:

Consolidate page workflows script

Script:
How to run it:python3 consolidate_page_workflows.py page-workflows.csv
Description: This script reads the CSV file containing page workflows from the Workflows Usage Report and consolidates them into space-level workflows using the Confluence REST API. When run, the script:

Prompts you to choose the grouping logic:
- 1: Group by Space Key + Workflow Name
- 2: Group by Space Key + Workflow Name + Workflow Markup
Automatically generates a unique label for each group:
WorkflowName (cleaned) + incremental number (e.g., SimpleApproval1)
Sends a curl request per group to the Confluence REST API to perform the consolidation.

In both cases, page workflows are consolidated as a label space workflow.

See: Moving your workflows to the cloud

Complex Confluence instance

Some things can increase the complexity of your migration, and you might need some help planning. For example, if the migration involves

a large amount of data or users
multiple products and apps

The Atlassian Migration Guide includes a range of resources and guides.

You can contact our Appfire support or an Atlassian Solution Partner to help find the best fit for your migration for large instances or instances with many users and user groups.

Cloud Migration Resources