Atlassian’s multi-year migration of its customer base off self-managed software and onto its Cloud platform reached a new milestone this spring, and the commercial consequences are now working their way through renewal conversations across the Jira and Confluence customer base. As of March 30, 2026, Atlassian stopped selling new Data Center licenses to new customers entirely — a step that pricing analysts describe as the most aggressive vendor-driven cloud migration currently underway in enterprise software.
Key takeaways: New Data Center purchases have been blocked for new customers since March 30, 2026, ahead of a full end-of-life for Data Center products by March 2029. Customers migrating from Data Center to Cloud report paying roughly 28% more on average. The Marketplace app ecosystem for Data Center has been frozen since December 2025, with no new app submissions accepted, adding pressure on customers who rely on third-party integrations.
A Migration That Has Been Building Since 2024
Atlassian’s move away from self-managed deployments did not begin this year. Server-based licensing — the company’s original on-premises product line — was retired entirely in February 2024, forcing every remaining Server customer to migrate either to Data Center (a more scalable, still self-managed option) or directly to Cloud. That earlier transition set the pattern for what has followed: Atlassian has consistently used end-of-life deadlines as the mechanism for pushing its installed base toward its own hosted Cloud infrastructure, rather than relying solely on pricing incentives to drive voluntary migration.
The next phase of that strategy became official in September 2025, when Atlassian announced a full end-of-life date for Data Center products of March 2029. That announcement gave the remaining Data Center customer base roughly three and a half years of runway — but it also set in motion a series of intermediate milestones, the most significant of which landed this past March: as of March 30, 2026, Atlassian stopped accepting new Data Center purchases altogether. Organizations that have not already adopted Data Center can no longer choose it as an option, regardless of their preference for self-managed infrastructure; Cloud is now effectively the only forward path for new Atlassian customers.
The Real Cost of Migrating to Cloud
For the existing Data Center customer base now facing the 2029 end-of-life deadline, the central pricing question is straightforward: how much more does Cloud actually cost compared to what they are paying today? Based on data gathered from organizations that have already completed the migration, the answer is a meaningful step up — customers moving from Data Center to Cloud report paying roughly 28% more on average for equivalent usage.
That average masks significant variation depending on user count, product mix, and which Cloud tier an organization selects. Atlassian’s Cloud pricing structure includes several tiers — Free, Standard, Premium, and Enterprise — and organizations migrating from a fully featured Data Center deployment often find that replicating their existing functionality requires stepping up to Premium or Enterprise Cloud tiers, rather than the entry-level Standard plan, which further widens the cost gap in practice compared to the average figure. Larger organizations, in particular, tend to see a bigger percentage increase than the headline average, since Data Center’s per-user pricing structure historically offered better economics at scale than Cloud’s tiered model has, at least prior to recent restructuring.
The AI Layer: Rovo Credits and Usage-Based Add-Ons
Adding another dimension to the pricing picture, Atlassian has layered its AI capabilities — branded Rovo — into the Cloud pricing structure using a credit-based consumption model rather than a flat per-user fee. As of early June 2026, Standard Cloud plans include an allotment of 25 Rovo AI credits per user per month as part of the base subscription. Beyond that allotment, additional AI-powered capabilities can generate further usage-based charges; the Virtual Service Agent capability, for example, can incur charges of roughly $0.30 per conversation once usage exceeds included limits.
This usage-based structure mirrors a broader pattern spreading across enterprise SaaS in 2026, in which AI functionality is billed as a distinct, metered line item rather than folded invisibly into the base subscription price. For budgeting purposes, this means organizations evaluating a migration to Atlassian Cloud need to model not just the base subscription cost difference relative to Data Center, but also a reasonably realistic estimate of AI feature usage, since that consumption-based spend can move independently of user-count-driven costs and is harder to forecast with confidence in a first-year migration.
The Marketplace Ecosystem Freeze
Beyond the core platform pricing, one of the more operationally significant — if less headline-grabbing — changes affecting Data Center customers is the freeze on the third-party app ecosystem that supports the platform. As of December 2025, Atlassian’s Marketplace stopped accepting new app submissions for Data Center, meaning the pool of available third-party integrations and extensions for Data Center deployments is now fixed and will not grow further, even as the platform itself remains supported through 2029.
For organizations with deep customization built on Data Center-specific Marketplace apps, this freeze adds a second, less visible pressure point pushing toward Cloud migration, independent of the direct subscription pricing gap. As vendors that build Marketplace apps increasingly focus their development resources on Cloud-only compatibility, Data Center customers may find that even apps they already rely on receive diminishing update and support investment over the remaining years of the platform’s supported life, regardless of what Atlassian itself does with core pricing.
How This Compares Across the Broader Market
Atlassian’s approach — combining a hard end-of-life deadline, a blocked path to new self-managed purchases, and a materially higher-priced Cloud alternative — represents one of the more forceful vendor-driven migration strategies currently visible in enterprise software. It differs meaningfully from Microsoft’s approach to Microsoft 365 pricing, for example, where price increases apply within an already Cloud-native product line, or from VMware’s approach, which restructures licensing within a still largely self-managed deployment model. Atlassian is unusual in explicitly using platform sunset dates as the primary lever, with pricing serving as a secondary reinforcement of the same underlying push.
For customers, that combination leaves comparatively little room for a middle path. Where a Microsoft or Salesforce customer facing a price increase can often negotiate discounts, adjust their SKU mix, or delay a renewal decision by a cycle, Atlassian Data Center customers are working against a fixed calendar deadline that does not move regardless of negotiation outcomes — which changes the nature of the internal planning conversation from “should we accept this price” to “when, within the available window, should we execute this migration.”
What Data Center Customers Should Be Doing Now
With roughly three years remaining before the 2029 end-of-life date, pricing and IT advisory firms tracking the migration consistently recommend that remaining Data Center customers begin formal Cloud migration planning well ahead of the deadline, rather than waiting for the final year or two of the runway. The rationale is twofold: first, migration projects of this scale — particularly for organizations with significant customization, integrations, or regulatory data-residency requirements — routinely take longer than initial estimates suggest; and second, organizations that migrate earlier retain more negotiating leverage on Cloud pricing and tier selection than those forced into a compressed, deadline-driven migration in the final months before end-of-life.
The 28% average cost increase associated with migration is unlikely to be the final word for any given organization — actual outcomes will depend heavily on tier selection, user count optimization, and how aggressively AI feature usage is managed. But as a planning baseline, it gives Data Center customers a realistic starting point for budgeting conversations that, for many organizations, are only now beginning in earnest.
Data Residency and Regulated Industries Face an Extra Layer of Complexity
For organizations in regulated sectors — financial services, healthcare, and government contracting among them — the Data Center-to-Cloud migration carries an additional layer of complexity beyond pricing alone. Data Center deployments have historically appealed to these organizations precisely because they allow data to remain within infrastructure the organization directly controls, which can simplify compliance with data residency and sovereignty requirements. Atlassian’s Cloud platform has expanded its regional hosting options and compliance certifications considerably in recent years, but organizations with especially strict regulatory obligations are, in many cases, still working through a parallel compliance review alongside the pricing and technical migration planning, which can meaningfully extend the overall migration timeline beyond what the cost comparison alone would suggest.
This dynamic is prompting some regulated organizations to begin their Cloud compliance review process well ahead of any final migration decision, treating it as a prerequisite gating step rather than something that can be resolved in parallel with the technical cutover itself. Given that the 2029 end-of-life deadline applies uniformly regardless of industry, organizations in these sectors are generally advised to build in meaningfully more lead time than the broader customer base.
The Competitive Response
Atlassian’s aggressive Cloud-first push has not gone unnoticed by competing project and knowledge management vendors, several of which have used the Data Center sunset as an explicit part of their own sales messaging over the past year, positioning themselves as alternatives for organizations unwilling to accept either the Cloud pricing increase or the loss of self-managed deployment control. Whether that competitive pressure meaningfully slows Atlassian’s own migration numbers remains to be seen, but it does mean Data Center customers evaluating their options over the next few years are unlikely to be short on alternative vendors actively courting their business as the 2029 deadline approaches.