Lessons Learned From Jira Admin Confessions

We’re just going to address the elephant in the room and say that we know that everyone is thinking about migrations as of late. You have probably already had several conversations with colleagues and co-workers about what’s next for your Atlassian instance(s), questioning what’s the best path forward and wondering how your migration journey will take shape.

You have also probably been looking for any tips that you can find and researching all things migration. In an effort to put together the best advice and first-hand experiences with Jira and Confluence migrations, we invited Atlassian Admins to share their admin-gone-wrong stories and any advice they might have for people starting on their migration journey. Thank you to everyone who took valuable time out of their day to send in their submissions. We learned so much when reading through everyone’s answers and wanted to share some of the key takeaways:

Migration Plan Proper Preparation

This is a BIG one. If you put in the time and effort to properly plan your Atlassian migration, you will see those efforts come to fruition during and after your migration. Build a solid strategy that lays out the exact steps you will follow to achieve a successful outcome. Take the time to audit your infrastructure, applications, people, and process, and then make a list of all possible migration scenarios. Ensure that you have adequate resources with the right technical expertise that can get you through every step and roadblock of the migration process.

“Allow plenty of time for multiple trial runs to staging environments.”

— Atlassian Solutions Architect

“Have a way back out if something goes wrong. You don’t want to be halfway through a migration, have something go catastrophically wrong, and have no way to get back up and running.”

— Sr. Atlassian Engineer

“Make sure to evaluate all of your Apps (availability as well as how/if data migrates)”

— Sr. Atlassian Engineer

Overestimate Costs for the Migration Journey

Much more than just a “lift-and-shift”, moving data is a time-consuming process, and this is one area where companies find themselves in trouble. They underestimate the man-hours involved with a cloud migration and the investment needed to ensure that you have the right technical expertise. In fact, fewer than 40% of companies were able to meet or exceed their targets for controlling costs and migrating to cloud, according to a report from Forrester. All of these missed targets with time, costs, and expertise add up to drastically impact the outcome of your migration.

“I underestimated the amount of time and testing that needs to be considered just for Apps and their data. Also, the efforts needed to research and confirm Apps that were Server ready but not necessarily Data Center or Cloud confirmed.”

— Atlassian Engineer

Test! Test! Test!

Another key to a successful migration is rigorous testing, a step that many decision-makers overlook. When you are migrating to Cloud without the proper testing, your instance is susceptible to various issues on import, data loss that you may not notice till after the fact, and broken integrations. The more testing you do, the more opportunities you have to resolve errors or issues before your new environment is up and running.

“We were impatient and didn’t do as many trial runs as I should have for our Atlassian Cloud migration. We were anxious to start taking advantage of the benefits of cloud, but this backfired on us since we had to go back, do re-works and deal with many more unexpected surprises than we had anticipated. This ended up costing us more time and resources in the end.”

— Director of DevOps Tools

Seek Support From an Atlassian Solution Partner

As we have mentioned a handful of times, make sure that you are equipped with the right resources. This includes finding a solution partner who understands the highly-complex migration process along with the intricacies of how the Atlassian tools operate within your organization. Having the right partner for your migration process will pay off tenfold in the long-run. Waiting to put the proper resources in place mid-migration journey (versus making that investment upfront) will cost you more in the long-run and will cause you an even bigger headache.

“Don’t try to pull this off alone. Select an Atlassian partner that has experience with your type of migration (size and complexity).”

— Atlassian Solutions Architect

Atlas Authority Migration Services

There is no one-size-fits-all with migrations. Every organization has unique business requirements, complexities, and its intrinsic way of using Atlassian’s robust products to power their operations. Migrating your Atlassian instance is a high-stakes journey, and Atlas Authority is here to serve as your support team in successfully getting you across the finish line. With our proven methodologies and extensive experience in the Atlassian ecosystem, we have you covered through every step of the migration process and are prepared to address any pain points that you have. Contact us and leave the intricacies and the nuances of your migration to our team so that we can make your migration journey as smooth and seamless as possible.

Share This