Plan and review the Atlassian Confluence migration and the data that Confluence will migrate

This guide assumes migration of your Confluence Server data into Confluence Cloud, following the Atlassian Migration Assistant instructions.

Some additional steps are required.

Only the current Comala Document Management workflow state and the user associated with the transition event are migrated as part of the Atlassian migration.

The workflow history is not migrated. A record of workflow activity can be added as a CSV file. The CSV file is created for a page using the Attach Activity option in the space tools document management dashboard. The file is added as a page attachment for each page with workflow activity.

A vendor check error is shown if the Attach Activity utility has not been run in a space.

The Comala Document Management app is not migrated and the Comala Document Management app must be installed. The server license is not transferable (a free temporary license is available).

Check the following

Product Comparison for the Comala Document Management app feature set in Cloud
Pages with restrictions - these are not migrated

Pages with restrictions are listed in the pre-migration vendor checks in the Atlassian Migration Assistant.

It is recommended that you should migrate individually each space where a workflow is applied.

More Atlassian resources are available on the Atlassian Migrate to Confluence Cloud support page.

Use your migration as an opportunity to clean up your server instance before running your test migration. The more data you migrate, the longer and more complex your migration is likely to be and could affect Cloud performance later on.