Last time we left at the crossroads of trying to decide between Jira Cloud vs Jira Data Center.
As we had already done significant investigation, (a proof of concept and user testing for Jira Data Center) we needed to shift gears and perform an initial investigation into the effort involved in moving to Jira Cloud. Was it worth the effort to scrap our current migration strategy and start over from scratch, or had we gone too far down the path with Data Center to give up on that now?
Is Cloud the best option for us?
After doing some research, comparing costs, looking at the pros and cons, and getting an idea of the difficulty/effort involved in performing a Cloud Migration vs a Data Center migration, we concluded that Cloud seemed like the better choice for us.
As I had mentioned in my previous article this was also the same conclusion/recommendation that I received from the Atlassian experts at the 2019 Summit, so we felt confident about this plan.
Oh No! Not another roadblock!
I took this to our decision makers, and we didn't get very far into presenting our findings before concerns were raised about data residency. The company I work for is a Canadian SaaS company and we needed to be sure that our policies would allow us to have our Jira data hosted outside of Canada. Apart from those concerns, everyone we presented to still agreed that Cloud looked like the better option if the data residency concerns could be resolved. It took several weeks for our governance team to evaluate any customer impact of Jira data residing outside of Canada. With this uncertainty, doubt began to set in about our future in the Cloud.
However, just when we were on the verge of giving up hope, we received the green light from our governance team to plan our move to Jira Cloud!
We're moving to the Cloud! How do we get there?
We have our decision! Now we just needed to figure out how we’re going to get there.
My first task was to find information gathering. I found several great resources on the Atlassian Community, articles others had written, Official documentation from Atlassian, as well as questions others had asked with helpful accepted answers. We know that we have a very large project ahead of us, but we have started leveraging a Trello board to break this large project down into smaller, more manageable tasks. When you look at the project from this view it doesn't feel quite so large anymore.
A sample of some of the items that we know we are going to have to tackle:
Stay tuned until next time!
Obviously, we aren't finished. I plan to write a final installment of this series where I will talk about how our production migration process went, and what things we learned during the migration, both in testing and production. I will also comment on what things we found extremely helpful in making this successful, as well as what things we wish we had more information about, or were aware of earlier in the migration process if any issue came up.
Jimmy SeddonCommunity Leader
Edit Nov. 6, 2020: Thank you for all your feedback. We’ve summarized and addressed your top concerns and questions on this thread. --- If you haven’t already read our recent announceme...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events