DC EOL: What to Plan for Now
Atlassian Data Center reaches end of life on 28 March 2029. Here's the full timeline, what it means for Australian enterprises, and five things you should do right now.
CLOUD MIGRATION & INFRASTRUCTURE
Data Center End of Life: What To Plan for Now
March 2029 sounds far away. It is not. Not once you factor in procurement cycles, change advisory boards, data residency assessments, and the fact that every other Data Center customer globally will be running the same race at the same time.
Atlassian has confirmed that all Data Center products reach end of life on 28 March 2029. After that date, every Data Center instance transitions to read-only: no new issues, no page updates, no workflow execution, no extensions.
For Australian enterprises running Jira, Confluence, or Jira Service Management on Data Center, this is not a technology problem you can defer. It is a planning problem that needs to start now.
The timeline is already in motion
The end-of-life date is the final milestone, but the changes started months ago. Here are the dates that matter for planning:
December 2025 (passed)
Atlassian shifted all development focus to Cloud. New Marketplace app submissions for Data Center were discontinued, and no new Data Center features are being built.
March 2026 (passed)
New organisations can no longer purchase Data Center licences or Marketplace apps. Existing customers retain expansion rights, but the window is narrowing.
March 2028
Existing customers lose the ability to purchase additional Data Center licences or expand their Marketplace app portfolio. Renewals are prorated only up to the end-of-life date.
28 March 2029 — hard cutoff
All Data Center licences expire and instances transition to read-only. This is a hard cutoff with no extensions.
A well-planned cloud migration typically takes six to twelve months to execute, with planning and budgeting adding another six to twelve months before that. Australian enterprises should be treating mid-2028 as their real deadline.
Why this is different from the Server end of life
When Atlassian Server reached end of life in early 2024, organisations could keep their environments running, unsupported but functional. Many Australian enterprises did exactly that, treating Data Center as a holding pattern while they evaluated Cloud.
That option does not exist this time. After 28 March 2029, Data Center instances go read-only. No new issues can be created, no pages can be updated, no workflows can run.
For organisations in financial services, government, education, and healthcare, industries where Atlassian tools underpin critical operational workflows, that is not an inconvenience. It is a business continuity risk.
What Australian enterprises specifically need to consider
Cloud migration for Australian organisations involves considerations that generic migration guides tend to skip over.
Data residency and sovereignty
Australian government agencies and regulated enterprises need certainty about where their data lives. Atlassian now offers data residency controls that allow organisations to pin data to specific geographic regions, including Australia. For organisations with the highest security requirements, Atlassian's Isolated Cloud offering, arriving in 2026, provides a single-tenant architecture.
Mapping your data residency obligations before you migrate is not optional. Moving to Cloud without understanding what regulations apply creates compliance risk that is far more expensive to resolve after the fact than before it.
Marketplace app readiness
Most Australian enterprises running Data Center depend on a portfolio of Marketplace apps: reporting tools, automation plugins, custom integrations. Not every Data Center app has a Cloud equivalent, and those that do may behave differently in ways that are not obvious until you test them.
Before migration, you need a complete inventory: which apps have Cloud versions, which are being rebuilt on Forge, and which will need replacement. This work should be underway well before migration execution begins, not treated as a step within it.
Licence cost modelling
Cloud licensing works differently from Data Center. Pricing structures, user tier thresholds, and bundled features all shift, and for organisations with large user bases the differences can be significant in either direction.
Many organisations find that consolidating unused seats, removing redundant apps, and right-sizing their licence tier during migration actually reduces their total Atlassian spend. Getting Atlassian licensing expertise involved early, not at renewal time, can save tens of thousands of dollars annually.
Integration and automation rework
If your Data Center environment has custom integrations, API connections to internal systems, scripted automation, or third-party middleware, these need assessment and potentially full rearchitecting for Cloud. Cloud APIs differ from Data Center APIs in ways that make a straight lift-and-shift technically risky.
For organisations already exploring MCP integration services or enterprise AI, the migration is an opportunity to modernise your integration layer at the same time, rather than migrating legacy approaches and rebuilding them again six months later.
The Atlassian Ascend program
Atlassian introduced Ascend specifically to support Data Center customers through this transition. Three elements are worth understanding now.
Dual licensing
Run Data Center and Cloud in parallel during your transition. This de-risks the migration considerably by allowing phased workload moves rather than a single cutover event.
FastShift
Targets migration completion in two to six months for organisations with more than 1,000 users, significantly faster than the typical twelve to sixteen month timeline for a conventional migration.
Enterprise pricing incentives
Cloud Enterprise discounts for organisations that commit before certain deadlines. These windows close progressively, and the organisations that investigate them earliest will secure the best terms.
Five things to do right now
Regardless of where you are in planning, these should be happening now.
Run a migration readiness assessment
Get a clear picture of your current environment: user counts, active projects, Marketplace apps, custom integrations, data volumes, and governance gaps. This is what a Platform Discovery engagement delivers.
Map your data residency and compliance requirements
Know what regulations apply to your data before you select a Cloud tier. For Australian government agencies, this is non-negotiable. For financial services, it is increasingly a board-level concern.
Audit your Marketplace app portfolio
Identify which apps have Cloud equivalents, which are transitioning to Forge, and which will need replacement. Start testing alternatives in a sandbox environment before you need them in production.
Model your Cloud licensing costs
Build a cost model that compares your current Data Center spend to projected Cloud costs, factoring in seat consolidation, app rationalisation, and Ascend incentives. The number is often better than organisations expect.
Set an internal deadline of mid-2028, not March 2029
Every organisation that has been through an Atlassian migration will tell you the same thing: it takes longer than the plan says. Build that reality into your timeline from the start.
What happens if you wait
The risk of waiting is not simply missing a deadline. It compounds. Every month of inaction means higher migration costs as demand concentrates closer to 2029, fewer Ascend incentives as early-mover discounts expire, more technical debt accumulating in an environment that is no longer receiving new features, and a compressed change management window that increases the likelihood of something going wrong.
The organisations with the smoothest migrations will be the ones that start their assessments this year.
How DI helps
Design Industries has been guiding Australian enterprises through Atlassian platform transitions for over 20 years. We have delivered cloud migrations across government, financial services, education, defence, healthcare, and mining, and we understand the specific requirements that make Australian migrations different from the global playbook.
Our work starts with a structured assessment that maps your current environment, identifies migration risks, models licensing costs, and gives you a clear plan before you commit to a timeline or a vendor.
If you are also evaluating how AI fits into your post-migration environment, our AI Fast Start and Rovo implementation services activate the Cloud-native AI capabilities that are not available on Data Center. You are not just migrating, you are upgrading what your platform can do.
For ongoing Atlassian support and implementation needs during and after migration, DI provides dedicated specialist resources who know your environment from day one.
YOUR REAL DEADLINE IS MID-2028
Start your migration assessment today
Get a clear picture of your environment, licensing costs, and a migration plan tailored to your organisation.
30 minutes. Same-day scheduling. No obligation.


