How to Migrate All Projects, Issues, and Configuration from One Jira Cloud Org to Another?

[Ayush Pathak]

Hi Community,

I need to migrate all data from one Jira Cloud organization (e.g., abc.atlassian.net) to another (e.g., xyz.atlassian.net). This includes:

• Projects (along with issues, comments, attachments)

• Boards and dashboards

• Workflows, custom fields, schemes

• Users and permissions

• Automation rules (if possible)

What is the best way to perform this migration?
Should I use a third-party app like Exalate, Project Configurator, or Revyz?
Or is there a built-in tool supported by Atlassian for Jira Cloud-to-Cloud migration?

I would appreciate any suggestions, best practices, or references from those who have done this before.

Thanks in advance!

[John Funk · Accepted solution]

Hi Ayush,

I recommend using the Revyz Data Manager for Jira app in the Atlassian Marketplace. 

[Ayush Pathak]

Thank you, @John Funk  Just to clarify— is Revyz a free tool, or are there any prerequisites or limitations I should be aware of before using it?

[John Funk]

It is a paid tool, but you can get a 30 day free trial. 

[Luka Hummel - codefortynine]

Hi @Ayush Pathak

If you are willing to use a marketplace app, you can try our app Deep Clone for Jira. Deep Clone can clone whole projects and issues, including the configuration across instances. You can read more about that here.

[OpsHub - Enterprise class Integration and Migration Solutions for Jira]

Hi @Ayush Pathak

Jira Cloud-to-Cloud migration can be more complex than it appears—especially when you want to move not just issues and projects, but also workflows, custom fields, boards, dashboards, permissions, and automation rules.

If you're looking for a more controlled and complete migration, OpsHub, an Atlassian Solutions Partner offers a purpose-built migration solution for this use case. It supports:

• Migrating projects with full fidelity (issues, fields, comments, links, attachments)
• Preserving structure, traceability, and add-on data
• Enabling users in the source system to use and edit data while migration is going on
• Avoiding manual rework post-migration—especially helpful when you’re not moving entire sites
• Handling schema differences and data transformations without manual scripts

Here is the YouTube video to see how OMM facilitates Jira Cloud migration

Hope it helps!