Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

After acknowledging the migration process explained in our documentation here: Migration Process Steps, here are the steps of a general You can take a look to the general steps for a Comala Document Management migration from Confluence Data Center/ Server to Confluence Cloud :below.

\uD83D\uDCD8 Instructions

0.First, please Install 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

...

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

Info

Comala Document Management

...

needs to be installed in the Cloud / Target instance for the app to be visible

...

on this part.

...

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

6. Click on Create new migration:

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

...

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

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

...

67.c. After getting completing the pre-migration checks and mitigating the 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 Choose Download report to save the CSV report file

    • remove Remove restrictions from the listed pages

    • choose 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 attachment verification : 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 go navigate to Space tools Document Management Attach Activity Generate CSV.

    • After clicking generate 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.

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

78.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

Info

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.

...

  • 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 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:

...

Screenshot 2024-03-08 at 16.24.42.pngImage AddedScreenshot 2024-03-07 at 20.57.12.pngImage Added

78.b.If you will manually recreate the workflow, select choose a default workflow (any workflow), change rename the name of the default workflow, and then start to recreate begin recreating your Data Center/Server workflow . Please recall keeping on Confluence Cloud. Remember to maintain the exact same name of names for the workflow statuses for them to be appropriately migrated (CDM It's capital to ensure they are migrated correctly (CDM is case-sensitive).

78.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.

...

...

Info

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. Also, please Please keep in mind that only the visible last document activity will be the last entry (that the page had in the source instance) will be visible.

But at the same timeHowever, the rest of the workflow history will be attached to the page in a CSV file . (if step 6 7 was completed).

Please note that pages Pages with restrictions in the source instance won’t apply the desired workflow if step 6 7 (Restrictions) is not completed.

...

Warning

There might be cases where you can encounter the error ‘Error - Must be admin’ or 'Forbidden - Must be admin', please ensure that the Comala Workflows for Confluence Cloud user has the corresponding space permissions, as explained here: Fixing Permissions Problem.

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@bc3e0baf
maxCheckboxfalse
sortmodified
showSpacefalse
reversetrue
typepage
cqllabel in ( "cdm-troubleshooting" , "cdm-product-confluence" , "cdm-action-permission" , "cdm-action-workflow" , "cdm-action-migrate" , "cdm-action-move" , "cdm-action-notify" , "cdm-action-restrictions" , "cdm-action-template" , "cdm-action-assign" ) and type = "page" and space = "SUPPORT"
labelskb-troubleshooting-article