What is migrated to Cloud? What is not migrated to Cloud?
What is migrated to Cloud?
Only the following is migrated with the Confluence Cloud Migration Assistant
current workflow status of each page
an entry in the workflow history
Any document that had a workflow applied while being in server, in each cloud space will have
a lozenge added to the content in cloud showing the current workflow status
an entry on each document’s workflow history saying "Document has changed to 'xxx' state"
Migration adds the last workflow state in server an attachment to the document in cloud.
These will be present as long as document has been properly migrated using the Atlassian Migration process and the linked user exists in the cloud site.
What is not migrated to cloud?
The following is not included in the migration
workflows
full page activity (the workflow history)
expiry date(s)
assigned approvers
assigned read confirmations
record of which page version was the final state
any metadata set or retrieved by get-metadata and set-metadata macros and workflow parameters
When migrating to Cloud
the Comala Document Management for Server app is not migrated
pages with restrictions identified in the Atlassian Migration Assistant App vendor checks screen must have the restrictions removed prior to migration
Each workflow in server can be translated to cloud compatible JSON code using the /wiki/spaces/AWPD/pages/617489050 option in workflow builder (from Comala Document Management v6. 17.10+). The code can be copied and pasted to the workflow Code Editor in a cloud site space.