The Complete Guide to Atlassian Data Center EOL
Atlassian is sunsetting most Data Center products. New customer sales ended March 30, 2026, existing customer expansion windows close March 30, 2028, and full end-of-life arrives March 28, 2029. This guide explains the timeline, migration paths, cost variables, and planning questions to answer now.
Key Questions Answered
Everything you need to know about the DC EOL transition
What is Atlassian Data Center End of Life?
Atlassian Data Center End-of-Life (EOL) is Atlassian's phased retirement of most Data Center product lines.
- Mar 30, 2026: New customer sales ended
- Mar 30, 2028: Expansions freeze for existing customers
- Mar 28, 2029: Support and maintenance end
Which products are affected by DC EOL?
Most major Data Center products are affected, with limited exceptions and transition paths:
- Affected: Jira Software, Jira Service Management, Confluence, Bamboo, Crowd, and most Data Center Marketplace apps
- Bitbucket Data Center follows a different hybrid licensing path
- Always validate your exact products, apps, and contract terms against Atlassian's current guidance
What are the migration options for DC EOL?
Current customers should compare several paths before committing:
- Migrate to Atlassian Cloud where product, compliance, app, and data requirements fit
- Remain on supported Data Center while planning a controlled transition
- Evaluate alternatives only when Atlassian Cloud does not meet validated requirements
What is the timeline for Atlassian DC EOL?
Key dates defining the sunset period:
- Dec 16, 2025: App ecosystem freeze
- Mar 30, 2026: New customer license sales ended
- Mar 30, 2028: User tier expansions freeze
- Mar 28, 2029: Full EOL and support end
What happens after DC EOL in 2029?
After the final deadline, organizations should expect material operating and security constraints:
- No Atlassian technical support or security patches for affected products
- Affected Data Center products and apps may move to read-only behavior
- Security, audit, and integration risks increase over time
Can I still buy new Data Center licenses?
For most affected products, new customer Data Center sales ended on March 30, 2026. Existing customers still have a limited window for renewals and some expansions.
- Mar 30, 2026: New customer sales ended
- Mar 30, 2028: Existing customer user and app expansion window ends
- Recommendation: validate your contract, renewal date, app portfolio, and migration runway now
Is this the same as the Server End of Support?
No. Server support ended in Feb 2024. This EOL applies specifically to Data Center products.
- Server: Ended Feb 15, 2024 (Past)
- Data Center: Ends Mar 28, 2029 (Future)
- Complex migrations can take months of discovery, testing, app remediation, and change management
The DC EOL Timeline
Critical milestones for existing Data Center customers
Ecosystem Freeze
No new Data Center app submissions to Marketplace
New Sales End
No new DC license sales for new customers
Expansions Freeze
Existing customers cannot add users or apps
Complete EOL
No support, no patches, read-only access
Impact by Organization Type
The transition affects different organizations in different ways
Regulated Industries
Healthcare, Finance, Government
- Validate each product against current Cloud compliance scope
- Map identity, residency, encryption, and audit requirements
- Review Marketplace apps separately from Atlassian products
- Record owner signoff for unresolved controls and exceptions
Heavily Customized
ScriptRunner, Groovy Scripts
- Inventory scripts, macros, automations, and integration dependencies
- Classify each customization as retain, redesign, replace, or retire
- Test Cloud equivalents against actual business behavior
- Plan remediation before committing to a cutover window
Large Enterprises
5,000+ Users
- Large datasets require measured test-migration evidence
- Identity and account collisions can delay migration
- Phased moves require clear data and ownership boundaries
- Cutover duration should be based on rehearsal results
Cost-Conscious
Mid-Market, Budget Constraints
- Model product tiers, user counts, apps, and identity needs
- Compare renewal timing with migration and dual-running costs
- Review storage, sandbox, and support requirements by tier
- Right-size users and apps before the Cloud commercial baseline
Hidden Costs of Cloud Migration
Commercial and delivery variables to model before approving a migration business case
Identity and Atlassian Guard
VariableModel the plan, user population, SSO, SCIM, and policy requirements in the current Atlassian pricing context.
Storage and Product Tier
VariableCompare current data volumes and growth with the storage and capability limits of candidate Cloud plans.
User and Billing Model
VariableReview active users, product access, renewal timing, and billing rules before setting the Cloud baseline.
Adoption and Change
Project-basedInclude communications, training, champions, support, and workflow changes in the transition plan.
Marketplace Apps
Portfolio-basedValidate Cloud availability, pricing, data handling, and replacement work for every in-scope app.
Integrations and Automation
Project-basedEstimate redesign, testing, and operating costs for integrations, scripts, macros, and automation rules.
Why AtlasOptima for Your DC Migration?
We combine readiness discovery, app and identity review, test migrations, reconciliation, cutover planning, and post-migration support to reduce avoidable risk and disruption.
Controlled Cutover Planning
Use rehearsals, validation owners, rollback triggers, and communications to plan the production move
License and App Review
Right-size users and rationalize Marketplace apps before establishing the Cloud baseline
Security Requirements Mapping
Review identity, residency, app permissions, audit controls, and owner signoffs
Customization Assessment
Classify scripts, macros, integrations, and automations for retention, redesign, replacement, or retirement
Atlassian Gold Solution Partner and Cloud Migration and Service Management Specialized Partner in AMER.
Read a legacy Server to Cloud migration case studyVerify on Atlassian Partner Directory
How to Evaluate an Atlassian Data Center Migration Partner
If you are comparing Atlassian partners in Canada, the United States, or broader North America, look for evidence that the partner can turn the EOL timeline into a decision-ready roadmap.
Current products, apps, custom scripts, automations, and integrations are inventoried before a recommendation is made.
The plan explains which workloads move to Atlassian Cloud, which need redesign, and which may need a different path.
Security, identity, data residency, audit, and stakeholder signoff are part of the migration scope.
The roadmap includes test migrations, validation owners, cutover planning, and post-migration support.
Plan Ahead, Migrate Smoothly
The earlier you start planning, the more options you have. We've helped many organizations navigate this transition — we'd be happy to help you too.