Methodology: vendor lifecycle, pricing and migration pages, partner and buyer-data sources, and one vendor-commissioned study, checked on 13 Oct 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.
An ITSM business case wins approval when it answers the four questions your CFO will ask anyway. What does staying cost? What does moving cost? What can go wrong either way? Why decide now? Answer each with dated facts and tie the decision to your contract's notice date.
This guide is for the Head of Service Management or ITSM platform owner taking that case to a CIO or CFO. It ends with a one-page template you can copy.
Key takeaways
- Cherwell Service Management reaches end of life on 31 Dec 2026, according to StrataCom and Beyond20 (as of 13 Oct 2026).
- Atlassian's new Cloud list prices took effect on 13 Oct 2026. Service Collection Standard, 100 agents, annual, moved from $19,700 to $21,000 (Atlassian pricing tables, as of 13 Oct 2026).
- Workflows, automations and SLA definitions are rebuilt, not migrated. Atlassian says migrated automation flows are disabled by default in Cloud (as of 13 Oct 2026).
- Vendor-commissioned ROI studies, such as the Forrester Consulting study of Jira Service Management commissioned by Atlassian, describe a composite organization, not yours (Atlassian blog, 8 Jan 2025).
What an ITSM business case has to prove
An ITSM business case is a short decision document that compares the full cost and risk of staying with the full cost and risk of moving, over the same period, and names the date the decision has to be made.
The date is easy to leave out. Without it, "let's revisit next quarter" wins, because doing nothing never shows up as a line item.
The CIO wants to know what breaks if you stay or move, and whether the team can deliver. The CFO wants a three-year total per option, cash timing, and the date a commitment becomes unavoidable.
Write for the CFO first. Then include at least three options: stay and renegotiate, upgrade with the same vendor, and move. A case that only presents "move" reads like a request, not an analysis.
The cost of staying: renewals and end-of-life dates
Staying is not free, and for several platforms it is not stable either. Put the dates that apply to you in your case, in the vendor's own words.
| Platform or product | Date | What happens | Source (as of 13 Oct 2026) |
|---|---|---|---|
| Atlassian Cloud (Jira Service Management, Service Collection) | 13 Oct 2026 | New list prices. Service Collection Standard, 100 agents, annual: $19,700 to $21,000 | Atlassian future pricing tables |
| BMC Helix ITSM OnPrem 23.3.04 and 25.2.01 | 3 Dec 2026 | End of version support | BMC product support page |
| Cherwell Service Management | 31 Dec 2026 | End of life | StrataCom; Beyond20 |
| System Center 2016 Service Manager | 11 Jan 2027 | End of extended support. Windows Server 2016 follows on 12 Jan 2027 | Microsoft Lifecycle |
| Opsgenie | 5 Apr 2027 | End of support; product shut down and data not yet migrated deleted | Atlassian |
| Jira Data Center, including Jira Service Management | 30 Mar 2028 | Last day for existing customers to buy new subscriptions or expansions | Atlassian |
| Jira Data Center | 28 Mar 2029 | End of life. Instances become read-only | Atlassian |
| System Center 2019 Service Manager | 9 Apr 2029 | End of extended support | Microsoft Lifecycle |
Microsoft dates are Pacific calendar dates; its lifecycle pages print 6:59:59 AM on the following day.
To turn the dates into a cost, price four things.
- The next renewal, not this year's invoice. For Jira Service Management and Service Collection, Eficode and Valiantys both put the 13 Oct 2026 list increase at 7.5% for Standard and Premium and 10% for Enterprise (as of 13 Oct 2026).
- Support exposure. Atlassian says Data Center renewals are prorated so they cannot run past end of life, and extended maintenance after 28 Mar 2029 is available only by exception (as of 13 Oct 2026). If your plan runs past a date like that, say what it means.
- The stack underneath. Staying on System Center 2016 Service Manager past 11 Jan 2027 also means Windows Server 2016 past its end date (Microsoft Lifecycle). Standing still can need its own upgrade project.
- Customization debt and workaround time. ServiceNow's implementation workbook (March 2021) warns that excessive customization "can create downstream maintenance costs" and "increase the testing time required for upgrades". Measure your own admin hours on upgrades, broken integrations and manual reports over the last 12 months.
The cost of moving: every line, including the ones that get dropped
A budget with only "new licenses" and "implementation partner" is incomplete. Vendr, which tracks software purchases, says ServiceNow implementation costs "can range from a significant portion to multiples of annual software spend" (last updated February 2026, as of 13 Oct 2026). Whatever platform you pick, give services their own lines.
Start with one principle. Workflows, automations, business rules, SLA definitions, macros and running SLA timers are rebuilt on the target, not migrated. Atlassian says "All migrated automation flows are disabled on the cloud by default post migration", and Freshworks lists "SLA policies and business rules" among elements to be "rebuilt or reconfigured manually post-migration" (as of 13 Oct 2026).
History is a separate workstream. ServiceNow says update sets "capture configuration details but exclude task or process data" (as of 13 Oct 2026). Configuring the new platform moves no closed incidents.
| Cost line | What it covers | Why it gets missed |
|---|---|---|
| New platform subscription, three years | Agent licenses, add-ons, uplift at each renewal | Only year one gets quoted |
| Implementation and configuration | Process design, forms, portal, catalog, roles | Usually the only services line quoted |
| Rebuild of logic | Workflows, automations, business rules, SLA definitions, macros, notifications | Assumed to come across with the data |
| Data migration | Incidents, requests, problems, changes, knowledge articles, CIs and relationships, attachments, SLA history | Configuration tools do not carry records |
| Integrations | Monitoring, identity, HR, chat and reporting feeds | Each needs its own test |
| Overlap licenses | Both platforms live through testing, cutover and hypercare | Go-live and contract end do not line up by default |
| Archive of the old platform | Read-only access or a full export for audit and retention | Some vendors delete data after cancellation |
| Training and hypercare | Agent and admin training, support after go-live | Treated as business as usual |
| Internal staff time | Mapping, user acceptance testing, reconciliation sign-off | Not invoiced, so not counted |
| Contingency | An explicit amount owned by the sponsor | Left implicit, then spent anyway |
Decide history scope in writing. itsm.tools (Brian Parks) describes three options: full history, active work only, or archive the old platform and migrate a smaller set. He calls full history "expensive, risky" and recommends "Archive the old, migrate what matters to the business." That is one view. Your case needs the chosen option, its cost and its effect on reporting and audit.
Then list the offsets. Atlassian offers step-up credits for unused Data Center maintenance and dual licensing for larger customers during migration, and says Cloud Enterprise bought by June 2027 "may be eligible" for a 10 to 20% first-year discount (as of 13 Oct 2026). Ask every shortlisted vendor in writing.
Risks on both sides, and how to reduce each one
A risk section that lists only migration risks implies staying is safe. Put both sides in one table.
| Risk | Side | How to reduce it | Evidence for the CFO |
|---|---|---|---|
| Running past end of support | Staying | Plan the exit before the date; price any extended support offered | Vendor lifecycle page |
| Renewal uplift with no alternative | Staying | Run a competitive evaluation before the notice deadline | Competing quotes |
| History left behind, reporting restarts from zero | Moving | Agree scope in writing; reconcile record counts by type after each load | Signed scope, reconciliation report |
| Automations and SLAs behave differently | Moving | Rebuild and test them on the target before cutover | Test results |
| Cutover fails | Moving | Test migration on real data, delta sync, go/no-go criteria, rollback plan | Go/no-go checklist with owners |
| Overlap costs run long | Moving | Align go-live with contract end; agree a short extension in advance | Contract terms |
| Data deleted after cancellation | Moving | Export and archive before termination; negotiate access in exit terms | Archive location and retention period |
Zendesk, for example, says that when you cancel "you lose access to your data", and after 90 days "the automated process begins to permanently delete service data" (Zendesk help center, as of 13 Oct 2026). Check your vendor's equivalent clause before signing anything new.
Benefits you can defend in front of a CFO
Benefits lose credibility fastest when they borrow someone else's numbers. Build yours from your own baseline.
- Pull 12 months of baseline data: volumes by type, time to resolve, SLA attainment, reopen rate and admin hours.
- Separate hard from soft benefits. Hard benefits are costs that disappear, such as licenses and support contracts; soft benefits are productivity gains. Total them separately.
- Count avoided cost. An upgrade project or extended support fee you no longer pay comes straight from the cost-of-staying section.
- Set review dates for each benefit and name who measures it.
Treat vendor-commissioned studies as context, not inputs. Atlassian commissioned Forrester Consulting to run a Total Economic Impact study of Jira Service Management. Atlassian's blog (8 Jan 2025) reports "a 275% return on investment", "$9.5 million in total benefits over a three-year period" and payback "in less than six months" for a composite organization (as of 13 Oct 2026). Cite it in an appendix, labeled as vendor-commissioned, and keep its figures out of your totals.
Tie the ITSM business case to your contract renewal
The renewal date is not your deadline. The notice date is. Find the auto-renewal and notice clause in your current contract and plan backwards from it. The list below runs backwards, from the notice deadline to the first step you take.
- Notice deadline. The last day to give notice or change your commitment.
- Decision. CIO and CFO approve or reject. Leave room for one round of questions.
- Competing quotes. Vendr says ServiceNow buyers "typically achieve savings on renewals by demonstrating competitive evaluation" (as of 13 Oct 2026). Even if you stay, it helps the negotiation.
- Test migration on real records. It turns migration risk into evidence.
- Discovery and inventory. Volumes, attachments, integrations, customizations, history scope.
There is no neutral public benchmark for how long these steps take. Freshworks says ServiceNow to Freshservice migrations "typically range from 4-12 weeks", and BMC Helix estimates 14 to 20 weeks for its Remedy on-premises to hosted BMC Helix ITSM migration service (as of 13 Oct 2026). Treat these as vendor claims, not your plan.
Watch quote expiry too. Valiantys notes that Atlassian quotes are generally honored until they expire, and an expired or replaced quote moves to the new pricing (as of 13 Oct 2026). A short bridge term can buy time, but price it in the case.
One-page ITSM business case template you can copy
One page, with detail in appendices.
| # | Section | What to write | Evidence the CFO will ask for |
|---|---|---|---|
| 1 | Decision and date | The decision you need and the notice deadline it must beat | Contract clause |
| 2 | Current state | Platform and version, contract end, agents, record volumes, key integrations | Contract, admin reports |
| 3 | Cost of staying, three years | Next-term renewal, support exposure, required upgrades, workaround time | Vendor quote, lifecycle pages, timesheets |
| 4 | Cost of moving, three years | Every line from the cost-of-moving table, including history scope and contingency | Vendor and partner quotes, internal effort |
| 5 | Options compared | Stay and renegotiate, upgrade with the same vendor, move | One total per option |
| 6 | Risks and mitigations | Both sides, each with an owner | The risk table |
| 7 | Benefits | Hard and soft, totalled separately, with baselines and review dates | 12-month baseline |
| 8 | Rebuilt vs migrated | Workflows, automations and SLA definitions rebuilt; records, knowledge and CIs migrated per agreed scope | Signed scope, test migration results |
| 9 | Timeline | Backwards plan from the notice deadline | Dated milestones with owners |
| 10 | Recommendation and ask | Recommended option, budget, who signs | Approval block |
FAQ
Methodology
We read lifecycle, pricing and migration pages from Atlassian, Microsoft, BMC Helix, Freshworks, ServiceNow and Zendesk, partner analyses from StrataCom, Beyond20, Eficode and Valiantys, buyer data from Vendr, and one vendor-commissioned Forrester study as reported by Atlassian. Every date, price and quote was checked on 13 Oct 2026. Where no neutral benchmark exists, we say so.
Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.