App Rationalization Framework: A Guide to Assessing Marketplace Apps

[#1]

Before and after an Atlassian cloud migration, sites often accumulate unused apps. Teams install apps to meet immediate needs, but over time, their purpose and usage are forgotten. This creates a pressing need to ensure that apps support, rather than slowing down, team performance. The Atlassian State of Teams 2025 report states that 89% of executives believe their organizations must accelerate to remain competitive. Excessive app usage can slow teams and risk this goal.

The "App Tax" You Didn’t Know You Were Paying

For Atlassian Platform Product Owners, an excess of apps impacts both budget and productivity:

• Each app requires onboarding. With 20 apps, your team must learn 20 different interfaces—increasing training costs, creating duplication, and leading to siloed knowledge.
• Duplicate features across apps lead to unnecessary costs, especially for similar tools like time-tracking apps.
• When data is spread across niche apps, visibility decreases, and AI tools are less effective, impacting productivity.

App Rationalization Framework: Keep, Swap, or Simplify?

Whether migrating to the Cloud, merging sites, or conducting an annual review, a clear strategy is essential. I met @Marcus Asmar, an Atlassian Senior Enterprise Technical Architect, this March in Munich, and he recommends treating each app as a strategic decision rather than just a technical requirement. He shared the following App Rationalization Framework in his workshop with us:

The Strategy	What it means for you	When to choose it
Replatform	Keep it. Move the app as-is.	It’s mission-critical and provides a unique, hard-to-replace capability.
Repurchase	Swap it. Find a new Cloud-native app.	The old app doesn't exist in the Cloud, but a better alternative does.
Refactor	Simplify. Use built-in Cloud features.	Cloud now has "native" features that replace the app's core use case.
Retire	Delete it. Stop using it entirely.	Usage is low, it’s redundant, or it no longer provides value.
Negotiate	Discuss. Fix legal or licensing terms.	The app is vital, but compliance or residency terms need a vendor fix.

There is no universally correct answer, and we should prioritize decisions that improve your team’s efficiency.

Handling the "But I might need it!" Conversation

A common challenge in site cleanup is concern over removing apps that may be needed later. Prioritize clarity over complexity. If a feature is not used regularly, avoid letting it create unnecessary bottlenecks. Designate these features as Phase 2 items and keep your migration lean. If a feature becomes essential in the future, it can be reinstated. Focus on the core functionality that delivers the most value.

The regular Health Check

Review your app list each year, focusing on new native features and actual usage data to stay efficient and lean.

1. Atlassian frequently introduces new native capabilities in its tool stack. Apps purchased last year may now be available as built-in features in Jira or Confluence Cloud. If the platform offers the functionality now natively, transition to it to reduce costs.
2. Review usage statistics. If you are paying for a high-tier user plan but only a few people use the app, consider retiring it.
   
   

Rationalization is a strategic approach. Maintaining a streamlined app list allows your team to focus on productive work rather than learning new tools.