Executive Summary
Atlassian's decision to end Server product sales (February 2024) and ultimately end Server support created the most consequential forced migration in the productivity software market. Every enterprise running Jira, Confluence, Bitbucket, or other Atlassian Server products must migrate to either Atlassian Cloud or Atlassian Data Center — and both options carry significant cost increases over the perpetual Server licensing model that enterprises budgeted against for years.
The cost increase is structural, not incidental. Server licensing was a one-time perpetual licence with modest annual maintenance. Cloud is an annual per-user subscription that scales with headcount and usage tier. For a 5,000-user enterprise moving from Server to Cloud Premium or Enterprise, the annual cost typically increases by 2–4× — from approximately $50K–$80K in Server maintenance to $200K–$400K+ in Cloud subscription. And that's before the Marketplace app cost explosion, which can double the increase again.
Key Findings
1. The Server-to-Cloud migration typically increases annual Atlassian costs by 2–4× — but 30–50% of that increase is addressable through user count optimisation, tier selection, and Marketplace app rationalisation before migration. Most enterprises migrate their full Server user base to Cloud without auditing who actually uses the tools. Server licences were purchased in bulk tiers (500, 2,000, 10,000 users) where the marginal cost per user was negligible. Cloud's per-user pricing makes every inactive user an avoidable cost.
2. 30–50% of Atlassian Server users are inactive, dormant, or using the tools so infrequently that their Cloud licence cost exceeds their usage value. Server's flat-tier pricing meant there was no cost to having 10,000 licensed users when only 6,000 were active. Cloud's per-user model changes this calculus entirely — every inactive user costs $50–$150+ per year depending on the product and tier. User cleanup before migration is the highest-ROI activity available.
3. Marketplace app costs frequently double or triple in the Server-to-Cloud migration — because app vendors switch from perpetual to per-user-per-month pricing, often at rates that exceed the Atlassian platform cost itself. A Marketplace app that cost $1,000 as a one-time Server purchase becomes $5–$15/user/month on Cloud. For 5,000 users, that single app becomes $300K–$900K annually. The Marketplace app portfolio — not the Atlassian platform — is frequently the largest cost driver in the cloud migration.
4. Atlassian offers migration-specific pricing concessions — loyalty discounts, extended promotional rates, and multi-year migration terms — but only when enterprises negotiate before migrating, not after. Atlassian's migration team has explicit pricing authority to ease the Server-to-Cloud transition. These concessions are not offered proactively — they must be requested as part of a commercial negotiation. Once you've migrated, the pricing leverage evaporates because the switching cost is established.
5. Data Center is a viable mid-term alternative for enterprises that need more time — but it's not a permanent solution, and Atlassian is pricing it to incentivise eventual Cloud migration.
The Forced Migration: Understanding Atlassian's Strategy
The Timeline
Atlassian announced the Server End-of-Life (EOL) roadmap in February 2021, giving enterprises approximately 3 years of notice. The phases are:
- February 2024: Atlassian stopped selling new Server licences. Existing Server customers could renew maintenance, but could not purchase additional user seats.
- February 2024: Server support and updates ended completely. Server installations continue to function, but security patches, bug fixes, and feature updates ceased.
- February 2026: Atlassian will end all Server support and will not provide patches for any new vulnerabilities.
Why This Creates Negotiation Leverage
The forced migration creates a narrow window for commercial negotiation — from the moment Atlassian sales contacts you about Cloud migration to the moment you actually migrate. Once the infrastructure, data, and users are on Cloud, Atlassian's pricing leverage increases dramatically because the switching cost compounds over time.
Atlassian's migration team operates with explicit pricing authority that is not available outside the migration context. Loyalty discounts, promotional rates, and extended contract terms are all available — but only during active migration negotiations, not after the fact.
The Data Center Bridge Strategy
Data Center is positioned as a "bridge" option for enterprises that need more time before Cloud migration. However, Atlassian's pricing makes Data Center increasingly expensive each renewal cycle, creating pressure to migrate to Cloud. If you're not already on Data Center, Atlassian will position it as a holding pattern during evaluation. If you're already on Data Center, Atlassian will use it as a negotiation baseline to accelerate Cloud migration discussions.
Data Center is a viable option for enterprises with 2–4 years of transition time, but it should not be viewed as a permanent solution. Use it strategically for negotiation leverage, not as an indefinite holding pattern.
Atlassian Cloud Pricing Architecture
Atlassian Cloud pricing is structured around three primary variables: per-user subscription cost, tier selection (Standard, Premium, Enterprise), and usage model (monthly or annual commitment).
The Tier Escalation Trap
Cloud tiers are not transparent in their feature differentiation. Atlassian positions Premium as the "standard" tier for most enterprises, and Enterprise as "advanced scenarios." In reality, the tier selection often becomes an all-or-nothing decision because of the way features are distributed across tiers.
Most enterprises migrate to Premium or Enterprise tier without evaluating whether Standard tier is sufficient for their user population. This results in overpaying by 50–100% for capabilities that many users don't require.
User Tier Pricing Is Regressive at Scale
Cloud's per-user pricing model is regressive at scale. A single additional user typically costs the same regardless of whether you're at 100 users or 10,000 users. However, bulk discounting and enterprise negotiation can change this calculus significantly. Enterprises with 1,000+ users should always negotiate enterprise rates rather than accept published per-user pricing.
The Server-to-Cloud Premium: Quantifying the Real Cost
The cost increase from Server to Cloud is substantial and multi-dimensional. Consider a typical 5,000-user enterprise migration:
Server model: Jira Server (perpetual licence $30K) + annual maintenance (10% = $3K). Confluence Server (perpetual licence $20K) + annual maintenance ($2K). Total annual recurring cost: $5K. Total first-year cost: $55K.
Cloud model (published pricing): Jira Cloud Premium (5,000 users × $7/user/month = $420K/year). Confluence Cloud Premium (5,000 users × $5/user/month = $300K/year). Total annual recurring cost: $720K. Total first-year cost: $720K.
This represents an 8× first-year cost increase and a 144× recurring cost increase. Even with aggressive negotiation, most enterprises experience a 2–4× cost increase.
User Count Optimisation: The Highest-ROI Migration Activity
User count optimization is the single highest-ROI activity in any Atlassian Cloud migration. Every user you don't migrate to Cloud is an annual savings of $600–$2,400+ per year depending on the product and tier.
Inactive User Cleanup
Most enterprises have 25–40% of their Server user base that is completely inactive. These are accounts that have not logged in within 90–180 days and are not expected to use Atlassian products in the foreseeable future. Deactivating these accounts before migration produces immediate and compounding savings.
Low-Activity User Reclassification
Beyond inactive users, many enterprises have a cohort of low-activity users who use Atlassian tools infrequently but would not tolerate being completely deactivated. These users often qualify for "viewer" access (read-only) or free-tier access, both of which cost significantly less than licensed access. Reclassifying these users before migration can reduce the migrated user count by an additional 15–25%.
Product-Specific Licensing
Not all users require access to all Atlassian products. An organization might have a Jira population of 5,000 users but a Confluence population of only 2,000 users. Cloud supports per-product licensing, which means you only pay for Confluence users who actually use Confluence. Many enterprises over-license by applying the same user count across all products.
Tier-Appropriate Licensing
Not all users require Premium or Enterprise tier access. Many organizations can operate effectively on Standard tier for 60–70% of their user population. Cloud supports mixed-tier licensing, allowing you to minimize costs by matching tier to actual feature requirements. This typically produces 20–30% savings compared to an all-Premium or all-Enterprise approach.
The Marketplace App Cost Explosion
Marketplace app costs are frequently underestimated in Cloud migration planning. Most procurement teams focus on Atlassian platform pricing negotiation while accepting Marketplace app costs at list price. This imbalance represents the largest single optimization opportunity in most migrations.
The "App Tax" on Total Migration Cost
In Redress engagements, Marketplace app costs represent 30–60% of the total Cloud migration cost increase — yet they receive less than 10% of the procurement attention. The platform subscription is negotiated; the app costs are accepted. This imbalance represents the single largest optimisation opportunity in most Atlassian Cloud migrations. Treat Marketplace app procurement with the same rigour as platform procurement.
A typical Marketplace app transition: A Server app purchased perpetually for $1,500 becomes a per-user-per-month Cloud licence at $8/user/month. For 5,000 users, that's $480K annually — a 320× cost increase. Most enterprises discover this cost explosion only after migration is underway, when switching costs are already incurred.
The Cloud Migration Negotiation Framework
Optimise Before Migrating
Complete user count cleanup (inactive users, low-activity reclassification, product-specific licensing, tier-appropriate licensing) and Marketplace app rationalisation before any commercial discussion with Atlassian. The optimised user count and app portfolio become the migration scope — ensuring you negotiate Cloud pricing on the efficient base, not the inflated Server base.
Establish Data Center as Alternative
If not already on Data Center, evaluate it as a supported bridge. Data Center provides negotiation leverage because it demonstrates that Cloud isn't your only option. Even if you intend to migrate to Cloud, signalling willingness to remain on Data Center for 2–4 years while "evaluating Cloud economics" activates Atlassian's migration pricing authority.
Request Migration-Specific Pricing
Atlassian offers migration-specific concessions: loyalty discounts for long-standing Server customers (10–25% off Cloud list pricing for 1–3 years), extended promotional pricing (discounted rates for the first 12–24 months), and multi-year migration terms (locked rates for the transition period). These must be requested explicitly — they are not offered proactively.
Negotiate Enterprise-Level Rates
For enterprises with 1,000+ users, engage Atlassian's enterprise sales team directly rather than purchasing through standard channels. Enterprise negotiations unlock custom per-user rates below published pricing, volume discounts beyond published tiers, multi-product bundling discounts, and premium support inclusion. The enterprise channel consistently delivers 15–30% better pricing than self-service purchasing.
Evaluate Competitive Alternatives
Document competitive evaluations for key Atlassian products: GitLab or GitHub for Bitbucket, Monday.com or Asana for Jira (for non-engineering teams), and Notion or SharePoint for Confluence. The evaluations don't require migration intent — they demonstrate that Atlassian is not the only option and create commercial pressure during the negotiation.
Negotiate Marketplace Apps Independently
Treat Marketplace app procurement as a separate commercial workstream. For each retained app, negotiate directly with the vendor: migration pricing, volume discounts, user count exclusions (not all users need every app), and multi-year rate locks. App vendors want to retain customers during migration — leverage this to secure rates that reflect your actual usage population, not the full Cloud user count.
Recommendations: 7 Priority Actions
Audit and Clean Up Users Before Migration
Deactivate inactive users (no login in 90+ days), reclassify low-activity users to viewer or free-tier access, and verify product-specific licensing requirements. The user count you migrate to Cloud becomes the cost base for the entire subscription — every unnecessary user is an annual cost for the duration of the agreement. This single activity typically reduces the migrated user count by 25–40%.
Right-Size Tier Selection by User Population
Don't migrate everyone to Cloud Premium or Enterprise. Audit which users require Premium features versus which need only Standard capabilities. Cloud supports mixed-tier environments. For most enterprises, 60–70% of users can operate on Standard tier at approximately half the Premium per-user cost — producing savings of $200K–$500K annually at enterprise scale.
Rationalise Marketplace Apps Before Migration
Inventory every Marketplace app, audit actual usage, and eliminate unused or redundant apps before migration. The app portfolio is frequently 30–60% of the total migration cost increase. Reducing the app count by 40–60% (typical for most enterprises) can save more than the platform pricing negotiation. Treat app rationalisation with equal rigour.
Negotiate Migration-Specific Pricing with Atlassian
Request loyalty discounts, extended promotional pricing, and multi-year migration terms through Atlassian's enterprise sales team. These concessions are available but not proactive — they require direct commercial engagement. For 1,000+ user enterprises, enterprise-negotiated rates consistently deliver 15–30% below published Cloud pricing.
Use Data Center as Negotiation Leverage
Even if you intend to migrate to Cloud, establish Data Center as a viable supported alternative. The willingness to remain on Data Center for 2–4 years removes the urgency that Atlassian relies on and activates their migration-incentive pricing authority. Negotiate Cloud terms while maintaining the Data Center option — don't commit to Cloud until the terms justify it.
Negotiate Marketplace App Pricing Directly with Vendors
For every retained Marketplace app, negotiate Cloud pricing directly with the app vendor — not through Atlassian. Request migration-specific rates, volume discounts for your actual user population (not the full Cloud user count), and multi-year rate commitments. App vendors are competing for Cloud migration retention and have pricing flexibility during the transition period.
Secure Multi-Year Rate Protection
Atlassian has historically increased Cloud pricing annually (5–10% increases are common). Negotiate multi-year rate locks as part of the migration agreement — the migration is Atlassian's best opportunity to lock you into a long-term Cloud commitment, which gives you leverage to demand rate protection in return. A 3-year rate lock prevents annual escalation from compounding the already-significant migration cost increase.
How Redress Can Help
Redress Compliance's Productivity Vendor Practice provides independent advisory on Atlassian Cloud migration — from user count optimisation and Marketplace rationalisation through migration pricing negotiation and ongoing Cloud cost governance. We maintain zero commercial relationships with Atlassian or any Atlassian partner.
User Count Optimisation
Comprehensive user audit — inactive cleanup, low-activity reclassification, product-specific licensing, and tier-appropriate assignment — reducing the Cloud user count by 25–40% before migration.
Marketplace App Rationalisation
App portfolio audit — usage analysis, elimination of unused apps, consolidation of overlapping functionality, and direct vendor negotiation for retained apps.
Migration Pricing Negotiation
Direct negotiation with Atlassian's enterprise sales team — migration-specific pricing, loyalty discounts, multi-year rate locks, and tier optimisation for the migrated user base.
TCO Comparison
Comprehensive Server vs. Cloud vs. Data Center total cost of ownership analysis — including infrastructure savings, administration reduction, and the complete Marketplace app cost impact.
Competitive Assessment
Evaluation of alternatives for applicable Atlassian products — creating competitive pressure that improves migration pricing and providing genuine options where alternatives deliver better value.
Cloud Cost Governance
Ongoing Atlassian Cloud cost management — annual user count review, Marketplace app audit, renewal preparation, and escalation protection to prevent cost drift post-migration.
100% Independent Advisory
Redress maintains zero commercial relationships with Atlassian, any Atlassian Solution Partner, or any Marketplace app vendor. Our only relationship is with you — ensuring our recommendations optimise your migration economics, not Atlassian's Cloud conversion metrics.
Get a Free Atlassian Deal Review
Our Productivity Vendor Practice will analyze your current environment and identify optimization opportunities specific to your situation.
Schedule a ConsultationDownload the Complete White Paper
Get the full negotiation framework, detailed cost analysis, and 7-phase implementation plan.
Download PDF →Join Our Newsletter
Get weekly insights on vendor pricing, licensing strategies, and contract negotiation tactics.
Subscribe NowBook a Meeting
Schedule a confidential consultation with our Productivity Vendor Practice team. We'll assess your current Atlassian environment and identify the optimal migration strategy.