Atlassian Ascend (Data Center EOL)
And what it means for Communardo Products customers
Earlier this week Atlassain made the announcement of launching Atlassian Ascend - basically announcing the end of life for Atlassian Data Center in 2029, which leaves Cloud as the only hosting platform for Atlassian's customers. While this came as a surprise for many - we expected this to happen. I want to take a moment to outline what this step means to our customers and how you can prepare best for the upcoming 3.5 years.
What is chaining for our customers?
Not a lot. Over the past two to four years, we successfully transformed our portfolio of Apps to the Atlassian Cloud. We are now ensuring our apps are Forge and Runs on Atlassian compliant.
This effort laid the groundwork for hundreds of successful Cloud migrations. Our products now solve business-critical tasks for customers on Cloud, rather than Data Center. Using the Confluence and Jira Cloud Migration Assistants simplifies the migration process even further.
We are continuing that path, providing our customers with the best possible solutions on the Atlassian Cloud platform. If you are still on Data Center you can rest assured, we will support you until the end of the timeline that is published by Atlassian.
What else is important to be aware of?
In the tech business and for Cloud apps in particular, trust is key. That’s why Communardo Products has invested in ISO 27001 certification years ago. Additionally, we just kicked of the process of becoming SOC 2 Type II compliant. On top of that we offer best in class Support and our Migration Hub is the central place for all migrating customers. If you need additional support during the migration phase we’re here to help and are also working closely together with Atlassian Solution Partners across the world, please reach out if you need any suggestion.
About Bitbucket and Apps for Bitbucket Data Center…
Things are slightly different here. Atlassians current messaging implies that Bitbucket Data Center will stick around for longer, although the licensing model will change to incorporate a Dual Licensing scenario. We’re waiting for more information but until than feel free to reach out with specific questions!
Thank you,
David Toussaint
CRO/CPO