Comala Document Management | Migration to Cloud (recap)

After reviewing the migration process detailed in our documentation Migration Process Steps, you can proceed to examine the general steps for migrating a Comala Document Management from Confluence Data Center/Server to Confluence Cloud below.


0. First, please install the Confluence Cloud Migration Assistance app in your source instance, if the app is already installed, please ensure it is on its latest version.

1. Go to Confluence Administration > General Configuration > Migration Assistant or just go directly to http://<YOUR_HOSTNAME>/admin/migration.action#home

Screenshot 2024-01-10 at 12.20.37.png

2. Click on ASSESS YOUR APPS and set Comala Document Management as ‘Needed in Cloud.’ Click Done.

Comala Document Management needs to be installed in the Cloud / Target instance for the app to be visible on this part.

Screenshot 2024-01-10 at 12.20.57.png

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 proceed with the remaining migration steps or directly move on to MIGRATE YOUR DATA.

6. Click on Create new migration:

7. Connect to the Cloud and name your migration process:

7.a. Complete the fields and click 'Choose what to migrate.'

7.b. Select the spaces, user groups, and apps. Click check for errors.

7.c. After completing the pre-migration checks and addressing any existing errors, click Review Migration and then select Run Now.

Note: in this step, you’ll need to check the ‘App vendor checks’:

  • Page restrictions verification:

    Pages with restrictions will not be migrated with their Comala Document Management data. With the release of Comala Document Management v6.17.7 and onwards, the Atlassian Migration Assistant pre-check App vendor checks screen now lists affected pages in a downloadable CSV file. 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:
    To maintain a record of the workflow history, the Attach Activity utility (available from Comala Document Management 6.18.0 or later) supports creating a record of workflow activity for a document as a CSV file. The file is then automatically attached to each page in your server instance.

    The workflow history CSV is subsequently migrated as an attachment for each page. The Attach Activity option needs to be executed for each space before migrating to cloud. (Please refer to our documentation ‘Add workflow history as an attachment using Attach Activity option’ for more details).

    • Please navigate to Space tools → Document Management → Attach Activity → Generate CSV.

    • Upon generating the CSV, the workflow history of each page will be attached to its corresponding page.

    • NOTE: We recommend disabling Confluence Notification when performing this action since all space or page watchers might be notified, potentially leading to numerous emails from Confluence sent to these users.

7.d. The migration process will start, and the progress will be visible in the Migrations dashboard.

8. 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:

If you are unable to see the migrated spaces at this point, please make sure that you have the correct access (Cloud Permissions) to the migrated Confluence spaces.

8.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 the target space and then:

Space Settings → Comala Document Management → Create New Workflow → Use a Temporal Name → switch to the JSON view ‘{}’.

  • Target instance view:


8.b.If you manually recreate the workflow, choose a default workflow (any workflow), rename the default workflow, and then begin recreating your Data Center/Server workflow on Confluence Cloud. Remember to maintain the exact same names for the workflow statuses to ensure they are migrated correctly (CDM is case-sensitive).

8.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 manually apply the desired workflows.

More information about these modes can be found here:

We recommend that you recreate and test your CDM Cloud Workflow in a testing space or Confluence Sandbox before proceeding with the migration.

8.d.The pages will be initialized and have the same last state in the Data Center/ Server. Please keep in mind that only the last document activity entry (that the page had in the source instance) will be visible.

However, the rest of the workflow history will be attached to the page in a CSV file (if step 7 was completed).

Pages with restrictions in the source instance won’t apply the desired workflow if step 7 (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: