| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Excerpt | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Manual Migration TasksAnchor | | manmigratetask |
| Table of Contents | ||||
|---|---|---|---|---|
|
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.
| Tip |
|---|
The migration pre-check in the Atlassian Migration Assistant includes a listing of pages in the migration with restrictions. |
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.
| Tip |
|---|
If using a custom workflow, you can use the server workflow builder Workflow Translator for Cloud to translate your workflow to cloud compatible JSON code. You can add this workflow to a cloud space by copying and pasting the translated cloud compatible JSON to the cloud app Code Editor. |
The Workflow Translator for Cloud in server will not translate any workflow elements and parameters that are not directly compatible in cloud. If any are present in the server workflow, these elements, such as workflow triggers or some state parameters, are listed separately in the Cloud Translator.
Workflow History/Document Activity
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 workflow state is added as a file attachment to each document in cloud.
If workflow history document activity 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
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
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
| Note |
|---|
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.
| Info |
|---|
Please feel free to raise a /wiki/spaces/CDMCD/pages/13951991809with the Comalatech Migration and Support team to help to answer any queries you in planning the migration. Please include with your request
|
