What the Dual Licensing Programme Actually Delivers
Atlassian's dual licensing programme is straightforward in concept: purchase an annual Cloud subscription and Atlassian extends your existing Data Center licence for the same period at no additional cost. In practice, this means running two fully operational environments simultaneously — your established Data Center instance handling production workloads while your Cloud instance undergoes configuration, user acceptance testing, and phased onboarding.
The 100 percent discount on DC renewal applies for up to 12 months from the date of Cloud commitment. This is not a trial or limited-feature arrangement. Both instances remain fully licensed, fully supported, and available for production use during the overlap period. For large enterprises with complex Jira and Confluence deployments, this is the difference between a forced cutover and a managed, phased transition.
Understanding the full Atlassian Data Center end of life migration roadmap is essential before entering any dual licensing agreement. The programme was specifically designed to de-risk the migration window — but only if you structure the agreement correctly from the outset.
The Three Components of the Programme
The dual licensing programme comprises three distinct elements that work in sequence. Step-Up Credits allow the unused value of your Data Center licence (calculated from the transaction date to expiry) to be applied against Cloud subscription costs. If you have eight months remaining on a $200,000 DC licence, approximately $133,000 of that value offsets Cloud charges. Dual Licensing then extends the DC licence at no cost for the Cloud subscription period. Ascend Loyalty Discounts layer on top for qualifying enterprise migrations, offering 10 to 20 percent Cloud discounts for customers committing to Cloud Enterprise by June 2027.
Navigating Atlassian's migration incentives is complex. We help enterprises structure agreements that maximize step-up credits, secure loyalty discounts, and eliminate transition risk.
In one engagement, a FTSE 500 organisation running Atlassian DC in parallel with cloud faced $2.8M exposure across a three-year migration. Redress structured a dual licensing agreement that recovered $640,000 in step-up credits and negotiated $180,000 in additional loyalty discounts. The engagement fee was less than 8% of the recovery.Who Qualifies: The Eligibility Rules
Atlassian's dual licensing programme is not open to all customers. The primary eligibility threshold is 1,001 or more users on an annual Cloud subscription. Customers below this threshold can purchase Cloud and run it alongside DC, but they will pay for both licences independently without the 100 percent DC extension discount.
Additionally, the programme applies only to customers transitioning from an active, paid Server or Data Center subscription. Lapsed licences, expired maintenance, or customers on community editions do not qualify for Step-Up Credits. The Cloud product purchased must be the direct equivalent of the DC product being transitioned — Jira Software DC migrating to Jira Software Cloud, Confluence DC to Confluence Cloud, and so on.
The timing matters as much as the user count. Dual licensing agreements initiated before March 30, 2026, benefit from the broadest range of migration incentives. After that date, no new Data Center licences are available for new customers, and the leverage dynamics shift in Atlassian's favour. Existing customers retain renewal rights until March 30, 2028, but the window for optimal negotiation is narrowing.
What Happens After 12 Months
The 12-month dual licence window is fixed. When it expires, you are paying for Cloud only. There is no automatic extension, no discretionary grace period, and no rollback path to Data Center pricing. Organisations that underestimate their migration timeline — and a significant proportion do — find themselves either forcing a rushed cutover to avoid paying for both licences, or absorbing an unbudgeted DC renewal cost while Cloud migration continues.
This makes pre-agreement planning critical. Before committing to the dual licence structure, you need an honest assessment of your migration timeline that accounts for app compatibility testing (up to 30 percent of Atlassian Marketplace apps may require alternatives), data migration complexity, user retraining, and integration reconfiguration. Build in a 20 to 30 percent buffer on your internal estimate before you negotiate the Cloud start date.
Running the Two Environments: Practical Considerations
Operating Cloud and Data Center in parallel is not simply a licensing question — it introduces real operational complexity. Your teams need clear governance rules for which environment handles which workloads, how data synchronisation is managed during the parallel period, and who has authority over configuration changes in each instance.
The most common model is a "dark launch" approach: Cloud receives all new projects and boards while legacy workloads remain on DC until they can be individually migrated. This avoids bulk data migration risk and lets teams self-select their transition timing. However, it requires maintaining two sets of administration policies, two sets of integrations, and two audit trails — none of which is free in terms of IT overhead.
Atlassian's cloud migration tools — including the Jira Cloud Migration Assistant and Confluence Cloud Migration Assistant — can migrate projects, spaces, and users selectively, supporting this incremental approach. However, they do not handle third-party app data, custom field configurations from complex schemes, or automation rules, which require manual reconfiguration on the Cloud side.
Rovo AI During the Dual Period
Atlassian's Rovo AI platform is now embedded into Premium and Enterprise Cloud subscriptions at no additional cost for most users. Standard plan customers receive Rovo access on a rolling basis. Critically, Rovo is a Cloud-only feature — Data Center instances running in parallel during the dual licensing period do not have access to Rovo capabilities. This creates an asymmetry that Atlassian uses deliberately: teams piloting on Cloud experience AI-powered search, knowledge synthesis, and automated workflows, while the DC environment remains static.
This is not incidental. Atlassian designed the dual licensing programme partly as a demonstration mechanism. The Cloud environment is intended to be more capable, more feature-rich, and more attractive than the DC instance. Understanding this dynamic helps you negotiate more effectively — you have the leverage of Atlassian's desire to showcase Cloud, and Atlassian has the leverage of an accelerating EOL timeline.
Negotiating Beyond the Standard Programme Terms
The published dual licensing terms are a floor, not a ceiling. Enterprise customers with significant spend — typically $500,000 or more in combined Atlassian annual licensing — have meaningful negotiating leverage for enhancements beyond the standard programme.
Specific terms that are negotiable include the duration of the dual licence period (beyond 12 months in exchange for multi-year Cloud commitment), the scope of Step-Up Credits (whether credits cover list price or negotiated price), the Ascend loyalty discount percentage (10 to 20 percent is the published range, but larger commitments can reach higher), and the inclusion of Jira Service Management agent licences in the bundle calculation.
Review your Atlassian cloud contract terms carefully before agreeing to any migration incentive structure. Key clauses to scrutinize include the definition of "equivalent" products for step-up credit purposes, the treatment of lapsed users in the user count calculation, and the conditions under which loyalty discounts vest or lapse.
Atlassian's fiscal year ends July 31. Deals signed in the April to June period — when Atlassian is pushing to close before year-end — can attract additional concessions. The Q4 window is the strongest negotiating moment for customers with renewal flexibility, though the compressed March 2026 deadline for DC end of sale has already reduced some of this leverage for organisations that delayed their migration planning.
The EOL Timeline and Why It Changes Your Leverage Over Time
The Data Center end of life roadmap has three hard dates that define the negotiating environment. March 30, 2026 marks the end of new DC licence sales. March 30, 2028 is the last date existing customers can expand or renew DC licences. March 28, 2029 is full end of life — when DC subscriptions expire and systems enter read-only mode.
Between now and March 2028, Atlassian still needs you to renew DC while you migrate. This creates legitimate bilateral dependency: Atlassian needs renewal revenue from DC, and you need the continuation rights to operate without disruption. This dependency is most valuable in the 2026 to 2027 window. After March 2028, expansion rights lapse and your leverage substantially diminishes.
For a full analysis of what these Atlassian pricing changes in 2026 mean for your renewal strategy, review the complete breakdown of list price increases and their impact on total contract value.
The enterprises that navigate the dual licensing programme most effectively treat it as one component of a broader Atlassian negotiation strategy — using their DC renewal as leverage, their Cloud commitment as the ask, and their migration timeline as the constraint that shapes the entire structure. Done well, it is possible to reduce total Atlassian spend over the 2026 to 2029 window by 15 to 25 percent compared to accepting the standard migration path.
Ready to structure your Atlassian migration agreement before your leverage window closes?
Our Atlassian licensing advisory specialists have negotiated dozens of enterprise dual licensing agreements across EMEA and North America.