Migration Health Checks - BigPicture data center -> cloud migration

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: Cloud vs. Data Center - Key Differences between Platforms.Preview.

⬜

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.

⬜

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.

3. Download the JAR file for exactly the same version:

   Open

   

4. Install the app with the file:

Open

⬜

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.

Open

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.

Open

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.

⬜

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.

⬜