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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi All,
For a customer I'm assessing the migration complexity to cloud of his environment. On the support pages I have found a lot of information about Jira+Confluence migration and in what order to execute. I haven't found yet in what order/sequence to execute a Jira+Bitbucket to cloud, hopefully you can give me some advise.
In the customer environment there is Jira+Bitbucket server products and we would like to migrate them to the cloud, which one should be migrated first, or should I take care of intermediate steps when migrating these products to cloud?
Thanks!
It does not really matter which way around you do these two. It's the same amount of work either way.
Thanks @Nic Brough -Adaptavist- ! One question to double check my approach;
In the meanwhile I was checking with my peers and one stated that it is important to first migrate Bitbucket to Cloud, otherwise the link between Jira and Bitbucket would disappear if you would do Jira first. Any comment on that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are going to have problems with links whichever way around you do it.
We have done hundreds of migrations of migrations to Cloud and when it is not massive, had no problems doing one or the other first.
(blatant plug for my employer, of course)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- thank you! Any advice on preventing problems with linking, or just accept and resolve after migration?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nothing specific, just build the "accept and resolve" into your migration plan. One minor thing that makes it a little easier is to change the application links at the beginning of the migration rather than after it.
On the Jira side, you might also want to find potential problems before you migrate. It's easy enough if you have database access - you can read the tables customfieldvalue, jiraissue and jiraaction (they hold the text of text and URL custom fields, the environment and description fields, and the comments, respectively, so searching them for your bitbucket URL might be useful, in case people have put links in instead of using the application link)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.