Merge multiple Jira Cloud sites

Still need help?

The Atlassian Community is here for you.

Ask the community

descriptionLearn how to merge and consolidate two or more Jira Cloud sites, or migrate a single project from one Jira Cloud site to another.

Important changes to our server and Data Center products

We’ve ended sales for new server licenses, and will end support for server on February 2, 2024. We’re continuing our investment in Data Center with several key improvements. Learn what this means for you

Overview

Jira Cloud does not currently support merging multiple sites and importing single projects from another cloud site. However, there are workarounds available and this page will outline those workarounds, along with some considerations for each option.

To determine which of these workarounds is most suitable for your migration needs, read our information on the different methods of migrating. There are three ways to merge multiple Jira Cloud sites:

  1. Import to Jira Data Center and use the Jira Cloud Migration Assistant

  2. Merge multiple sites in Jira Data Center

  3. Import issues using CSV import

To stay updated on the progress of this feature request, watch  JRACLOUD-72570 - Getting issue details... STATUS

Notify support of your migration window

If you’ll be performing your migration over a weekend or holiday, or are migrating over 1,000 users to cloud, get in touch at least two weeks in advance to let us know. This is so we can ensure we have extra support on hand during your migration.

Learn more about how we support cloud migrations.

1. Import to Jira Data Center and use the Jira Cloud Migration Assistant 

This approach may not work for all customers. We recommend that you test this approach 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 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 destination cloud site. This is the simplest approach to maintain your setup and configuration and only requires downtime for one of your cloud sites.

How to use this approach

Let's say you have two Jira Cloud sites: Jira Cloud A and Jira Cloud B. You want to move all or some issues from Jira Cloud B into Jira Cloud A (your destination site) so you can have a single, consolidated cloud site. To do this you’ll need to:

  1. Install the latest version of Jira Data Center. You can do this by generating a free trial license from my.atlassian.com. Note that Jira Data Center trial licenses last for 30 days. If you need more time to complete your migration, no problem – licenses can be extended to 90 days upon request.

  2. Create a backup of Jira Cloud B. This will contain the users and projects you'd like to import to Jira Cloud A. Note that next-gen projects are not available in Jira Data Center and will need to be converted into classic projects for the backup to work using this method.

  3. Import your data from Jira Cloud B to Jira Data Center.

  4. Use the Jira Cloud Migration Assistant to move and merge your projects from Jira Data Center into Jira Cloud A.

Limits to this approach

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.

2. Merge multiple sites in Jira Data Center

This approach may not work for all customers. We recommend that you test this approach 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 approach uses a Jira Data Center instance, which allows you to import specific projects. You can use this method to combine entire 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.

How to use this approach

Let's say you have two Jira Cloud sites: Jira Cloud A and Jira Cloud B. You want to move all or some issues from Jira Cloud B into Jira Cloud A (your destination site) so you can have a single, consolidated cloud site. To do this you’ll need to:

  1. Install the latest version of Jira Data Center. You can do this by generating a free trial license from my.atlassian.com. Note that Jira Data Center trial licenses last for 30 days. If you need more time to complete your migration, no problem – licenses can be extended to 90 days upon request.

  2. Create a backup of Jira Cloud B. This will contain the projects you'd like to import to Jira Cloud A. Note that next-gen projects are not available in Jira Data Center and will need to be converted into classic projects for the backup to work using this method.

  3. Import your data from Jira Cloud B to Jira Data Center.

  4. Create an XML backup of Jira Data Center. This will be used later for project imports.

  5. Create a backup for Jira Cloud A.

  6. Import the backup of Jira Cloud A to Jira Data Center.

  7. Use the Jira Data Center backup you created in step 4 to import the projects you want from Jira Cloud B to Jira Data Center. You should now have the projects you want from both Jira Cloud A and Jira Cloud B in Jira Data Center.

  8. After successfully importing all the required projects, create a backup of Jira Data Center

  9. Import that backup file into your destination Jira Cloud site.

If the attachments are not included during the project restore, the imported project will not have attachments associated with it. Attachments can’t be restored separately because the database entries for the attachments will be missing.

Limits to this approach

  • App data and users will not be migrated. 

  • Next-gen projects are not available in Jira Data Center and will need to be converted into classic projects for the backup to work using this method. Learn more about Jira Cloud backups
  • 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.

3. 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.

How to use this approach

Let's say you have two Jira Cloud sites: Jira Cloud A and Jira Cloud B. You want to move all or some issues from Jira Cloud B into Jira Cloud A (your destination site) so you can have a single, consolidated cloud site. To do this you’ll need to:

  1. Search for all the issues in the required projects in Jira Cloud B, and export them as CSV.

  2. Create the projects as empty in your Jira Cloud A site.

  3. Import the CSV file to the projects in your Jira Cloud A site.

Limits to this approach

  • App data and users will not be migrated. 

  • This approach only merges issues, not entire 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.

  • Links to Confluence pages under the Mentioned On section in Jira issues will not be imported. We have an open feature request where you can learn more or vote for this issue to be resolved.

More information and support

We have a number of channels available to help you with your migration to cloud.


Last modified on Apr 19, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.