Editorial photograph of a software team collaboration board, representing Atlassian Jira and Confluence enterprise deployment
Article · Atlassian · Dual Licensing

Atlassian Dual Licensing. Running Cloud and Data Center in parallel.

Enterprises mid migration from Atlassian Data Center to Cloud run both deployments in parallel. The dual licensing structure carries hidden cost traps. This article maps the mechanics and the levers.

Read the Framework Atlassian Hub
2Parallel deployments
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Enterprises mid migration from Atlassian Data Center to Atlassian Cloud run both deployments at the same time. The dual licensing structure carries a cost overlap window that runs 6 to 24 months depending on the migration plan.

The Atlassian dual licensing model gives migrating customers a structured overlap, but the commercial mechanics still leak budget when the migration runs long, the user counts diverge, or the third party app licensing is misaligned across both deployments.

Read this alongside the Atlassian pillar hub, the Cloud migration guide 2026, the Data Center end of life, and the Vendor Shield subscription.

Key Takeaways

What every Atlassian customer needs to know about dual licensing

  • Dual licensing is structured. Atlassian offers a Migration Subscription that gives free Cloud access during the active Data Center subscription, capped at the matching user tier.
  • Data Center end of life. Atlassian Data Center remains supported through 2029 with stepped price increases each year.
  • User count parity. The free Cloud access during migration is capped at the Data Center user tier. Above that, additional Cloud users bill at the Cloud rate.
  • Third party app overlap. Marketplace apps require separate Cloud and Data Center licenses. The overlap doubles the third party spend for the migration window.
  • Migration window. The Migration Subscription runs until the Data Center subscription expires or the customer drops Data Center. Most successful migrations run 9 to 18 months.
  • Cloud Pricing. Annual upfront billing gives 13 percent savings versus monthly billing. The 5 year commit on Cloud Enterprise gives additional discount bands.
  • Renewal lever. Trade a 3 to 5 year Cloud Enterprise commit for 25 to 40 percent discount, plus extended Migration Subscription window, plus third party app credits.

Dual licensing structure mechanics

Atlassian offers a structured path to running Cloud and Data Center in parallel during a migration. The Migration Subscription is the commercial wrapper.

Migration Subscription mechanics

ElementMechanicsBuyer side note
Free Cloud accessTied to Data Center user tierCap matches DC tier, additional Cloud users bill separately
Cloud featuresFull Cloud Standard or Cloud PremiumCloud Enterprise requires a paid upgrade during migration
DurationUntil DC subscription expires9 to 18 months typical
Marketplace appsNot included in Migration SubscriptionSeparate Cloud app licenses required
Migration toolsAtlassian Cloud Migration Assistant includedFree, but professional services often required
SupportBoth deployments fully supportedPremier Support recommended for migration

When dual licensing applies

  • Active Data Center customer. Migration Subscription is available to customers with an active Atlassian Data Center license.
  • Migrating to Cloud. Customer must declare intent to migrate.
  • User tier match. Free Cloud users match the Data Center user tier. Above the tier, Cloud users bill at the Cloud rate.
  • Time bound. Migration Subscription expires when Data Center subscription expires or when customer drops Data Center.

Atlassian Data Center timeline and price moves

Atlassian announced Data Center remains supported through 2029, but the pricing path through that window pushes customers toward Cloud migration.

Atlassian Data Center price uplift 2026 through 2029

  • 2026. 10 to 15 percent list price uplift on Data Center renewal.
  • 2027. Additional 10 to 15 percent uplift expected. Stacks on 2026.
  • 2028. Additional uplift, scope to be announced.
  • 2029. Data Center subscription end of support announced.
  • Post 2029. No Atlassian Data Center subscription renewals.

Marketplace app vendor timing

  • Top 10 apps. Cloud equivalents available for the top marketplace apps. Validate feature parity.
  • Mid tier apps. 70 percent of marketplace apps have Cloud equivalents in 2026.
  • Long tail apps. Some niche Data Center apps have no Cloud equivalent. Plan for replacement, retirement, or custom build.

Atlassian migration patterns

Three dominant migration patterns cover most enterprise Atlassian transitions. Each pattern carries different dual licensing math.

Three dominant patterns

  • Big bang. Single cutover from Data Center to Cloud, typically over a weekend. Lowest dual licensing cost (1 to 3 month overlap). Highest risk and disruption.
  • Phased by project. Migrate Jira projects in waves, Confluence spaces in waves. 9 to 18 month overlap. Moderate dual licensing cost.
  • Phased by team. Migrate teams or business units in waves. 12 to 24 month overlap. Highest dual licensing cost but lowest user disruption.

Pattern selection criteria

PatternOverlap windowBest for
Big bang1 to 3 monthsSingle business unit, low complexity, willing to absorb risk
Phased by project9 to 18 monthsMulti tenant environment, project segmentation possible
Phased by team12 to 24 monthsFederated organization, autonomous teams, change management heavy

Cost overlap math during dual licensing

The dual licensing window carries cost overlap in three categories: Atlassian licenses, third party marketplace apps, and operational support.

Three cost overlap categories

  • Atlassian core licenses. Migration Subscription gives free Cloud users at the Data Center tier. Excess Cloud users bill at the Cloud rate during overlap.
  • Marketplace apps. Cloud and Data Center app licenses are separate. Most marketplace apps double bill during overlap.
  • Operational support. Data Center infrastructure (servers, database, monitoring) plus Cloud operational support during overlap.

Overlap cost as percent of annual spend

PatternAtlassian licenses overlapMarketplace overlapTotal overlap as percent of annual
Big bang (2 months)15 percent15 percent15 to 20 percent of annual
Phased by project (12 months)40 percent80 percent60 to 90 percent of annual
Phased by team (18 months)60 percent120 percent90 to 130 percent of annual

Worked example: 4,500 user Atlassian migration

A financial services customer runs Atlassian Data Center across 4,500 users (Jira plus Confluence plus Bitbucket plus Jira Service Management). The Data Center annual spend is 950K USD plus 380K USD in marketplace apps.

Current Data Center spend

Line itemAnnual spendNotes
Jira Data Center340K USD4,500 user tier
Confluence Data Center290K USD4,500 user tier
Bitbucket Data Center180K USD2,000 user tier
Jira Service Management Data Center140K USD800 agent tier
Marketplace apps380K USD14 apps across 4 products
Total annual1.33M USD--

Phased by project migration plan

  • Migration window. 14 months, phased by project across 4 quarters.
  • Cloud licensing. Cloud Enterprise on Jira plus Confluence at 4,500 users. Migration Subscription covers users during overlap.
  • Marketplace overlap. 280K USD additional during the 14 month overlap window for parallel Cloud apps.
  • Negotiated commercial terms. 5 year Cloud Enterprise commit. 35 percent discount off Cloud Enterprise list. 12 month Migration Subscription extension. 200K USD marketplace credit applied.
  • 3 year Cloud TCO. 3.45M USD versus 5.31M USD at list (35 percent saving).

Seven Atlassian dual licensing procurement levers

The seven dual licensing levers

  1. Migration Subscription extension. Negotiate a 12 to 18 month extended Migration Subscription window in the Cloud commit.
  2. User tier parity. Match Cloud user tier to Data Center tier during overlap. Right size both.
  3. Marketplace credits. Negotiate marketplace credits to offset the third party app overlap.
  4. Cloud Enterprise discount. Drive to 30 to 40 percent off Cloud Enterprise list on a 3 to 5 year commit.
  5. Phased migration discipline. Stage the migration to minimize the dual licensing window where possible.
  6. Premier Support during migration. Bundle Premier Support for the migration window only, then drop to Standard.
  7. Renewal trade. Trade 3 to 5 year Cloud Enterprise commit for the discount, Migration Subscription extension, and marketplace credits, all in writing.

What to do next

The seven step checklist takes an Atlassian dual licensing position from current state to a negotiated migration.

  1. Inventory the Data Center user population. Jira users, Confluence users, Bitbucket users, Jira Service Management agents.
  2. Audit the marketplace app footprint. Every Data Center app, the vendor, the Cloud equivalent status, the user count.
  3. Pick the migration pattern. Big bang, phased by project, phased by team. Match to organization shape.
  4. Model the dual licensing window. Atlassian core, marketplace, operational support overlap by quarter.
  5. Validate Cloud user count. Right sized Cloud population, not the historical Data Center tier.
  6. Open the negotiation. 30 to 40 percent discount on Cloud Enterprise, Migration Subscription extension, marketplace credits.
  7. Document the renewal order language. Volume tier, migration window, marketplace credits, true down right at the migration end, all explicit.

Frequently asked questions

What is Atlassian Migration Subscription?

Migration Subscription is Atlassian's structured commercial wrapper for customers running Cloud and Data Center in parallel during a migration. It gives free Atlassian Cloud access to active Data Center customers, capped at the matching user tier, for the duration of the active Data Center subscription.

The free Cloud access covers Atlassian core licenses (Jira, Confluence, Bitbucket, Jira Service Management) at Cloud Standard or Cloud Premium tier. Cloud Enterprise requires a paid upgrade during migration. Marketplace apps are not included in the Migration Subscription.

How long can we run Data Center and Cloud in parallel?

The Migration Subscription runs until the Data Center subscription expires or the customer drops Data Center. In practice, most successful enterprise migrations run 9 to 18 months in parallel. Big bang migrations run 1 to 3 months. Heavily federated organizations migrating team by team can run 12 to 24 months.

Atlassian Data Center remains supported through 2029. The price uplift each year through 2029 pushes customers toward Cloud migration, but the deployment option is available for customers who need to extend the timeline.

Do marketplace apps count under Migration Subscription?

No, marketplace apps do not count under Migration Subscription. Cloud and Data Center marketplace app licenses are separate. During the migration window, most enterprises double bill for parallel marketplace apps across both deployments.

The buyer side discipline is to audit the marketplace app footprint, identify which Data Center apps have Cloud equivalents, plan for retirement of apps with no Cloud version, and negotiate marketplace credits at the Cloud Enterprise commit to offset the overlap cost.

What happens to Data Center after 2029?

Atlassian announced Data Center end of support in 2029. Post 2029, no new Atlassian Data Center subscription renewals will be available. Customers running on Data Center after 2029 will be on unsupported software, with no security patches, no bug fixes, no feature updates.

The migration window is the period from now through 2029, with stepped price increases on Data Center each year to incentivize earlier migration. The buyer side discipline is to plan the migration on the right timeline for the organization, not on the Atlassian sales calendar.

Can we get a discount on Cloud Enterprise during migration?

Yes, Cloud Enterprise customers can negotiate volume discounts during a Data Center migration. Typical discounts run 25 to 40 percent off Cloud Enterprise list on a 3 to 5 year commit. Volume discount bands trigger at 1,000 plus users, with steeper bands at 5,000 plus users.

The renewal lever is to bundle the Cloud Enterprise commit with the Migration Subscription extension and marketplace credits. A 3 to 5 year Cloud Enterprise commit gives the buyer side leverage to demand the migration window extension and the marketplace credits as part of the same negotiation.

How does Redress engage on Atlassian dual licensing?

Redress runs Atlassian dual licensing advisory inside the Vendor Shield subscription, the Atlassian licensing services practice, and on engagement basis where a Data Center to Cloud migration is in flight. The output is a Data Center inventory, a marketplace footprint analysis, a migration pattern recommendation, a dual licensing cost model, and a negotiation memo.

The engagement is led by Atlassian commercial professionals on the buyer side. We have run Atlassian advisory across financial services, technology, manufacturing, and public sector customers running Atlassian portfolios from 500 users to 35,000 users.

How Redress engages on Atlassian dual licensing

Redress runs Atlassian dual licensing advisory inside the Vendor Shield subscription, the Atlassian licensing services, the Software Spend Assessment, and the Renewal Program.

Read the related Cloud migration guide 2026, the Data Center end of life, the enterprise negotiation cloud pricing guide, the Cloud pricing enterprise guide 2026, the Cloud contract negotiation, the marketplace app licensing, the Rovo AI licensing, the pricing changes 2026, the benchmarking page, the about us page, and the contact page.

Score your Atlassian migration readiness in under five minutes.
Open the Health Check →
White Paper · Atlassian

Download the Atlassian Enterprise Pricing Guide.

Buyer side reference on Atlassian Cloud Enterprise pricing and dual licensing. Volume tiers, Migration Subscription mechanics, marketplace app overlap math, and the seven levers procurement carries to an Atlassian deal.

Independent. Buyer side. Written for CIOs, CFOs, procurement leaders, and Atlassian contract owners running an active migration or Cloud Enterprise renewal. No Atlassian kickback. No conflict on the table.

Atlassian Enterprise Pricing Guide

Open the white paper in your browser. Corporate email only.

Open the Paper →
2029
Data Center EOL
35%
Cloud Enterprise discount
500+
Enterprise Clients
$2B+
Under advisory
100%
Buyer side

The dual licensing window leaks budget on the marketplace app side, not the core Atlassian side. The free Cloud users during Migration Subscription cover Jira and Confluence. The 14 third party apps double bill for 18 months. That is where the cost overlap math hides.

Former Atlassian Enterprise Sales Director
On the buyer side, 11 Atlassian migrations in 2025
More Reading

More from this practice.

Atlassian Hub →
Atlassian Pillar Hub
Atlassian · Hub
Atlassian Pillar Hub
Master Atlassian licensing reference.
20 min read
Atlassian Cloud Migration 2026
Atlassian · Guide
Atlassian Cloud Migration 2026
Migration patterns and playbook.
20 min read
Atlassian Data Center EOL
Atlassian · Article
Atlassian Data Center EOL
The 2029 timeline and price moves.
16 min read
Cloud Enterprise Negotiation
Atlassian · Guide
Cloud Enterprise Negotiation
Discount bands and renewal levers.
18 min read
Marketplace App Licensing
Atlassian · Guide
Marketplace App Licensing
Cloud and Data Center app mechanics.
14 min read
Editorial photograph of enterprise contract negotiation strategy

Land Atlassian Cloud Enterprise at the right tier. Independent advisors, end to end.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Atlassian commercial intelligence, monthly.

Cloud Enterprise discount bands, Migration Subscription mechanics, marketplace app math, Data Center EOL planning, and Atlassian renewal lessons from every Atlassian engagement we run on the buyer side.