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!


Migration to Atlassian Cloud is too slow

Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 19, 2023

Dear Team,

We are facing major issue in one of our ongoing Cloud Migration project due to ultra slow migration speed. The Jira instance data (including attachments) is in excess of 1.5 TB. The attachments were already uploaded in small batches but the project data migration through JCMA is taking a lot of times. To migrate 1500 projects it has taken approx. 3 weeks. Infra, network speed are optimal as per Atlassian's recommendations. We tried importing a blank project and that too took more than 2 hours. Seems like migration of project configurations is taking a lot of time. We are in touch with the migration team via MOVE ticket and their troubleshooting is in progress. 

Has anyone faced similar challenges during any of the migrations in the past. If yes how was it resolved ? Any help or guidance would be highly appreciated.



2 answers

4 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 19, 2023

Hi @abhishek_sharma03,

For cloud migrations in general, but definitely when it is at this size, you should work with Atlassian migration support and/or a solution partner. I know tools exist to help you migrate your attachments separately and before you migrate your actual product data ahead of time, which may already help you reduce downtime significantly when you are ready to migrate in production.

Seems you are already in touch with migration support and that is definitely the right path. I would suggest to have some patience to see what comes out of the troubleshooting exercise. Apart from that, it may also be a good idea to start considering:

  • if you really need to migrate everything from your old instance or if you can reduce scope;
  • if it is feasible to migrate your attachments separately before your actual migration;
  • how you might take a phased approach to your migration, in case it is not possible to migrate everything at once during your foreseen migration window

Hope this helps! 

2 votes
Jehan Bhathena
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 19, 2023

Hey @abhishek_sharma03 ,

In my experience, the migration depended on the Attachment size that was being migrated, and to be sure we had optimal results we performed the migration during off hours at times.

We also used a Backup setup where we moved selective projects and used that machine for migration since that machine could be dedicated to the migration efforts.

Since you mentioned 1.5TB of data I think the migration would go into Days, but not sure if going into 'weeks' is a known symptoms.

We broke our migration according to project activities and Attachment size to reduce the machine load and make the movement quicker, agreed this took more time but we had lesser failures and corrections to do after the migration.

Hope this helps.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events