---
title: "Fixing BigGantt Migration Issues in Jira Cloud Migration Assistant (JCMA)"
canonical: "https://support.appfire.com/space/SUPPORT/3588985365/Fixing%20BigGantt%20Migration%20Issues%20in%20Jira%20Cloud%20Migration%20Assistant%20(JCMA)"
format: markdown
---
This article explains how to fix a BigGantt Data Center to Cloud migration issue in Jira Cloud Migration Assistant (JCMA) when the migration reports that it cannot fetch the database dump.

> ℹ️ Use this procedure when a BigGantt migration fails because JCMA cannot find or use the expected database dump. In the resolved case behind this article, the issue was caused by using an outdated dump rather than one created immediately before the migration.

# Problem

During a BigGantt migration from Data Center to Cloud, JCMA may fail with an error indicating that it cannot fetch the database dump. This usually happens when the dump name does not match the migration name exactly, when the JCMA migration option was not re-enabled before the run, or when the selected dump is outdated.

# Symptoms

- The migration fails with a message that JCMA cannot fetch the database dump.
- The migration starts but does not use the expected dump.
- A rerun behaves differently from an earlier attempt.
- The migration succeeds only after creating a new dump right before the migration.

# Prerequisites

- Access to the BigGantt app configuration in the source Data Center environment.
- Permission to run a migration in Jira Cloud Migration Assistant.
- A newly created BigGantt database dump available in BigGantt configuration.

# Solution

## Step 1: Create or verify the correct database dump

Open the BigGantt configuration in your Data Center instance and check the list of available database dumps. Confirm that the dump you plan to use is current and was created for the migration you are about to run.

**Expected result:** You can identify a fresh dump that matches the current migration activity, rather than an older dump from a previous attempt.

## Step 2: Make sure the migration name matches the dump name exactly

In JCMA, verify that the migration name matches the dump name in BigGantt character for character, including capitalization and punctuation.

> For example, **Migration Plan** and **migration-plan** are treated as different names.

**Expected result:** The migration name in JCMA is an exact match for the dump name stored in BigGantt.

## Step 3: Re-enable the JCMA migration option before each attempt

In the source environment, go to **Apps > BigGantt App Configuration > Advanced > Technical info > Data migration** and make sure **Allow JCMA migration** is enabled before rerunning the migration.

**Expected result:** The migration setting is turned on and ready for the next migration attempt.

## Step 4: Rerun the migration using the fresh dump

Start the migration again in JCMA after confirming the exact name match and enabling the migration setting. If you previously used an older dump, create a new one immediately before the rerun.

**Expected result:** JCMA fetches the correct dump and the migration proceeds successfully.

## Verification

Confirm that the migration completes without the “cannot fetch the DB dump” error. If available, review the JCMA migration dashboard and verify that the run used the intended dump. A successful outcome strongly indicates that the root cause was either an outdated dump or a mismatch between the migration name and dump name.

# Preventive Guidance

- Create the database dump as close as possible to the migration run time.
- Use a consistent naming convention for migration plans and dumps.
- Double-check exact name matching before every migration attempt.
- Re-enable **Allow JCMA migration** before each rerun, since this setting must be toggled on for every attempt.

> ✅ Best practice: if a migration fails and you suspect a dump issue, do not reuse an older dump automatically. Generate a fresh dump, verify the exact name match, and rerun the migration.