Atlassian will end all Jira Data Center products on March 28, 2029 at 23:59 PST, after which instances become read-only. The phase-out starts March 30, 2026, when new customers can no longer buy Data Center subscriptions; existing customers can keep renewing and expanding until March 30, 2028. Organizations should begin planning a migration to Jira Cloud now, since large environments typically take months to move.

If your organization runs Jira Software Data Center, Jira Service Management Data Center, or Confluence Data Center, Atlassian has already set a firm end date and started winding down the product line in phases. This guide covers the exact Jira Data Center end-of-life timeline, what triggers each deadline, and the realistic migration paths — cloud, hybrid, or a negotiated extension — available to Data Center customers today.

What Is Happening to the Jira Data Center?

Atlassian announced on September 8, 2025 that all Data Center products — including Jira Software, Jira Service Management, and Confluence — will reach end of life on March 28, 2029. After that date, Data Center subscriptions and their associated Marketplace apps expire and the software becomes read-only: existing data stays accessible, but no new issues, updates, or configuration changes can be made.

This isn't a sudden cutoff. Atlassian is winding down support in phases over roughly three years, starting March 30, 2026, specifically to give customers time to test and execute a migration before the final deadline. The company has stated it will continue providing technical support, security bug-fixes for critical vulnerabilities, and Data-Center-to-Cloud connectors through the full transition window, up to March 28, 2029.

One notable exception: Bitbucket Data Center is not part of this end-of-life plan. Atlassian is instead offering existing Bitbucket Data Center customers a Bitbucket Hybrid License, letting them run both Bitbucket Data Center and Bitbucket Cloud simultaneously, in recognition of how sensitive source code repositories can be to migrate. Jira Align Data Center is also excluded from this particular end-of-life announcement.

What Is the Jira Data Center End-of-Life Timeline?

The Jira Data Center end-of-life process unfolds across four key dates between 2024 and 2029, each of which restricts a different purchasing or support option. Missing an early deadline doesn't end your access immediately, but it does close off options you may want later.

Date	What Changes
February 15, 2024	Atlassian Server products (the predecessor to Data Center) reached full end of support.
March 30, 2026, 23:59 PST	New customers can no longer purchase new Data Center subscriptions or Data Center Marketplace apps.
March 30, 2028, 23:59 PST	Existing customers lose the ability to purchase new Data Center subscriptions, expand seat counts, or buy new Marketplace apps for Data Center.
March 28, 2029, 23:59 PST	Full end of life. Data Center subscriptions and apps expire; environments become read-only. Renewals cannot extend past this date.

A few details worth flagging directly from Atlassian's own FAQ on this transition:

Existing customers are defined as any organization that paid for a Data Center subscription before March 30, 2026 — this status is what determines eligibility to keep purchasing through 2028.
Through the full window, Atlassian will keep providing technical support and critical security fixes, so a Data Center instance doesn't become unsupported the moment the 2026 deadline passes — it simply becomes unavailable to new customers.
After March 28, 2029, environments that haven't migrated go read-only: you can view historical data, but you cannot create, edit, or execute workflows.
Atlassian has said it will offer multi-year Data Center extensions beyond 2029 by exception only, for organizations with unresolved regulatory or technical blockers — this requires directly contacting an Atlassian account team rather than being a default option.

Why Is Atlassian Ending Data Center?

Atlassian is consolidating its product investment into Atlassian Cloud, stating that more than 99% of its customer base is already on cloud or actively moving there — including a majority of its regulated and enterprise customers. The company frames the shift as necessary to deliver AI-embedded workflows, unified data, and faster feature releases that it says are harder to sustain across a self-hosted product line.

Atlassian has publicly stated it shipped over 1,000 new features to cloud in 2024 alone, deploying updates roughly 8,000 times per month — a release cadence the company says isn't realistically achievable for a self-managed Data Center architecture. [VERIFY] Whether that pace of innovation justifies the migration cost for a specific organization is a case-by-case calculation, not a given.

Migration Options Compared

Data Center customers today have three realistic paths forward, and the right one depends heavily on regulatory requirements, source-code sensitivity, and how customized the current environment is.

Option	Best For	Key Trade-off
Migrate to Jira Cloud	Most organizations, especially those without hard data-residency or air-gap requirements	Per-user cost is typically higher than Data Center, but includes AI features, automatic updates, and no infrastructure management
Bitbucket Hybrid License (Bitbucket only)	Organizations with sensitive source code that can't fully leave self-hosted infrastructure	Only available for Bitbucket — does not apply to Jira or Confluence Data Center
Continue on Data Center by exception	Regulated industries (e.g., government, defense) awaiting compliance certifications like FedRAMP High	Requires direct negotiation with Atlassian; not guaranteed and framed as a temporary bridge, not a permanent option

For most Jira Data Center customers, migrating to Jira Cloud is the path Atlassian is actively steering the market toward, supported by tools like the Atlassian Migration Program, free cloud migration trials, and — for qualifying customers — a FY26 Cloud Enterprise Edition discount of 10–20% off the first year for purchases made by June 2027.

Government and defense customers face a narrower set of choices: Atlassian Government Cloud achieved FedRAMP Moderate authorization, but FedRAMP High and Impact Level 5 environments were still in development as of this writing, with no published authorization date. Agencies handling classified or IL5-level data should treat the 2029 deadline as a hard constraint requiring early, direct engagement with Atlassian rather than a wait-and-see approach.

How to Plan a Jira Data Center Migration

A Jira Data Center migration typically moves through five stages, and enterprise-scale environments should expect this process to take months rather than weeks, particularly where custom scripts, integrations, or compliance reviews are involved.

Audit your environment. Inventory every Marketplace app, custom workflow, integration, and script (for example, ScriptRunner-based automations) currently running in your Data Center instance. Anything relying on direct database access or server-side scripting will likely need to be rebuilt for cloud, since Jira Cloud doesn't expose the underlying database (RDBMS) directly.
Assess cloud readiness. Use Atlassian's Cloud Platform vs. Data Center comparison resources and tools like Portfolio Insights to identify feature gaps, guardrail limits, or automation-rate limits that could affect your specific setup before committing to a timeline.
Run a migration trial. Atlassian's cloud migration trials run for the duration of your existing Data Center subscription — longer than a standard seven-day cloud trial — giving teams real time to validate workflows, permissions, and integrations before cutting over.
Engage a Solution Partner for complex environments. Highly customized instances, especially those with regulatory requirements or heavy scripting, benefit from an Atlassian Cloud Migration Specialized Solution Partner rather than a self-managed cutover.
Execute and validate. Migrate data in stages where possible, validate against your audit from step one, and keep the Data Center environment available in parallel until the cloud instance is confirmed stable — Atlassian's dual licensing option exists specifically to avoid double-paying during this overlap for larger customers.

Common Mistakes and Misconceptions

Misconception 1: “2029 is far away, so there's no urgency yet.”

The 2029 date is the final deadline, not the first constraint. New customers already can't buy Data Center as of March 2026, and existing customers lose expansion and renewal flexibility in March 2028 — waiting until 2028 or 2029 to start planning compresses a multi-month migration into a much smaller window.

Misconception 2: “My Data Center license just stops working the day it expires.”

It doesn't disappear — it goes read-only. You retain access to historical data, but you lose the ability to create, edit, or run new workflows, which for most active teams is functionally the same as losing the tool for day-to-day work.

Misconception 3: “Everything in Data Center has a direct cloud equivalent.”

Cloud doesn't provide direct database (RDBMS) access, and custom server-side scripts (like ScriptRunner's Groovy scripts) generally don't migrate automatically — cloud alternatives typically use JavaScript/TypeScript or Jira's own expression language instead, which means custom logic often needs to be rewritten, not just moved.

Misconception 4: “This only affects Jira and Confluence.”

The end-of-life list also includes Jira Service Management Data Center, Bamboo Data Center, Crowd Data Center, and any Marketplace apps built for these affected Data Center products — an audit needs to cover the full Atlassian footprint, not just Jira.

Misconception 5: “Bitbucket customers are affected the same way as Jira customers.”

Bitbucket Data Center was explicitly carved out of this end-of-life announcement. Bitbucket customers get a Hybrid License allowing continued use of Bitbucket Data Center alongside Bitbucket Cloud — a materially different, more flexible path than what's available for Jira or Confluence Data Center.

Frequently Asked Questions

When does the Jira Data Center reach the end of life?

Jira Data Center, along with other affected Data Center products, reaches full end of life on March 28, 2029 at 23:59 PST. After this date, subscriptions and Marketplace apps expire and environments become read-only.

Can I still buy Jira Data Center after 2026?

New customers cannot purchase Data Center subscriptions after March 30, 2026. Existing customers who purchased before that date can continue buying new subscriptions, expanding seats, and purchasing Marketplace apps until March 30, 2028.

What happens if I don't migrate before the deadline?

If you take no action, your Data Center license expires on March 28, 2029 and the environment becomes read-only: you can view existing data, but you cannot create, edit, or run new workflows, and no further security updates will be issued.

Is the Bitbucket Data Center also ending?

No. Bitbucket Data Center is excluded from this end-of-life plan. Existing Bitbucket Data Center customers instead get access to a Bitbucket Hybrid License, allowing continued use of both Bitbucket Data Center and Bitbucket Cloud.

What are my options besides moving to Jira Cloud?

Outside of migrating to Jira Cloud, options are limited: Bitbucket customers can use the Hybrid License, and some organizations with unresolved regulatory or technical blockers may negotiate a multi-year Data Center extension with Atlassian by exception.

Is there a way to extend Data Center support past 2029?

Atlassian has said it will offer extended maintenance for certain Data Center customers by exception after the 2029 deadline, intended for organizations facing unique regulatory or technical migration challenges. This isn't guaranteed by default.

Does the end-of-life affect Jira Align?

No. Jira Align Data Center is explicitly excluded from this particular Data Center end-of-life announcement, though it follows its own separate support and release lifecycle.

What discounts does Atlassian offer for migrating to the cloud?

Atlassian has stated it offers a Cloud Enterprise Edition discount of 10 to 20 percent off the first year for customers purchasing by June 2027, along with extended cloud migration trials, step-up credits, and dual licensing for larger customers.

Conclusion

The Jira Data Center end-of-life timeline gives organizations a genuinely workable runway — but only if the planning starts well before the 2028 and 2029 deadlines actually bite. The organizations that will struggle aren't the ones with the most complex Data Center environments; they're the ones that treat March 2029 as a single date instead of the last step in a sequence that's already begun narrowing their options. Whether the right path is a full Jira Cloud migration, the Bitbucket Hybrid License, or a negotiated extension, the decision is far easier to make — and far cheaper to execute — with a year or two of runway than with six months.

Jira Data Center End of Life: Full Timeline & Options