What will not be migrated by the Confluence Cloud Migration Assistant?

Owned by Robert Alexander Marshall
Last updated: Jul 05, 2024
1 min read

What is not migrated?

  • the workflow

  • full-page activity (full workflow events and activity history)

  • expiry date

  • assigned approvers

  • assigned read confirmations

  • record of the page version that was the final state

  • any metadata set or retrieved by get-metadata and set-metadata macros* and workflow parameters

* Comala metadata macros are not a feature available in the cloud app.

Our integration with the Confluence Cloud Migration Assistant currently migrates the 'current state' of the page.

Pages with restrictions are not migrated successfully. These pages are displayed in the Atlassian Migration Assistant App vendor checks screen downloadable CSV report file. Permission restrictions need to be removed for a successful migration.

The page activity (aka workflow history), workflow markup, and other data are not included.

If workflow event and activity history must be maintained for audit

  • use the Attach Activity utility in each server space to add a record as a CSV file attachment to each page before migration

  • or retain the server instance in a ‘read-only’ mode

What is migrated?

  • current workflow status

  • an entry in the workflow history - "Document has changed to 'xxx' state"

This requires the successful migration of the page and the associated user.

Further information