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
Hi Folks 👋
As you may have heard, Atlassian Server products are coming to their End of Life in February 2024. We are gradually seeing more and more organizations start to consider their options:
In these next few paragraphs, I'll explain the importance of why you should start working on decision-making and migration now, not later. You'll see that delaying the process isn't beneficial for customers and partners alike. So, before we dive in, ask yourself what's holding you back at the moment?
One of the first steps that Atlassian advises in their process for moving to the cloud is to ask the question: Has your organization made the decision to move to Cloud? Decision-making takes time. We have seen that making a decision to go to the Cloud for any organization is a process in itself – and can take a significant amount of time to complete.
Some organizations have embraced a “Cloud-first” strategy – at least in principle. But even in that situation, the decision to move to the Atlassian Cloud can take time. “Cloud-first”, for some organizations, may mean that they prefer moving all of their applications to one type of Cloud solution, such as Azure, Google or Amazon. Atlassian products are hosted within AWS, so this might not match up with your company’s or SISO team’s preference. Having the proper conversation with the right people, and making the decision, is a process that needs to happen sooner rather than later – so that you can decide on the best option for your company’s Cloud strategy.
Other organizations might be bound by compliance or other factors that may lead them to consider that Cloud is not an option for them. For these organizations, the decision-making will also take time, because there may be different considerations to take into account during the process. Legislation is also evolving – so maybe Cloud is an option after all. In short – evaluating your options takes time.
Over the past few years, we have discovered that Cloud migrations take time. I'd like to pause here, just for a moment, to focus on the technical elements of a migration. A typical Cloud migration, from start to finish, may take up to 6-9 months. This is the time required, from the initial decision-making on whether to move to the Cloud (or not), right up to the point when your organization has finished the migration and is ready to use the Atlassian Cloud.
After making the decision to move to the Cloud, preparation has to take place and raises further questions: How are we going to move to the Cloud?
Will it be accomplished as a “Lift & Shift“, or will we use the opportunity to ‘clean house’ and optimize our current Atlassian instances before moving to the Cloud or Data Center? In the preparation phase, decisions also have to be made on how to move to the Cloud as a technical exercise. This typically involves an Atlassian Partner which can be found via Atlassian's Partner Directory. There are also considerations around the usage of apps or add-ons which have to be taken into account.
Lift and Shift = If you want to keep all your data – issues, attachments, and apps – then the “Lift and Shift” approach may be right for you. You’ll know this is the way to go if, after you’ve completed your audits (part of the Assessment phase), all of the data in your instance is useful and relevant to your current business, and your teams will continue to work on all your projects. More information on choosing the right strategy here.
These are all decisions that have to be made during the preparation phase. This takes time and involves both your business and IT stakeholders in the process. The actual migration itself normally only takes a fraction of the preparation time, as a general rule of thumb. But yes, preparation is key – and it takes time!
From a capacity point of view, everyone is in the same position and has the same or similar deadline: February 2024.
Some of you may even have shorter deadlines if renewals are coming up and you're not considering renewing your server products as a result of the decision to move to the Cloud. Either way, a migration requires effort from both Atlassian and Atlassian partners who will work alongside your own teams to make the migration a success. It may sound a little bit like an 🐘 elephant in the room, but both Atlassian and Atlassian partners only have a finite capacity at any given time. If the majority of organizations migrating to Cloud decide to move within the same timeframe, this could stretch the limits of capacity.
Both Atlassian and Atlassian partners are committed to meeting the highest quality of service expected. You can even look to see if they've been acknowledged by Atlassian as specialized in Agile at Scale, ITSM and of course Cloud. It helps to indicate that they have the proven knowledge and experience to achieve the level of quality of service you need for your organization. And this is why I think starting on time, with a good migration plan, and the right partner, is paramount to success.
Not only will it spread the load for both Atlassian and its partners, but it will also ensure that you derive the best possible outcomes and quality of service for your organization.
This brings us back to the title of this article: the clock is ticking. So, consider starting the process sooner rather than later, even if it's just to instigate that first conversation, in order to make sure your organization can journey through their Cloud migration smoothly.
💭 Tell us, what's holding up your migration to the Cloud? There's a whole community ready to help you through your concerns and share their own experiences... let's keep talking and drop a message below 👇
Laura Holton _ACE Rotterdam_