Atlassian Is Ending Confluence Data Center: The Full Picture
Confluence Data Center end of life is no longer a distant possibility — it is a confirmed deadline. In September 2025, Atlassian announced the final end-of-life timeline for all Data Center products, including Confluence Data Center, Jira Data Center, Jira Service Management Data Center, Bamboo Data Center, Crowd Data Center, their associated mobile applications, and every Data Center Marketplace app. By March 28, 2029, all Data Center licenses will expire, and installations will enter a read-only state. For organizations that have relied on self-managed Confluence for years, possibly decades, this announcement demands immediate attention and a well-considered plan.
The one notable exception is Bitbucket Data Center, which will receive a hybrid license model rather than full discontinuation. Every other Data Center product, however, follows the same sunset trajectory. This article lays out the complete timeline, explains what it means in practice, identifies the risks of inaction, and presents the options available to your organization — including open-source alternatives like xWiki that restore the control and data sovereignty that many teams valued in the Data Center model.
The Complete End-of-Life Timeline
Atlassian has structured the Data Center end of life as a graduated process spanning roughly three and a half years. Understanding each milestone is essential for planning your transition, because certain options close permanently at each stage.
December 16, 2025: No New Data Center Marketplace App Submissions
As of this date, Atlassian's Marketplace no longer accepts new app submissions targeting the Data Center platform. Existing apps can still receive updates, but the ecosystem is effectively frozen in terms of new entrants. If you were hoping a new tool would solve a particular workflow gap on Data Center, that door has closed. This is the first signal that the Marketplace ecosystem around Data Center is being wound down deliberately, and it has direct implications for organizations that depend on third-party apps — a topic we explore in detail in our guide to Confluence Marketplace apps after Data Center EOL.
March 30, 2026: No New Data Center Subscriptions for New Customers
Starting March 30, 2026, organizations that do not already hold a Data Center subscription will be unable to purchase one. Atlassian is closing the front door. If your organization was considering a new Confluence Data Center deployment, or if a subsidiary or newly acquired business unit needs its own license, that option will no longer exist. Existing customers can still renew and expand, but the customer base is now capped.
March 30, 2028: No Expansion for Existing Customers
This is where the constraint tightens significantly. After March 30, 2028, even existing Data Center customers can no longer expand their licenses — no additional user tiers, no new product additions. Renewals of existing subscriptions are still permitted, but you are locked into your current footprint. For growing organizations, this means your Confluence Data Center environment cannot scale with you beyond whatever license tier you hold at that point.
March 28, 2029: All Data Center Licenses Expire
On this date, all Data Center licenses across every product — Confluence, Jira, JSM, Bamboo, Crowd — expire simultaneously. Installations transition to a read-only state. You can still access your data, but you cannot create, edit, or delete content. No new security patches will be issued. No technical support will be available. All Data Center Marketplace app licenses also expire on this date. Your Confluence instance becomes, in effect, an archive — one that grows increasingly vulnerable with every passing day.
Why Atlassian Is Making This Move
Atlassian's decision to sunset Data Center products is the culmination of a strategic shift that has been underway for several years. The company discontinued Server licenses in February 2024 and has been steering customers toward Atlassian Cloud ever since. The Data Center end of life extends that trajectory to its logical conclusion.
From Atlassian's perspective, consolidating on a single cloud platform simplifies their engineering and support operations, allowing them to focus investment on a unified product experience rather than maintaining parallel deployment models. Cloud delivery also enables Atlassian to roll out new capabilities more rapidly, including their AI-powered assistant, Rovo, which is designed exclusively for the cloud platform.
The commercial model shifts as well. Data Center licensing operates on annual subscriptions with user-tier pricing. Cloud subscriptions use per-user monthly pricing, which for many organizations at scale represents a significant cost increase — a reality we examine in our total cost of ownership comparison. Atlassian has framed the transition as enabling innovation and improved collaboration, and for some organizations the cloud platform will genuinely be the right fit. But the move is not without trade-offs, particularly for organizations with strict data residency, compliance, or customization requirements.
The Real Risks of Waiting
It is tempting to treat March 2029 as a distant deadline and defer planning to a later budget cycle. This is a mistake, and the risks compound the longer you wait.
Security Exposure
After the end-of-life date, Atlassian will not issue security patches for Confluence Data Center. Any vulnerability discovered after March 2029 — and vulnerabilities in widely-deployed enterprise software are discovered regularly — will remain unpatched. Confluence has historically been a target for exploitation, and running an unpatched instance connected to your network is a risk that most security teams and auditors will not accept. For organizations subject to NIS2 or DORA regulations, this alone may constitute a compliance violation.
Compliance Failures
The read-only state creates a particularly insidious compliance problem. Under GDPR and similar data protection regulations, organizations must be able to respond to data subject access requests and deletion requests. A read-only Confluence instance cannot delete personal data. You can still export or read it, but you cannot fulfill a right-to-erasure request within the system itself. This creates a gap that regulators take seriously, and the penalties for non-compliance are substantial.
Operational Degradation
Even before the final deadline, operational challenges will mount. As Marketplace apps stop receiving updates (many vendors will shift focus to cloud equivalents well before 2029), integrations will break. Compatibility with newer browsers, operating systems, and authentication providers will erode. Your IT team will spend increasing effort maintaining an environment that is actively decaying, diverting resources from productive work.
Marketplace App Cliff
All Data Center Marketplace apps expire on the same date as your Confluence license. This means every third-party tool your teams depend on — diagramming tools, workflow engines, reporting dashboards, compliance add-ons — stops working simultaneously. There is no gradual wind-down of the app ecosystem; it is a cliff edge. Planning for this requires a thorough inventory of your app dependencies, which we cover in our Marketplace apps after EOL guide.
Budget Compression
Organizations that delay their migration planning until 2028 will face compressed timelines and inflated costs. Migration services, whether to Atlassian Cloud or to an alternative platform, will be in high demand as the deadline approaches. Vendors and consultants will be capacity-constrained, and your negotiating position weakens when you are operating under urgency. Starting the planning process now, when you have the luxury of time for proper evaluation and phased execution, is both strategically and financially prudent.
Your Three Options
With the Data Center end of life confirmed, every organization running Confluence Data Center faces a decision. There are, broadly, three paths forward.
Option A: Migrate to Atlassian Cloud
This is the path Atlassian is actively promoting and has built migration tooling to support. For organizations with straightforward Confluence deployments, limited customization, and no data residency constraints that conflict with Atlassian's cloud regions, this can be the path of least resistance. Atlassian offers migration assistants, and the content and space structures translate directly.
However, Atlassian Cloud comes with trade-offs. Per-user pricing at scale can be significantly more expensive than Data Center licensing. Customization options are more limited. Data residency is constrained to Atlassian's available regions. And you remain on a vendor's platform — meaning future pricing changes, feature deprecations, or strategic shifts are outside your control.
Option B: Move to xWiki — Open-Source, Self-Hosted
For organizations that chose Confluence Data Center specifically because they valued self-hosting, data control, and customization, xWiki represents a natural successor. xWiki is an open-source enterprise wiki platform licensed under the LGPL, with a mature feature set that includes structured content, granular permissions, workflow automation, and an extension ecosystem of over 900 components.
xWiki provides a dedicated Confluence migration toolset — the Migrator Pro — that handles content, users, permissions, and macro conversion. Because xWiki is self-hosted (or hosted on managed infrastructure like MassiveGRID's xWiki hosting), you retain full control over your data, your deployment environment, and your upgrade timeline. There are no per-user license fees for the software itself, and the platform can be extended or customized without vendor gatekeeping. Our detailed comparison of xWiki and Confluence covers the feature and architectural differences in depth.
Option C: Do Nothing
This is not a viable option, but it is worth stating explicitly because organizational inertia is powerful. Doing nothing means operating an increasingly insecure, non-compliant, and degrading system until March 2029, at which point your Confluence environment becomes a read-only archive with no vendor support, no security patches, and no Marketplace app functionality. The cost of "doing nothing" is not zero — it is the accumulated risk and eventual emergency migration cost compressed into whatever timeline remains.
A Practical Planning Timeline
The window between now and March 2029 may seem generous, but enterprise migrations — particularly those involving years of accumulated content, complex permission structures, and deeply embedded workflows — require deliberate planning and phased execution. Here is a realistic timeline.
Q1–Q2 2026: Audit and Assess
Begin with a thorough inventory of your Confluence Data Center environment. Catalog your spaces, page counts, attachment volumes, user counts, and permission structures. Identify every Marketplace app in use and document what it does, who uses it, and whether alternatives exist. Assess your compliance obligations — which regulations apply, what data residency requirements you have, and what your security team requires from any replacement platform. This audit is the foundation for every subsequent decision.
Q3–Q4 2026: Evaluate and Pilot
With your audit complete, evaluate your options against your actual requirements. If you are considering Atlassian Cloud, run Atlassian's migration assessment tools and understand the cost implications at your user count. If you are evaluating xWiki, deploy a pilot instance — either self-hosted or on MassiveGRID's managed infrastructure — and test the migration of a representative space using the Migrator Pro. Involve your end users in the pilot; their feedback on the day-to-day experience is essential. This phase should produce a clear recommendation and a migration plan with resource estimates.
2027: Execute the Migration
With a chosen platform and a tested migration plan, 2027 is the year to execute. Plan for a phased migration — department by department or space by space — rather than a single high-risk cutover. Run the source and destination systems in parallel during each phase, allowing users to verify content and adjust to the new environment. Address macro conversions, rebuild integrations, and train your teams. A phased approach spreads the workload and reduces risk.
2028: Decommission and Clean Up
By 2028, your migration should be complete and your new platform established as the primary system. Use this year to decommission your Confluence Data Center environment, archive any remaining data per your retention policies, and close out the licensing. Having a full year of buffer before the March 2029 deadline provides safety margin for any complications and ensures you are not operating under deadline pressure.
Start the Conversation Now
The Confluence Data Center end of life is not a surprise — Atlassian has been signaling this direction for years. What it is, however, is a firm deadline that removes the option of indefinite deferral. The organizations that will navigate this transition most smoothly are the ones that start planning now, while all options remain open and timelines are comfortable rather than compressed.
Whether you ultimately choose Atlassian Cloud, xWiki, or another platform entirely, the first step is the same: understand what you have, understand what you need, and begin evaluating your options with clear criteria. If self-hosting, data sovereignty, and freedom from per-user licensing are important to your organization, we encourage you to explore xWiki on MassiveGRID as part of that evaluation. And if you need help thinking through the infrastructure side of any migration path, our team is available to discuss your requirements.
Frequently Asked Questions
When exactly does Confluence Data Center reach end of life?
All Confluence Data Center licenses expire on March 28, 2029. However, the wind-down begins much earlier: new customer subscriptions close on March 30, 2026, and license expansion for existing customers ends on March 30, 2028. After the final date, Confluence Data Center installations enter a read-only state with no further security patches or support.
What happens to my data after March 2029?
Your Confluence Data Center installation will enter a read-only mode. All existing content — pages, spaces, attachments, comments — remains accessible for reading and export, but you cannot create, edit, or delete any content. The data stays on your own servers since it is a self-hosted product, but the system is essentially frozen. This creates compliance challenges, particularly around GDPR right-to-erasure obligations.
Can I still use Confluence Data Center after the end-of-life date?
Technically, the software will still function in read-only mode on your servers. However, you will receive no security patches, no technical support, and no Marketplace app functionality. Running an unpatched enterprise application connected to your network introduces significant security risk and may violate compliance requirements for regulated industries.
What are the alternatives to Confluence Data Center?
The primary alternatives are Atlassian Cloud (Atlassian's recommended path), self-hosted open-source platforms like xWiki, and other commercial wiki or knowledge management platforms. The right choice depends on your requirements around data residency, budget, customization needs, and compliance obligations. Our xWiki vs Confluence comparison provides a detailed feature-by-feature analysis.
How long does a typical migration from Confluence take?
Migration timelines vary significantly based on the volume of content, complexity of permissions, number of Marketplace apps in use, and the degree of customization. A small team with a few hundred pages might complete a migration in days. A large enterprise with thousands of spaces, custom macros, and complex integrations should plan for three to twelve months, including pilot testing and parallel operation. Starting early gives you the luxury of a phased, low-risk approach.
Will Atlassian release security patches for Data Center after the end-of-life date?
No. Atlassian has stated that no security updates, bug fixes, or technical support will be provided for Data Center products after the end-of-life date. Any vulnerabilities discovered after March 28, 2029, will remain unpatched. This is consistent with Atlassian's handling of the earlier Server product end of life.
Is Atlassian forcing everyone to move to the cloud?
Atlassian has made cloud their sole supported deployment model going forward, with the exception of Bitbucket Data Center which receives a hybrid license. While Atlassian frames this as enabling faster innovation and better collaboration, the practical effect is that organizations must either adopt Atlassian Cloud or move to a different platform. For organizations that require self-hosted deployment, open-source platforms like xWiki provide a path that preserves that capability.
Can I renew my Data Center license before it expires?
Existing customers can renew their current Data Center subscriptions until the final expiration date of March 28, 2029. However, you cannot expand your license (add users or products) after March 30, 2028. Renewal only extends your access to the current license tier — it does not postpone the end-of-life date itself. All licenses, regardless of renewal timing, expire on March 28, 2029.
Written by MassiveGRID — As an official xWiki hosting partner, MassiveGRID provides managed xWiki hosting on high-availability infrastructure across data centers in Frankfurt, London, New York, and Singapore.