Atlassian Cloud migration. Negotiate the migration framework on your terms.

The Atlassian Cloud migration is the load bearing Atlassian licensing conversation at the 2026 renewal cycle. The publisher's opening position anchors the migration against the customer's full deployment population, with the cumulative effect that Atlassian's preferred trajectory is broad Cloud coverage at the upper end of the customer scale.

A buyer side approach reframes the conversation. The migration is anchored against actual deployment segmentation, actual user counts, the right user tier, the loyalty discount on offer, and the dual track question. Run that way, the migration matches the customer's real estate rather than the publisher's preferred broad Cloud coverage.

This approach typically delivers twenty to thirty five percent improvements in the Atlassian Cloud migration outcome at the upper customer scale. Read the related Atlassian enterprise pricing, the Atlassian Cloud migration guide, and the Atlassian Data Center end of life.

The Atlassian Cloud migration intersects with five principal commercial dimensions:

1. Data Center end of life. The migration is anchored against the Data Center end of life timeline.
2. Cloud tier choice. Standard, Premium, or Enterprise tier on Cloud.
3. User tier. Where the customer's user count lands inside Atlassian's tier ladder.
4. Loyalty discount. The migration loyalty discount offered against the existing Data Center contract.
5. Dual track. How Data Center and Cloud run alongside one another during migration.

The five dimensions compound, which is why the Cloud migration runs as the load bearing Atlassian licensing conversation at the 2026 renewal cycle.

Data Center end of life

Data Center end of life is the principal commercial pressure on the Atlassian Cloud migration. Atlassian anchors the conversation against its preferred Cloud trajectory, and the end of life date for Data Center is what produces the migration timing across the customer's Atlassian estate.

Atlassian typically anchors the migration against its preferred Cloud trajectory at the upper customer scale, with the end of life date producing the migration timing that drives the Cloud contract. A buyer side approach pushes back. The end of life conversation is anchored against the customer's actual Data Center estate and the customer's actual readiness, rather than the publisher's preferred broad timetable.

Read the broader Atlassian Data Center end of life for the full Data Center picture.

Cloud tier choice

Tier choice is the second principal commercial dimension. Atlassian segments Cloud across four tier populations, and the tier the customer lands on is what drives the Cloud licensing cost.

1. Free tier. For the smallest deployments.
2. Standard tier. For mainstream deployments without advanced governance.
3. Premium tier. Adds advanced administration, analytics, and uptime SLA.
4. Enterprise tier. For the upper customer scale, with unlimited instances, advanced security, and dedicated support.

The cumulative effect of the four tier choices is an Atlassian Cloud tier mapping that should track the customer's actual needs rather than the publisher's preferred broad tier upgrade. Read the broader Atlassian enterprise pricing for tier pricing detail.

User tier

User tier is the third principal commercial dimension. Atlassian segments Cloud across four user tier bands, and where the customer's user count lands is what drives the Cloud licensing cost.

1. Small user tier. User count below the small tier threshold.
2. Medium user tier. User count between the small and large tier thresholds.
3. Large user tier. User count above the large tier threshold.
4. Unlimited user tier. Available at the Enterprise tier.

The cumulative effect of the four user tier bands is an Atlassian user tier mapping that should track actual usage rather than the publisher's preferred broad user tier escalation. Read the broader Atlassian Cloud migration guide for the user tier detail.

Loyalty discount

The loyalty discount is the fourth principal commercial dimension. Atlassian offers the loyalty discount against the existing Data Center contract at the migration cycle, and it is the principal commercial lever during migration.

1. Year one loyalty discount. Applied to the first year of the Cloud contract.
2. Year two loyalty discount. Applied to the second year of the Cloud contract.
3. Year three loyalty discount. Applied to the third year of the Cloud contract.
4. Bespoke loyalty discount. Negotiated at the upper customer scale.

The cumulative effect of the four discount steps is an Atlassian loyalty discount mapping that should track the customer's actual position rather than the publisher's preferred broad three year decay.

Dual track

Dual track is the fifth principal commercial dimension. Atlassian offers dual track operation against the broader Atlassian estate at the migration cycle, and it runs alongside the Data Center contract and the Cloud contract during migration.

Dual track typically segments across four populations:

1. Parallel dual track. Data Center runs alongside Cloud throughout the migration cycle.
2. Staged dual track. Data Center migrates to Cloud in phases across the migration cycle.
3. Partial dual track. Part of the Data Center estate migrates to Cloud; the remainder stays on Data Center.
4. Bespoke dual track. A negotiated dual track arrangement tailored to the customer.

Read the broader Atlassian Cloud migration negotiation guide for the dual track detail.

Exposure

Exposure on the Atlassian Cloud migration typically segments across four populations:

1. User count drift. User counts creep upward across the Cloud contract.
2. Tier escalation. The Cloud tier escalates from Standard to Premium or Premium to Enterprise.
3. Loyalty discount expiry. The migration loyalty discount expires, exposing the customer to full list Cloud pricing.
4. Migration support cost. Professional services and integration cost during migration.

Exposure typically delivers material cost across the Atlassian Cloud migration at the migration cycle. Read the broader Atlassian Cloud migration guide for the exposure detail.

The buyer side moves

A buyer side approach to the Atlassian Cloud migration has eleven moves that compound across the Atlassian contract:

1. Anchor the Cloud migration against actual deployment, actual users, actual user tier, and the loyalty discount on offer rather than the publisher's preferred broad Cloud trajectory.
2. Anchor the Data Center end of life conversation against the customer's actual Data Center estate, so the timing matches the customer's actual readiness.
3. Run tier choice across the four Cloud tier populations and pick the tier that matches the customer's actual needs.
4. Run user tier mapping across the four user tier bands so user pricing tracks actual usage.
5. Run the loyalty discount across the four discount steps so it matches the customer's actual contract position.
6. Run dual track across the four dual track options so the migration approach matches the customer's actual estate.
7. Negotiate the Cloud tier against the publisher's preferred broad upgrade pressure.
8. Negotiate the user tier against the publisher's preferred broad user count assumptions.
9. Negotiate the loyalty discount against the publisher's preferred broad three year decay.
10. Negotiate dual track against the publisher's preferred broad cutover pressure.
11. Run the broader Atlassian renewal alongside the Cloud migration, so the migration sits inside the renewal cycle rather than running as a separate conversation.

The approach is set out in detail in the Atlassian Cloud migration negotiation guide, the Atlassian enterprise pricing landing, and the broader Atlassian Cloud migration guide. Read the related Atlassian Data Center end of life and the Atlassian enterprise pricing download.

How we engage

• Atlassian migration scoping. Six week engagement that scopes the Cloud migration, anchors the user tier, and identifies the immediate commercial moves at the next Atlassian renewal cycle. Atlassian advisory practice.
• Atlassian renewal negotiation. Renewal negotiation engagement that handles the Cloud migration, Data Center end of life, user tier, and the broader Atlassian renewal conversation across the renewal cycle. Atlassian renewal practice.
• Atlassian Cloud advisory. Advisory engagement that handles tier choice, user tier, loyalty discount, and the broader Atlassian Cloud contract across the migration cycle. Atlassian Cloud advisory.
• Vendor Shield. Always on multi vendor management posture that covers Atlassian alongside the broader enterprise software estate. Vendor Shield.
• Run the calculator. The software spend assessment sizes the Atlassian contract against the customer's actual deployment.