Home/Journal/How to Time an Atlassian Data Center Renewal Against the 2028 Deadline
Atlassian · Renewal Timing

How to Time an Atlassian Data Center Renewal Against the 2028 Deadline

Atlassian has said it will stop selling new Data Center licences after 30 March 2026 and let existing customers renew only through 30 March 2028, with the product retiring after that. That makes your remaining Data Center renewals a timed decision: each one either buys migration runway at a capped cost or hands Atlassian a compounding increase against a product you are being pushed off. The timing is the leverage, so plan it backward from 2028, not forward from your next invoice. Confirm the exact dates against Atlassian's current notices.

A renewal against a retiring product is a different exercise from an ordinary one. The vendor knows you must move eventually, list prices have already risen, and every renewal you sign is one of a finite number left. The buyer's advantage is that the deadline is fixed and public, which means it can be planned for rather than reacted to. The full migration and cost picture sits in our Atlassian Data Center end of life 2026 guide; this article is the timing playbook within it.

What is the Atlassian Data Center 2028 deadline?

On Atlassian's stated path, no new Data Center licences are sold after 30 March 2026, existing customers may renew through 30 March 2028, and Data Center retires after that window. The practical reading for a buyer is simple: 2028 is your last renewal, so the renewals between now and then are the ones where timing and term length decide your cost. Treat the dates as the frame of the negotiation and verify them against Atlassian's latest published notices before you commit.

The deadline is fixed, which makes it plannable. A buyer who maps renewals backward from March 2028 controls the sequence. A buyer who renews forward from each invoice lets the vendor set the tempo and the price.

Should I do one more Data Center renewal or move to Cloud now?

That is the central timing question, and the answer turns on migration readiness and the term length available. A final multi-year Data Center renewal can be a deliberate purchase of runway: it holds a known cost while you plan and execute the move, provided the term reaches usefully toward 2028 and the annual uplift is capped. Moving to Cloud now removes the deadline entirely but commits you to user-tier pricing and its own cliffs.

PathWhat it buysTiming risk to manage
Final Data Center renewalMigration runway at a known, capped cost; time to plan the move properlyTerm must reach toward 2028; uncapped uplift erodes the value fast
Migrate to Cloud nowRemoves the deadline; access to Cloud-only capability and Rovo AIUser-tier pricing cliffs; migration effort under your own clock
Wait and decide laterOptionality, brieflyFewer renewals left, rising list, and a compressed migration window

Model both numbered paths on total cost to 2028 and beyond before you choose. The migration-side cost discipline is in Atlassian Data Center to Cloud migration cost control, and the platform context is the Jira Service Management platform page.

How do the Data Center price increases change the timing?

Atlassian has raised Data Center list prices materially, with reported increases in the range of 15 to 40 percent depending on product and tier. Because those rises compound against a product on its way out, the cost of waiting is real and the cap you negotiate on each renewal's uplift is the single most important commercial term. A renewal with an uncapped increase is a renewal that gets more expensive precisely as your leverage shrinks.

The timing implication is to lock a capped, multi-year renewal earlier rather than absorbing successive uncapped annual rises. The mechanics of holding those increases down are in Atlassian price increases and protection clauses.

A backward-planned renewal timeline

Plan from March 2028 and work back. The sequence below keeps the deadline working for you instead of against you.

  1. Now: fix your migration decision date. Decide when you will commit to Cloud or to a final Data Center term, and put that date in the calendar before the vendor sets one for you.
  2. 9 to 12 months before each renewal: build the position. Reconcile your user tiers and app licences, model both paths to total cost, and prepare a credible Cloud alternative so the Data Center renewal is contestable.
  3. 6 months before: negotiate the term and the cap. If you are renewing, push for a multi-year term that reaches toward 2028 with a hard uplift cap. The term length is your protection against the next list increase.
  4. Through the window: stage the migration. If you are moving, sequence it so you are not paying for both environments any longer than necessary, and so the final Data Center term ends as the Cloud go-live lands.
  5. Approaching 2028: avoid the last-minute renewal. A renewal signed against the deadline with no alternative is the weakest position available. Make the decision early enough that you are never negotiating with the clock at zero.

This is Map, Benchmark, Leverage, Close applied to a deadline: map the renewals left, benchmark both paths, use the planned alternative as leverage, and close on a capped term timed to your migration.

Free download · The ITSM Renewal Timing Playbook

Our ITSM Renewal Timing Playbook sets out how to sequence renewals against vendor deadlines and fiscal cycles so timing becomes a lever rather than a liability.

What to do next

Count the Data Center renewals you have left before March 2028 and put a migration-decision date in the calendar now, because that single date is what converts the deadline from the vendor's pressure into your plan. We have negotiated more than $420M of ITSM contract value across 500-plus engagements and average a 30% reduction, and against fixed deadlines the saving comes from timing and capped terms as much as rate. When you want the renewal sequence and the Cloud-versus-Data-Center model run end to end, the engagement is our renewal advisory service on fixed fee or gainshare.

Book a renewal review.

We map your remaining Data Center renewals, model both paths to 2028, and time the term against the deadline. Fixed fee or gainshare.

Book a renewal review →

Frequently asked questions

What is the Atlassian Data Center 2028 deadline?
Atlassian has stated that no new Data Center licences sell after 30 March 2026, that existing customers can renew through 30 March 2028, and that Data Center retires after that. The 2028 date is the last renewal window, which makes the timing of your final renewals a deliberate negotiation. Confirm the exact dates against Atlassian's current notices.
Should I do one more Data Center renewal or move to Cloud now?
It depends on migration readiness and the term available. A final multi-year Data Center renewal can buy runway at a known cost if the term reaches toward 2028 and the uplift is capped. Moving to Cloud now removes the deadline but commits you to user-tier pricing. Model both first; it varies by estate.
How do Data Center price increases affect renewal timing?
Atlassian has raised Data Center list prices materially, reportedly in the range of 15 to 40 percent depending on product and tier. Because rises compound against a retiring product, the timing of your renewal and the cap you negotiate on its uplift are the main levers on what the final years cost.

The ITSM Negotiation Brief

Vendor moves, benchmark data, and renewal alerts for ITSM buyers.

ITSM Negotiations

Independent, buyer-side ITSM contract negotiation. Fixed fee or gainshare. Not affiliated with any ITSM vendor.

Services
NegotiationRenewal AdvisoryOptimization
Platforms
ServiceNowFreshserviceIvanti
Company
AboutContactJournal
Independent. Not affiliated with ServiceNow, BMC, Atlassian, or any ITSM vendor.Privacy · Terms · Disclaimer · Editorial Standards · Newsletter · Glossary · Est. 2019