Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Table of Contents | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Excerpt | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Manual Migration TasksDue to differences in the Atlassian cloud and server platforms, the migration of the Atlassian Migration Assistant only migrates the following
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 migrationThe 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, errors may occur when completing the space setup and applying your Comala Document Management workflow in the cloud site. Page restrictionsAny page with Confluence view or edit restrictions cannot be included in migration to 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 appBefore migration, install the Comala Document Management for Cloud app.
The Workflow Translator for Cloud does not translate a workflow element or parameter that is not directly compatible with the cloud app. If any incompatible elements are present in the server workflow, these elements, such as workflow triggers or some state parameters, are listed separately in a report in the workflow translator. Workflow events and activities historyOnly 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 need to consider options of
Tasks after completing the Atlassian migration processOnce 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 issuesAfter 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 historyThe 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
Running Attach ActivityBefore 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
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. The Attach Activity utility generation of page activity attachments is ignored by any workflow triggers in server with the
Support
|