Next month, February 2024, brings the end of support for all Atlassian Server products. Now is the final countdown to ensure your Server departure plan is in motion.
With the support deadline looming, and worries about security, data compliance, and performance on many organisations' minds, it's not too late to discuss your options with our migration experts.
As experts in Atlassian tools, Cloud and Data Center deployments, and Marketplace Apps, our team is well-placed to offer advice and migration support that is right for the needs and goals of your business.
We’ve prepared some frequently asked questions to help guide your Server end of life decisions:
How long does it take to migrate from Server?
Many factors affect how long it takes to migrate. When deciding on your approach, your key requirements and future goals should be considered alongside the risks of being on unsupported software.
There are many ways to minimise risk while allowing breathing space to align your tools with your longer-term objectives.
For many, Atlassian Cloud is the final destination. Whether this means a hybrid cloud-and-on-prem approach in the shorter term or a phased migration to Cloud with only essential projects and processes moved in line with Server support ending, every organisation's needs are unique.
While moving to a single-node Data Center deployment is often the quickest and simplest approach, Data Center licences come with an increase in cost vs Atlassian Server products – and in this case, you'd be getting a very similar experience to your current Server deployment. In the longer term, with a multi-node set up, there are some great benefits from being on Data Center, which are ideal for some businesses. Plus, for those organisations with specific data residency and flexibility needs, Cloud may not be the right choice in its current state.
If Cloud is your goal, a start-fresh approach may be the right answer. This means setting up new instances on Atlassian Cloud products and beginning all future projects on your new set-up. You can set your old instances to read-only so information is still accessible, but historical projects are not within your new set-up. This option is great for those looking to clean up their dirty Jira and Confluence spaces, allowing best practices to be implemented from the start.
On top of the deployment, factors like how much data you’re moving over, the complexity of your set-up, and the add-ons you rely on all make a difference. These are just some of the variables that can affect your migration timeline, alongside your internal processes and ensuring your stakeholders keep the project on track.
What are the options for moving from Atlassian Server?
Migrate to Atlassian Cloud
Move your Server data to Cloud, either as a complete migration or partial move that gets you off Server but might not have everything you need on day one – allowing for flexibility with the deadline.
Your migration timeframe, budget, and complexity will influence your approach for moving to the cloud and what you take with you initially.
Migrate to Atlassian Data Center
Moving to a single-node Data Center set up gives you the benefit of a faster and likely smoother migration. However, moving to a multi-node gives you all the benefits of Data Center.
Consider whether you plan to stay on-premise long-term or whether you’re using it as a stepping stone on your journey to Cloud.
Our managed services, helping with daily tool administration, infrastructure management and public cloud hosting, can provide an easier transition to Data Center – allowing your teams to focus on long-term strategy, not tool management.
Start fresh on Cloud or Data Center
If moving your existing data is not essential, or you’re happy with some manual work recreating your current set-up, then starting fresh might be a good option. You’ll purchase new licences and start your instances from scratch.
The benefit is being able to follow best practices from the start and set up a new clean tool for your users. But if there’s anything you want from your existing tools then there’s work involved in reestablishing your platforms.
Explore other options
Review your Atlassian set-up. Does it fit the long-term goals of your organisation, and what requirements do your teams have for your tools? Other options like GitLab or monday.com could provide the right fit for different department needs.
Can we stay on Server and not migrate?
Yes, but it is definitely not recommended. The problem with using unsupported software is bigger than not getting new updates or bug fixes. Security issues are one of the main concerns and could mean your data is compromised – which could cost you even more in the long run.
How can we prepare for our migration?
Understand your current set-up, perform housekeeping activities and clean up your instances so you’re ready to only take essential data over to your new platform.
Create a thorough migration strategy and plan to ensure your move is kept on track and continues to meet business requirements.
Ensure all major stakeholders are informed and available to provide information and help during your migration.
Talk to our migration experts to explore the options that fit best with the needs of your organisation.
What about migrating my apps?
There are often significant differences between on-prem apps and their Cloud counterparts. This is because Atlassian Cloud infrastructure is different to the on-premise infrastructure – these key differences in access points and technologies on Atlassian Cloud mean that features have to be built in different ways. Unfortunately, it isn’t as simple as mimicking what has already been created for on-premise.
Adaptavist and other app creators are working closely with Atlassian to deliver outstanding features, but if you rely heavily on apps, these differences are worth understanding.
Have other questions or want to discuss your options?
Speak to our migration team