Page Comparison

Manual Migration Tasks

Due to differences in the Atlassian cloud and server platforms, the migration of the Atlassian Migration Assistant will only migrate migrates 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 Workflow events and activity history are not included in the migration. If this is required, additional actions must be considered to maintain an audit of workflow history.

Several manual tasks also need to be undertaken to complete the set of your cloud site. These tasks include

After migration, you need to log out and log in to the Cloud instance to avoid user migration issues.

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 in the cloud site.

Page restrictions

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

Contact support if you have a significant number of pages with restrictions

.

Install Comala Document Management app

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

Workflow

events and activities 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 or Document Activity). The current workflow state is added as a file attachment to each document in cloud custom content accessible by the cloud app.

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

• before migration, export the workflow history as CSV for each page by running the Attach Activity utility to create the CSV file and add it as an attachment to 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

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

The full workflow history and page status to Cloud cannot be migrated to the cloud and they are not accessible in the cloud app. If you need to retain access to a record for each page you must consider

• exporting the workflow history as CSV for each page by running the Attach Activity utility before migration

• or running your legacy server instance as 'read only

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

Running Attach Activity

Before migration, run the Attach Activity utility on a space-by-space basis to generate and attach workflow events and activity history for each page with workflow activity in the space.

The Attach Activity utility creates a CSV file of the workflow events and activities on each page in the space. The CSV file for each page is added as an attachment to each page

In space tools

• open the Document Management dashboard

• choose Attach History tab

The Attach Activity utility generation of page activity attachments is ignored by any workflow triggers in server with the attachmentadded or attachmentchanged event to avoid triggering an unwanted action.

Support