This guide assumes you will migrate migration of your Confluence Server data into Confluence Cloud, following the Atlassian Migration Assistant instructions.
| Note |
|---|
Be aware that there are some 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.
| Info |
|---|
The workflow history is not migrated. A record of workflow activity can be imported added as a CSV attachment for each pagefile. The CSV file can be created and added as an attachement to each page in a space is created for a page using the Attach Activity option in the space tools document management dashboard. If . 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, a vendor check error is displayed in the Atlassian Migration tool. |
The Comala Document Management app is not migrated and the Comala Document Management app must be installed. The server license is not transferable (although a free temporary free license is available).
You should be sure to checkCheck the following
- What is migrated to the Cloud?
- Product Comparison for the Comala Document Managment Management app feature set in Cloud
- Cloud Roadmap to give you an overview of any critical features you might require and when they will be availablePages 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.
| Tip |
|---|
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. |
.png?version=1&modificationDate=1720536157140&cacheVersion=1&api=v2&width=145)
.png?version=1&modificationDate=1720536157140&cacheVersion=1&api=v2&width=150)
