What is migrated to Cloud?
What is migrated to Cloud?
The Confluence Cloud Migration Assistant migrates the data and users including
the source space pages and the publish and sync status
the target space pages and the publish and sync status
Any pages that had been published and synced while being in server, in each cloud space will have
a publishing status lozenge added to the pages in cloud in both the source space and the target space showing the current publishing status
What is not migrated to cloud?
The following is not included in the migration
the Comala Publishing for Server app is not migrated
blog post publishing status
publishing conditions for a space such as
Copy label/Not copy label
Copy blog posts/Not Copy blog posts
When migrating to Cloud
the Comala Publishing for Cloud app must be separately installed in the cloud instance prior to migration
both the source and the target space must be selected together to be migrated to Cloud
Comala Publishing migration will only be fully completed if both the source and the target space are migrated to Cloud.
pages with restrictions identified in the Atlassian Migration Assistant App vendor checks screen must have the restrictions removed prior to migration
if the publishing configuration in Data Center/Server includes conditions not supported in Cloud such as Copy label, publishing status for these pages may differ once migrated to Cloud
the Comala Publishing app requires a separate license purchase for your cloud instance
When migrating Comala Publishing from server to cloud, if you choose to migrate pages with restrictions, migration now sets the page publishing status in the source space to NEW if a source page or the linked target space page have page restrictions. This avoids misaligning the publishing status for these pages in the cloud spaces.
Support
Feel free to raise a ticket with our support team.