Migration Jira Project from cloud Atlassian organization to another cloud atlassian organization

[Salvatore Di Franca]

Hello,

I need to migrate all work items from a Jira Project in my cloud Atlassian organization to another cloud Atlassian organization.

How can I do that ?

I can't find a specific solution

Thanks

[Daria Kulikova_GitProtect_io]

Hello @Salvatore Di Franca ,

Here is an article on Atlassian on how to copy the data from cloud to cloud: https://support.atlassian.com/organization-administration/docs/copy-jira-data/ 

Also, it's worth having a backup of your instance before starting the migration. That way, if anything doesn’t go as planned, you can easily roll back and restore your data.

[Diana_Architect_ZigiWave]

@Salvatore Di Franca , hi. hope you've managed to execute your migration successfully by now. i'll just add another tool for future - ZigiOps. Fully no-code data integration solution that is great for migrations: no limitations of the data transfer, none of your data is stored in it (all safe), plus it's easy to use. Feel tree to explore it, if you're curious - it comes with a free trial (or book a demo, also free an easy).

Regards, D.

[Ankita Mehta-OpsHub_ Inc]

Hi @Salvatore Di Franca

Migrating a Jira project between two Atlassian Cloud orgs is doable and with the right tool, it can be smooth and low risk. The key is to think beyond just moving issues, and evaluate how well the migration preserves structure, context, and continuity.

Here are a few important things to consider when choosing a migration tool:

• Rich data sync
  Look for a migration tool that supports beyond migration of just issues - attachments, comments, custom fields, workflows, and history should come along too.
• User mapping support: The tool should handle differences in user accounts across orgs to keep assignee and reporter info accurate.
• Issue hierarchy and traceability: Make sure it preserves Epic → Story → Sub-task structures, issue links, and dependencies.
• Sprint and board continuity: Boards, sprints, and filters should be recreated correctly to avoid disrupting agile workflows.
• Downtime and disruption: Can the tool minimize downtime or support live sync to reduce impact on active teams?
• Compliance and audit needs: For regulated environments, retaining timestamps, status transitions, and change history is a must.

 If you're planning a Jira-to-Jira Cloud migration and need more control over what gets migrated, you might want to explore OpsHub Migration Manager, an Atlassian Partner solution. It supports full-fidelity migration including custom issue types, workflows, attachments, and history without any disruption to your team. Just connect the source and target instances and let the platform handle the rest.

Drop us a line if you want to see a demo or have some questions.

[Marc - Devoteam]

Hi @Salvatore Di Franca 

You will need to export all issues to a CSV file and then import this CSV file.

Export

https://support.atlassian.com/automation/kb/how-to-export-issues-from-jira-cloud-in-csv-format/ 

Import

https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/