Guide in migrating JIRA tickets from our company to another company

[Sherwin Soriano]

We are merging with another company and they also use JIRA cloud, is there any guide or link that I can check on how we can migrate our tickets to their JIRA?

I am assuming we wont need any plug-ins?

[Trudy P Claspill]

Hello @Sherwin Soriano 

You can find Atlassian guidance here

Transfer data from one Atlassian instance to another 

And here is a community post you may find useful.

https://confluence.atlassian.com/cloudkb/how-to-merge-two-jira-cloud-instances-691011863.html

If the task seems overwhelming you might also consider engaging an Atlassian Solution Partner. You can find a partner serving your area and with specialized knowledge matching your needs in the Atlassian Partner Directory.

https://partnerdirectory.atlassian.com/

Disclosure: I work for Praecipio , an Atlassian Platinum Solution Partner.

[Dr_ Ankita Mehta-OpsHub_ Inc]

Hi @Sherwin Soriano

Yes, you can migrate tickets from one Jira Cloud site to another. Whether you need an additional tool depends on how much data you want to move and how different the two Jira setups are. A few things to check:

• Data scope: Decide whether you need to move only tickets or also comments, attachments, links, custom fields, and other related data.
• Transform on the fly: If the two Jira setups use different fields, workflows, or configurations, you may need to transform the data during migration.
• History & traceability: Check that comments, attachments, relationships, and other historical information remain intact after the move.
• Downtime: If teams need to continue working in the source Jira during migration, look for an approach that supports migration without disrupting them.
• Scale: The number of projects and tickets can also influence which migration approach makes sense.

In your case, you may want to explore OpsHub Migration Manager (OMM), a purpose-built migration tool. It supports phased or full Jira migrations, with no downtime, disruption, or data loss, while preserving historical data and supporting data transformation between different Jira setups.

Hope it helps!