For Atlassian Marketplace vendors, Cloud migration is no longer just a roadmap item. Connect is on the path to end of support in Q4 2026, Data Center sales for new customers stop on March 30, 2026, and Forge pricing becomes consumption-based from January 1, 2026. That means moving to Cloud is no longer only a technical decision — it directly affects product strategy, delivery, and margin.
But one thing is often underestimated: getting an app to run in Cloud is not the same as getting it ready to succeed there.
Migration is not just a rewrite
Many Atlassian Marketplace vendors begin with a simple question: how do we move this app to Cloud?
In practice, the harder question is: how do we make this app work well in Cloud over time?
For Marketplace apps, migration usually means more than rewriting code. It often includes rethinking architecture, adapting to Forge or hybrid models, revisiting integrations, and preparing for a different operational model.
The hidden costs Atlassian Marketplace vendors often miss
1. Re-architecting takes longer than expected
A Data Center or Connect app often carries assumptions that do not translate cleanly into Cloud. Background processing, storage patterns, authentication flows, infrastructure control, and backend-heavy logic may all need to be redesigned rather than simply moved.
This is one of the biggest hidden costs in migration projects: the work is not just rewriting code, but deciding what should be rebuilt, what should be simplified, and what should no longer exist in the Cloud version.
For vendors, that means effort estimates based only on “feature migration” are often too optimistic.
2. Security and compliance add real delivery effort
Cloud app delivery is not only about shipping functionality. Atlassian’s Marketplace expectations now include stronger security workflows, including questionnaires, partner verification, vulnerability scanning, and required Privacy & Security disclosures. These requirements affect both onboarding and ongoing app updates.
That creates a second layer of work around the migration itself. Even when the app is technically ready, release timelines can still slow down if the team is not prepared for documentation, review responses, or remediation work.
For smaller vendors especially, this becomes a real bandwidth problem: the same internal team is often expected to handle migration, release quality, security evidence, and customer support at the same time.
3. Forge is easier to manage, but not free to run
Forge is a strong path forward, but it should not be treated as “free hosting.” Atlassian’s Forge pricing takes effect on January 1, 2026 and shifts the platform to a consumption-based pricing model with a free tier followed by paid usage. Atlassian also provides usage monitoring specifically so vendors can track the costs they are generating.
That changes the economics of Cloud apps.
A Forge app may be easier to operate from an infrastructure perspective, but it can still become expensive if compute usage, storage reads and writes, or function execution patterns are not designed carefully. This matters even more for apps that are automation-heavy, data-heavy, or AI-driven.
In other words:
Forge reduces operational overhead, but vendors still need cost-aware engineering.
4. Performance problems often appear after launch
Many migration projects focus on passing test cases and reaching release. But Marketplace apps do not live in a controlled test environment. They run across real tenants, different usage patterns, different data volumes, and sometimes unpredictable integrations.
That is when new problems tend to appear:
latency under real load
inefficient API usage
rate limit issues
tenant-specific edge cases
support tickets that were invisible during migration testing
This is why Cloud readiness is broader than Cloud compatibility. A release can be technically complete and still not be operationally ready.
5. Migration is not the end of the cost
Another common mistake is treating migration as a one-time project. In reality, once the Cloud version launches, a new phase begins:
bug fixing
performance tuning
release follow-up
support requests
feature parity improvements
compatibility and compliance updates
For many vendors, this post-launch work becomes just as important as the migration itself.
So the real question is not only, “How much does migration cost?” It is also, “What will it take to maintain this app successfully after migration?”
What smart vendors do differently
The strongest Marketplace teams do not treat migration as a one-time project. They plan for:
architecture fit, not just feature parity
security readiness, not just release speed
cost control, not just infrastructure reduction
long-term maintenance, not just initial launch
That is usually the difference between an app that simply reaches Cloud and an app that performs well there.
Final thought
For Atlassian Marketplace vendors, Cloud migration is no longer just about moving away from legacy frameworks or meeting platform deadlines. It is also about making sure the app is ready to perform well, stay compliant, and remain sustainable after launch.
The teams that approach migration with that broader view will be in a much stronger position in the years ahead.
If your team is currently reviewing migration options, rethinking architecture, or simply comparing possible paths forward, it may be helpful to discuss the challenges early.
At DS Solution, we work with Marketplace vendors on Forge development, Connect and Data Center migration, and long-term app maintenance — and we’re always happy to exchange ideas.
