Atlassian Dual Licensing During Migration: Avoiding Double Payment

I sold platform subscriptions for years, and the overlap is one of the quietest margin contributors in any migration. The buyer is focused on the technical move, the renewal lands on its usual date, and nobody connects the two until both invoices are sitting on the desk. The vendor did not hide it; they just did not volunteer the credit you never asked for. This article is the buyer-side fix. It sits under our Atlassian Data Center end of life migration and cost guide, which is the hub for the whole transition.

Why do you end up paying for both Data Center and Cloud?

Because a real migration runs both platforms in parallel for months. You stand up Cloud, move projects, re-point integrations, validate, and only then decommission Data Center. If your Data Center renewal falls inside that window and you renew for a full term out of habit, you are now paying maintenance on the platform you are leaving while you pay subscription on the one you are joining. The double payment is not a penalty; it is a timing failure, and timing is something you can negotiate.

How do you avoid the double payment?

Three moves, taken together before either contract is signed. First, scope the overlap window honestly against your migration plan. Second, claim a Cloud migration credit or free-use period sized to that window, so Cloud runs during the move without a second bill. Third, align the Data Center renewal so you bridge only the months you need rather than committing to a full term you will abandon. Each is ordinary; the failure is doing them separately or too late.

How long does the overlap last, and why does the clock matter?

The overlap runs from a few months on a small instance to a year or more on a large estate with many marketplace apps and integrations. That range is exactly why you scope it deliberately rather than guess. The deadline adds pressure on both sides: Atlassian stops new Data Center sales after 30 March 2026 and supports renewals only through 30 March 2028, with retirement following in 2029. That clock is leverage if you plan around it and a liability if you let it plan around you. The timing detail is in Atlassian Cloud migration timeline: negotiating from the EOL clock, and the broader cost controls are in Atlassian Data Center to Cloud migration cost control.

What about the marketplace apps in the overlap?

Apps are the part of the overlap that catches buyers out, because you may be re-licensing them on Cloud while still paying for them on Data Center. Inventory every app, confirm which have Cloud equivalents and which need replacement, and fold their overlap into the same credit conversation. The app-specific cost control is in Atlassian marketplace app re-licensing on Cloud cost control. Treat the apps as part of the migration commercials, not an afterthought once both stacks are live.

What is your leverage here?

More than the deadline suggests. Atlassian wants the Cloud migration to land and to report it, which makes the account team willing to discuss credits and date alignment when you raise them early and in writing. A clear migration plan, a scoped overlap, and a credible willingness to time the move on your terms rather than the renewal date give you a real position. The platform context for the destination sits on the Jira Service Management platform page.

The firm has run this sequence across more than 500 engagements and $420M+ in ITSM contract value, averaging a 30% reduction by timing the move and the contracts together rather than separately. The discipline behind it is in our guide to ITSM renewal negotiation.

What does the double payment actually cost you?

Put it in concrete terms. If your Data Center maintenance runs into six figures and your Cloud subscription is similar, a six-month overlap with no credit is half a year of one of those bills paid for nothing, on a platform you are decommissioning. Stretch the overlap to a year on a large estate and the waste is a full duplicate term. That is not a rounding error; on a sizeable migration it is frequently the single largest avoidable cost in the whole project, and it is entirely a function of timing and a credit you either asked for or did not.

The reason it slips through is ownership. The migration team is measured on a clean technical cutover, procurement is measured on the renewal, and nobody owns the seam between them. Assign that seam to one person, give them the migration plan and both contract dates, and the double payment becomes a line item you manage rather than a surprise you absorb.

What to do next

Map your migration timeline, scope the overlap, and bring the Cloud credit and the Data Center renewal date into one conversation before either is signed. When you are ready to run it, the engagement goes through our renewal advisory service on fixed fee or gainshare, and the full transition is mapped in the Atlassian Data Center end of life guide.

Frequently asked questions

Why do you end up paying for both Data Center and Cloud during migration?

Because the two platforms run in parallel for months while you move, and if the Data Center renewal overlaps the Cloud subscription without a credit, you carry both bills. Atlassian offers migration credits and dual-use windows, but you must ask and align the dates.

How long does the dual-licensing overlap usually last?

From a few months on a small instance to a year or more on a large multi-app estate. Scope it deliberately and negotiate a credit or free Cloud period that covers it.

What should you negotiate to avoid double payment?

A Cloud migration credit sized to your timeline, an aligned Data Center renewal date, a co-terminated end date, and price protection on any bridging renewal against the 15 to 40 percent Data Center increase. We average a 30% reduction.