Last updated Sep 28, 2023

Enable Migrate all data at once

We've deprecated the 'Migrate all data at once' feature

On September 1, 2024, we're removing the option to migrate all data at once from the Jira Cloud Migration Assistant. Until then, we'll continue to support and maintain the feature's current functionality.

There are no actions developers need to take in response to this change. Automated migration paths work the same whether using project-by-project or migrate all data at once.

For more information, see the deprecation notice in the changelog.

The 'Migrate all data at once' option in the Jira Cloud Migration Assistant (JCMA) lets customers migrate data in bulk, without having to select specific items. Apps selected as 'Needed in cloud' in the App Assessment screen are included in the bulk migration.

This page provides instructions for enabling the feature in versions of the JCMA where the option is behind a feature flag. It also explains how apps are handled during a bulk migration.

For more about the feature and how it impacts app migrations, see Migrate all data at once.

Setting the Feature Flag

Starting with JCMA 1.9.4, the feature is enabled by default and no longer behind a feature flag.

  1. Visit the Dark Feature page for your Jira site at <Jira_URL>/secure/SiteDarkFeatures!default.jspa
  2. Enter com.atlassian.jira.migration.single-path-including-apps.migrations in the text box.
  3. Select Add. dark-feature-bulk-app-migrations.png

App Custom Fields and App Workflow Rules

The following versions of the JCMA support the 'Migrate all data at once” option for apps that implement custom fields and workflows rules.

  • Available behind feature flag: JCMA 1.9.7 through 1.9.16
  • Enabled by default: Starting with JCMA 1.9.17

To enable support for JCMA versions 1.9.7 through 1.9.16:

  1. Visit the Dark Feature page for your Jira site at <Jira_site_URL>/secure/SiteDarkFeatures!default.jspa.
  2. Enter com.atlassian.jira.migration.disable.preflights.custom.and.workflow in the text box.
  3. Select Add. dark-feature-bulk-app-migrations-custom-field-workflow.png

Before the Migration

All pre-flight checks directly relating to Marketplace apps are validated during the 'Pre-migration checks' screen.

dev-mode can be used to trigger a migration for all apps installed on your instance as well as to skip the pre-migration checks for these apps.

In general, the pre-migration checks within the JCMA provide feedback if any actions need to be taken prior to running a migration. To be included in the bulk migration, apps selected as 'Needed in cloud' must be pre-installed on your cloud site.

Your cloud site must not have any existing projects. Projects in the trash will be cleared out during the migration.

During the Migration

Similar to Project by Project migrations, the bulk migration consists of a core migration phase and an app migration phase.

Core migration

During this phase, all data related to the native operation of Jira is moved through Atlassian systems to migrate the customers data from their server instance to a cloud instance. This includes and is not limited to projects, issues, users, and attachments.

As part of this phase, all pre-installed apps on the cloud site is temporarily removed and re-installed before the conclusion of this phase.

If there are any errors during the re-installation of apps during this phase, the migration does not proceed and app migration does not begin.

This re-installation step is listed as the "Preparing apps" step in the migration details screen for a Bulk Migration


App migration

After core JIRA data has been moved to the cloud, your app's migration path is executed on the server. For more about how app migration works, check out Migrate your apps.


For more about the migration methods that Atlassian supports, check out Cloud migration methods.

To get help or report an issue, visit our support page.

Rate this page: