| Info |
|---|
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 ways to move data to another Jira Cloud site. The method you choose will depend on your needs. To help you decide, this page describes each method and some of their respective limitations.
Perform a cloud-to-cloud migration
Jira cloudCloud-to-cloud migration lets helps you migrate move users and Jira Software and Jira Core projects and related issues, configurations, users and groups Work Management projects from one cloud site to another. In a cloud-to-cloud migration, data is copied from one cloud site to another. Using You can use this method , you can consolidate two to combine data across two or more cloud sites, or split a site by moving some projects to a new site.
Limits to this approach
App data is not migratedcloud site into multiple cloud sites, duplicate a cloud site, or copy specific projects from one cloud site to another.
Limitations
Team-managed projects aren’t supported.
Jira Service Management is not isn’t 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 methodApp data isn’t migrated.
Group membership isn’t preserved. You must You’ll need to add users to their respective groups after migrating.
| Info |
|---|
We are actively working to support all fields, configurations, preserving group membership, and more in the subsequent releases. |
Some fields or configurations might not be supported. Before choosing this method, check https://migration-docs.atlassian.net/wiki/spaces/CTCM/pages/37158913/What+we+migrate+with+the+early+access+program?focusedCommentId=932249605
Learn how to move your data with cloud-to-cloud migration
Import to Jira Data Center and use the Jira Cloud Migration Assistant
This approachfor Jira
Use the Jira Cloud Migration Assistant via Jira Data Center
| Note |
|---|
This method may not work for all customers. We recommend that you test this method before performing a production migration. This will help you anticipate the issues that you may encounter during your migration and resolve them in advance. |
If you can’t perform a cloud-to-cloud migration, this is the next simplest way to maintain your setup and configuration and only requires downtime for one of your cloud sites.
This method requires setting up a Jira Data Center instance. This method involves importing You’ll need to create a backup of your the data from your source cloud site and using use the Jira Cloud Migration Assistant to move your data into the target import that data into your destination 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.
You can use this method to consolidate two cloud sites or move specific projects from one Jira Cloud site to another.
Limitations
Team-managed projects aren’t available in Jira Data Center and will need to be converted into company-managed projects for the backup to work using this method. Learn more about Jira Cloud backups
Jira Service Management isn’t supported.
App data isn’t migrated.
Some fields or configurations may might not be supported. Check https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html before choosing this methodBefore choosing this method, check what gets migrated with the Jira Cloud Migration Assistant.
Knowledge of how to install and set up a Jira Data Center instance is required.
| Note |
|---|
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
multiplesites 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’lland import into Jira Cloud manually
| Note |
|---|
This method may not work for all customers. We recommend that you test this method before performing a production migration. This will help you anticipate the issues that you may encounter during your migration and resolve them in advance. |
This method requires setting up a Jira Data Center instance. You’ll need to create backups of all your Jira Cloud sites, merge them through a Jira Data Center instance, and import them back the backups in Jira Data Center, then import the backups into your destination cloud site.
Limits to this approachLimitations
Team-managed projects aren’t available in Jira Data Center and will need to be converted into company-managed projects for the backup to work using this method. Learn more about Jira Cloud backups
App data and users will not be aren’t 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.
| Note |
|---|
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 approachand importing into Jira Cloud manually
Use a CSV file to import issues
This method 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 Data Center instance, or if you only want to migrate move a small number of projects and issues.
Limits to this approach
App data and users will not be migrated.
Limitations
This approach only merges issues, not projects.
App data and users aren’t migrated.
Before importing the CSV file, you'll need to recreate the project and set up the project's configurations (e.g., Workflow , or Permission SchemesScheme) 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 Learn more about importing attachments into Jira Cloud using CSV External System Importer
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.