Atlassian Cloud migration. The buyer side negotiation framework.

A working framework for CIOs, CFOs, and procurement teams running the Atlassian Server or Data Center to Cloud migration negotiation, with the eight buyer side moves that recover eighteen to thirty four percent against the Atlassian account team's opening Cloud migration proposal.

Executive Summary

The Atlassian Cloud migration is one of the largest forced commercial transitions in the enterprise software estate in 2026. The Atlassian Server end of support deadline closed in February 2024 and the Atlassian Data Center renewal cycle continues to drive enterprise customers onto the Cloud subscription model. The migration is rarely a like for like commercial substitution. The published Cloud per user list pricing typically runs forty to one hundred percent above the equivalent Data Center user pricing, the Cloud edition catalog introduces Premium and Enterprise tiers that did not map cleanly onto the Data Center baseline, and the Marketplace app re entitlement adds a parallel commercial conversation that is rarely surfaced in the account team's migration framing. The migration is therefore not a technical exercise. The migration is a commercial reset, and the buyer side discipline at the negotiation determines whether the enterprise pays the full Cloud migration premium or recovers the structural leverage available at the migration cycle.

This paper sets out the Redress Compliance Atlassian Cloud migration negotiation framework. The framework coordinates eight commercial moves across a single migration cycle: the edition mapping from Data Center to Cloud Standard, Premium, or Enterprise; the user count restructure against the audited active baseline; the Migration Investment Program credit attach; the Loyalty Discount attach for existing Data Center customers; the Marketplace app re entitlement at the Cloud catalog; the multi year price lock; the Cloud renewal uplift cap; and the alternative tooling conversation that anchors the negotiation against Microsoft Azure DevOps, GitLab Ultimate, GitHub Enterprise, ServiceNow, and Linear. Read the related Atlassian Cloud Enterprise negotiation download, the Atlassian Cloud migration 2026 download, the GitHub Enterprise negotiation download, the GitLab Ultimate negotiation download, and the multi vendor negotiation scorecard. Run against the practice corpus, the coordinated framework typically delivers eighteen to thirty four percent recovery against the Atlassian account team's opening Cloud migration proposal across the contracted three year term, with the upper end of the range available at the Cloud Enterprise tier when the buyer credibly stages the alternative tooling conversation in parallel with the migration negotiation.

Background and Market Context

The Atlassian commercial landscape changed structurally in February 2024 when the Atlassian Server end of support deadline closed. The closure forced every Server customer to either migrate to Cloud, migrate to Data Center, or accept that the underlying products no longer receive security patches or feature updates. The forced migration created a one time commercial reset for every enterprise Atlassian customer. The Atlassian account team uses the forced migration to anchor the next three year Cloud commitment at the highest possible edition, the highest possible user count, and the longest possible commitment term. The buyer side response needs to anchor against the account team's preferred framing rather than accept the framing as the starting point.

The Data Center to Cloud migration continues to run alongside the Server end of support exit. The Atlassian Data Center product remains supported, but the Atlassian account teams in 2026 are aggressively repositioning Data Center customers onto the Cloud subscription model. The Data Center customer that holds on Data Center faces three structural cost pressures. First, the Data Center user pricing has carried published annual price increases at five to fifteen percent above the prior contracted rate across the past three renewal cycles. Second, the Data Center governance feature catalog has fallen behind the Cloud Enterprise catalog, which limits the customer's ability to deploy advanced automation, sandboxing, and audit features without migrating. Third, the Marketplace app catalog on Data Center has narrowed as third party app developers shift their feature investment onto the Cloud platform.

The financial stakes scale with the customer footprint. A mid market enterprise running one thousand to three thousand Atlassian users on Server or Data Center faces a one to four million dollar three year Cloud commitment at the migration. A large enterprise running five thousand to fifteen thousand Atlassian users faces a five to twenty million dollar three year Cloud commitment. An upper customer scale enterprise running twenty thousand to fifty thousand Atlassian users faces a twenty to seventy million dollar three year Cloud commitment. The discount band differences across the Cloud Standard, Premium, and Enterprise editions translate into one to twenty million dollar swings in the all in Cloud migration cost across the contracted term, which means the buyer side discipline at the migration is one of the highest leverage commercial activities the CIO and procurement team run across the contracted year.

The Atlassian product catalog at the Cloud migration includes Jira Software, Jira Service Management, Confluence, Jira Product Discovery, Compass, Atlas, Loom, and the broader Atlassian Marketplace app catalog. The catalog interacts commercially with adjacent enterprise tooling at Microsoft Azure DevOps, GitHub Enterprise, GitLab Ultimate, ServiceNow ITSM, Linear, Notion, Slack, and the broader collaboration tooling estate. The buyer side response anchors the Atlassian Cloud migration against the alternative tooling conversation rather than running the migration as a single product conversation. The competitive narrative does not need to be fully implemented. The competitive narrative needs to be credibly framed at the migration negotiation. Read the related GitHub Enterprise negotiation download, the GitLab Ultimate negotiation download, the ServiceNow services practice, and the Microsoft services practice.

The Atlassian account team also operates a documented commercial framework inside each enterprise account. The framework includes the Loyalty Discount program for existing Server and Data Center customers, the Migration Investment Program credit for documented migration milestones, the multi product discount for customers committing to Jira, Confluence, and Jira Service Management on the same Cloud contract, and the multi year price lock that caps the annual price increase across the contracted term. The framework is rarely surfaced as a coordinated commercial conversation. The framework is typically scattered across multiple account team owners and is surfaced one move at a time as the account team responds to the buyer side leverage at each negotiation stage.

The buyer side Atlassian Cloud migration negotiation therefore runs against four structural realities. First, the Atlassian Cloud migration is a forced commercial reset rather than a like for like substitution. Second, the Cloud edition catalog requires explicit mapping against the customer's required governance feature set rather than accepting the account team's Cloud Enterprise framing as the default. Third, the user count restructure against the audited active baseline is the single highest leverage commercial move at the migration. Fourth, the Migration Investment Program credit, the Loyalty Discount, and the multi year price lock are typically not surfaced unless the buyer raises each as a distinct line item at the migration order form.

Edition Mapping: Cloud Standard, Premium, and Enterprise

The first commercial move is the edition mapping. The Atlassian Cloud catalog runs three editions on Jira, Jira Service Management, and Confluence: Cloud Standard, Cloud Premium, and Cloud Enterprise. Each edition carries a distinct per user price, a distinct governance feature set, and a distinct support tier.

Cloud Standard

Cloud Standard is the entry edition. The published per user price typically sits at the lowest tier of the Cloud catalog. Cloud Standard includes the core Jira, Jira Service Management, and Confluence functionality with limited governance, limited automation, and limited support. Cloud Standard is the appropriate edition for the customer that is migrating off Server or Data Center to capture the underlying functionality without adopting the advanced governance feature catalog.

Cloud Premium

Cloud Premium sits at the middle tier. The published per user price typically runs fifty to seventy percent above Cloud Standard. Cloud Premium adds advanced automation, advanced reporting, sandbox environments, project archiving, and twenty four by seven support. Cloud Premium is the appropriate edition for the customer that requires the advanced automation and reporting catalog but does not require the audit logs, release tracks, or the unlimited automation tier.

Cloud Enterprise

Cloud Enterprise is the upper tier. The published per user price typically runs two to three times above Cloud Standard. Cloud Enterprise adds unlimited automation, unlimited sandbox environments, release tracks, audit logs, data residency, and the Atlassian enterprise support tier with a dedicated technical account manager. Cloud Enterprise is the appropriate edition for the customer that operates the Atlassian estate at the upper user scale, requires data residency or audit log compliance, or operates the release track and sandbox catalog across multiple production tenants.

The buyer side edition map

The Atlassian account team typically anchors the Cloud migration against Cloud Enterprise. The framing assumes the customer requires every governance feature in the Enterprise catalog. The buyer side response inverts the framing. The buyer side response maps the customer's required governance features against the lowest viable edition. The map typically reveals that fifty to seventy percent of the customer's active user base can run on Cloud Standard with the remaining thirty to fifty percent of the user base running on Cloud Premium or Cloud Enterprise. The mixed edition deployment is supported by Atlassian Cloud at the contract level and is one of the highest leverage commercial moves at the migration. The practice has documented engagements where the mixed edition deployment recovered an additional fourteen to twenty six percent against the Atlassian account team's opening Cloud Enterprise proposal.

User Count Restructure and the Audited Active Baseline

The second commercial move is the user count restructure. The Atlassian Cloud subscription is billed per active user across the contracted term. The Atlassian account team typically anchors the Cloud migration against the customer's contracted Server or Data Center user count rather than the audited active user baseline. The restructure against the audited baseline is the single highest leverage commercial move at the migration.

The audited active user count

The audited active user count is the user population that has logged into the Atlassian estate across the prior ninety days. The audit typically reveals that the active user count sits twenty to forty percent below the contracted user count. The gap is the result of inactive users, departed employees, contractor accounts that were not deprovisioned, service accounts that were billed as named users, and duplicate accounts across multiple Atlassian instances. The buyer side response audits the active user count against the contracted user count at the migration preparation, removes the inactive and duplicate users, and rightsizes the contracted Cloud user count against the audited baseline.

The user tier discount band

The Atlassian Cloud per user price drops at defined user tier breakpoints. The published Cloud user tier breakpoints sit at one hundred, two hundred fifty, five hundred, one thousand, two thousand, five thousand, ten thousand, and fifteen thousand users. The discount band at each tier breakpoint ranges from three to twelve percent against the prior tier. The buyer side response sizes the contracted user count just above the next tier breakpoint rather than at the prior tier ceiling, because the additional user count at the upper tier carries the contracted tier discount band across the full contracted user count.

The user count growth provision

The Atlassian Cloud subscription typically forces the customer to true up the user count at the renewal cycle. The true up provision allows the Atlassian account team to expand the contracted user count at the prior contracted per user rate without renegotiating the underlying edition discount. The buyer side response inserts a user count growth provision in the original Cloud order form that allows the customer to expand the contracted user count by a defined percentage at no recovery penalty across the contracted term. The practice has documented engagements where the user count growth provision delivered an additional five to eleven percent against the Atlassian account team's opening proposal at the contracted renewal cycle.

Migration Investment Program and the Loyalty Discount

The third and fourth commercial moves are the Atlassian Migration Investment Program credit and the Loyalty Discount attach. These two commercial vehicles are typically scattered across multiple Atlassian account team owners and are rarely surfaced as a single commercial conversation at the migration negotiation.

The Migration Investment Program credit

The Atlassian Migration Investment Program is a funded migration credit that the Atlassian account team can attach to a documented Server or Data Center to Cloud migration. The credit is funded against documented migration milestones, including the migration readiness assessment, the migration pilot deployment, the migration cutover, and the post migration adoption milestones. The published Migration Investment Program credit typically delivers twenty to forty percent of the first year Cloud subscription value at the upper customer scale. The credit is typically not surfaced unless the buyer raises the migration credit as a distinct line item at the original Cloud order form. The buyer side response treats the Migration Investment Program credit as a distinct commercial vehicle alongside the underlying Cloud subscription discount and inserts a credit attach provision in the original Cloud order form.

The Loyalty Discount

The Atlassian Loyalty Discount is a published discount available to existing Server and Data Center customers that migrate to Cloud at the contracted Server or Data Center renewal cycle. The Loyalty Discount typically delivers five to fifteen percent against the published Cloud subscription rate at the first year of the Cloud commitment. The discount is structured as a multi year tapered discount that decreases across the contracted Cloud term. The buyer side response inserts the Loyalty Discount as a distinct line item at the Cloud order form and renegotiates the tapered discount profile against a flat discount profile across the contracted term, which preserves the discount value across the multi year commitment.

The multi product discount

The Atlassian Cloud catalog runs a multi product discount for customers committing to Jira Software, Jira Service Management, and Confluence on the same Cloud contract. The multi product discount typically delivers five to twelve percent against the published per product rate at the upper customer scale. The discount is structured against the combined product spend rather than the individual product spend. The buyer side response maps the customer's full Atlassian product catalog at the migration preparation and renegotiates the multi product discount against the combined product spend, which is typically not the account team's opening framing.

The Marketplace App Re Entitlement

The fifth commercial move is the Marketplace app re entitlement. The Atlassian Marketplace app catalog runs as a parallel commercial conversation alongside the underlying Cloud subscription and is rarely coordinated against the Cloud migration negotiation.

The Marketplace catalog

The Atlassian Marketplace runs more than five thousand third party apps that extend the Jira, Confluence, and Jira Service Management functionality. The Marketplace apps installed on Server or Data Center are not automatically entitled on Cloud. The customer that migrates to Cloud needs to re entitle every Marketplace app at the Cloud catalog. The re entitlement carries three structural commercial moves. First, the buyer maps every Marketplace app at the Server or Data Center estate against the active usage baseline. Second, the buyer identifies the Cloud equivalent for each in scope Marketplace app or the alternative app at the Cloud catalog. Third, the buyer renegotiates the app entitlement at the Cloud catalog with the third party app vendor.

The Marketplace app pull through

The Atlassian Marketplace app pull through is the structural arrangement where the Marketplace app spend transacted through the Atlassian billing stream counts against the Atlassian Cloud subscription commitment at a defined credit rate. The pull through rate sits at the published rate for the in scope Marketplace apps. The buyer side response maps the Marketplace app pull through at the migration preparation and renegotiates the third party app pricing against the bundled Cloud subscription rather than the standalone app rate. The practice has documented engagements where the Marketplace app re entitlement recovered an additional five to twelve percent against the Atlassian account team's opening Cloud migration proposal.

The Multi Year Price Lock and the Renewal Uplift Cap

The sixth, seventh, and eighth commercial moves are the multi year price lock, the renewal uplift cap, and the alternative tooling conversation that anchors the Cloud migration against the broader collaboration tooling estate.

The multi year price lock

The Atlassian Cloud subscription typically carries an annual price increase across the contracted term. The published annual price increase typically sits at five to fifteen percent above the prior contracted per user rate. The multi year price lock is the buyer side provision that caps the annual price increase across the contracted term. The published price lock typically caps the annual price increase at the consumer price index plus a defined percentage, with the cap typically sitting at three to seven percent for the upper customer scale. The buyer side response inserts the multi year price lock at the original Cloud order form and benchmarks the contracted price lock against documented engagements at the upper customer scale.

The renewal uplift cap

The renewal uplift cap is the related provision that caps the contracted per user rate at the Cloud renewal cycle. The cap is typically structured at the consumer price index plus a defined percentage, with the cap typically sitting at five to ten percent at the renewal cycle. The buyer side response inserts the renewal uplift cap at the original Cloud order form and ties the cap to the documented engagement benchmarks at the upper customer scale. The renewal uplift cap is one of the highest structural leverage moves at the Cloud renewal cycle, because the cap removes the most common Atlassian commercial lever at the renewal negotiation.

The alternative tooling conversation

The Atlassian Cloud migration negotiation anchors against the alternative tooling conversation at Microsoft Azure DevOps, GitHub Enterprise, GitLab Ultimate, ServiceNow ITSM, Linear, and the broader collaboration tooling catalog. The competitive narrative does not need to be fully implemented. The competitive narrative needs to be credibly framed at the migration negotiation. The Atlassian account teams in 2026 will move aggressively on the Cloud subscription discount band, on the Migration Investment Program credit, and on the multi year price lock when the buyer credibly opens the alternative tooling conversation in parallel with the Cloud migration negotiation. Read the related GitHub Enterprise negotiation download, the GitLab Ultimate negotiation download, the ServiceNow Now Platform negotiation download, and the Microsoft EA renewal playbook.

Common Mistakes and Traps

1. Accepting the Atlassian account team's Cloud Enterprise framing without auditing the required governance features. The framing assumes every active user requires the Enterprise governance catalog. The corrective move maps the required governance features against the active user base and runs a mixed edition deployment with the majority of the user base on Cloud Standard and the minority on Cloud Premium or Cloud Enterprise.
2. Sizing the Cloud migration against the contracted Server or Data Center user count. The contracted user count typically sits twenty to forty percent above the audited active user baseline. The corrective move audits the active user count across the prior ninety days, removes inactive and duplicate users, and rightsizes the contracted Cloud user count against the audited baseline.
3. Missing the Migration Investment Program credit at the original Cloud order form. The credit is typically not surfaced unless the buyer raises the migration credit as a distinct line item. The corrective move inserts the Migration Investment Program credit attach provision in the original Cloud order form with documented migration milestones across the contracted term.
4. Accepting the tapered Loyalty Discount profile across the contracted Cloud term. The tapered discount profile decreases across the contracted term and erodes the discount value at the back end of the commitment. The corrective move renegotiates the tapered discount profile against a flat discount profile across the contracted term, which preserves the discount value across the multi year commitment.
5. Skipping the Marketplace app re entitlement audit at the migration preparation. The Marketplace app re entitlement is a parallel commercial conversation that is rarely coordinated against the Cloud migration negotiation. The corrective move maps every Marketplace app at the Server or Data Center estate, identifies the Cloud equivalent or alternative, and renegotiates the app entitlement at the Cloud catalog with the third party app vendor.
6. Accepting the published annual price increase without a multi year price lock. The published annual price increase typically sits at five to fifteen percent above the prior contracted per user rate and compounds across the contracted Cloud term. The corrective move inserts a multi year price lock at the original Cloud order form that caps the annual price increase at the consumer price index plus a defined percentage.

Five Recommendations from Redress Compliance

1. Map the required governance features against the lowest viable Cloud edition and deploy a mixed edition model. The Atlassian account team typically anchors the Cloud migration against Cloud Enterprise on the assumption that every active user requires the Enterprise governance catalog. The corrective action maps the required governance features against the active user base and runs a mixed edition deployment with fifty to seventy percent of the user base on Cloud Standard and the remaining thirty to fifty percent on Cloud Premium or Cloud Enterprise. Measure the move at the all in Cloud subscription cost, with a target of fourteen to twenty six percent recovery against the standard Cloud Enterprise framing. Timing window: complete the governance feature mapping at least one hundred twenty days before the migration cutover.
2. Audit the active user count and rightsize the contracted Cloud user count against the audited baseline. The Atlassian account team typically sizes the Cloud migration against the contracted Server or Data Center user count, which sits twenty to forty percent above the audited active user baseline. The corrective action audits the active user count across the prior ninety days, removes inactive and duplicate users, and rightsizes the contracted Cloud user count against the audited baseline. Measure the move at the recovered user count value, with a target of twelve to twenty two percent recovery against the standard contracted user count. Timing window: complete the active user audit at least sixty days before the migration cutover.
3. Insert the Migration Investment Program credit and the Loyalty Discount as distinct line items in the original Cloud order form. The Migration Investment Program credit and the Loyalty Discount are typically not surfaced unless the buyer raises each as a distinct line item at the migration order form. The corrective action inserts the Migration Investment Program credit attach provision in the original Cloud order form with documented migration milestones across the contracted term, and inserts the Loyalty Discount as a flat discount profile rather than the tapered discount profile across the contracted Cloud term. Measure the move at the recovered first year Cloud subscription value, with a target of eight to fifteen percent recovery against the standard Cloud commitment proposal.
4. Renegotiate the Marketplace app catalog at the Cloud migration with the third party app vendors. The Marketplace app re entitlement is a parallel commercial conversation that the Atlassian account team rarely coordinates with the underlying Cloud subscription negotiation. The corrective action maps every Marketplace app at the Server or Data Center estate against the active usage baseline, identifies the Cloud equivalent or alternative app, and renegotiates the app entitlement at the Cloud catalog with each in scope third party app vendor. Measure the move at the recovered Marketplace spend, with a target of five to twelve percent recovery against the standard Marketplace app renewal proposal. Timing window: complete the Marketplace mapping at least one hundred twenty days before the migration cutover.
5. Insert the multi year price lock and the renewal uplift cap at the original Cloud order form. The published Atlassian Cloud annual price increase typically sits at five to fifteen percent above the prior contracted per user rate and compounds across the contracted term. The corrective action inserts a multi year price lock that caps the annual price increase at the consumer price index plus three to seven percent across the contracted term, and inserts a renewal uplift cap that caps the contracted per user rate at the consumer price index plus five to ten percent at the renewal cycle. Measure the move at the avoided annual price increase, with a target of three to nine percent recovery against the standard published annual price increase. Timing window: hold both redlines through final signature.

Frequently Asked Questions

The negotiation covers the Server end of support exit, the Data Center to Cloud migration path, the edition mapping from Server or Data Center to Cloud Premium and Cloud Enterprise, the user count restructure, the loyalty discount attach, the Migration Investment Program credit, the multi year price lock, and the Marketplace app re entitlement. The buyer side framework coordinates the eight commercial moves across a single renewal cycle.

The practice has documented engagements where the coordinated negotiation delivered eighteen to thirty four percent recovery against the Atlassian account team's opening Cloud migration proposal. The upper end of the range is available at the Cloud Enterprise tier when the buyer credibly stages the Microsoft Azure DevOps or the GitLab Ultimate alternative in parallel with the migration negotiation.

The preparation should start at least one hundred fifty days before the contracted Server end of support date or the Data Center renewal. The longer lead time is needed because the edition mapping, the user count restructure, the Marketplace app re entitlement, and the loyalty discount documentation each require their own preparation sequence.

The Atlassian Migration Investment Program typically delivers twenty to forty percent of the first year Cloud subscription value as a migration credit at the upper customer scale. The credit is funded against documented migration milestones and against a multi year Cloud commitment. The credit is typically not surfaced unless the buyer raises the migration credit as a distinct line item at the original Cloud order form.

The Atlassian Cloud user count is billed per active user across the contracted subscription term. The buyer side response audits the active user count against the contracted user count, removes inactive and duplicate users, and rightsizes the contracted user count against the audited baseline. The practice has documented engagements where the rightsizing delivered fifteen to twenty eight percent recovery against the Atlassian account team's opening user count proposal.

Cloud Standard is the entry edition with a published per user price and limited governance features. Cloud Premium adds advanced governance, automation, and analytics, with a price typically running fifty to seventy percent above Standard. Cloud Enterprise adds unlimited automation, sandboxes, release tracks, audit logs, and enterprise support, with a price typically running two to three times above Standard. The buyer side response maps the customer's required governance features against the lowest viable edition rather than accepting the account team's Cloud Enterprise framing as the default.

Atlassian Marketplace apps installed on Server or Data Center are not automatically entitled on Cloud. The buyer side response maps every Marketplace app, identifies the Cloud equivalent or the alternative app, and renegotiates the app entitlement at the migration. The practice has documented engagements where the Marketplace app re entitlement recovered an additional five to twelve percent against the Atlassian account team's opening Cloud migration proposal.

The most common mistake is accepting the Atlassian account team's Cloud Enterprise framing without auditing the actual user count or mapping the required governance features. The framing typically sizes the migration against the Server or Data Center contracted user count rather than the audited active user baseline, which inflates the migration value by fifteen to twenty eight percent before the negotiation begins.

How Redress Compliance Engages on the Atlassian Cloud Migration

The practice runs four engagement models against the Atlassian Cloud migration. The Vendor Shield always on advisory subscription covers the Atlassian account alongside the broader collaboration tooling estate. The Renewal Program runs a structured twelve month managed sequence around the Cloud migration cycle. The Benchmark Program sizes the Atlassian commitment against more than five hundred documented engagements. The software spend assessment sizes the Atlassian estate alongside the broader Microsoft, ServiceNow, GitHub, and GitLab footprint. Read the related Atlassian Cloud Enterprise negotiation download, the Atlassian Cloud migration 2026 download, the GitHub Enterprise negotiation download, the GitLab Ultimate negotiation download, the ServiceNow Now Platform negotiation download, the Microsoft EA renewal playbook, the multi vendor negotiation scorecard, and the software spend health check.