Check what is migrated to Confluence Cloud

What is migrated to Cloud?

Only the following app data is migrated with the Confluence Cloud Migration Assistant

• current workflow status of each page

• an entry in the workflow historyW

In each cloud space after migration, a document that had a workflow applied while being in server, has

• a workflow state byline lozenge added

• an entry on each document’s workflow history saying "Document has changed to 'xxx' state"

Migration adds the last workflow state in the server as a custom contents attachment to the migrated cloud document.

These are present as long as the document is successfully 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 events and activities on each page)

• expiry date(s)

• assigned approvers

• assigned read confirmations

• record of the last page version for a workflow with a final state

• 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

• app page report macros are not migrated

  • app report macros are available in cloud

Pages with restrictions identified in the Atlassian Migration Assistant App vendor checks screen must have the restrictions removed before migration.

In the cloud site

• the Comala Document Management for Cloud app must be separately installed 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

• any Comala workflow applied in the server instance needs to be created manually in the cloud instance