Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Tips for Migrating 3 Projects to a Different Jira Instance (Both Cloud)


Does anyone have any tips for migrating 3 projects from one instance of Jira to a different instance?  I've found some techniques, but wondering if there are some hints or "gotchas" I need to be aware of.


3 answers

3 accepted

2 votes
Answer accepted

Try out Atlassian's Early Access Program for the cloud-to-cloud migration. We are currently using it and it already works pretty well and is supposed to be finalized soon.

Much faster and easier than any other options out there. You can migrate it project by project. But I would also recommend creating a free test site under your organization first to test it out.


Thank you!   

How can i get access to the Atlassian's Early Access Program?

@Cheri Hansen This is the entry point to the documentation of the cloud-to-cloud migration:

Actually, I can't see the documentation mentioning the early access program but as far as I know, you still can't access the features by default, yet. You need to create an Atlassian support ticket to get at least the source site enabled for the EAP. The destination site doesn't necessarily need to be enabled for the EAP.

Best regards,

2 votes
Answer accepted

Here are some hints from my past experience:

  • Create a separate free project in Atlassian (with you and a few people) to test your importing procedures before the "big day"
  • When importing the data, create a custom field to mark from which project that issue is coming from - if this field won't be used in the future, you can drop it later. But if anyone asks for a custom query/board/dashboard, this one may be useful
  • The attachments are the riskier part of the export/import procedure. Be sure to validate they were imported correctly

Regards and success !!

1 vote
Answer accepted

I need a little more background before providing a proper answer for you but I’ll give it a shot. 🤓

Is the source instance server, cloud, or data center? You state that both are cloud but I didn’t want to assume you’re migrating cloud-cloud without clarification.

If both instances are cloud and you can hold off for a bit, I believe Atlassian plans to release their cloud-to-cloud migration tool this quarter. But the roadmap could change and it may not get released until next year. So be sure to follow up on the roadmap.  

If it can’t wait and both are cloud instances, then you’ll have to make a “server” backup of your cloud instance and pull it down into a server version of Jira. Once the server instance is operational, you’ll need to restore the backup you took in the cloud to this server instance. Then using the migration tool, you’ll be able to select the desired project(s) and migrate to the desired instance(s).

If the source instance is server or data center, then you should be able to simply install the migration assistant and migrate them as I describe at the end of the previous paragraph.

Now, if you only care about the issues and not the project and it’s configuration, then you can export the desired issues to a csv file and then import them into the target instance.

Please note that this approach will not migrate attachments nor the issue history and may break links in the tickets—-unlike the other methods described above.

Let me know if you need further clarification. 

Sorry that i was not clear.  Both instances are cloud.   

Thank you for your help!  I'll be paying attention to the status of the cloud-to-cloud migration too.

Have a good day!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events