You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have been migrating small test Jira Projects to the cloud to learn how JCMA works and where there are gaps, e.g, missing issue icons, issue priorities. This has been very useful to do.
Now, I want to test run a full migration of our Jira server into the Sandbox. I'll be migrating ~44 projects and ~33,700 issues.
Has anyone run this sort of test? If so, any tips or lessons learned? How long did it take, etc.?
University of Washington
Hello @vthomas9 ,
Adding to Josh - we are Atlassian Solution Partners and we have migrated around 10 of our customers, so I can give you some points that came to my mind in regards of testing. Every instance is specific though.
There can be many more, just don't underestimate the testing and you'll be fine :) There are many helpful documentations on JCMA (Josh posted some of them), so these might be helpful.
Wow, thanks for this useful information! I've been reading the tons of migration docs that Atlassian provides; however, the docs are missing key practical info, such as, how to run test migrations.
I've migrated small test projects and have flushed out a few gaps. I tried migrating one of our more complex projects. This did not migrate correctly. The project contains about six Boards. JCMA migrated a subset of the project. I'm not sure why, but my hypothesis is that I have to migrate the full set of projects associated with the six Boards.
Josh from the Atlassian Cloud Migration Team here!
Glad to hear your tests have been beneficial so far. For your End-to-End test migration to the sandbox, I'd recommend clearing your cloud sandbox first and then (if applicable) copying any data from your production site to the sandbox. This is to make sure you have a solid replica in the test environment that would mirror your production migration.
Next, make sure you take a look through the Jira Pre-Migration Checklist and check out What Gets Migrated With JCMA. This is help ensure common migration errors/mistakes can be avoided and your team has an understanding what to expect in Jira after migration.
As every data shape and server environment is different, it is hard to give an exact number of how long the migration can run, but that is the goal of Testing! For this size of migration, I'd expect a few hours, or longer, for the Jira issues to migrate (that estimate can vary depending on apps, attachments, etc.).
If you run into any issues or have Planning questions, please don't hesitate to reach out to us!
Josh Harris | Cloud Migrations Manager
Hi @Josh Harris
Nice to meet you!
I've read through the migration docs and have created the following draft migration plan based on what I have read.
Does this plan make sense? Do you see anything that is missing?
Once I complete testing, I will add more details to this plan or runbook, as @Adam Rypel _MoroSystems_ mentioned.
I have a some questions listed below. Can you help answer them?
Hi @vthomas9 !
I'd recommend reaching out to the Cloud Migration Team through embedded link! Our team works through MOVE tickets and will be happy to address your questions and support your migration.
Hi @Josh Harris
Thanks for this info. We've been running test migrations.
We don't have a sandbox for our Confluence since we purchased Standard. We ran a full test of everything to the cloud. To prepare for our Prod cutover I will need to clear out our Cloud Confluence and all the users.
Q: How do I clear out Cloud Confluence Prod and the User list?