Merge multiple instances of Jira Cloud

Still need help?

The Atlassian Community is here for you.

Ask the community

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

Merging multiple sites and importing single projects from another cloud site are not currently supported features in Jira Cloud. However, there are workarounds available. This page outlines those workarounds, along with some considerations for each option. 

To stay updated on the progress of this feature request, please watch  JRACLOUD-72570 - Provide support for "Single Project" imports between Jira Cloud sites GATHERING INTEREST

Method one: Merge sites in Jira Server

The recommended approach is to use a temporary Jira Server application, which allows you to import specific projects. Using this method you can combine entire sites, or import only particular projects from one Jira Cloud site to another.

If you choose this method you'll need to take Jira backups from all your Jira Cloud sites, merge them through a temporary Jira Server application, and then import them back to you final cloud site as shown in the diagram below:

Diagram showing the steps two merge multiple Jira Cloud sites

Let's say you have two Jira Cloud sites: Jira Cloud A and Jira Cloud B. You want to move all or some projects from Jira Cloud B into Jira Cloud A so you have a single, consolidated cloud site. The basic outline of this process is:

  1. Install the latest version of Jira Server. You can do this using a free evaluation license
  2. Create a backup for Jira Cloud B. This will contain the projects you'd like to import to Jira Cloud A.
  3. Next, import your data from Jira Cloud B to Jira Server.
  4. Create an XML backup of Jira Server. This will be used later for project imports.
  5. Create a backup for Jira Cloud A
  6. Import the backup for Jira Cloud A to Jira Server.
  7. Using the Jira Server backup you created in step 4, import the projects you want from Jira Cloud B to Jira Server. You should now have the projects you want from both Jira Cloud A and Jira Cloud B in Jira Server.

    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.

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

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

Limits to this approach

  • App data and users will not be migrated. 
  • Requires knowledge of how to install and set up a server application.
  • 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. This way, you can anticipate the issues that you may encounter during migration and resolve them in advance.

Method two: Import issues through CSV

Another approach would be to export and import your issues via CSV. This approach is generally recommended when you don't have experience installing server applications. 

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 so you have a single, consolidated cloud site. The basic outline of this process is:

You would first need to search for all the issues in the required project(s) in Jira Cloud B, and export them as CSV. Then, you will import the CSV file to the project in your Jira Cloud A site.

If you want to migrate attachments as well, you'll need to follow additional steps

Limits to this approach

  • App data and users will not be migrated. 
  • Before importing the CSV file, you'll need to recreate the project and set up the project's configurations on the target site, including Workflow, Permission Schemes, etc. This manual configuration may take some time.
  • This approach only merges issues, not entire projects.
  • Issue History will not be retained – for example, timestamp of issue transitioned or issue updated.
  • You'll need to follow additional steps 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 Nov 21, 2019

Was this helpful?

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