Need Help Migrating Projects Across Different Atlassian Organizations

[Prabakar]

Hi Team,

I’m looking to migrate a few projects from one Atlassian organization to another, including all associated data such as issues, attachments, comments, users, workflows, and custom fields.

We attempted to use the Data Transfer option, but it appears to only support transfers between sites within the same organization.

Example Scenario:

• Source: x.atlassian.net (Org A)
  Projects: P1, P2
• Target: y.atlassian.net (Org B)

Both sites belong to separate Atlassian organizations, and we need to move P1 and P2 from Org A to Org B.

Could you please advise on the best approach or tools available to perform this type of cross-org migration?

Thanks in advance!

[Marc -Devoteam-]

HI @Prabakar 

This should be possible from instance to instance, you will need to be org admin in both instances, as I can do this.

You could try to make a full backup of your site and create a new site on the other organization, import the backup and then move the data from one site to the other.

Use the 30 day trail (standard or premium), most of the time you can also do this with 3rd party tooling

See also documentation, that outlines options, like;

https://confluence.atlassian.com/adminjiraserver0818/merging-jira-instances-1167724788.html 

https://community.atlassian.com/forums/Jira-Service-Management/Merging-two-instances-into-one/qaq-p/2910811 

[Pallavi Shirodkar]

Hi @Prabakar 

Because it only allows transfers inside the same organization, the "Data Transfer" option will not function for moving Jira projects and all related data (issues, attachments, comments, users, workflows, and custom fields) between two different Atlassian organizations on Jira Cloud.

You can use the following tool

Jira Cloud Cloud Migration Tool + Configuration Manager: To move projects between Jira Cloud sites across various enterprises, use these two tools together. These applications enable the lossless transfer of user-generated content, configurations, and entire project data. To make the migration process easier, Configuration Manager is deployed on the target Jira Cloud site and the Cloud Migration Tool is temporarily installed on a Jira Server or Data Center instance.

Hope this helps!

[Ankita Mehta-OpsHub_ Inc]

Hi @Prabakar

Welcome to the Atlassian Community! 

Moving projects between separate Atlassian organizations can be tricky because the native Data Transfer option doesn’t support cross-org migrations. Here are a few things to consider:

• Permissions & access: You’ll need admin access in both organizations to perform the migration and manage user permissions in both Org A and Org B.
• Data fidelity: Ensure all project-related data including issues, comments, attachments, workflows, and custom fields are mapped correctly to avoid data loss.
• Custom fields & configurations: Custom fields and workflows from Org A need to be replicated or mapped to Org B, as these won’t transfer automatically.
• Downtime & disruption: Plan for minimal downtime and ensure the migration is non-disruptive, especially for ongoing work in Org B.
• Phased migration: To reduce risks, migrate in stages, starting with a few projects, like P1 and P2, and validate before migrating the rest.
• Transformation on the fly: If needed, you can adjust field values, workflows, or issue types during migration to align with Org B’s setup.

In this case, you may want to consider an enterprise-grade data migration platform, OpsHub Migration Manager (OMM), an Atlassian Solution Partner for it can help you with:

1.  Data transformation on the fly, making it easier to map fields and workflows as you migrate.
2. Keeping the history intact and helps you move without downtime or disruption.
3.  Phased or full migrations between different Atlassian organizations and allows for data transformation on the fly, making it easier to map fields and workflows as you migrate.
4.  Migration of comments, attachments, relationships, custom field mappings, workflows and more with high fidelity. Its reverse sync option keeps everything up to date both in source and target during the ongoing migration process.

Hope it helps! :) 

[Valerie Knapp]

Hi @Prabakar , thanks for your post.

Have you checked out the cloud migration assistant - https://support.atlassian.com/migration/docs/what-is-jira-cloud-migration-assistant/ ?

I think this is more what you need. Also, if there is budget, a lot of people use a solution partner for this kind of complex migration (no pressure) - https://partnerdirectory.atlassian.com/ 

Please consider also to open a support ticket for 'migration support' to the service desk, just in case you get stuck and need help - https://support.atlassian.com/contact/#/ 

Best wishes