Atlassian Hub
Atlassian Cloud migration. Negotiate on your terms.
The Atlassian Cloud migration is a negotiation, not a clerical move. Read the loyalty discounts, the dual subscription window, and the user banding before you commit.
The Atlassian Cloud migration is a negotiation, not a clerical move. Read the loyalty discounts, the dual subscription window, and the user banding before you commit.
The forced move from Server and Data Center to Cloud is the moment Atlassian has the most leverage, so the buyer wins are the terms you set before you migrate.
The migration is 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 Atlassian end of support timeline is published on the Atlassian cloud migration page. Use it to plan, but treat the migration offer as an opening position, not a fixed price.
A clean user count, the full loyalty credit, a generous dual subscription window, and a capped renewal. Each of these is negotiable if you raise it before committing to the migration date.
Atlassian migration 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 |
Atlassian Cloud prices 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.
Each edition adds capability and cost, set out on the Jira pricing page. Premium adds availability and admin controls, while Enterprise adds scale and unlimited instances. Many teams pay for Enterprise to get one feature.
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 standard advice is to migrate fast to capture the loyalty discount before it expires. We disagree. In roughly half of the Atlassian moves we 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. The buyer side move is to 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.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
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.
The costly traps are structural and surface after the migration, not during it. They are written into the renewal mechanics and the user count you carry across.
Plan against the published end of support dates and negotiate the dual subscription window. Atlassian outlines support and security policy on its trust and security pages, which helps justify the overlap you ask for. The Confluence pricing page shows how editions map across products.
Atlassian Cloud is priced per user in tiers across Standard, Premium, and Enterprise editions. Pricing steps at user thresholds, so the band your user count lands in often matters more than the per user rate itself.
Effectively yes, because Atlassian has retired Server and is steering customers off Data Center toward Cloud. That makes the move a negotiation, since the vendor holds maximum leverage when the alternatives are being withdrawn.
A dual subscription window lets you run the old Server or Data Center estate and the new Cloud estate in parallel during cutover. Its length is negotiable, and a longer overlap reduces the risk of a rushed migration.
Yes, migration loyalty credits are time limited and shrink the longer you wait. Buyers who delay past the early window often lose a quarter or more of the available credit, so the window matters as much as the rate.
Only if evidenced need justifies it. Many teams move to Enterprise for a single feature and pay the premium across every user. Match the edition to real requirements rather than buying the top tier by default.
Inactive accounts inflate the user count and can push you into a higher priced tier band. Cleaning the user list before you quote often drops you a band and saves more than the migration discount itself.
The first renewal after migration is where the largest uplift usually lands, not the migration quote. Cap that renewal increase in writing before you sign the migration deal, or the saving you negotiated erodes quickly.
Clean the user list, right size the edition, confirm the loyalty credit, and price a dual subscription window before you commit a date. Bring that evidence to the table so the migration applies to a correct, smaller estate.
Loyalty discount math, dual subscription windows, user tier banding, and the buyer side levers that move a Cloud Enterprise quote.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
