Retry failed migration steps in Jira Cloud Migration Assistant
If your migration is INCOMPLETE or FAILED, you can retry only the steps that failed, from the same migration plan. Jira Cloud Migration Assistant (JCMA) skips every step that already completed, and runs again only the failed steps and any steps that didn't run because of the failure. You don't need to create a new migration plan or delete partially migrated data from your Cloud site. Retrying doesn't create duplicate data.
Retrying covers core migration steps, such as project import, attachments, and assets upload. For example, if a project fails during import, retrying runs the import and attachment steps for that project. Retrying doesn't cover app migration. To retry an app migration, see Re-run a Marketplace app migration.
What happens when a step fails
Data shared across projects isn't imported yet. If a project fails during export, preprocessing, or import, JCMA doesn't import data shared across projects, such as filters and dashboards, so that none of it is missed. If only attachments fail, this data is still imported.
App migration waits. If any core migration step fails, app migration doesn't start automatically, and the migration shows App migration on hold. You choose whether to retry the failed steps or continue to app migration. Nothing happens until you choose. Data shared across projects, such as filters and dashboards, isn't imported until you retry the failed steps or continue to app migration. If your plan doesn't include Marketplace apps and you can't retry the failed steps, contact Atlassian Support for help migrating data shared across projects.
You get an email. JCMA emails the admin who started the migration, whether or not the migration plan includes Marketplace apps. The email shows how many steps failed and how many times the migration has been retried, and explains your options.
A countdown starts. The migration details show how many days you have left to retry.
Before you begin
Use Jira Cloud Migration Assistant 1.21.0 or later. We recommend 1.27.0 or later, which fixes some known issues with retrying.
Be a Jira system administrator on your source site, the same as for running a migration.
If the failure was caused by your data or configuration, find and fix the cause first. For example, if a step failed because a custom field is missing from your Cloud site, add the custom field before you retry. You can fix the cause on your source site or your Cloud site, and the retry uses your latest data. Retrying doesn't fix the original problem, so a step that failed for a reason you haven't addressed will fail again. If you're not sure what caused the failure, check with Atlassian Support before you retry. Learn how to troubleshoot your Jira migration
If you can't find the cause, contact Atlassian Support after the first failed attempt, before you retry. Support can help you find and fix the cause, so that your retry succeeds.
If your migration is large, contact Atlassian Support before you retry, and wait for Support to confirm before you select Retry failed steps.
Retry the failed steps
Open the Jira Cloud Migration Assistant and go to the Migrations dashboard.
Find the failed or incomplete migration and select View details.
Select Retry failed steps.
The migration status changes to RETRYING, and then to RUNNING. When the failed steps complete, the steps that depended on them run. Then data shared across projects is imported and app migration starts automatically.
Continue to app migration instead
If your migration plan includes Marketplace apps, you'll also see Continue to app migration. Select it to start app migration without retrying the failed steps. We recommend retrying the failed steps first, because apps that depend on the failed projects might not migrate successfully.
You can't undo this. App migration includes only the projects that migrated successfully, and you can't retry the failed steps from this migration plan afterwards. To migrate the failed projects, create a new migration plan for them.
Retry limits
You can retry a migration up to 3 times. If you need more retries, contact Atlassian Support to raise the limit.
You can retry a migration for a limited time after it started. The migration details show how many days are left. This is separate from the 12-day limit for re-running an app migration.
Retry attempts are counted separately from the automatic retries JCMA makes for temporary errors.
If Retry failed steps isn't shown, the migration isn't eligible for a retry (for example, because app migration has already started), or it has reached a limit. The migration stays INCOMPLETE or FAILED.
Was this helpful?