The End of an Era – Atlassian Pulls the Plug on Data Center

On 8 September 2025, Atlassian announced the end of life of their Data Center (DC) products, with full retirement by 28 March 2029.

Atlassian’s “cloud only” future is now non-negotiable – and every organisation still relying on Data Center needs to treat this as a strategic imperative, not just a technical migration.

What Atlassian Announced

Here are the milestones Atlassian published and what they mean:

Date	Milestone	What It Means
Dec 16, 2025	No new Data Center apps accepted	Innovation on DC halts. App vendors must pivot to Cloud.
Mar 30, 2026	End of new DC subscriptions for new customers	All new Atlassian deployments must start in Cloud.
Mar 30, 2028	End of license expansions + DC Marketplace apps	Last date for existing customers to purchase DC licenses, apps or expansions.
Mar 28, 2029	End of Life. Data Center goes read-only	DC becomes an archive. No new work.

Bitbucket Data Center will have a dual-license option, allowing Bitbucket DC and Bitbucket Cloud to run side by side.
Atlassian has also committed to extended maintenance past 2029 for some customers by exception (likely at higher cost).

Why Atlassian Is Doing This

Atlassian’s narrative:

• Innovation acceleration – focusing on one platform, Cloud, brings developer efficiencies.

• Scale & agility – advanced features are already Cloud-native.

• Ecosystem alignment – Marketplace apps pushed to Cloud only, forcing more on-platform monetization.

• Customer revenue momentum – finalise the move to recurring revenue for Atlassian’s shareholder benefit. The Atlassian ‘lock-in’ effect means that customers are unlikely to churn.

Quirk’s perspective: this move was inevitable. Atlassian has been nudging customers toward Cloud for years. However, assurances were given that Data Center would never be retired. Given the delays, extensions and generally poor project management of Server end of life, it will be worth following along at home to see if it runs smoother this time.

What This Means for You

1. Your DC environment becomes constrained

After 2028 you can’t expand users, add apps, or adjust licenses. Marketplace innovation also freezes.

2. Migration will be more complex than you think

Most DC instances have:

• Marketplace apps (not all with Cloud equivalents)

• Custom integrations and scripts

• Heavy workflow / permission customisation

• Regulatory and compliance dependencies

3. You can’t wait until the last moment

Late migrations (2028–29) risk capacity shortages with partners and Atlassian support.

4. Delaying will cost more

Extended maintenance past 2029 will come at a premium. Technical debt compounds.

5. It’s an opportunity

• Clean up clutter and legacy workflows

• Rationalise your app portfolio (prioritizing apps that have ‘Runs on Atlassan’ status)

• Re-architect integrations

• Adopt Cloud-native features and AI

Quirk’s Perspective

At Quirk, we believe this is a strategic transformation, not just a migration.

Our recommended steps

1. Run a discovery / audit phase – apps, integrations, workflows and jobs to be done before the dealine.

2. Prioritise migration paths – phase work by risk and importance.

3. Leverage Atlassian programs – take some time to understand the support that Atlassian and Partners are offering.

4. Build a change management plan early – don’t underestimate the time it takes to migrate data and test.

5. Talk to app vendors – ensure critical Cloud equivalents exist and if not, ask app vendors about their plans to build on Cloud..

6. Budget for contingencies – migrations always cost more than planned.

What Quirk Is Doing

We’re here to help with Migrations:

• Audits of software and workflows for DC customers

• Informed comparisons between DC and Cloud equivalents

• Engagement with Atlassian partners we can work with app developers on your behalf, or create custom workflow solutions

• Project management to plan early, reduce risk, and build a Cloud-ready architecture

Final Thoughts

Atlassian’s move to retire Data Center was inevitable – but not surprising. The real question is whether you migrate on your terms or get forced into a scramble closer to 2029.

The next few months are critical. Use them to assess, plan, and pilot.

If you’d like Quirk to help you run discovery, audit, build your roadmap, or pilot a migration, get in touch.