Manual migration tasks

Manual Migration Tasks

Due to differences in the Atlassian cloud and server platforms the migration of the Atlassian Migration Assistant will only migrate the following

• the current workflow state data for each page

• the user details for the change to the current state in the Comala Document Management workflow for each page

You will need to undertake and check some manual tasks to complete the set of your cloud site. These tasks include

User migration

The migration of the actual users for access must be done as part of the Atlassian Migration Assistant. If the migration has not included the users then errors may occur when completing the space setup in cloud and applying your Comala Document Management workflow.

Page restrictions

Any page with view or edit restrictions cannot be included in migration to Cloud with the page restrictions in place. You will need to temporarily remove the restrictions to allow migration of these pages to take place without any errors.

If you have a significant number of pages with restrictions please contact support.

Install Comala Document Management app

Prior to migration you will need to install the Comala Document Management for Cloud app.

Workflow History

Only the current state of a page with an applied workflow is exported as part of the Atlassian migration process. We do not support migration of workflow history (also known as Page Activity). The workflow state is added as a file attachment to each document in cloud.

If workflow history is required for audit you may need to consider options of either

• exporting this as CSV for each page

• or running your legacy server instance as 'read only'

Tasks after completing the Atlassian migration process

Once you have enabled migration and undertaken the migration using the Atlassian Migration Assistant, to complete your cloud site you need to undertake tasks for

• Page:
  Setting workflow state in cloud
• Page:
  Use Workflow Translator for Cloud in server to translate your server workflows to cloud compatible code
• Page:
  Apply your Comala Cloud workflow to the content
• Page:
  Recreate your Comala workflow in Cloud using workflow builder or the JSON editor
• Page:
  Add and configure any additional apps to your cloud site

Avoiding migrated user login issues

After the migration process has been completed it is recommended to exit and log in so migrated users are available (otherwise, the Cloud instance doesn’t recognize them).

Maintaining an audit history

If your organization is in a Compliance/Regulatory industry and you periodically get audited, then you will be required to keep Confluence on a Server running in read-only mode so auditors can review your previous Workflow History/Page Activity. The same goes for the Page Status.

You cannot migrate the full workflow history and page status to Cloud.