Manual migration tasks
- Robert Alexander Marshall
Manual Migration Tasks
Due to differences in the Atlassian cloud and server platforms, the migration of the Atlassian Migration Assistant only 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
The hosted platform app workflows are not migrated. These can be translated to cloud-compatible templates and copied to the cloud. Some workflow elements are not translated and must be added using the cloud app workflow builder visual editor.
Page workflow events and activity history are not included in the migration data. If this is required, additional actions must be considered to maintain an audit of workflow history.
Hosted app tasks and migration considerations
Maintain 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.
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). When a workflow is applied, only this last workflow state is accessible in the cloud.
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 readonly
The CSV file attachment is not accessible by the cloud workflow. The migrated last workflow state, accessible by an applied cloud workflow, is added as a separate file attachment under custom content for a page.
If your organization is in a Compliance/Regulatory industry and you periodically get audited, then you can be required to keep Confluence on a Server running in read-only mode so auditors can review legacy workflow events and activities on the historical documents. The same goes for the Page Status.
Run 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
Each time the utility is run, a new Attach Activity CSV file is generated for each page and added as an additional attachment to the page.
FROM V6.18.5 SERVER FROM V7.2.1 DATA CENTER
The Attach Activity utility generation of page activity attachments is ignored by any workflow triggers in server used for theattachmentadded or attachmentchanged events. This avoids triggering an unwanted action.
Page restrictions
Any page with Confluence view or edit restrictions cannot be included in migration to the cloud with the page restrictions in place. Pages with restrictions are listed in the CCMA migration prechecks.
The migration pre-check in the Atlassian Migration Assistant includes a report listing pages with restrictions.
You will need to temporarily remove the page-level restrictions of pages before migration. If required, the page restrictions must be added to the pages in the cloud after completing the migration.
Avoiding migrated user login issues
You can manage user migration using the Atlassian CCMA.
The actual users' access must be migrated as part of the Atlassian Confluence Cloud Migration Assistant (CCMA) migration plan.
If the migration does not include the users, errors can occur when completing the space set up and applying your Comala Document Management workflow on the cloud site.
After the migration process has been completed, it is recommended that migrated users log in, exit, and log in again so they are available (otherwise, the Cloud instance may not recognize them).
Atlassian CCMA checks
The CCMA includes prechecks for users, groups, page restrictions, data and vendor apps, including Comala Document Management. These must be completed to avoid blocking a migration, including confirming the vendor apps needed in the cloud.
Cloud site tasks
Several manual tasks also need to be undertaken to complete the setup 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.
Install Comala Document Management app
Before migration, install the Comala Document Management for Cloud app.
You can use the server workflow builder Workflow Translator for Cloud in the server or data center app to translate a custom server workflow template to cloud-compatible JSON code.
You can then add the workflow template to a cloud space by copying and pasting the translated cloud-compatible workflow code to the cloud app code editor.
Tasks after completing the Atlassian CCMA migration
Once you have enabled migration and undertaken the migration using the Atlassian CCMA, to complete your cloud site, you need to undertake the following tasks
Workflow elements not translated by the workflow translator will need to be added to the cloud workflow using the cloud workflow builder visual editor or code editor.
The migrated data includes the last workflow state for the page. If you require a different workflow state for your pages (for example, if you use a different workflow in the cloud), you can undertake the following task
If you removed the page-level restrictions of pages before migration, these page restrictions, if required, must be added to the migrated pages in the cloud.
Support
