Why These Dates Are Non-Negotiable
Atlassian's Data Center end-of-life programme is structural, not commercial. Unlike a typical software vendor EOL announcement that is sometimes extended or softened under customer pressure, these dates reflect Atlassian's fundamental strategic commitment to being a cloud-first company. Atlassian has been explicit in public communications — including its 2025 Ascend announcement — that the Data Center product line will not continue beyond 2029. The three milestone dates are published on Atlassian's official licensing pages and have been communicated consistently across partner channels.
For enterprise teams managing Jira, Confluence, Bitbucket, Bamboo, or other Atlassian Data Center products, these dates are operational deadlines, not aspirational targets. Missing them — or arriving at migration unprepared — means either operating on unsupported, non-updateable software after March 2029, or undertaking an emergency migration under time pressure that costs significantly more than a planned migration. Understanding exactly what each date means is the first step in avoiding both outcomes.
For the full context of what the Data Center EOL means commercially and contractually, see our comprehensive Atlassian Data Center end-of-life and migration guide and our dedicated page on Atlassian Data Center end of life.
The Three Critical Milestones
Atlassian stopped selling new Data Center subscriptions to new customers as of March 30, 2026. This milestone has already passed. The consequence: no organisation that does not already have an active Data Center subscription can acquire one. Existing customers retain their subscriptions and can renew them, but the installed base is now closed. No new entrants. If you are reading this as an organisation that has been evaluating a DC deployment, that option is gone.
The practical impact for existing customers: this milestone creates a clean line between organisations that have managed Atlassian relationships with active DC entitlements (and have the right to continue renewing until 2028) and organisations that do not. It also marks the formal beginning of Atlassian's end-state — from this point, the DC product line is in managed decline.
Importantly, Atlassian also stopped selling multi-year Data Center renewals in 2025. Existing DC customers can only renew on an annual basis going forward. This removes the option to lock pricing over multiple years that had previously been available, and it means annual renewal conversations will increasingly carry the cloud migration conversation as a parallel track.
From March 30, 2028, existing Data Center customers can no longer purchase expansions to their existing licences. This means no user count increases, no new product additions (adding Confluence DC if you only have Jira DC), and no new Marketplace app licences associated with Data Center. The consequence is that the Data Center estate is effectively frozen at its 2028 size.
This milestone creates a hard planning horizon for organisations that are growing. If your user base is expanding — through organic growth, acquisitions, or headcount increases — you need to be on Atlassian Cloud before March 2028 to add those users to your Atlassian tooling. An organisation that reaches this milestone still on Data Center with a growing headcount faces an immediate operational problem: it cannot licence the additional users it needs.
For organisations with significant Marketplace app dependency — custom integrations, third-party apps critical to engineering or operations workflows — March 2028 is also the deadline for completing or confirming cloud-compatible alternatives. Atlassian Marketplace app vendors have been migrating to cloud-compatible versions, but not all have done so. Apps with no cloud version represent migration blockers that need to be identified and resolved before 2028.
March 28, 2029 is the hard end-of-life date. All Atlassian Data Center product licences and associated Marketplace app licences expire. Products move to read-only mode — data remains accessible but the environment can no longer be modified, updated, or administered. Atlassian will provide no technical support, no security updates, and no compatibility maintenance after this date.
The implications are serious for any organisation still operating Data Center after this date. A read-only ITSM environment means no new tickets, no workflow changes, no integration updates. A read-only Confluence means no new pages, no content updates. From an information security standpoint, running unsupported software without security updates in a production environment creates compliance exposure — particularly for organisations in regulated industries subject to SOC 2, ISO 27001, or sector-specific frameworks. Most compliance frameworks require that production systems receive timely security patches; Atlassian will not be providing them for Data Center after March 2029.
What These Dates Mean for Your Migration Planning
A realistic cloud migration timeline for a large enterprise Atlassian deployment is twelve to eighteen months from the moment execution begins — and that assumes planning and discovery work has already been completed. Organisations that have not started planning are already operating with a constrained timeline. Here is how the migration phases map against the remaining EOL runway.
| Phase | Activity | Typical Duration | Must Complete By |
|---|---|---|---|
| Discovery | Inventory projects, spaces, users, Marketplace apps, integrations | 4–8 weeks | Q3 2026 |
| Cloud readiness | App compatibility, data residency, SSO/LDAP, compliance review | 8–16 weeks | Q4 2026 |
| Pilot migration | Migrate a non-critical project/space to Cloud, validate tools and process | 4–8 weeks | Q1 2027 |
| Wave execution | Migrate production projects/spaces in waves; validate each before next | 6–18 months | H1 2028 |
| DC decommission | Validate data, confirm no residual DC dependency, switch off DC environment | 4–8 weeks | Q3 2028 |
Organisations that have not completed a discovery exercise by mid-2026 are at risk of hitting the March 2028 expansion freeze before their migration is complete — a scenario that forces them to either accelerate the migration on a compressed timeline (at significantly higher cost) or operate with a frozen Data Center estate that cannot grow. The window is narrower than it appears. For detailed migration planning guidance, our Atlassian cloud migration guide 2026 covers the full methodology.
Dual Licensing: The Bridge Provision
Atlassian introduced a dual licensing programme to support organisations that need to run Cloud and Data Center environments in parallel during migration. Under dual licensing, an organisation with an active DC subscription can run an equivalent Cloud instance simultaneously — both environments fully functional — without paying the full licence cost for both. This provision exists specifically to enable a migration that can be validated before cutting over, rather than requiring a hard switchover on a fixed date.
The dual licensing programme is not indefinite — it is available during the migration period. Organisations should engage their Atlassian account team or channel partner to activate dual licensing as part of the migration programme, not as a long-term cost reduction strategy. Using dual licensing to delay migration rather than to facilitate it will result in the organisation being in a worse position as the 2028 and 2029 deadlines approach. For the contractual mechanics of dual licensing and how it interacts with annual renewal pricing, our Atlassian cloud contract negotiation guide covers the relevant provisions.
Rovo AI and the Cloud Pricing Context
Atlassian's cloud pricing model has shifted materially in 2026 with the integration of Rovo AI into base cloud subscriptions. Rovo — Atlassian's AI platform covering search, chat, agents, and automation — is now embedded into Premium and Enterprise cloud tiers, with Standard inclusion scheduled for later in 2026. The previous model, where Rovo was a $20 per user per month add-on, has been replaced with an integrated pricing approach.
This is commercially relevant for Data Center customers assessing migration economics for two reasons. First, the effective per-user cost of Atlassian Cloud has changed, and migration cost models built before early 2026 should be recalculated. Second, the Rovo capability embedded in Cloud has no Data Center equivalent — DC customers do not have access to Atlassian's AI features regardless of their subscription tier. This creates a genuine capability gap that grows with each Rovo capability release, and it is one of the most concrete arguments for accelerating migration that Atlassian makes to its own account teams.
For enterprise buyers, the Rovo integration also changes the negotiation dynamics for cloud contract terms. When negotiating the Cloud contract, the inclusion of Rovo in base tiers is a valuable provision — but it should be paired with robust commercial protections: annual price increase caps, multi-year commitment terms that include Rovo explicitly, and clarity on what happens to Rovo pricing if it is ever separated from the base subscription again. Our Atlassian pricing changes 2026 guide covers the full commercial landscape.
Isolated Cloud: The Option for Regulated Industries
One of the most significant developments for regulated industry Data Center customers is Atlassian's announcement of Isolated Cloud — a dedicated, single-tenant cloud deployment model targeting financial services, defence, and other highly regulated sectors. Isolated Cloud is scheduled for broader availability in 2026, and it directly addresses the primary objection that has kept many regulated-sector enterprises on Data Center: data sovereignty and workload isolation requirements.
For organisations in regulated industries that have held back on cloud migration due to FedRAMP, DISA IL, or equivalent requirements, Isolated Cloud deserves serious evaluation in 2026. If the isolation and compliance posture meets requirements, migrating to Isolated Cloud rather than traditional Data Center renewal is the path that preserves Atlassian functionality through and beyond the 2029 deadline while satisfying the regulatory requirements that precluded standard Cloud. Confirm the specific compliance certifications and data residency provisions with Atlassian directly, and factor Isolated Cloud economics into your migration TCO model.
What to Do Now: The Enterprise Action List
If your organisation is still operating Atlassian Data Center products, the following actions should be completed in 2026 regardless of where you are in the migration planning cycle:
- Confirm your current DC subscription renewal date — annual renewal is now the only available option. Know your next renewal date and ensure you have adequate runway to negotiate cloud transition terms at renewal rather than being forced into a renewal continuation.
- Complete a Marketplace app compatibility audit — identify every third-party app in your DC environment, confirm whether a cloud-compatible version exists, and flag any apps with no cloud equivalent as migration blockers requiring vendor escalation or replacement.
- Quantify your user count trajectory through 2028 — if you expect headcount growth that will require user licence increases, model whether that growth exceeds the March 2028 expansion freeze threshold.
- Evaluate Isolated Cloud eligibility if you are in a regulated industry — confirm data residency, certification, and isolation requirements against what Isolated Cloud offers in 2026.
- Activate dual licensing to begin a parallel Cloud pilot environment — this costs nothing additional under the programme and removes the risk of a hard-cut migration.
- Negotiate your Cloud migration contract before your DC renewal — using the DC renewal as leverage in the Cloud contract negotiation is the most effective way to extract commercial concessions. The closer you are to the 2028 freeze date, the less leverage you have.
Need independent guidance on Atlassian Data Center migration timing and cloud contract terms?
Our Atlassian advisory specialists help enterprises plan the migration, negotiate the cloud contract, and avoid the commercial traps in the transition — buyer-side only.The Data Center EOL timeline is the most consequential commercial and operational event in the Atlassian ecosystem in a decade. Understanding the exact milestones — and what each one means for your specific deployment — is the prerequisite to managing it effectively. For the full migration strategy, cloud contract negotiation guidance, and commercial framework, our complete Atlassian Data Center EOL and migration guide provides everything enterprise teams need. For Atlassian Cloud pricing, negotiation levers, and what changed in 2026, the Atlassian pricing changes guide is essential reading. Subscribe to our enterprise licensing newsletter for quarterly updates on Atlassian's EOL programme, and contact us to discuss your specific migration situation in confidence.