JCMA: Is it possible to trigger an app data migration independently of the core Jira data migration?

[Craig Schwarze _ProjectBalm_]

Our client recently completed a JCMA transfer from Jira Data Center to Jira Cloud. The core Jira data (projects, issues, users, groups) migrated successfully, but the app data migration for a Marketplace apps did not complete as expected.

The original transfer is now in a settled state and cannot be retried (HTTP 409 on the migration progress endpoint).

We need to re-run the app data migration phase only. Creating a new migration plan appears to require re-selecting projects and re-running the full migration pipeline — including the core Jira data phase — before the app migration phase executes.

Is there a supported way to execute only the app data migration stage of a JCMA transfer without re-running the core Jira data migration?

[Himanshu Tiwary · Accepted solution]

Hi @Craig Schwarze _ProjectBalm_ ,

As far as Atlassian currently supports, you cannot reopen an existing JCMA transfer and then only run the app phase on the existing transfer ID.

There are two different features 

• Rerun unsuccessful app migrations. This is only available for existing failed or incomplete app migrations and only within Atlassian’s re-run window.
• Separate Marketplace app data migration. With new versions of JCMA, you can create a new transfer to migrate only app data, without re-running Jira core data, if the associated projects were migrated within the last 14 days.

if the existing transfer is no longer available and is no longer re-runnable, the current support options do not include the ability to reopen and only run the app phase on the existing transfer. https://support.atlassian.com/migration/docs/migrate-marketplace-app-data-separately/