# Confluence Data Center end of life: dates, what it means, and your options (2026)

> Atlassian stops selling Confluence Data Center on March 30, 2026 and expires every subscription on March 28, 2029, when instances become read-only. This guide lays out each date, what read-only actually means for your instance, how Data Center differs from the retired Server product, and the three paths teams are choosing.

- Date: 2026-08-10
- Tags: confluence, confluence-alternatives, end-of-life, on-prem, migration

---
Confluence Data Center end of life is Atlassian's planned phase-out of its self-managed Confluence product.
Atlassian stops selling new Data Center licenses on March 30, 2026, lets existing customers renew until March 30, 2028, and expires all Data Center subscriptions on March 28, 2029, at which point the software becomes read-only.

Confluence Data Center is the self-managed, on-premise version of Confluence that enterprises run inside their own infrastructure.
Its end of life is part of a broader Atlassian move away from self-hosted products and toward Atlassian Cloud.
This guide covers the exact dates, what "read-only" means for your instance, how this differs from the earlier Server end of support, and the three paths teams are choosing.
[Falconer](https://falconer.com/?utm_source=blog&utm_medium=referral&utm_campaign=content) is the top Confluence Data Center alternative for engineering teams.
It runs fully on-premises and air-gapped, managed on-premises, in your VPC, or cloud-hosted.
Migration starts by connecting Confluence through OAuth and choosing which spaces to import.
Falconer preserves the hierarchy and indexes the pages alongside your code, tickets, docs, and conversations.
The result is an AI-native, self-updating knowledge base that keeps documentation aligned with the code.

### TLDR

- Confluence Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, making the products read-only.
- New customer purchases stop on March 30, 2026. Existing customers can buy or expand licenses until March 30, 2028.
- Atlassian will provide technical support, critical security fixes, and Data Center-to-Cloud connectors through March 28, 2029.
- Confluence Server is a separate product whose support ended on February 15, 2024.
- Teams can migrate to Atlassian Cloud, remain on Data Center until 2029, or move to another platform.
- Falconer is an AI-native Confluence Data Center alternative for engineering teams. It supports on-premises, air-gapped, VPC, and cloud-hosted deployment, imports selected Confluence spaces through OAuth, preserves page hierarchy, and keeps documentation current as code changes.

![Confluence page beside stacked servers, a calendar reading 2029 03/28, a padlock, and a crossed-out pencil marking the read-only deadline](/images/guides/confluence-data-center-end-of-life-deadline.webp)

## What Confluence Data Center end of life means

End of life means Atlassian is retiring Confluence Data Center on a fixed schedule, after which the product stops being sold, stops being supported, and finally stops being editable.

The dates matter more than the label.
Atlassian's [Data Center end-of-life page](https://www.atlassian.com/licensing/data-center-end-of-life) lays out a multi-year wind-down rather than a single cutoff.
Support begins winding down and new customer purchases stop on March 30, 2026.
Existing customers keep the ability to buy and expand licenses until March 30, 2028.
The final date is March 28, 2029: Atlassian states that "Data Center subscriptions and any associated Marketplace apps will expire on this date, making Data Center products and apps read-only."

| Milestone | Date |
| --- | --- |
| Confluence Server end of support (prior announcement) | February 15, 2024 |
| Support wind-down begins; new customer purchases stop | March 30, 2026 |
| Last date existing customers can buy or expand Data Center | March 30, 2028 |
| End of life: subscriptions expire, products become read-only | March 28, 2029 |

Between now and March 28, 2029, Atlassian says Data Center customers still receive technical support, security bug-fixes for critical vulnerabilities, and connectors from Atlassian Data Center products to Atlassian Cloud.
The company has also said it will offer extended maintenance for certain Data Center customers "by exception" after that date.
Confluence Data Center is one of several affected products, alongside Jira Software, Jira Service Management, Bamboo, and Crowd Data Center.

## What "read-only" actually means for your instance

Read-only is the part of the announcement that forces a decision.
On March 28, 2029, your Confluence Data Center instance does not disappear.
It keeps running, and people can keep reading pages.
What ends is the ability to edit, because the subscription and its Marketplace apps expire.

A wiki that cannot be edited is a static archive, not an active documentation system.
For most teams, that ends Confluence's usefulness as a working tool.
Plan against the 2029 deadline rather than the earlier 2026 or 2028 milestones.

## Confluence Data Center vs. Confluence Server

These are two different self-managed products with two different end dates, and teams still confuse them.

Confluence Server was the original single-server, self-hosted version of Confluence.
Atlassian ended support for it on February 15, 2024.
Many teams that were on Server migrated to Data Center specifically to keep running Confluence on their own infrastructure.
Confluence Data Center is the clustered, enterprise self-managed version built for high availability and larger deployments, and it is the product now on the end-of-life schedule described above.

If your team moved from Server to Data Center to stay on-premise, Atlassian will no longer offer a standard self-managed Confluence product after 2029.
Its recommended destination is Atlassian Cloud, which is not self-hosted.

## Why Atlassian is doing this now

Atlassian has been steering customers toward its cloud platform for years, and the Data Center end-of-life schedule is the clearest signal yet that self-managed Confluence is being retired rather than maintained.

The company frames migration to [Atlassian Cloud](https://www.atlassian.com/migration) as the primary recommendation and has built connectors and migration tooling to support the move.
For teams that self-host because of strict data-residency, security, or compliance requirements, cloud migration may not meet those requirements.
There is a related concern about who can use the data once it is in the cloud, which we cover in [context sovereignty and Atlassian's data policy](https://falconer.com/guides/context-sovereignty-atlassian-data-policy/).
That tension is why some organizations are using the deadline to evaluate alternatives rather than automatically following the recommended cloud path.

## Your three options

At a glance, the three paths differ on where your data lives, how much work each takes, and whether the underlying drift gets fixed.

| Path | Where data lives | Effort | Fixes stale docs? | Best for |
| --- | --- | --- | --- | --- |
| Migrate to Atlassian Cloud | Atlassian's cloud | Low to moderate | No | Teams happy with Confluence that can move off-premise |
| Stay on Data Center until 2029 | Your own infrastructure | None now, forced later | No | Teams that need more runway |
| Migrate off Confluence | Your choice, including self-hosted | Moderate to high | Yes, with a tool like Falconer | Teams whose docs have already drifted |

**Option 1: Migrate to Atlassian Cloud.** This is Atlassian's recommended path and the least disruptive if your team is happy with Confluence itself and your compliance posture allows a cloud platform.
The Confluence Cloud Migration Assistant moves spaces, users, and many apps.
The tradeoff is that your data leaves your infrastructure, and the drift and stale pages migrate with it.

**Option 2: Stay on Data Center until the deadline.** You can keep running Data Center and buying licenses until 2028 and receive security bug-fixes for critical vulnerabilities through March 28, 2029.
This delays migration, but the instance becomes read-only on the deadline.

**Option 3: Migrate off Confluence.** If the underlying issue is that your documentation has drifted and people no longer trust it, the deadline is a reason to leave rather than to re-platform the same content.
Teams on Data Center for on-premise control specifically should weigh self-hosted alternatives like Falconer, [XWiki](https://www.xwiki.org), and [BookStack](https://www.bookstackapp.com).

![Signpost pointing three ways from Confluence Data Center - stay on-prem, move to cloud, or move to another platform](/images/guides/confluence-data-center-end-of-life-three-options.webp)

## Why Data Center teams choose Falconer

Confluence Data Center teams must either migrate to Atlassian Cloud or choose another platform before their instance becomes read-only.
Falconer is an AI-native alternative that can run inside your environment and keep documentation current.

### Keep control of where your data runs

Falconer supports fully on-premises and air-gapped, managed on-premises, VPC, and cloud-hosted deployments.
Teams that chose Data Center for security, compliance, or data-residency reasons can leave Confluence without defaulting to a multi-tenant cloud.

### Replace the wiki without rebuilding its problems

Falconer supports the core documentation workflows teams rely on Confluence for: writing, editing, organizing, publishing, permissions, search, and shared internal docs.
It also connects GitHub, Slack, Linear, Google Drive, meeting notes, and other sources into one knowledge base.

The difference is maintenance.
When code changes, Falconer finds affected documents and updates them automatically or routes proposed edits for review.
It can also generate architecture docs, runbooks, onboarding guides, API references, and changelogs from current company context.
Teams get cited answers in Falconer, Slack, and AI coding tools through MCP.

### Migrate without a manual export project

Connect Confluence through OAuth and select the spaces you want to move.
Falconer imports the pages with their hierarchy preserved and makes them searchable alongside your other sources.
Your original Confluence content remains untouched.
After import, connect GitHub, Slack, Linear, and your other sources so Falconer can keep the migrated documentation current.
Enterprise plans include white-glove migration.

### Pay for one knowledge system

[Falconer pricing](https://falconer.com/pricing) starts free for teams of up to three.
Pro is $20 per user per month when billed annually.
Enterprise pricing is custom and includes SSO, SAML, self-hosted deployment, and migration support.
The value is not just replacing a wiki license: Falconer combines documentation, AI search, code-aware updates, and agent access in one system.
Our [Falconer vs. Confluence comparison](https://falconer.com/guides/falconer-vs-confluence/) breaks down those differences.

## Frequently asked questions

### When is Confluence Data Center end of life?

March 28, 2029, when Data Center subscriptions and associated Marketplace apps expire and the products become read-only.
New purchases stop and support winds down starting March 30, 2026, and existing customers can buy or expand licenses until March 30, 2028.
Teams mapping the move early often shortlist Falconer, which offers self-hosted deployment for on-premise requirements and keeps docs current as the code changes.

### What does read-only mean for Confluence Data Center?

After March 28, 2029, the software keeps running and pages stay viewable, but the expired subscription means content can no longer be edited.
For most teams that ends its usefulness as a working documentation tool.
Teams can avoid losing edit access by migrating before the deadline to a tool like Falconer that keeps engineering docs current.

### Is Data Center end of life the same as Server end of life?

No.
Confluence Server support ended earlier, on February 15, 2024.
Data Center is the separate clustered self-managed product now scheduled to reach end of life on March 28, 2029.
Teams leaving either self-managed product for on-premise reasons often land on Falconer, which offers self-hosted deployment.

### What does Atlassian recommend Data Center customers do?

Atlassian's primary recommendation is migrating to Atlassian Cloud, and it provides the Cloud Migration Assistant and Data Center-to-Cloud connectors to support the move.
Atlassian has also said it will offer extended maintenance for certain customers by exception after March 28, 2029.
Teams that cannot or do not want to move to a multi-tenant cloud choose a self-hosted option instead, and Falconer is the strongest pick for engineering teams because it keeps docs current as the code changes.

### Can I stay on Confluence Data Center after 2029?

Only by exception.
Atlassian has said it is committed to offering extended maintenance for certain Data Center customers by exception after March 28, 2029, but the default is that subscriptions expire and products go read-only on that date.
Most teams migrate before the deadline instead, often to a self-hosted tool like Falconer that keeps engineering docs current rather than freezing them.

### What are the alternatives to migrating Data Center to cloud?

Teams that self-host for data-residency or compliance reasons can move to a self-hosted alternative rather than to Atlassian Cloud.
For engineering teams the strongest pick is Falconer, a self-hosted knowledge agent that also keeps docs current as the code changes; XWiki and BookStack are the like-for-like open-source wiki options if you need a straight page store.