Migrating to Confluence Cloud
1. Overview
To migrate from a hosted instance, use the Atlassian Confluence Cloud Migration Assistant (CCMA) to transfer spaces, users, and groups. It includes a migration pathway for Comala Publishing data, including your source and target spaces.
However, there are differences between the features and functionalities of the hosted and cloud versions of Comala Publishing. You can check the differences here.
The supported CCMA migration pathway for Comala Publishing migrates the following:
The source space pages and their publish and sync status
The target space pages and their publish and sync status
Both the spaces linked for publishing (the source and target space) in the data center instance must be selected in the same migration plan in the CCMA.
After migration is complete, the current publishing status lozenge (from the data center instance) is added to the migrated pages in Confluence Cloud in both the source space and the target space.
The Published status lozenge in our data center app is displayed as Synced in the cloud app.
We recommend upgrading to the latest versions of the Comala Publishing for Data Center app and our Confluence Cloud app before migrating to Confluence Cloud.
2. Pre-requisites
Before you review the Confluence Cloud platform features and the apps needed in the cloud, ensure the following:
Install the latest app versions
You must update your Confluence Data Center instance with the latest Comala Publishing for Data Center app version and the Atlassian Confluence Cloud Migration Assistant (CCMA). Before migrating, you must also install the latest version of our app in Confluence Cloud.
Review app functionality in Confluence Cloud
You can review the product comparison for our cloud and data center apps. We also recommend installing and exploring our Comala Publishing app in Confluence Cloud.
See: Product comparison
If the publishing configuration in your data center instance includes conditions not supported in Confluence Cloud, such as Copy label, the publishing status for these pages can differ once they are migrated to Confluence Cloud.
3. Pre-migration assessment
As part of your migration planning, you should assess your current hosted instance usage. For more information, check out the Atlassian Cloud Migration Guide and the Atlassian Confluence pre-migration checklist. For example, review and check:
Users in Atlassian Cloud - You must also ensure that your Confluence Cloud site user limit is not exceeded. You can migrate your users before other data to ensure users are present in the cloud and the email domains are validated
Permissions - Before starting a migration, ensure that you have:
Administrator permissions in your Confluence Data Center and Cloud instances
Confluence view and edit permissions in each space to be migrated. Page-level restrictions can also prevent migration of the app data and need to be removed as one of your steps before starting a migration
4. Pre-migration steps
Before starting a migration, ensure that you have installed and are using the latest version of the Comala Document Management app in both your hosted data center instance and your cloud site.
You should then complete the following to prepare your instance:
Set up your Confluence Cloud site
You must create a Confluence Cloud site and install Comala Publishing for Cloud and any other apps you need in the cloud. You must have administrator permission for the site when creating and running a migration.
If you are using Comala Publishing together with Comala Document Management to manage your documentation and automatically publish your approved documents, you can migrate the data for both apps using the CCMA. You should review the migration information and product comparison for the Comala Document Management app.
Remove page restrictions
Restricted pages can cause Comala publishing status conflicts in your migrated pages. To avoid misalignment of the publishing status for pages migrated with restrictions from the source or target space in the data center instance, their publishing status is set as NEW in the source space page in Confluence Cloud.
Pages with restrictions are identified in the Atlassian Migration Assistant App vendor checks screen. These page restrictions can be removed before migration to ensure that the current publishing status data is migrated and added to each page in Confluence Cloud.
5. Production migration
We recommend migrating a production instance in several smaller groups of linked publishing spaces, instead of all at once. This makes it easier to review results and fix any issues.
5.1 Migration process steps
5.2 Atlassian EAP Cloud-first migration
Atlassian is rolling out an EAP for creating migrations from the Data Center to the Cloud for your cloud organization. You must apply to opt into this Atlassian EAP. It lets you create migrations from your cloud organization and is currently designed for organizations with fewer than 10,000 users.
5.3 Migration of complex instances
Some things can increase the complexity of your migration, and you might need some help planning. For example, if the migration involves
Large amounts of data or users
Several products and apps
The Atlassian Migration Guide includes a range of resources and guides.
If you have any questions or require assistance, contact Appfire support.
6. Resources
Need support? Create a request with our support team.