The buyers who paid least set the terms before touching the migration tooling, because a loyalty credit applied to an inflated estate is still an inflated estate
The forced move is the moment Atlassian has the most leverage. Everything a buyer wins is won before the migration date is agreed.
Prepared by Redress Compliance · August 19, 2026 · Atlassian Cloud migrations advised. 15 to 25 files, 2024 to 2025.
Executive summary
Inactive user drag: 10 to 25 percent of migrated accounts were inactive and pushed estates into a higher priced user band, across roughly 15 to 25 migrations advised between 2024 and 2025.
Loyalty decay: migration credits fell by a quarter or more for buyers who delayed past the early window, which is the pressure the vendor is relying on.
Edition overreach: teams moved to Cloud Enterprise for one feature and paid the full premium across every user on the estate.
The renewal after migration is where the real uplift lands, so it has to be capped in the migration deal rather than revisited afterwards.
Why is the Atlassian Cloud migration a negotiation?
Because Atlassian is ending the alternatives. With Server retired and Data Center under pressure, the move to Cloud is effectively forced, which is exactly when a vendor holds the most leverage.
The end of support timeline is published on the cloud migration page. Use it to plan, but treat the migration offer as an opening position rather than a fixed price.
What Atlassian wants from the move
- Recurring revenue: Cloud converts a one time license plus maintenance into an annual subscription.
- Edition upsell: the migration is the moment to push Premium and Enterprise tiers.
- Lock in: once data is in Cloud, switching cost rises sharply.
What the buyer wants in return
A clean user count, the full loyalty credit, a generous dual subscription window and a capped renewal. Each of those is negotiable if you raise it before committing to the migration date.
Wider context sits in the Atlassian licensing hub.
How does Atlassian Cloud pricing work in 2026?
Per user, in tiers, across Standard, Premium and Enterprise editions. The tier band you fall into can matter more than the per user rate.
So the user count is the first thing to get right, and it is the thing most estates carry across untouched. Rates are published on the Jira pricing page and the Confluence pricing page.
The three editions
- Standard: core function for most teams.
- Premium: higher uptime, advanced admin, more automation.
- Enterprise: multi instance scale and central governance.
Why the user band is the first lever
Pricing steps at user thresholds, so trimming a small number of inactive accounts can drop you into a cheaper band. Clean the user list before you quote, not after.
The four levers and where they apply
| Lever | What it controls | Typical buyer side win |
|---|---|---|
| User cleanup | Tier and price band | Drop a band by removing inactive accounts |
| Loyalty credit | Migration discount | Full early window credit, not the decayed rate |
| Dual window | Parallel run time | Longer overlap to de risk cutover |
| Renewal cap | Post migration uplift | Capped increase versus open ended |
- Your quote benchmarked against real closed Atlassian migrations by user band
- Renewal cap and dual window language flagged with replacement wording
- The inactive user position quantified, so the band question is settled first
What migration traps cost buyers the most?
The costly traps are structural and surface after the migration rather than during it. They are written into the renewal mechanics and the user count you carry across.
Three post migration traps
- Uncapped renewal: the first renewal after migration is where the real uplift lands.
- Tier creep: user growth quietly pushes you into the next price band.
- Edition stickiness: downgrading an edition later is harder than choosing right at the start.
How to time the migration window
Plan against the published end of support dates and negotiate the dual subscription window. Atlassian sets out its trust and security policy, which helps justify the overlap you ask for.
A longer dual subscription window costs little to ask for and removes most of the risk from a rushed cutover.
The Atlassian Cloud migration playbook
The user cleanup, the loyalty credit window, the dual subscription overlap and the renewal cap to write before you agree a date.
Get the playbook →What 15 to 25 Atlassian migrations showed
Across the Cloud migrations advised on between 2024 and 2025, the buyers who paid least set the terms before touching the migration tooling.
The three patterns that recurred
- Inactive user drag: 10 to 25 percent of migrated accounts were inactive and pushed estates into a higher priced user band.
- Loyalty decay: migration loyalty credits fell by a quarter or more for buyers who delayed past the early window.
- Edition overreach: teams moved to Cloud Enterprise for one feature and paid the full premium across every user.
All three compound. An oversized edition applied to an inflated user count, renewed without a cap, is the expensive version of the same migration.
Research briefingConverting off Data Center before the deadlineWhat the end of support timeline actually forces, and which terms are still open while the vendor holds the leverage.
Where the common advice on Atlassian migration is wrong
The standard advice is to migrate fast to capture the loyalty discount before it expires. We disagree.
In roughly half of the moves advised, the rush meant inactive users and oversized editions were carried straight into Cloud, so the loyalty credit was dwarfed by a baseline that was too big.
Clean the user list and right size the edition first, then migrate with the credit applied to a smaller, correct estate. Speed that locks in waste is not a saving.
The loyalty discount is real, but a discount applied to an inflated estate still leaves you paying for users who left and features no one uses.
Enough on its own to push an estate into a higher priced band.
Credits fell by a quarter or more past the early window.
Standard, Premium and Enterprise, matched to evidenced need.
Your first five moves
- Export the full Atlassian user list and identify every inactive account before anybody quotes a band.
- Remove the inactive users to confirm which price band you should actually land in.
- Match the edition to evidenced need rather than to the one feature that started the conversation.
- Negotiate the dual subscription window long enough to de risk the cutover, because it costs little to ask for.
- Cap the first post migration renewal in the migration deal itself, since that is where the real uplift lands.
Frequently asked questions
Why is the migration a negotiation at all?
Because Atlassian is ending the alternatives. With Server retired and Data Center under pressure the move is effectively forced, which is when a vendor holds the most leverage.
What separated the buyers who paid least?
They set the terms before touching the migration tooling, rather than migrating first and negotiating against a baseline already locked in.
How many migrated accounts are inactive?
Between 10 and 25 percent in the files advised, which is frequently enough on its own to push an estate into a higher priced user band.
What happens to the loyalty credit if you wait?
It decays. Migration credits fell by a quarter or more for buyers who delayed past the early window.
Should you migrate fast to capture the credit?
No. In roughly half the moves advised, the rush carried inactive users and oversized editions straight into Cloud, and the credit was dwarfed by the baseline.
Why does the user band matter more than the rate?
Because pricing steps at user thresholds. Trimming a small number of inactive accounts can drop you into a cheaper band entirely.
What is edition overreach?
Teams moving to Cloud Enterprise for one feature and paying the full premium across every user on the estate.
What is the dual subscription window?
A period where the old and new estates run together. Its length is negotiable, it costs little to ask for, and it removes most of the cutover risk.
Where does the real uplift land?
On the first renewal after migration. That is why the cap belongs in the migration deal rather than in a later conversation.
Can you downgrade an edition later?
It is harder than choosing correctly at the start. Edition stickiness is one of the three traps that surface after the migration rather than during it.