Atlassian Data Center End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Atlassian Data Center versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| End of Sale — New Customers | Data Center | Jan 1, 2016 | Mar 30, 2026 | 107 days past EOL | EOL |
| End of Sale — Existing Customers | Data Center | Jan 1, 2016 | Mar 30, 2028 | 624 days remaining | Active |
| Data Center Support (Jira, Confluence) LTS | Data Center | Jan 1, 2016 | Mar 28, 2029 | 987 days remaining | Active |
Atlassian Data Center lifecycle status — the real story
Atlassian has now retired all three of its self-managed licensing tiers in sequence. Server reached end of life February 15, 2024 — no further security patches for any Server product. Data Center is now on the same clock: new-customer sales ended March 30, 2026; existing customers can still renew or expand Data Center and Marketplace app licenses through March 30, 2028; and on March 28, 2029, all Data Center licenses expire and the software switches to read-only — installations keep running but stop receiving updates, and stop functioning as licensed software once the license check fails.
The three licensing models are easy to conflate but behave very differently at end of life: Server is already fully unsupported; Data Center is self-hosted but time-boxed to the 2029 date above, with Atlassian committing to technical support and critical-severity security fixes only through that date; Cloud is Atlassian's actively developed, indefinitely supported product and the only tier with no published end date. Atlassian's own guidance is unambiguous: migrate to Cloud, and Data Center exists mainly as a bridge for organizations with hosting, compliance, or data-residency requirements Cloud can't yet meet.
One notable exception: Bitbucket Data Center will not reach end of life on the 2029 date — Atlassian is instead offering existing Bitbucket Data Center customers a hybrid license covering both Data Center and Cloud, so treat Bitbucket separately from Jira and Confluence Data Center when assessing exposure. As with any vendor's published EOL policy, dates and program details (the hybrid-license terms in particular) can be refined before they take effect — the practical takeaway for any organization still on Data Center is that the runway is now fixed in years, not indefinite, and migration planning should start well before the 2028 renewal cutoff, not the 2029 expiry.
What does Atlassian Data Center end of life mean for your organization?
When a version of Atlassian Data Center reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Atlassian Data Center should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Atlassian Data Center versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Atlassian Data Center has 1 version past end of life — security patches have stopped, but CVE disclosures haven't. Tell us where to reach you and we'll match you with vetted extended-support providers for your stack. Free, no obligation.