Migration to Atlassian Cloud is too slow

Question

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.

BR

Abhishek

Walter Buggenhout · Answer

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!

Jehan Bhathena · Answer

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.