Migrate project to another Jira [CLOUD to CLOUD]

[Albert Manuel]

Hi there,

I need to migrate 5 projects from one Jira Cloud instance to another. I'm only looking to move the projects themselves—no global settings, users, or configurations.

What would be the best and simplest way to handle this migration?

Thanks!

[Usman]

Hello @Albert Manuel 

Yes you will need to do this from the Source Jira instance. There is a Cloud Migration tool that allows you to migrate only the projects you select, rather than the entire instance.

During the migration setup, you can choose to migrate only the specific projects you want. For users and groups, select the option: "Only users and groups related to the selected projects." This ensures only those directly associated with the projects are moved, minimizing unnecessary data transfer.

After migration, you can remove any unwanted users or groups if needed. This method avoids transferring global settings or unrelated configurations. This is the most direct and supported method for moving projects between Jira Cloud instances with minimal manual effort. 

Please see the guide here - https://support.atlassian.com/organization-administration/docs/copy-jira-data/

[Albert Manuel]

Thanks @Usman 

What if i don't want to copy any users or groups?

Users exist in both instances under tge same email address  --- but i dont want any groups or settings beside the tickets / workflows / statuses / links to be copied. Looking at the link you gave me, seems like i need to copy some users ir groups, i can't exclude them 100%

[Ankita Mehta]

Hi @Albert Manuel, 

f you're only migrating a few projects between Jira Cloud instances — and not global configurations or users — that simplifies things, but there are still a few key aspects to keep in mind: 

• Custom fields & workflows: If the destination instance doesn’t have the same setup, you may need to recreate fields and workflows to ensure data maps correctly. 
  Issue hierarchy & links: Parent–child links, Epic–Story relationships, and other references can break if not handled carefully. 
• Attachments, comments, and history: These aren't always included in all migration approaches. Make sure your method explicitly supports them if you need full fidelity. 
  Issue keys: Jira may regenerate issue keys unless specifically preserved — which can affect references in documentation or integrations. 
• Delta changes: If teams keep working while migration is in progress, consider how updates made during the transition will be captured.                                                 

You may consider an Atlassian partner’s enterprise – grade migration tool, OpsHub Migration Manager (OMM)  that support high-fidelity, audit-friendly migrations with zero downtime and non - disruption. 

Let me know if you have questions or you may also request a demo here

Good luck with your migration!

[Diana_Architect_ZigiWave]

@Albert Manuel hi. I see  that Usman has given you some directions on how to proceed. In case you want to explore other options - check out ZigiOps. It's a 100% no-code integration platform that can execute migrations with an ease (Jira to Jira or any other system). No limit of the data you transfer + none of your data will be stored.  We do offer free  trial (you can also book a demo, too) - so you can test it yourself. 

Regards,

Diana

[Javier Pozuelo -Exalate-]

Hi @Albert Manuel

I'm the Community Manager at Exalate, and I've seen many teams encounter this exact challenge when trying to move specific Jira Cloud projects between instances.

One option worth considering is a third-party solution like Exalate. https://exalate.com/migration/

While Exalate isn’t a migration tool in the traditional sense, it can be used to migrate projects, issues, attachments, comments, custom fields, and more between Jira instances.

You also have the option to keep both instances in sync, which can be especially helpful for gradual migrations. 

Let me know if you have any questions. Or, if you prefer, you can directly book a one-on-one video call where we can show you how Exalate would work for your use case: https://exalate.com/book-demo/

Best of luck with the migration! 

[arielei]

Hey @Albert Manuel 

If you are an Org Admin then go to admin.atlassian.com and select your domain.

Then go to Settings and on the left menu under "Data Management" you can do "Data Transfer" and select the projects you want to move to another cloud.

Hope that helps.

Ariel. 

[Albert Manuel]

@arielei do i need to do this from the Jira i want to move, or from thwe one i want to move to ?

[arielei]

Hey @Albert Manuel 

see this guide that was shared by Atlassian Team @Usman 

https://support.atlassian.com/organization-administration/docs/copy-jira-data/