--- title: "Step 2 - Migrate your data using the migration assistant" canonical: "https://support.appfire.com/space/CPCL/2223505609/Step%202%20-%20Migrate%20your%20data%20using%20the%20migration%20assistant" format: markdown --- > Macro (aura-html) > Macro (legacy-content) # Overview You can migrate your Comala Publishing app data for your linked source space(s) and target space(s) from a hosted instance using the [Atlassian Confluence Cloud Migration Assistant (CCMA)](https://marketplace.atlassian.com/apps/1219672/confluence-cloud-migration-assistant?hosting=datacenter&tab=overview) ![cdmdc_howitworks_migrate.png](media://e744b6a6-5980-4e92-836c-8c5c54a5d563) When creating a migration plan, the **Migration Assistant** lets you connect to your destination cloud instance and choose what to migrate It also automatically runs pre-migration checks. These include the following app vendor checks for the Comala Publishing app: - **Cloud feature parity** - Checks that the publishing status is transferred to Confluence Cloud and source and target spaces are linked - **Paired spaces** - Checks if linked pairs of publishing spaces - the source space and the target space - are both selected and included in the migration - **Page restrictions** - Are there explicit or inherited page restrictions on documents that might prevent publishing data migration? # Prerequisites You must have completed: - **Prerequisite tasks** on the [Migrating to Confluence Cloud](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/646643910) page - **CCMA tasks** in[ Step 1 - Assess and prepare your migration](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/2223669466). # Migrate your data You can migrate your instance when you have assessed your apps and prepared them and their users for migration. Each migration can include one or more spaces. - Choose **Migrate your data** ![Migration Assistant home screen extract - migrate your data](media://fedae5f0-dd4e-4a17-bf34-aae26661a1fd) > ℹ️ If you have saved a migration plan or there are existing migration plans, you can choose the **Create new migration** option in the **Migration dashboard**. The migration assistant takes you through the following steps: ![Atlasian Migration Assistant - how migration works summary with Connect to cloud button](media://e744b6a6-5980-4e92-836c-8c5c54a5d563) ### 1. Connect to Cloud Name your migration for reference, choose migration as a **Testing** or **Production stage**, and connect to the destination cloud site > ℹ️ You must be signed in as the **Site Administrator** for the Atlassian cloud site you're migrating to. ### 2. Choose your migration options Choose your migration options - what to migrate (spaces, pages, attachments, users, groups, and vendor apps) ![ccma_choose_migration_options.png](media://1389556e-52a5-4ba4-8235-94d67b634062) Ensure that you select both of the paired spaces linked for publishing - the source and target spaces. The CCMA includes a **Publishing Space Pair migration check**. ### 3. Run pre-migration checks The migration assistant automatically runs a **Check for errors** for each of your system, app versions, apps, spaces, user, and user group data This includes specific **App vendor checks**. ![Atlassian Migration Assistant Apps - checks all succesful](media://63613aae-2484-4858-a548-91af229a1e4e) **App vendor checks** are run for the apps marked as **Needed in Cloud**. Warnings can be viewed and, if necessary, resolved before proceeding with the migration. ![App vendorchecks warning summary](media://ebd07bb2-3bf0-4b01-9773-68b71e059c59) These include the following app vendor checks for the Comala Publishing app: --- #### Cloud Feature Parity Check Checks that the linked source and target spaces are transferred to Confluence Cloud and that their publishing status is transferred for each page. ![ccma_cloudfeatureparitycheck.png](media://854e7bec-a830-4258-931f-93c8761a2807) > ℹ️ Publishing page status in data center - **New**, **Out of Sync,** and **Published** - are transferred to Confluence Cloud as **New**, **Out of sync,** and **Synced** --- #### Publishing Space Pair Migration Check Checks that both the source and target spaces are selected in the planned migration to Confluence Cloud. ![ccma_publishingspacepairmigrationcheck.png](media://82af2d77-3a21-485e-9c49-dfe2708d9bee) You can view a list of the missing spaces by downloading a CSV file report. You need to start a new migration and ensure the missing spaces are included. --- #### **Page restrictions verification** Checks and warns of page restrictions on pages included in the source and target spaces. These can prevent the migration of publishing-related data. ![ccma_pagerestrictionsverification_publishing.png](media://32802c8d-69e6-4f40-add1-f08329efc3c6) You can view a list of the affected pages in the source and target spaces included in the migration by downloading a CSV file report. Page restrictions can be left in place, and the current migration can be completed with migration errors for the restricted pages However, we recommend that you: - **Review** the restricted pages - **Remove** the page restrictions from the source and target spaces (if appropriate) - **Re-run the check** You can either: - [Remove all restrictions](https://support.atlassian.com/confluence/kb/how-to-remove-all-restrictions-from-pages-within-a-space/), or - Delete only the restrictions of pages identified in the downloaded report You can then restore any required page restrictions on the migrated pages in Confluence Cloud. > ℹ️ Page restrictions are not a migration blocking error. If required, you can run the migration with the page restrictions and the errors. However, migrated pages with restrictions have the publishing status set as **New** in the source space in Confluence Cloud to avoid misalignment of publishing status. --- # Run migration If a blocking error is returned in any **Pre-migration checks**, you cannot undertake the migration until it is resolved. If there are no blocking errors, you can choose **Run now** to start your migration or **Save** it to the **Migrations dashboard** to run it later. When the migration is successful for spaces linked for publishing, the following are shown as **COMPLETE** for the: - Source space - Target space - Comala Publishing app ![image](media://a97d73b6-5199-4199-a63e-4e19c9c00e54) > ℹ️ For each space included in the migration, the app migration occurs after the space data is migrated. You can use the dropdown option for the app migration progress to view details of the app data migration. For example, in some cases, app migration can be set as **Complete**, but the migration might not have generated any data tasks as selected spaces have no publishing data, or relevant pages are restricted and cannot be included in the migration tasks for the app. ![ccma_appmigration_complete_notasksgenerated_contextualmessage.png](media://04eb877d-db47-4ad9-bb70-84376e9c4b69) > ✅ You can also check the migration status in the CCMA Migrations dashboard. If the migration fails, check the logs in the CCMA and re-run the migration using the dropdown option in the migrations dashboard. If there are repeated problems or you have a complex instance, contact our [support](http://appf.re/support). # Next step [Step 3 - Post-migration](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/2223800446)