Atlassian Data Center end of life in 2029. The dates, the options and the price of waiting.

Atlassian Data Center becomes read only on March 28, 2029, and expansions stop a year earlier. The fixed deadline favors Atlassian, so price Cloud and Data Center on a clean user count and negotiate early.

What does Atlassian Data Center end of life actually mean?

It means Atlassian stops supporting Data Center altogether. On March 28, 2029, Data Center subscriptions and the Marketplace apps attached to them expire, and the products become read only. Until then, existing customers get technical support and fixes for critical security vulnerabilities, but new purchases stop a year earlier, on March 30, 2028.

There is also a second, older clock. Under the Atlassian end of life policy, each feature release or Long Term Support release is supported for two years from its ship date. After that, Atlassian stops shipping security fixes and support for that version, even while your subscription is still paid.

What changes when a version or the platform reaches end of life?

A release past its two year window keeps running, but without fixes or support, which most security and compliance teams will not accept. At the platform date the choice disappears, because the instance turns read only. Treat the dates as fixed and the migration offer as negotiable.

• No security patches. New vulnerabilities go unfixed on the affected versions, and your team carries the exposure alone.
• No vendor support. Incidents are no longer covered, including the upgrade failures you would need help with most.
• Compliance exposure. Unsupported software fails many audit, cyber insurance and customer security questionnaires.
• Read only data. At the 2029 platform date, users can still see content but cannot create or edit it, so the instance stops being a working tool.

Why does a fixed deadline strengthen Atlassian's hand?

A cutoff you cannot move, combined with a decision you cannot avoid, gives the seller the stronger position. Time pressure is what pushes buyers into accepting the first migration offer. The earlier you engage, the more of that pressure shifts back to Atlassian.

Which Data Center dates matter, and what should you do before each?

Four dates on the Atlassian end of life schedule decide what you can still buy. Atlassian publishes them on its Data Center licensing pages, and each one closes an option.

Data Center subscriptions normally run 12 months, and Atlassian will sell terms of up to 24 months on request. A site on annual terms today faces two or three more renewals before 2029, each priced by Atlassian. Extended maintenance after 2029 exists only by exception, so do not plan around it.

Atlassian has run this sequence before. Server support ended on February 15, 2024, and customers still on Server after that date lost security fixes and support.

What are the realistic paths at Data Center end of life?

There are two supported paths: move to Atlassian Cloud, or stay on Data Center until March 28, 2029 and migrate later. Running unsupported is a third path in name only. The choice between the first two turns on data residency, customization and scale.

When is Cloud the right call?

Cloud fits when you want Atlassian to carry hosting and upgrades and your customization is moderate. Pricing and editions sit on pages such as the Confluence pricing page, and the band your user count lands in drives the bill.

• Lower operational load. Atlassian runs hosting, scaling and updates, and your platform team stops patching.
• Faster feature access. Cloud receives new capability first, and Rovo, Atlassian's AI product, runs only in Cloud (Data Center content can reach it only through connectors).
• Tier sensitivity. User bands and editions need active management every year, because Cloud bills on what you provision.

When does staying self managed still make sense?

Where residency rules or deep customization rule out Cloud today, Data Center can bridge the gap until 2029. Treat it as a bridge with an end date. Confirm the renewal curve for each remaining term before you rely on it, and budget for a second project later.

Regulated buyers should also ask about Atlassian Government Cloud, which carries FedRAMP Moderate authorization for US public sector work, and Isolated Cloud, a dedicated single customer environment announced for 2026. Ask for current availability and pricing in writing.

How did Atlassian Data Center pricing change?

Data Center list prices rose across recent renewal cycles, so the assumption that staying put is cheap no longer holds. The increases reset the comparison between staying and moving, and our Data Center price increase tracker shows how the steps stacked up.

What does the increase history tell you?

• Step increases. Several cycles carried double digit percentage rises on Data Center list prices.
• Tier pressure. User growth compounded the rate increases, because crossing a tier boundary reprices the whole subscription.
• Narrowing support. What you get for the money fell as the roadmap tightened and new features went to Cloud only.

How should you benchmark the two offers?

Compare the Cloud quote and the Data Center renewal against the same clean user count, over the same three years. Atlassian posts pricing and policy changes on its company blog, which helps you see the next increase coming. Migration paths and cost estimates are on the cloud migration hub.

Why we advise against holding on to Data Center until the last renewal

The usual advice is to stay on Data Center as long as possible to defer the Cloud subscription. We disagree. In roughly half of the sites we reviewed, renewals rose 20 to 40 percent while the roadmap narrowed, so deferring cost more than the migration it postponed.

Price both paths now against a clean, right sized user count, and negotiate while time is still on your side. Waiting to avoid Cloud usually means paying more for a shrinking option.

End of life is a date you cannot move, so the only variable left is how much negotiating room you still hold when you finally engage.

How much can a user cleanup save before you migrate?

Usually more than any migration discount, because the cleanup saving repeats every year. The example below is hypothetical, and the $150 per user annual rate is a round figure for illustration, not an Atlassian price.

Say your Jira Data Center site counts 2,300 licensed users. An export shows 450 accounts with no login in the past 12 months, so the clean count is 1,850. Assume a 15 percent first year discount on the Cloud offer.

The cleanup is worth $67,500 a year and $192,375 over three years. The discount on the uncleaned count is worth $51,750, once. Carrying inactive users into Cloud is one of the patterns we saw repeatedly, as the section below shows.

How do step up credits change the timing?

Atlassian gives a prorated credit for unused Data Center maintenance when you move to Cloud. Say you paid $240,000 for a 12 month renewal and cut over after 5 months. The 7 unused months are worth $140,000 ($240,000 x 7 / 12), so the credit and the renewal date should be planned together.

How does the answer change for a small site and a very large one?

• Under 500 users. Negotiating room is smaller, so the savings come from cleanup, edition choice and timing. Commercial and Academic licenses with 11 or more users qualify for a free Cloud migration trial that matches the rest of the Data Center term, up to 12 months.
• Several thousand users. Dual licensing, step up credits and the Cloud Enterprise discount all come into play, and each needs to be written into one agreement.
• Above 20,000 users. The standard migration trial covers user tiers up to 20,000, so anything larger has to be arranged with Atlassian directly. Expect a phased migration across instances and ask for a dual run window long enough to cover it.

How do you check your own position before you ask for a quote?

Start with data you already hold, so the first quote is built on your numbers. These sources are enough for most sites.

• License details in each product's administration console. They show the licensed tier, the current user count and the expiry date.
• my.atlassian.com. It lists every Data Center license, app license and renewal date under your account.
• The user directory with last login dates. Export it and flag accounts with no login in 12 months, service accounts and duplicates.
• The Jira and Confluence Cloud Migration Assistants. Their app assessment shows which Marketplace apps have a Cloud version and which do not.
• Your version numbers against the end of life policy. A release shipped more than two years ago is already unsupported.

Marketplace apps deserve their own line in the budget, because they expire with the platform in 2029. Our note on Marketplace app licensing at end of life covers how app prices move when you migrate.

What will the Atlassian account team say, and how should you answer?

Expect some version of these lines during a Data Center exit, and have the reply ready.

• "The Enterprise discount ends in June 2027." Ask for the quote with and without the program, so you can see what the discount is worth against the edition being proposed.
• "You need Enterprise to match your Data Center controls." Ask which control, in writing. Then check whether Premium, or Premium with Atlassian Guard, covers it. Our Premium versus Enterprise comparison lists the real differences.
• "Price your full current user count and adjust later." Decline, and send the cleaned count as the basis of the quote. If they insist, ask in writing when and how the tier can be reduced during the term.
• "Data Center renewals will only get more expensive." Ask for the next renewal quote now, alongside the Cloud quote, and compare them over three years.
• "Dual licensing is only for larger customers." Ask for the eligibility threshold in writing. Atlassian's own licensing terms describe extending the Data Center subscription for up to 1 year at a 100 percent discount while you run both, so ask why your site would not qualify. Our guide to running Cloud and Data Center in parallel explains how the overlap works.

Which contract terms should you ask for in the migration deal?

Ask for the whole package in one negotiation, before you commit a migration date. Once the date is public inside your company, the account team knows you have to sign.

1. A cap on the first Cloud renewal. The migration discount means little if year 2 resets to list.
2. A dual run window in months, covering apps. Parallel running is where migrations overrun, and paying twice for that period is avoidable.
3. The step up credit calculation written into the order. State the unused months and how the credit applies to the first Cloud invoice.
4. A loyalty credit for your years on Server and Data Center. It is negotiable, but only before the date is committed.
5. The right to change edition at the first renewal. If Enterprise features go unused, you need a way back to Premium.
6. A per user price for growth. Additional users during the term should cost the same rate as the base count.

If these terms do not land, price an exit from Atlassian too, for example service desk work on ServiceNow, as in our Jira versus ServiceNow review. Our Cloud migration negotiation guide covers the full sequence.

What have we seen in recent Data Center end of life negotiations?

Between 2024 and 2025, as the Data Center timelines tightened, I reviewed roughly 15 to 25 Atlassian sites. The deadline drove rushed and expensive decisions in most of them, and the same three patterns kept appearing.

Which mistakes cost buyers the most?

• Engaging late. Sites that engaged inside the final year accepted offers 10 to 20 percent above what earlier movers secured.
• Treating the renewal as routine. Data Center renewal quotes arrived 20 to 40 percent higher than the prior term in several cases, and some were signed without a Cloud comparison.
• Carrying waste forward. Inactive users and oversized editions migrated unchanged, which locked the waste into the new subscription.

Doing nothing is the fourth mistake, and it only looks cheap. Running unsupported is a security and compliance exposure, and in 2029 the data becomes read only anyway. Our Cloud migration guide covers the technical plan once the commercial terms are set.

What to do next

1. This month. Confirm the end of support date for every Data Center version you run, and note your next renewal date.
2. Before any pricing. Export and clean the user list, and list the Marketplace apps you actually use.
3. Same basis for both quotes. Price Cloud and a Data Center renewal against the same right sized count, over three years.
4. Look back. Pull your last three Data Center renewals to see the increase trend.
5. Engage early. Start talks while the deadline still leaves you room, and well before June 2027 if Enterprise is on the table.
6. One package. Negotiate loyalty credit, edition fit, step up credit and a dual run window together.
7. Before the date is set. Get the cap on the first Cloud renewal in writing before you commit a migration date.

Frequently asked questions