---
title: "Migration Health Checks - BigPicture data center -> cloud migration"
canonical: "https://support.appfire.com/space/DLP/2215313524/Migration%20Health%20Checks%20-%20BigPicture%20data%20center%20-%3E%20cloud%20migration"
format: markdown
---
> Macro (aura-html)
## Pre-Migration Health Check – BigPicture (Data Center → Cloud)
Conducting a pre-migration health check for the BigPicture app is essential to ensure a smooth migration from **Data Center to Cloud**. Below is a comprehensive pre-migration checklist based on known compatibility, behavior, and data fidelity considerations specific to BigPicture migrations via JCMA.
> ✅ Use this checklist **before initiating JCMA** to ensure BigPicture, tasks and projects migrate properly. dvafgd
## SECTION 1: App Compatibility & Versioning
| **Task** | **Action** | **Notes** | **Status** |
| --- | --- | --- | --- |
| 1. Check the version. | Confirm that your **BigPicture Data Center version is at least 8.11**, as JCMA-based migrations are supported from this version onward. | | - [ ] |
| 2. Installing BigPicture Cloud. | Please confirm that **BigPicture Cloud version** is installed in the destination Jira Cloud site. | | - [ ] |
| 3. BigPicture DC vs Cloud. | Review the differences between BigPicture DC and Cloud with this article: [https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211186614](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211186614) . | | - [ ] |
## SECTION 2: **Project and Data Inventory**
| **Task** | | **Notes** | **Status** |
| --- | --- | --- | --- |
| 1. Check Projects. | List all Jira projects that are **linked to Boxes in BigPicture** and run **data integrity checks** using the BigPicture admin tools or custom scripts. | | - [ ] |
| 2. Check Dependencies. | Review task mappings and crucial task dependencies that may need to be recreated post-migration. | | - [ ] |
| 3. Check Permissions. | Document current **Box-level permissions** (Admins, Editors, Viewers).
Identify any **project-based rules** that might grant automatic access and determine whether to replicate them in Cloud. | | - [ ] |
| 4. Check task hierarchy. | Resolve **incomplete task links**, orphaned structures, or inconsistent Box hierarchies. | | - [ ] |
| 5. Check APIs and scripts. | Identify any **external integrations**, e.g. REST APIs, scripting (ScriptRunner), external databases and plan to **manually reconfigure these** post-migration, as they are not handled by JCMA. | | - [ ] |
## SECTION 3: **JCMA Readiness & Environment Setup**
| **Task** | **Action** | **Notes** | **Status** |
| --- | --- | --- | --- |
| 1. Reinstall BigPicture. | When you migrate from **Jira Data Center** to **Jira Cloud**, you will be asked to reinstall BigPicture to prepare a **JCMA** dump.
The reinstallation ensures data consistency in the dump by deactivating **BigPicture** on other nodes (Jira instances in a **Jira Data Center** cluster) and preventing other nodes from making modifications to the database during database dump creation.
To reinstall **BigPicture**:
1. Uninstall the app.
2. Go to [the BigPicture Marketplace page](https://marketplace.atlassian.com/apps/1212259/bigpicture-project-management-ppm?hosting=datacenter&tab=versions).
3. Download the **JAR** file for exactly the same version:
4. Install the app with the file:
 | | - [ ] |
| 2. Prepare a JCMA snapshot in BigPicture on Jira On-premise. | Navigate to **BigPicture App Configuration **>** Advanced **>** Database dumps **>** New dump **>** JCMA dump**. Creating a JCMA snapshot will restart the App and may take a significant amount of time and resources, so the process is recommended during non-business hours. | | - [ ] |
| 3. Naming the snapshot. | Enter a unique **Migration name,** as you will later need to identify this snapshot in JCMA and complete the **Description** field. The provided **Migration name** can be edited later. | | - [ ] |
| 4. For BigPicture on Jira Cloud. | Navigate to **Apps **>** BigPicture App Configuration **> **Advanced **>** Technical info **> **Others **>** Data migration** and enable the **Allow JCMA migration** option.
 | | - [ ] |
| 5. On Jira On-premise: | Navigate to **Jira Administration **>** System **>** Import and Export **>** Migrate to cloud **>** Assess your apps**.
Then assign the **Needed in cloud** status for each App.
Click **Done**.
 | | - [ ] |
## SECTION 4: Final Pre-Migration Readiness
| **Task** | **Action** | **Notes** | **Status** |
| --- | --- | --- | --- |
| 1. Test Environment. | Test Migration (Optional but Highly Recommended) - Prepare a Test Environment by setting up a **Jira Cloud** sandbox site and perform a trial migration with a subset of data. | | - [ ] |
| 2. Run JCMA. | Run a **JCMA "dry run"** and observe if the migration reaches 100% or hangs. Review logs. After running the migration, you can track its progress from the **Migration dashboard**. | | - [ ] |
| 3. Check for any errors. | If there was an error encountered for some reason, then in many cases, **retrying the migration** after correcting the configuration resolves the problem entirely. | | - [ ] |
| 4. The app will restart itself. | 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**. | | - [ ] |
## SECTION 5: BigPicture **Post-Migration Validation & Cleanup Checklist**
| **Task** | **Action** | **Notes** | **Status** |
| --- | --- | --- | --- |
| 1. Check the app’s status. | Check that **BigPicture** **Cloud** is installed and functioning in the target **Jira** site and no **BigPicture**-related errors appeared during migration | | - [ ] |
| 2. Check your boxes after the migration. | Compare number, names, and hierarchy of **Boxes** with pre-migration state. | | - [ ] |
| 3. Check the task structure. | Review** scheduling rules**, task structures, milestones, and custom views. Ensure all tasks, links, parent-child hierarchies, and dependencies are intact. | | - [ ] |
| 4. Check the permissions. | **Users** should see appropriate modules based on role and access. Confirm that permissions for **Admin**, **Editor**, **Viewer** were applied correctly. | | - [ ] |
| 5. Re-add APIs if needed. | Manually reconnect **APIs**, **plugins**, or **external tools** used with BigPicture | | - [ ] |
| 6. Check the app after some time to ensure that everything works. | Schedule a follow-up **audit** and re-check configuration, access, and performance 2–4 weeks post-migration. | | - [ ] |
## Optional Tools & Guidance
- [Migration using Jira Cloud Migration Assistant (JCMA)](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297896980).
- [Migration to Cloud with JCMA: Migration process.](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2056650844)
- [Backup, restore, and migrate](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212266044).
- Review whether BigPicture Cloud meets your compliance and security requirements.
- If needed, please check our internal API list on the [Developer Portal](https://developer.bigpicture.one/reference/whatisbigpicture) for any potential use after the migration.
- Use Appfire's support if you encounter any blocking errors during the migration process itself.