After acknowledging the migration process explained in our documentation here: Migration Process Steps, here are the steps of a general migration from Confluence Data Center/ Server to Confluence Cloud:
\uD83D\uDCD8 Instructions
0. First, please Install the Confluence Cloud Migration Assistance app in your source instance.
1. Go to Confluence Administration > General Configuration > Migration Assistant or just go directly to http://<YOUR_HOSTNAME>/admin/migration.action#home
2. Click on ASSESS YOUR APPS and set Comala Document Management as ‘Needed in Cloud.’ Click Done.
Note: The Comala Document Management app needs to be installed in the Cloud / Target instance for the app to be visible here:
3. Now, in the Cloud Migration Assistant Home, click on PREPARE YOUR APPS; you should see something like this:
4. Review the users, groups, and email domains and click Done.
5. Then continue with the other migration steps or go directly to MIGRATE YOUR DATA.
6. Click on Create new migration:
7. Connect to the Cloud and name your migration process:
6.a. Complete the fields and click 'Choose what to migrate.'
6.b. Select the spaces, user groups, and apps. Click check for errors.
6.c. After getting the pre-migration checks and mitigating the existing errors, click Review Migration and Run Now.
Note: in this step, you’ll need to check the ‘App vendor checks’:
Page restrictions verification : (Please refer to our documentation What content will not be migrated successfully because of page restrictions? for more details).
choose Download report to save the CSV report file
remove restrictions from the listed pages
choose the Refresh button in the App vendor checks
Pages CSV activity attachment verification : (Please refer to our documentation ‘Add workflow history as an attachment using Attach Activity option’ for more details).
Please go to Space tools → Document Management → Attach Activity → Generate CSV.
After clicking generate CSV, the workflow history of each page will be attached to its corresponding page.
6.d. The migration process will start, and the progress will be visible in the Migrations dashboard.
7. Once the migration is completed, you can check the migration details, go to the new cloud instance, and rebuild the Comala space workflow in the migrated space/s:
7.a. Go to Space Settings → Document Management → Edit Workflow → Use Visual Builder to recreate the workflow manually.
Or click on Use code editor to paste the generated JSON code from the Data Center/ Server instance using the Workflow translator for cloud if you have CDM V6.18.0+.
To use the Workflow Translator feature, go to the source instance, check for the desired workflow, click edit, and select Translator
Copy and paste the JSON workflow obtained in the cloud instance (step 'a’).
On Confluence Cloud, go to your space and then
Space Settings → Comala Document Management → Create New Workflow → Use a Temporal Name → switch to the JSON view ‘{}’.
Target instance view:
More details about the workflow translator can be found here:
7.b. If you will manually recreate the workflow, select a default workflow (any workflow), change the name of the default workflow, and then start to recreate your Data Center/ Server workflow. Please recall keeping the exact same name of the workflow statuses for them to be appropriately migrated (CDM It's capital sensitive).
7.c. If you want to use ‘Space workflow mode’, please enable the space workflow. This action will apply the same workflow to all pages in the space.
But, on the other hand, if you want to use ‘Page workflow mode’, please do not enable the space workflow; instead, go to the desired pages and apply the desired workflows.
More information about these modes can be found here:
Add a Comala Document Management workflow to an individual page (page mode)
Add a Comala Document Management workflow to all content in space (space mode)
7.d. The pages will be initialized and have the same last state in the Data Center/ Server. Also, please keep in mind that only the visible document activity will be the last entry that the page had in the source instance.
But at the same time, the rest of the workflow history will be attached to the page in a CSV file. (if step 6 was completed).
Please note that pages with restrictions in the source instance won’t apply the desired workflow if step 6 (Restrictions) is not completed.
Note: you can get more details about what Comala Document Management features are migrated and what is not in our documentation here: