Can I still buy Data Center licenses after March 30, 2026?

No. New license sales end on this date. Only existing customers can renew or expand until March 2028.

How do I handle Marketplace apps with no Cloud equivalent?

You must perform a gap analysis. Some vendors offer migration paths; others may require you to pivot to a different app or build custom functionality via Atlassian Forge.

What is the "Atlassian Ascend" program?

Atlassian Ascend is a dedicated initiative providing resources, partner support, and financial incentives to help enterprises move to Cloud before the 2029 deadline.

How to budget for a Data Center to Cloud migration?

Your budget should account for: 1. Dual Licensing: Paying for both DC and Cloud during the transition. 2. Consulting Fees: Professional services for complex data mapping. 3. App Subscriptions: Cloud app pricing often differs from Data Center tiers.

The Master Guide: Atlassian Data Center End of Life (EOL) 2029

The "Cloud-First" era has officially evolved into the "Cloud-Only" mandate. In September 2025, Atlassian announced the final sunset for its Data Center (DC) products. For enterprises running Jira, Confluence, or Bitbucket on-premise, the countdown has begun.

By March 28, 2029, the Data Center deployment as we know it will cease to exist. This guide provides the technical and strategic roadmap required to navigate this transition, mitigate risks, and plan your move to Atlassian Cloud.

1. The Official Atlassian Data Center EOL Timeline

Understanding the timeline is the first step in risk mitigation. Atlassian is winding down support in three distinct phases:

Phase 1: End of Sale — March 30, 2026

As of March 30, 2026, Atlassian will stop selling new Data Center subscriptions to new customers. If your organization is not already on the platform, you will no longer be able to purchase a Data Center license for Jira, Confluence, or Jira Service Management.

Phase 2: Expansion Cutoff — March 30, 2028

For existing customers, the window to grow your infrastructure closes on March 30, 2028. After this date, you can no longer increase user tiers or purchase new Marketplace apps for your Data Center instance.

Phase 3: Final End of Life — March 28, 2029

The final Atlassian Data Center end of life date is March 28, 2029 (23:59 PST). On this date:

Subscriptions officially expire.
Support for Jira Data Center end of life and Confluence Data Center EOL enters its final stage.
Systems transition into read-only mode.

Timeline-to-Action Summary

Given the multi-year wind-down, here is what organizations should be doing at each stage:

Timeframe	Action
Now – Q4 2025	Complete a full inventory of Marketplace apps, custom integrations, and user counts. Begin a formal assessment of Cloud readiness.
Q1 – Q2 2026	Lock in any needed license expansions before the End of Sale date. Run a Proof of Concept migration on a non-production instance.
Q3 2026 – Q4 2027	Execute cleanup of inactive users, archived projects, and redundant data. Begin phased production migrations for lower-risk products first.
Q1 – Q2 2028	Complete any remaining license tier increases before the Expansion Cutoff. Finalize Marketplace app replacements.
Q3 2028 – Q1 2029	Execute final production cutovers. Complete post-migration validation, SSO reconfiguration, and user acceptance testing.

Also read our blog on: Deep Dive into the 2026 End of Sale & Licensing Strategy

2. What Happens After March 28, 2029? (The Read-Only Reality)

A common question asked is: "Will Data Center go read-only after March 28, 2029 — what happens to writes?"

The answer is a hard yes. Once your license expires post-EOL, your environment will enter read-only mode — the state Atlassian DC products enter when the subscription lapses, where all write operations (creating, editing, commenting, transitioning issues) are disabled while read access to existing data is preserved.

No New Content: Users can view historical tickets and pages but cannot create, edit, or comment.
Security Vulnerabilities: Atlassian will stop providing security bug fixes for critical vulnerabilities.
Compliance Failure: Running unpatched, EOL software creates direct exposure under multiple regulatory frameworks (see the compliance section below for specifics).
Marketplace Breakdown: Marketplace app vendors will shift development resources to Cloud-native versions. Apps that depend on Data Center APIs or server-side plugins will stop receiving updates and compatibility fixes.

3. Critical Business Risks & Compliance

"What does Atlassian Data Center end of life (March 28, 2029) mean for our company?"

Beyond the technical hurdles, the business risks are substantial. Staying on a legacy system after the Data Center EOL impact on compliance and audits becomes clear leads to:

Security Risks: Unpatched instances are prime targets for zero-day exploits.
Operational Stagnation: You lose access to AI-driven innovations like Atlassian Intelligence and Rovo.
Data Sovereignty Issues: For regulated industries, moving to Cloud requires careful assessment of Atlassian data residency options. Atlassian currently offers data residency for in-scope product data in regions including the US, EU, and Australia. Isolated Cloud — Atlassian's deployment option designed for organizations with strict data isolation requirements — may also be relevant for highly regulated environments.

Compliance Risk Matrix

The table below maps the specific risks of running EOL Data Center software to the regulatory frameworks most commonly implicated:

Risk	GDPR	HIPAA	DORA
Unpatched CVEs (no security fixes)	Art. 32 — obligation to implement "appropriate technical measures" to ensure security of processing	§ 164.312 — Technical Safeguard requirements for systems handling ePHI	Art. 9 — requirement for ICT risk management frameworks including patch management
No vendor support SLA	Art. 28 — processor obligations and data processing agreements may lapse with EOL status	§ 164.308(a)(1) — risk analysis and management requirements	Art. 15 — ICT third-party risk requirements for contractual arrangements
No data processing agreement updates	Art. 28 / Art. 46 — processing agreements must reflect current technical and organizational measures	§ 164.314 — Business Associate Agreement requirements	Art. 28 — contractual arrangements with ICT service providers
Loss of audit trail integrity	Art. 5(1)(f) — integrity and confidentiality principle	§ 164.312(b) — Audit controls	Art. 12 — logging and monitoring requirements

Warning

This matrix is a starting point for risk conversations with your compliance and legal teams — not legal advice. The specific impact depends on your data types, jurisdictions, and how your auditors interpret "reasonable" controls for EOL software.

4. The 4-Phase Migration Roadmap

Successfully migrating from Data Center to Cloud is not a "lift-and-shift" event—it is a transformation.

Step 1: Assessment & Inventory

Audit your Marketplace apps. Identify those with no Cloud equivalent and determine if you can move to a native Cloud feature instead.

Resource: Atlassian Cloud Migration App Assessment Guide

Step 2: Cleanup

Minimize migration risk and complexity by offloading technical debt. Delete inactive users, archived projects, and redundant attachments that are no longer business-critical.

Step 3: The Proof of Concept (PoC)

Initiate a Cloud migration trial to test your existing workflows. Use this phase to validate SSO, LDAP configurations, and network restrictions.

Step 4: Execution & Cutover

You have two primary paths for the final move:

The Native Tooling Path: Use the Jira Cloud Migration Assistant (JCMA) and Confluence Cloud Migration Assistant (CCMA). These are Atlassian's free, built-in tools for migrating project data, users, and configurations to Cloud. They handle the majority of standard migrations, but have known limitations:

Certain Marketplace app data may not transfer and requires manual re-import or vendor-specific migration tools.
Complex automation rules and custom field configurations can require post-migration manual verification and adjustment.
Large instances may hit timeout or performance issues during migration, requiring migrations to be run in batches.
Attachments and inline images in some content types may need post-migration validation.

For detailed documentation on JCMA and CCMA capabilities and limitations, see Atlassian's official migration guides linked at the bottom of this page.

The Third-Party Managed Service Path: For organizations where the native tools' limitations are a dealbreaker — large user counts, complex Marketplace app ecosystems, or strict downtime requirements — a third-party migration service can provide custom scripting, parallel environment validation, and more granular control over the cutover process.

5. Key Terms & Definitions

Several terms in Atlassian's EOL communications can be ambiguous. Here are precise definitions:

Term	Definition
End of Sale (EOS)	The date after which Atlassian stops selling new Data Center subscriptions to new customers. Existing customers can still renew.
End of Life (EOL)	The date after which Atlassian stops all support, security patches, and bug fixes for Data Center products. Subscriptions expire.
Read-Only Mode	The state a Data Center instance enters when its license expires. All write operations are disabled; read access to existing data is preserved.
Bitbucket Hybrid License	A licensing option allowing organizations to keep source code repositories on-premise (Bitbucket Data Center) while using Bitbucket Cloud for collaboration features.
Isolated Cloud	An Atlassian Cloud deployment option designed for organizations with strict data isolation and compliance requirements, providing dedicated infrastructure separation.
JCMA / CCMA	Jira Cloud Migration Assistant / Confluence Cloud Migration Assistant — Atlassian's free, built-in tools for migrating Data Center data to Cloud.

6. Strategic Exceptions: Bitbucket & Alternatives

While Jira Service Management Data Center EOL and Confluence are set in stone, there are exceptions:

Bitbucket Hybrid License: Atlassian understands the sensitivity of source code. They are offering a Bitbucket Hybrid License, allowing you to keep code on-prem while leveraging Cloud collaboration.
Jira Align: Currently, the self-hosted version of Jira Align follows a separate support policy.
The "Refusal" Path: Organizations that legally cannot move to a public cloud may need to evaluate on-prem alternatives to Jira/Confluence like OpenText or GitLab.

What Comes Next

The three-year wind-down gives every organization time to plan — but that window narrows with each phase. The End of Sale in March 2026 is the first hard gate, and organizations that haven't started assessment by then are already behind.

If you're evaluating migration paths, timeline risks, or how your Marketplace app stack maps to Cloud, we've done this across hundreds of Atlassian environments and can give you a straight answer on what your specific migration looks like.