---
title: "Migration to Cloud with JCMA: Migration process"
canonical: "https://support.appfire.com/space/DLP/2056650844/Migration%20to%20Cloud%20with%20JCMA%3A%20Migration%20process"
format: markdown
---
> Macro (aura-html)

This page is part of the series about the [https://appfire.atlassian.net/wiki/spaces/DLP/pages/297896980](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297896980). 

It covers the migration process of BigPicture, BigPicture Enterprise, BigGantt, or BigTemplate using the Jira Cloud Migration Assistant (JCMA) app.

## Migration process

1. Initiate a migration process in JCMA:
  1. Navigate to **Jira Administration **>** System **>** Import and Export **>** Migrate to cloud**.
  2. Click the **Create a migration **button.

![Screenshot of initiating the migration process.](media://273d91e5-c625-4f6e-b323-c609092c8afe)

2. Read the information about the migration process.

![Screenshot of migration process explanation.](media://9823aacf-edb1-4470-8f3b-f60a5971b2d7)

3. Provide the **migration name **(the one you used for creating the JCMA snapshot in BigPicture).  
[important] “Migration 3” and “migration-3” are different names. Make sure that the name is an exact match. **If no JCMA dump matches the migration name, the latest JCMA dump will be used as a fallback.**
4. Choose your destination Jira Cloud site.

![Screenshot of providing the migration name.](media://b5cf12e2-92cb-42b1-a822-cb7a9e6a5838)

5. Select the preferred migration method:
  1. **Choose what to migrate**, or
  2. **Migrate all data at once** (you can find more information about this step in the [next section](https://appfire.atlassian.net/wiki/spaces/DLPDRAFT/pages/2053832754))

![Screenshot of migration options.](media://1ed25afc-a886-4b61-bcfa-93ac76a954cb)

6. If you have selected **Choose what to migrate** in the previous step:
  1. Define your migration options, such as Projects, User and groups, and Apps.
  2. When ready, click the **Check for errors** button.

![Screenshot of checking errors before the migration.](media://bf69f2a2-339b-4639-b1d5-c15c83acf786)

c. Select **All **to migrate all the apps with an automated path that are marked as **Needed in the cloud **in your app assessment.   
If you select **None**, no apps will be migrated.

![Screenshot of selecting apps to be migrated.](media://21884710-c17a-411c-9792-eaf3452247eb)

7. Proceed by clicking **Review migration**.

![Screenshot of checking for errors before the migration.](media://1ea597ca-d5ad-436b-8f85-4c32b1553d79)

8. You can run your migration now or save it and come back later. You will not be able to add or remove projects after you have saved. For that reason, if you would like to make any changes, make them now.

![Screenshot of reviewing the migration.](media://46060abd-a092-4f84-8cc6-5758ef77c9b1)

9. After running the migration, you can track its progress from the **Migration dashboard**.

[important] During the migration, your BigPicture/ BigPicture Enterprise/ BigGantt app on Jira Cloud will restart to reflect the state of the migrated app from Jira On-premise.

10. Once the migration is complete, the status will be updated accordingly.  
[BigPicture Jira Cloud]  You will see the **Migration completed successfully** message once you enter **Apps **>** BigPicture App Configuration **>** Advanced **>** Technical info, you will see the "Migration completed successfully" message.**  
The message will disappear after the next BigPicture update.

![Screenshot of checking the migration completion on the BigPicture App configuration page.](media://8508640a-acaf-4211-b531-14c940aed0de)

[Jira On-premise]  The **Progress **column in the **Migration dashboard** (**Jira Administration** > **System** >** Import and Export** > **Migrate to cloud**)** **informs about the migration status.  
You can also expand the **Actions** menu and click **View details**. 

![jira-administration-system-migration-dashboard.pngaScreenshot of the Migrations dashboard in Jira.](media://08989ab6-94e3-4acd-b822-10b8cfae9a22)

On the details page, you can find detailed information on the migration.

![Screenshot of the Migrations dashboard details in Jira.](media://c8cdbefd-7501-488b-8987-51d3b8cd7664)

### Additional instructions for the “Migrate all data at once” option

The following steps apply only to the **Migrate all data at once** option (Step 5 in the migration process). 

When the app migration gets stuck at 0% and has not progressed in the last 15 minutes, go to BigPicture/ BigPicture Enterprise / BigGantt/ BigTemplate on the target Jira Cloud instance.

![Screenshot of additional instructions for the migration.](media://b503ad87-dc54-4ff5-807c-57e07f55e6c3)

> 📝 If you see the following screen, it means you do not have sufficient permissions to add-ons in Jira Cloud. In this case, you must follow the procedures described on the [Insufficient JIRA Permissions in BigPicture](https://appfire.atlassian.net/wiki/spaces/DLP/pages/298092419) page.
> 📝 
> 📝 ![Screenshot of a message that access to BigPicture is needed.](media://754870c6-4462-404e-93b6-dff269afbbb7)

Once you define sufficient permissions, return to BigPicture/BigGantt on Jira Cloud:

1. Go to **App Configuration **>** Advanced **>** Technical info**.
2. Under the *Others > Data migration *section, enable the **Allow JCMA migration** toggle switch.
3. Under the *Pending data migration* section, click the **Trigger pending migration** button.

![Screenshot of the Trigger pending migration button on the BigPicture App configuration page.](media://a2ee9883-3d15-41a8-9e36-dff98816a1c6)

4. After refreshing the page, you will see a message that the migration is in progress.

![Screenshot of the message that migration is in progress.](media://72cbd70d-99a8-47a5-8cfb-16707d8a50cb)

5. Now, you can return to the **Migration dashboard** on Jira On-premise and track the progress.

![Screenshot of the Migrations dashboard in Jira.](media://920f8a91-92c8-40a3-8144-523423b9eb52)

## JCMA migration common mistakes

| **Issue** | **Possible cause** | **Solution ** | **Related documentation** |
| --- | --- | --- | --- |
| Migration of the BigPicture app fails at 1% | missing JCMA-compatible BigPicture data dump | Prepare a JCMA dump(snapshot) on the DC instance. Ensure the snapshot's Migration Name is the same as your migration name. | [https://appfire.atlassian.net/wiki/spaces/DLP/pages/297896980/Migration+using+Jira+Cloud+Migration+Assistant+JCMA#Create-a-JCMA-snapshot](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297896980/Migration+using+Jira+Cloud+Migration+Assistant+JCMA#Create-a-JCMA-snapshot)   
point 1. |
| Migration of the BigPictue app fails at 1% | switch “Allow JCMA migration” on cloud instance in off state | For BigPicture on Jira Cloud:<br>1. Navigate to **Apps **>** BigPicture App Configuration **> **Advanced **>** Technical info **> **Others **>** Data migration**.
2. Enable the **Allow JCMA migration** option. | [https://appfire.atlassian.net/wiki/spaces/DLP/pages/297896980/Migration+using+Jira+Cloud+Migration+Assistant+JCMA#Create-a-JCMA-snapshot](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297896980/Migration+using+Jira+Cloud+Migration+Assistant+JCMA#Create-a-JCMA-snapshot)   
point 2. |

---