Migrating Atlassian to Cloud usually means running Data Center in parallel for a window. That window is where buyers double pay. This guide lays out the dual licensing cost and the levers that contain it.
Migrating Atlassian to Cloud usually means running Data Center in parallel for a window. That overlap is where buyers double pay. The lever is a short, funded window with migration credits, not an open ended dual run.
Atlassian retired Server, so the live choice is Cloud or Data Center. Most enterprises are moving to Cloud, and most cannot flip a switch. They run both for a period, and that period costs money.
The Atlassian migration guidance frames the move as a project. The licensing question is simpler. How long do you pay for two platforms, and who funds the overlap.
A parallel run is rarely a choice. It is the gap between starting a migration and finishing it, during which both platforms must stay live.
Projects, history, and marketplace apps move in phases. The Atlassian Data Center licensing stays active until the last team is cut over, so both bills run together.
Not every Data Center app has a Cloud equivalent on day one. Teams wait for parity per the Atlassian Cloud migration resources, and the wait extends the parallel run if it is not planned and time boxed.
The dual cost is the sum of both platforms for the overlap, plus any tier mismatch. It is predictable, which means it is controllable.
During the window you pay Data Center maintenance and Cloud subscription together. The longer the window, the larger the double bill. A drifting window is the most common overrun.
The Atlassian Jira pricing shows Cloud and Data Center price on user tiers that do not line up neatly. Buying the wrong Cloud tier while still paying Data Center compounds the overlap cost.
Atlassian dual run cost drivers
| Driver | Effect | Lever |
|---|---|---|
| Window length | Both bills run together | Time box and fund the window |
| Tier mismatch | Wrong Cloud tier during overlap | Size the Cloud tier to real users |
| DC renewal timing | Locks 12 months | Align renewal to cutover |
| Unclaimed credits | Pays full price twice | Claim migration and loyalty credits |
The common advice is to renew Data Center for a full year and migrate to Cloud at a comfortable pace. We disagree. In roughly half of the migrations we have reviewed, a leisurely parallel run added 10 to 25 percent to the total cost and a mid migration Data Center renewal locked the buyer 12 months past the intended cutover. The buyer side move is to time box the window, align the Data Center renewal to the cutover date, and claim the migration credits before they expire. A relaxed migration feels safer and quietly funds two platforms for longer than the project needs, which is exactly the outcome the renewal calendar encourages.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The Atlassian dual run is not a technical cost. It is a calendar cost. Shorten the window and align the renewal, and the double bill shrinks with it.
Three levers contain the parallel run cost. Each is about timing and entitlement, not about discount alone.
Set a hard cutover date and fund the overlap to it. A window with a deadline and an owner does not drift. A window without one always does.
Do not sign a full year Data Center renewal in the middle of a migration. Negotiate a short term or co term the Data Center end date to the planned cutover.
The right window is the shortest one your teams can actually deliver. Every extra month is a month of paying twice.
Work back from a fixed cutover date. Sequence teams by complexity and app dependency. Hold the date, and align the Data Center renewal so it expires at or just after cutover.
Atlassian migrations require a parallel run because projects, history, and marketplace apps move in phases, so Data Center stays live until the last team cuts over to Cloud. During that window both platforms are licensed and billed at the same time.
Running Atlassian Cloud and Data Center in parallel costs the sum of both platforms for the overlap window plus any tier mismatch. In our engagements a drifting parallel run added 10 to 25 percent to the total migration cost in double licensing.
No. Atlassian retired Server, so the two live options are Cloud and Data Center. Most enterprises are moving to Cloud, and the licensing question is how long they pay for Data Center in parallel during the migration.
Avoid double paying by time boxing the migration window, aligning the Data Center renewal to the cutover date, sizing the Cloud tier to real users, and claiming migration credits before they expire. The overlap cost is driven by the calendar, so the calendar is the lever.
Avoid signing a full year Data Center renewal in the middle of a migration, because it can lock you 12 months past the intended cutover. Negotiate a short term renewal or co term the Data Center end date to the planned cutover instead.
No. Atlassian Cloud and Data Center price on user tiers that do not line up neatly, so buying the wrong Cloud tier while still paying Data Center compounds the overlap cost. Size the Cloud tier to real active users before the parallel run begins.
Yes. Migration and loyalty credits can offset a meaningful part of the move, yet they went unclaimed in roughly half of the migrations we reviewed. They are time bound, so claim them before they expire rather than discovering them after the window closes.
An Atlassian parallel run should be the shortest window your teams can deliver, planned back from a fixed cutover date and sequenced by complexity and app parity. Every extra month is a month of paying for two platforms at once.
Atlassian Cloud and Data Center benchmarks, dual run cost control, migration credits, and the buyer side moves across the Atlassian estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
