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. 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 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 the Comala Document Management for Cloud app must be separately installed in the cloud instance any Comala workflow applied in the server instance needs to be created manually in the cloud instance the Comala Document Management app requires a separate license purchase for your cloud instance. The server/data center license is not transferable Each workflow in server can be translated to cloud compatible JSON code using the /wiki/spaces/AWPD/pages/14256308236 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. What is migrated to Cloud?
What is not migrated to cloud?
get-metadata
and set-metadata
macros and workflow parameters