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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am Pushpkant, I am an Atlassian Consultant at Modus Create. I have helped numerous organisations successfully migrate to Atlassian Cloud. Last month, we migrated one of our clients from Data Center to Jira Cloud. It was a long journey for us where we had many rounds of discussion with the stakeholders explaining them the nietigirites of the migration and had to explain them the challenges in this activity. Since it was a large enterprise the complexity of the project was extreme. Here are more details:
Now to the good stuff…. (pick and choose here - these are prompts to get you started!)
Hi @Pushpkant Garg,
It's great to be aware of Cloud migration use cases.
Here you mention a couple of key apps, and my question is: Did you have to put aside any other app that didn't support the migration process, or did the cloud (or other apps in the cloud) fulfilled the necessities you have?
Thanks ahead for your response; I'm curious!
@Huwen Arnone There are many apps and both the scenarios are valid and encountered.
If I list a couple of major apps which need to have manual data migration
There are many apps which we discontinued after this migration. One of the major app is "Script Runner for Jira". The unavailability of behaviours on Cloud is a BIG turn off for this app. JWME is a good alternative to this plugin. There are many features of Scriptrunner is replaced by Automation for Jira.
There are many apps which are available on Server but not on Cloud. We have to leave them and look for alternate plugin or Custom solution to be configured.
Let me know if I have answered your queries.
This is very interesting and insightful. Thank you very much for taking the time to share this information 🙌👏🏼👏🏼
Xray was amongst the first Apps to be included in the Jira Cloud Migration Assistant.
And this method has been successfully used by many customers.
In case of any incident, please get in touch with Xray Support (http://xraysupport.getxray.app); we would gladly assist you.
Rogério Paiva [Xray Support Team]
Hi @Pushpkant Garg and thank you for sharing your journey! How long did the whole process (pre-migration -> migration -> testing) took? Did you keep a migration runbook?
Hello @Alex Koxaras _Relational_
Apologies for delayed response. Have been very busy lately with migration stuff.
There are multiple factors which determines the timeline of the project. It varies between 3 weeks to 3 months. Currently, I am working on a project which is running from last 4 months and we are going-live in Nov.
Hope this helps.
I'm interested in knowing more about the phased approach.
1. How did you group the data in phases? meaning which ones did you choose to migrate first? and last?
2. How did you handle the project dependencies? I can imagine for example projects like Service Desk has relationship with many other projects - how did you handle this?
3. How did the phased roll out happen? - were these specific projects made read only once migrated to cloud? did you freeze the server changes?
4. Did you have people having to use both cloud and server for a period of time?
5. Anything else you would like to share we need to consider for phased approach?
Thank you for sharing your experience. Hopefully we learn from you and not repeat same mistakes in our migration.