---
title: "Migration to Cloud with JCMA: How to repeat migration"
canonical: "https://support.appfire.com/space/DLP/2057338993/Migration%20to%20Cloud%20with%20JCMA%3A%20How%20to%20repeat%20migration"
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 explains how to re-run the migration process of BigPicture, BigPicture Enterprise, BigGantt, and BigTemplate using the Jira Cloud Migration Assistant (JCMA) app.

## Repeat the migration process

> ❌ It is **not recommended** to reset Jira Cloud to solve migration problems. 
> ❌ 
> ❌ However, if there is no other way and you decide to reset Jira Cloud, **you have to uninstall BigPicture first**. Once BigPicture is uninstalled, you can reset Jira Cloud.

If you make any mistakes during the migration process in JCMA (for example, forgetting to provide the correct **Migration name** of your JCMA snapshot), you can run the migration process again.

1. Prepare a JCMA snapshot in BigPicture on Jira On-premise.  
You can either:
  1. Edit the **Migration name** and use the same JCMA snapshot (if you entered the wrong **Migration name** for your JCMA snapshot).  
Go to **BigPicture App Configuration **>** Advanced **>** Database dumps **and edit the JCMA snapshot you created before.
    or
  2. Create a new JCMA snapshot as described in the **How to prepare for migration** section above.
2. Enable the **Allow JCMA migration** option in **Apps **>** BigPicture App Configuration **>** Advanced **>** Technical info **>** Others **>** Data migration** section on Jira Cloud.  
 [important] You must re-enable the **Allow JCMA migration** option in the Jira Cloud instance before each migration attempt or rerun.
3. Go to the **Jira Administration **>** System **>** Import and Export **>** Migrate to cloud **>** Assess your apps **section.
4. Assign the **Needed in cloud** status for each App.
5. Click **Done**.
6. Initiate the migration process as described in the **Migration process** section.

---