Resolve data errors during migration with remediation

Import and export data errors can surface during a migration, even after pre-migration checks pass. When the Jira Cloud Migration Assistant (JCMA) detects fixable errors, it automatically pauses the migration with the status Paused for Remediation. You can fix these errors directly in the assistant or by using a CSV file, without starting over or contacting Atlassian Support.

How data error remediation during migration works

  • When remediable errors occur during import or export, affected projects transition to the Paused for Remediation status.

  • An email notification is sent to the migration creator with details of the affected projects and a link to the remediation dashboard.

  • A countdown banner in the migration assistant shows the remaining days and attempts.

    • If three failed attempts occur, the migration transitions to the Incomplete status.

    • If 14 days lapse without action, the migration transitions to the Failed status.

Before you begin

Before you apply remediations, you will need to complete the following steps:

  • Check your permissions. To migrate, you need to be a system admin in the source instance and an organization admin in the destination cloud site.

  • Ensure you have access to the email account associated with the migration creator to receive remediation alerts.

  • Review the remediation window banner in the migration assistant. You have up to 14 days and three attempts to submit remediations before the migration expires or fails.

Resolve data errors during migration

You can resolve data errors during migration directly from the JCMA user interface or by using a CSV file.

Resolve errors directly in JCMA

  1. Open Jira Cloud Migration Assistant and navigate to your paused migration plan.

  2. Select Fix remediable errors to view the list of affected projects and error details.

  3. Select an affected project to expand the error list.

  4. Enter the corrected values into the designated input fields for each error.

  5. Select Save to validate and apply your changes.

  6. Review the validation status on the screen.

  7. Select Resume migration.

The migration status changes to Resume Initiated and continues processing only the remediated projects. Projects that previously succeeded are not re-run.

Resolve errors in bulk using a CSV file

  1. From the remediation dashboard, select Download CSV to download the CSV file (or a ZIP file containing project CSV files).

  2. Open the CSV file in your spreadsheet editor.

  3. Locate the Fix column and enter the required correction for each listed item.

  4. Save the CSV file.

  5. Return to the remediation screen and select Upload CSV to submit the corrected file.

  6. Review the validation status on the screen.

  7. Select Resume migration.

The migration status changes to Resume Initiated and continues processing only the remediated projects. Projects that previously succeeded are not re-run.

Troubleshoot data error remediation

What happens if all three remediation attempts fail?
If you run out of all three attempts without resolving the errors, the migration status changes to Incomplete. If that happens, review the remaining errors and initiate a new migration plan or resolve the underlying data in the source instance.

What happens if the 14-day window expires?
If you don’t take action is taken within 14 days, the paused migration automatically expires and transitions to Failed. If that happens, review the remaining errors, fix the underlying data in the source instance, and retry failed migration steps.

Still need help?

The Atlassian Community is here for you.