Server end of life reset the cost of every Atlassian Marketplace app. This is the buyer side framework for Data Center app tiers, Cloud migration pricing, and the moves that stop app cost from outrunning the platform.
Server end of life moved Atlassian customers onto higher Data Center and Cloud tiers, and because Marketplace apps are priced to match the host tier, every paid app was repriced upward at the same time, often unbudgeted.
Server end of life forced every customer onto Data Center or Cloud. Atlassian sets out the paths on its Data Center migration pages and its journey to Cloud resources. Both destinations are priced higher than the retired Server tiers.
Because Marketplace apps are priced to match the host tier, the platform move repriced the apps automatically. The app line moved without anyone changing a single app.
An app sold for a Server instance was priced for that tier. The same app on Data Center is priced for the Data Center tier. The capability did not change. The price did, because it tracks the host.
Data Center apps are priced by user tier, in the same bands as the host product. Atlassian lists the host product bands on its Jira pricing pages, and Marketplace apps follow the same tier structure.
Atlassian publishes the host product bands for Confluence on its Confluence pricing pages, and Marketplace apps follow the same user tier structure.
Crossing a user threshold raises the platform and every paid app together. A handful of extra accounts can move the whole estate into the next band. Clean the user list before you size the tier.
Atlassian destinations after Server end of life
| Destination | App pricing basis | Best fit | Cost watch out |
|---|---|---|---|
| Data Center | User tier band | Regulated or customized | Tier crosses on user growth |
| Cloud Standard | Plan and user band | Smaller standardized teams | Feature gaps need apps |
| Cloud Premium | Plan and user band | Larger Cloud estates | Premium plus app tiers |
| Cloud Enterprise | Plan and user band | Multi instance estates | Negotiated, model app line |
Cloud migration repackages the estate into a plan and a user band. Some Server apps have direct Cloud equivalents. Some do not, and need a replacement or a workflow change. Either way the app line must be modeled before the platform quote is signed.
For each paid app, decide whether it moves as is, is replaced by native Cloud capability, or is retired. Native features in higher Cloud plans sometimes remove the need for a paid app entirely.
The common advice is to migrate the platform first and sort out the Marketplace apps afterward. We disagree. In roughly 17 of the 25 Atlassian estates we reviewed in 2024 and 2025, the app line was 40 percent or more of the platform cost, and migrating before auditing locked unused apps into the new higher tier. The buyer side move is to audit and right size the apps before the platform quote, retire what no team uses, and model the app tier on the destination so the apps inform the choice between Data Center and Cloud. The apps often decide the destination, so they cannot be an afterthought.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Audit the apps before you move the platform. The destination that looks cheaper on the host product can be the more expensive one once the Marketplace tiers land on the quote.
White Paper · Atlassian
Atlassian Cloud Migration Guide 2026
What an Atlassian Cloud migration actually costs in 2026, the Data Center end of life pressure, and the buyer side moves that cap the bill. Read it free.
Atlassian ended sales and then support for its Server products, which forced customers onto Data Center or Cloud. Atlassian documents the migration paths on its migration pages, and the change reset the cost of every Marketplace app tied to those products.
Marketplace apps are licensed to match the host product tier, by user count on Data Center or by the Cloud plan and user band. The app price is tied to the platform tier, so the user count drives both at once.
App cost rose because Data Center and Cloud tiers are priced higher than the old Server tiers, and apps are priced to match the host tier. Moving the platform automatically repriced every paid app on it.
It depends on the estate. Cloud suits standardized teams that want managed infrastructure. Data Center suits regulated or highly customized environments. Model the full app tier cost on both, because the apps often decide the answer.
Yes. Migration is the moment to audit which apps are still used, consolidate overlapping apps, and right size the user tier. Many estates carry paid apps that no team has opened in months.
Yes. Both host product and app prices step up at user tier thresholds. A small increase in user count can push you into a higher tier on the platform and on every paid app at the same time.
Plan at least one hundred and twenty days ahead, and treat the migration and the renewal as one event. The app audit and tier modeling take time, and rushing into the Cloud quote locks in unaudited app cost.
Across the Atlassian estates we reviewed in 2024 and 2025, the largest savings came from removing unused apps and right sizing user tiers before migration, not from negotiating individual app discounts.
A buyer side review of your Atlassian Marketplace apps, Data Center tiers, and Cloud migration path. Used across more than five hundred enterprise software engagements.
Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Independent review of your Atlassian estate and app spend. Corporate email only.
Open the Hub →The platform migration had a budget. The Marketplace apps did not. When we added the app tiers to the Cloud quote, the apps cost more than the platform, and nobody had modeled that line before the project started.
Confidential consultation. No follow up sales call unless you ask for one.
Oracle Eloqua framework signals, Eloqua edition signals, marketable contact tier signals, Eloqua advanced intelligence signals, Eloqua app cloud signals, and the broader Oracle commercial leverage signals.
