Reducing Atlassian Marketplace Costs: Consolidation and Renegotiation

How Marketplace App Spend Gets Out of Control

Atlassian Marketplace apps are designed to be frictionless to install. Any admin with the right permissions can add a new app in minutes, often on a free trial basis, without a formal procurement decision or budget approval. Over the lifecycle of a large enterprise Atlassian instance, which typically spans five to ten years, this dynamic produces an estate of 80 to 200 apps, many installed by individuals who have since left the organisation and for use cases no longer active.

The billing model reinforces the drift. Apps are licensed per user, aligned to the Jira or Confluence user count on the instance. As user counts rise, every installed app renews at the higher tier automatically. The cost of any single app appears modest in isolation. The aggregate cost of 100 apps renewing at enterprise user tiers represents a material spend line that finance and procurement functions rarely scrutinise with the same rigour applied to the base licence.

The pricing changes Atlassian introduced across 2025 and 2026, including the shift to maximum quantity billing for Cloud apps from July 2025, have changed the cost calculation for Marketplace apps in ways that require active analysis. Organisations auto-renewing on historical pricing assumptions are likely paying more than the equivalent Cloud model, or in some cases less. The only way to know is to model it explicitly.

Step One: The App Usage Audit

No consolidation or renegotiation strategy can proceed without accurate data. The Atlassian Cloud Migration Assistant provides a starting list of installed apps across instances, but the most operationally useful tool for DC environments is the App Usage for Jira capability available in Jira DC version 8.20 and above. This provides actual usage data: not just what is installed, but which apps are being actively used and by what proportion of the licensed user base.

Cross-referencing installation lists against actual usage data consistently produces three categories. Apps with active, broad usage across the majority of licensed users are the core estate that must be handled carefully in both migration and renegotiation. Apps with low usage, typically fewer than 20 percent of licensed users engaging with the functionality, are renegotiation candidates where user tier reduction is a realistic ask backed by data. Apps with zero or near-zero usage are immediate decommission candidates with no business case for continued licence fees.

A structured audit across a typical large enterprise Atlassian estate identifies 20 to 40 percent of apps in the zero-usage category. Eliminating shelfware before Cloud migration planning reduces both migration complexity and ongoing cost base. The financial impact of eliminating unused apps alone, before any vendor renegotiation, commonly produces 5 to 15 percent reduction in total Atlassian spend. That is savings achievable immediately, independent of any migration timeline decision.

Migration as the Cost Reset Moment

The DC-to-Cloud migration is primarily understood as a technical programme. Its role as a cost reduction mechanism is systematically underused. The migration window creates a natural reset point for the entire Marketplace app estate, and organisations that deliberately use it as such consistently extract more commercial value from the transition than those who execute a straightforward lift-and-shift of their current DC portfolio into Cloud.

Two migration approaches produce structurally different outcomes for Marketplace cost. The selective migration approach audits the DC estate first, identifies which apps are genuinely required on Cloud, and migrates only those apps. This produces a leaner Cloud app portfolio with materially lower ongoing costs. The clean-slate approach removes all apps at migration time and selectively reintroduces only apps explicitly requested by users post-migration. This approach frequently reveals that a significant proportion of previously installed apps are not missed when no longer automatically available.

Both approaches are operationally valid depending on the organisation's change management capacity and IT governance maturity. What is not valid is carrying every DC app into Cloud automatically without assessment. That locks in current spending levels and forfeits the reset opportunity entirely.

Renegotiating Marketplace App Licences: What Works

Marketplace apps are sold by independent software vendors, not by Atlassian directly, so renegotiation is a vendor-by-vendor engagement rather than a single commercial relationship to work through an Atlassian account team. The migration context provides consistent leverage worth using systematically.

Vendors know that customers approaching Cloud migration are making active decisions about which apps to carry forward. Vendors who want to retain the customer relationship on Cloud have motivation to offer competitive Cloud pricing, migration support commitments, and extended parallel trial access during the transition. For apps with significant annual spend, initiating this conversation six to twelve months before migration gives vendors time to respond commercially while maintaining negotiating pressure from the migration choice conversation.

Enterprise Cloud Edition customers additionally have access to multi-instance pricing for Marketplace apps, allowing organisations deploying an app across multiple Atlassian instances to pay based on unique users across all instances rather than per-instance. For organisations with multiple Jira or Confluence instances, this can produce meaningful savings compared to individual per-instance licences. One important change from January 2026: Atlassian discontinued bundled promotion codes for Marketplace apps. Multi-app discount codes that previously allowed ISV partners to offer discounts across two or more apps simultaneously are gone. Every app discount must now be negotiated individually with each ISV vendor, making the per-app engagement more important than before.

Native Cloud Features That Eliminate Paid Apps

The most direct path to Marketplace cost reduction is often not negotiating a better price for an existing app but eliminating the need for it entirely by using capabilities now native to Atlassian Cloud. Atlassian has significantly expanded what Cloud plans include natively, particularly at Premium and Enterprise tiers, with many native capabilities directly overlapping with previously required third-party Marketplace apps.

Automation for Jira, included natively across all Cloud plans, covers a substantial portion of the workflow automation functionality that ScriptRunner and similar apps provided in DC environments. Advanced roadmaps in Jira Software Cloud Premium reduce dependence on third-party portfolio management apps. Confluence's native Cloud editor has absorbed many macro capabilities that previously required paid apps for diagrams, templates, and embedded content. Atlassian Guard, included in Cloud Premium and Enterprise, covers security governance functionality that DC customers previously purchased through separate apps.

Before committing to purchasing Cloud versions of existing DC apps, a feature-by-feature comparison against what the current Cloud plan tier provides natively is a necessary step. The answer frequently reveals that native Cloud capabilities cover 60 to 80 percent of what the third-party app provided, and the paid app can be eliminated or replaced with a lower-cost alternative serving only the remaining gap use cases. Across a full enterprise app estate, this analysis typically identifies five to ten apps per hundred where complete elimination is possible through native feature substitution.

Connecting Cost Reduction to the Broader Atlassian Contract

Atlassian Marketplace app costs are separate from core platform licensing, but they should be considered together in total cost of ownership analysis and negotiation strategy. The Cloud contract negotiation process provides context for what the total Atlassian relationship costs and what total spend leverage exists.

Organisations with significant total Atlassian spend, platform plus Marketplace, have more negotiating surface than those who treat each element as a standalone procurement. Demonstrating total spend awareness and active management of the Marketplace estate signals commercial sophistication that influences the overall relationship dynamic with Atlassian's account team, even if Marketplace app contracts are technically separate ISV relationships.

The Data Center EOL timeline creates time-bounded leverage for Marketplace cost reduction that diminishes as the deadline approaches. Vendors who need to transition customers to Cloud before 2029 have motivation to offer migration incentives and commercial terms that will not be available once the wind-down is complete. This leverage exists now and will narrow progressively through 2027 and 2028.

Practical Steps to Start Reducing Marketplace Costs Now

The sequence that produces the best results begins with the audit. Run App Usage analysis across all DC instances, generate the full installation and usage data, and segment apps into active, underused, and unused categories. This takes time but is the essential foundation for every subsequent decision.

Eliminate the unused apps immediately. There is no reason to wait for migration planning to remove apps nobody is using. Decommission them now, cancel licence renewals at next renewal date, and remove the cost from the current budget. This is the fastest win and carries no migration risk: removing unused apps cannot impact users who were not using them.

For underused apps, engage the vendor at next renewal with a tier reduction request. User-based pricing means that reducing the licensed user count to a tier that reflects actual usage is a legitimate commercial ask. Vendors may resist, but the combination of accurate usage data and the migration choice conversation creates leverage for tier rationalisation. For the remaining active apps, build a Cloud migration assessment that covers Cloud version availability, feature parity, and pricing comparison between DC renewal cost and Cloud version cost. Use this to drive both the migration sequencing decision and the vendor negotiation strategy for Cloud contracts.

Our team of Atlassian licensing and Marketplace cost specialists provides structured app estate audits, vendor negotiation support, and Cloud migration cost modelling across the full Atlassian spend footprint. The combination of shelfware elimination, tier renegotiation, native feature substitution, and migration credit optimisation consistently produces 20 to 35 percent reduction in total Atlassian cost for organisations that approach it systematically. Contact us to build the cost reduction plan before the migration window closes.