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.
There are four methods you can use to migrate data between Jira cloud sites, including the new cloud-to-cloud migration feature. However, there are limitations to each method. This page outlines each method and their respective limitations.
Use Jira cloud-to-cloud migration
Jira cloud-to-cloud migration lets you migrate Jira Software and Jira Core projects and related issues, configurations, users and groups from one cloud site to another. Using this method, you can consolidate two cloud sites, or split a site by moving some projects to a new site.
Limits to this approach
App data is not migrated.
Jira Service Management is not supported.
With the EAP release, some fields or configurations may not be migrated. Check What we migrate with the early access program before choosing this method.
Group membership isn’t preserved. You must add users to groups after migrating.
We are actively working to support all fields, configurations, preserving group membership, and more in the subsequent releases.
Learn how to migrate with Jira cloud-to-cloud migration
Import to Jira Data Center and use the Jira Cloud Migration Assistant
This approach requires setting up a Jira Data Center instance. This method involves importing a backup of your data from your source cloud site and using the Jira Cloud Migration Assistant to move your data into the target cloud site. This is the simplest approach to maintain your setup and configuration and only requires downtime for one of your cloud sites.
Limits to this approach
App data will not be migrated.
Jira Service Management is not supported.
Some fields or configurations may not be supported. Check https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html before choosing this method.
Knowledge of how to install and set up a Jira Data Center instance is required.
We strongly encourage performing a dry-run of the import and doing User Acceptance Testing on a test cloud site (which can be created using a free trial) before proceeding with the import on your production cloud site.
Learn how to migrate via Jira Data Center using the Jira Cloud Migration Assistant
Merge multiple sites in Jira Data Center
This approach uses a Jira Data Center instance, which allows you to import specific projects. You can use this method to combine multiple sites, or to import only particular projects from one Jira Cloud site to another.
If you choose to use this method, you’ll need to create backups of all your Jira Cloud sites, merge them through a Jira Data Center instance, and import them back into your destination cloud site.
Limits to this approach
App data and users will not be migrated.
Knowledge of how to install and set up a Jira Data Center instance is required.
Merging sites usually takes quite some time to complete, especially for large sites.
We strongly encourage performing a dry-run of the import and doing User Acceptance Testing on a test cloud site (which can be created using a free trial) before proceeding with the import on your production cloud site.
Learn how to migrate by merging multiple sites in Jira Data Center
Import issues using CSV import
This approach involves exporting and importing your issues via a CSV file. This method is recommended if you don’t have experience installing and setting up a data center instance, or if you only want to migrate a small number of projects and issues.
Limits to this approach
App data and users will not be migrated.
This approach only merges issues, not projects.
Before importing the CSV file, you'll need to recreate the project and set up the project's configurations (e.g. Workflow, or Permission Schemes) on the destination site. This manual configuration may take some time.
Issue History (e.g. timestamp of issue transitioned or issue updated) will not be retained.
Additional steps are required to import attachments. See https://confluence.atlassian.com/cloudkb/importing-attachments-into-jira-cloud-using-csv-external-system-importer-966669960.html
Links to Confluence pages under the Mentioned On section in Jira issues will not be imported. To stay updated on this feature request or vote for it to be resolved, watch this feature request.