Thank you for being a part of the early access program. This community site allows you to provide feedback through page or inline commenting. We will use your comments to improve our product and documentation. Anybody on the internet can view your comments. To know your rights and responsibilities as a customer of our cloud products, read our Atlassian Cloud Terms of Service.
You need to be an organization admin or a site admin to access Jira cloud-to-cloud migration. Learn more about admin permissions
This page describes how to use the Jira cloud-to-cloud migration feature to migrate your projects and related data from one cloud site to another.
1. Access the Jira cloud-to-cloud migration feature
Log in to your source cloud site (the Jira cloud site you want to migrate your projects from).
Go to Settings > System.
Click Migrate cloud site from the left navigation menu.
The Migration overview screen shows you details about your source site.
These details include:
Number of projects
Number of users and groups
The plan you’re currently subscribed to
Links to the documentation you may need
2. Create a migration
From the Migration overview screen, click Manage migrations. This will take you to the Migrations dashboard, which will be empty until you create a new migration.
Click Create a migration.
3. Select your destination cloud site
First, enter a name for your migration. This will help you identify a migration on the dashboard if you need to run more than one migration.
Next, choose the destination site where you want to migrate your data to. By default, all Jira cloud sites that you are a site admin for will appear in the dropdown list. If you still don’t see your site listed, you’ll need to:
Check if you have site admin permissions for the destination site
Check if your destination site is under the same organization as your source site. If your site is under a different organization, you will need to transfer products to your organization.
If you want to migrate to a new site, follow these instructions to create a new site and add it to your organization.
Make sure your destination site has the same user-installed apps as your source site. This will reduce the chance of a migration failing, although app data will not be migrated. To migrate app data, you will need to contact each Marketplace Partner directly.
Once you’ve selected your destination site, click Choose projects to proceed.
4. Choose projects you would like to migrate
You can choose to migrate all or some of your projects. Currently, team-managed projects (formerly next-gen projects) in Jira Software are not migrated. We recommend checking what we migrate with the Jira cloud-to-cloud feature in the early access program.
When selecting projects, all users, groups, issues, and configurations related to the selected projects will also be selected for migration. With the EAP release, we don’t preserve group membership, so you’ll need to add all your users to groups after you migrate. With the upcoming release, we’re planning to provide an option to preserve group membership.
Once you’ve selected projects, click Check for conflicts to proceed.
5. Check for conflicts
In this step:
We'll save your migration. The migration will appear on the dashboard.
We’ll check for conflicts in your migration.
We’ll check if:
You have the same products and licenses in your source and destination sites. You’ll need to have the same Jira products in your destination site as your source site. For example, if you have Jira Software and Jira Core in your source site, and you have Jira Service Management in your destination site, you will need to add Jira Software and Jira Core to your destination site. If there is a product you don’t want to use after migrating, set up a free trial for that product, then deactivate the trial after your migration is complete.
You have duplicate projects. Duplicate projects are projects with the same name or key that exist in both the source and destination site. To resolve this, you’ll need to delete the duplicate project, or change the product name or key in either source or destination site.
You can also remove duplicate projects from your migration if you don’t want to migrate them. You can download the CSV file to see the list of duplicate projects.
Projects, boards, and filters are publicly available and searchable online. Some permissions in your source may be set to Public. Anyone on the internet can access your projects or data. We migrate your permissions as they are configured. To resolve this, you’ll have to either update your permissions or click Continue with public access.
This step only checks for the issues mentioned above. You may encounter other issues during the migration process.
6. Review your migration
Once you’ve resolved all conflicts, click Review to proceed to review your migration.
You can proceed to review your migration without resolving any conflicts, but you won’t be able to run the migration until all conflicts have been resolved.
On the Review migration screen, you’ll see a summary of your migration.
You’ll also see the number of users and groups, and the list of projects you’ve selected to include in your migration.
Users, groups and individual projects are all marked with a pre-migration status, indicating each entity’s readiness for migration.
Pre-migration status | Description |
READY | There are no errors or conflicts with the selected users, groups or projects and you can proceed to run your migration. |
FIX | There is an error or conflict with the selected users, groups or a specific project. You’ll have to check for conflicts again and resolve the conflicts before you can proceed to run your migration. |
CHECK | There is an error or conflict with the selected users, groups, or a specific project. You can run the migration, but we recommend that you check for conflicts again and check the warning. |
If you haven’t resolved any conflicts from the previous step, you’ll need to go back to do so. Click the View errors and warnings link to go back to the Check for conflicts screen and resolve any conflicts.
If your source Jira site is actively in use, we recommend you always check for conflicts before you run your migration even if no errors or warnings were found the last time a check was performed. This is to make sure that the feature checks for the latest changes to your Jira cloud data. Click Rerun checks to check for conflicts from within the Review migration screen.
Once you've resolved all conflicts and reviewed your migration, you will be able to run your migration. Click Run migration to proceed.
7. Run your migration
When you run your migration, you’ll be redirected to the Migrations dashboard. For more details about how to use the dashboard, see the Using the dashboard section.
To see the detailed progress of a specific migration, click View details.
The View details screen shows you the migration status and progress of users, groups, and individual projects.
While a migration is running, the migration status of users, groups, and projects will keep changing. There are five possible migration statuses.
Migration status | Description |
QUEUED | This item is next in queue to be migrated. |
RUNNING | This item is currently being migrated. |
COMPLETE | This item was successfully migrated. |
INCOMPLETE | This item was partially migrated. For example, this could mean 10 out of 15 users were migrated. |
FAILED | This item could not be migrated. |
Using the dashboard
The Migrations dashboard lets you see all your saved, running, complete, incomplete, failed and expired migrations all in one place.
From the dashboard, you can:
Track the progress of your running migrations.
Click the More options (•••) menu to access more actions for a migration, including to:
Run a saved migration
Edit a saved migration (add or remove projects from a saved migration)
Check for conflicts before running a migration
Visit the destination site you’ve selected for a migration
You can’t rerun a complete, incomplete, or failed migration.
Expired migrations
Migrations will expire after 14 days due to GDPR restrictions. Expired migrations are grayed out on the dashboard. The migration data will no longer be available and you won’t be able to perform checks or run the migration. For more information, see GDPR restrictions for Jira cloud-to-cloud migration
