A business case fails when it leads with the platform and asks finance to care. Finance does not care that Cloud has better integrations; finance cares what the next three years cost under each option. So build the case as a comparison: the cost of staying versus the cost of moving, both fully loaded, both over the same window, with the risk of the 2029 retirement priced in. This article sits under our Atlassian Data Center end of life 2026 migration and cost guide.
Pull your current Atlassian Data Center spend, user count, and app (Marketplace) list. Those three numbers anchor every line of the model. Without them the business case is opinion.
What goes in an Atlassian Cloud migration business case?
Five components, built as a side-by-side. Get all five on one page and finance can make the call.
- Cost of staying on Data Center, projected forward with the announced list increases and your hosting and upgrade labor.
- All-in cost of Cloud, including the subscription, app re-licensing on Cloud, and any Rovo AI add-on.
- One-time migration cost, covering data, workflow rebuild, integrations, and a short dual-running overlap.
- Value of the Ascend incentives, including the migration discount, dual-licensing and any loyalty credit.
- Risk of the 2029 retirement, priced as the premium of a forced late migration versus a planned one.
The detail behind the Cloud number is in Jira Service Management Cloud Enterprise pricing 2026, and the incentive levers are in Atlassian Ascend program discounts.
What to do next: build a single three-year table with two columns, stay and move, and one row per component above. That table is the business case.
How do you show the cost of staying on Data Center?
The do-nothing option is not a flat line, and that is the heart of the case. Atlassian has announced Data Center list increases that have run in the range of 15 to 40 percent, so your renewal cost rises year over year even before you add capacity. On top of the license, you carry the hosting, patching, upgrade and security labor that Cloud absorbs. Project all of that forward to the 2029 retirement and you have an upward curve, not a stable cost.
Finance responds to that curve because it reframes the decision. The question stops being "why spend money to move" and becomes "why keep spending more to stay on a platform that retires in 2029." Be conservative and cite the increases as announced ranges rather than inventing a single figure, and note that the exact uplift varies by product and deal.
What to do next: model the Data Center renewal forward three years at the announced increase range, add your internal hosting and upgrade labor, and show that total as the baseline.
What does the Cloud side of the model need?
The Cloud number is more than the subscription, and leaving out the extras is how a business case gets ambushed in committee. Include three things the subscription does not cover by default.
| Cloud cost line | Why it matters | Watch for |
|---|---|---|
| Subscription by user tier | The core recurring cost | User-tier pricing cliffs as you grow |
| Marketplace app re-licensing | Your Data Center apps re-price on Cloud | Apps that cost more, or do not exist, on Cloud |
| Rovo AI add-on | Optional, around $20 per user per month | Buying it for the whole base on day one |
App re-licensing is the line most often missed. Your Marketplace apps do not migrate for free; they re-price under Cloud terms, and some cost more or have no Cloud equivalent. The way to control that is in Atlassian Marketplace app re-licensing on Cloud. Treat Rovo as optional and scope it to real users rather than the whole base. The avoidance of the user-tier jump is in how to avoid the Atlassian Cloud user-tier pricing cliff.
What to do next: price the apps and AI separately from the subscription so finance sees the true all-in Cloud cost, not just the per-user headline.
What is the strongest argument for finance?
That doing nothing is neither free nor stable. Data Center list prices are rising, support ends, and a migration forced into the final months before retirement costs more, in rushed services and lost leverage, than one planned on your own timeline. The business case finance approves is the one that shows moving now, with the Ascend incentives captured and the costs scoped cleanly, beats waiting and migrating under duress.
Pair that with timing discipline. You negotiate the best Cloud deal while a Data Center renewal is still a credible option, which is the window the end-of-life clock leaves open through the 30 March 2028 renewal cutoff. The timing method is in how to time an Atlassian Data Center renewal against the 2028 deadline, the platform context is on our Jira Service Management platform page, and the deeper finance framing is in our gated CIO and CFO Guide to ITSM Cost.
What to do next: put the do-nothing curve and the net-of-incentives move cost on one slide, recommend a sign-by date tied to your migration timeline, and let the three-year net position make the argument.
Book a renewal review.
We build the three-year model, capture the Ascend incentives, and hand you a business case finance will approve. Fixed fee or gainshare: no savings, no fee.
Book a renewal review →Frequently asked questions
- What goes in an Atlassian Cloud migration business case?
- The cost of staying on Data Center with announced increases, the all-in Cloud cost including app re-licensing and Rovo AI, the one-time migration cost, the Ascend incentive value, and the 2029 retirement risk, all over a three-year window.
- How do I show the cost of staying on Data Center?
- Project current spend forward with the announced list increases, which have run in the 15 to 40 percent range, plus your hosting and upgrade labor. That rising curve into 2029 is the do-nothing baseline.
- What is the strongest argument for finance?
- That doing nothing is not free or stable. Prices rise, support ends, and a forced late migration costs more. Moving on your timeline with Ascend incentives captured wins on the three-year net position.
Doing nothing is not free.
We have negotiated $420M+ in ITSM contract value across 500+ engagements. Let us build the Atlassian Cloud migration case your CFO will sign.
Book a renewal review →