---
title: "BigPicture Migration Compatibility and Best Practices for JCMA 1.24.1"
canonical: "https://support.appfire.com/space/SUPPORT/3755245585/BigPicture%20Migration%20Compatibility%20and%20Best%20Practices%20for%20JCMA%201.24.1"
format: markdown
---
# BigPicture Migration Compatibility and Best Practices for JCMA 1.24.1

This article provides guidance on migrating **BigPicture** from Jira Data Center to Jira Cloud using the **Jira Cloud Migration Assistant (JCMA) 1.24.1**, covering version compatibility, configuration requirements, and known limitations.

## Summary

This article addresses multiple aspects of the BigPicture migration process, including:

- Compatibility between JCMA 1.24.1 and BigPicture versions.
- Recommended Jira Data Center versions for migration.
- Essential pre-migration configuration steps and data limitations.

---

## Use Case 1: Version Compatibility (JCMA & BigPicture)

When planning a migration, it is critical to ensure that the versions of JCMA, Jira Data Center, and BigPicture are aligned.

### Compatibility Details

- **JCMA Support:** JCMA 1.24.1 fully supports migrating BigPicture data to Jira Cloud.
- **BigPicture DC Version:** Automated JCMA migration is supported for BigPicture Data Center versions **8.64.3 and later**.
- **Jira Data Center Version:** JCMA 1.24.1 is compatible with supported Long Term Support (LTS) releases:
  - Jira 9.4.x
  - Jira 9.12.x (Recommended for Jira 9 users)
  - Jira 10.x (Ensure BigPicture is on version `8.70.1.x` or later for Jira 10 compatibility)

---

## Use Case 2: Pre-Migration Configuration

Successful migration requires specific settings to be enabled in both the source (Data Center) and target (Cloud) environments.

### Solution/Workaround

1. **Enable Cloud Migration:** In the target Jira Cloud instance, navigate to **Apps** > **BigPicture App Configuration** > **Advanced** > **Technical info** > **Others** > **Data migration** and enable **"Allow JCMA migration"**.
2. **Generate Database Dump:** On Jira Data Center, create a dedicated JCMA snapshot:
  - Go to **BigPicture App Configuration** > **Advanced** > **Database dumps** > **New dump** > **JCMA dump**.
  - **Important:** Assign a unique **Migration name**.
3. **Match Migration Names:** When configuring the migration plan in the JCMA interface, you must use the **exact same Migration name** defined in the step above to ensure JCMA links and imports the correct data dump.

---

## Use Case 3: Migration Limitations and Post-Migration Tasks

Certain data types and configurations are not automatically handled by JCMA and require manual intervention.

### Known Behaviors & Manual Steps

- **Data Overwrite:** JCMA app migration for BigPicture **overwrites** existing data on the Cloud target. It does not support merging data from multiple sources.
- **Phased Migrations:** Ensure all Jira projects referenced by BigPicture Boxes are migrated either before or in the same batch as the BigPicture app migration.
- **Non-Migrated Items:**
  - **What-if scenarios:** These are not transferred and must be manually noted or exported.
  - **JQL Filters & Scope:** Custom field IDs change in Cloud. Validate Box scope definitions and Quick Filters that use JQL post-migration.
  - **External Integrations:** Any custom REST API integrations or scripts interacting with BigPicture tables must be reconfigured for the Cloud environment.
- **Dry Run:** It is highly recommended to perform a full dry run in a staging or sandbox environment to validate ID mappings and Box configurations before the production cutover.

---

**Related Resources:**

- [Migration using Jira Cloud Migration Assistant (JCMA)](https://support.appfire.com/space/DLP/297896980/Migration+using+Jira+Cloud+Migration+Assistant+(JCMA))
- [Migration Health Checks - BigPicture data center -> cloud migration](https://support.appfire.com/space/DLP/2215313524/Migration+Health+Checks+-+BigPicture+data+center+-%3E+cloud+migration)