Cherwell replacement before the December 31, 2026 end of life: Ivanti Neurons vs ServiceNow vs Freshservice vs JSM
Short answer
Ivanti lists Cherwell Service Management (CSM) with an end-of-life date of December 31, 2026 on its own Product End of Life hub. If you are still on Cherwell today, there are about two months left, which is not enough time for most teams to design, build and cut over a new ITSM platform properly. So do two things at once. First, protect yourself: take a full data export, confirm with your Ivanti account team exactly what happens to your tenant or on-premises licence, and agree any interim arrangement in writing. Second, choose a destination on fit, not panic. Ivanti Neurons for ITSM is the lowest-friction path if you want to stay with Ivanti and keep a similar no-code configuration style. ServiceNow fits larger or fast-growing organisations that want one platform for IT, HR and operations and can fund a platform team. Freshservice is the quickest to stand up for a mid-sized internal IT team that wants ITIL processes without heavy administration. Jira Service Management is the natural fit when your engineering teams already live in Jira. Freshservice and JSM publish prices; ServiceNow and Ivanti are quote-only.
Contents
- What Ivanti has actually confirmed about Cherwell end of life
- If you are starting now: what to do in the time left
- What you are actually migrating: Cherwell concepts and where they go
- The four realistic Cherwell replacements at a glance
- Ivanti Neurons for ITSM: the path of least resistance
- ServiceNow ITSM: the platform choice
- Freshservice: the fastest route to a working ITIL desk
- Jira Service Management: the choice when engineering already lives in Jira
- Pricing: what is public and what is not
- Which Cherwell replacement fits your situation?
- Frequently asked questions
What Ivanti has actually confirmed about Cherwell end of life
Before you plan anything, separate what the vendor has said from what you have heard. We checked Ivanti's own pages on Oct 31, 2026. The Ivanti Product End of Life hub lists "Cherwell Service Management (CSM) (EoL 12/31/2026)" and also "Cherwell Asset Management (CAM) (EoL 12/31/2026)". The original announcement, posted on the Ivanti Innovators Hub announcement thread on October 31, 2023, reproduces Ivanti's customer email: Ivanti "will End of Life the Cherwell Service Management solution, on December 31, 2026", additional licences can be bought before end of life, and "contract end dates will not go past December 31, 2026".
| Question | What Ivanti says | Where |
|---|---|---|
| End-of-life date for CSM | December 31, 2026 | Ivanti Product End of Life hub (checked Oct 31, 2026) |
| Can contracts run past that date? | No: contract end dates will not go past December 31, 2026 | Ivanti customer email quoted in the Innovators Hub announcement (Oct 31, 2023) |
| Ivanti's go-forward product | Ivanti Neurons for ITSM | Ivanti CSM End-of-Life FAQ and Ivanti's Cherwell history page |
| On-premises perpetual licences after EoL | The product keeps running, but Ivanti stops providing support | Ivanti CSM End-of-Life FAQ (sign-in required; wording as republished by Ivanti partners) |
| Cloud (hosted) tenants after EoL | The tenant is discontinued and no longer accessible 30 days after the end-of-life date | Ivanti CSM End-of-Life FAQ (sign-in required; wording as republished by Ivanti partners) |
Two notes on the table. Ivanti's CSM End-of-Life FAQ sits behind an Ivanti community sign-in, so we could not read it directly; the last two rows use the FAQ wording that several Ivanti partners have republished, and you should confirm them with your Ivanti account team for your own contract. And none of this tells you what Ivanti will offer you commercially for a late move. That is a conversation to have now, in writing.
If you are on Cherwell cloud, the deadline is sharper
A hosted Cherwell tenant does not keep running unsupported the way an on-premises install does. If the FAQ wording holds for your contract, you have the end-of-life date plus 30 days to get your data out. Request and test a full export before December, not after.
If you are starting now: what to do in the time left
A careful ITSM replacement normally involves requirements, design, build, data migration, testing, training and a cut-over. Squeezing all of that into the weeks left in 2026 is how teams end up with a new tool configured like the old one, with none of the clean-up they wanted. Our advice is to split the work into what must happen before the deadline and what can follow it.
Before December 31: protect the service and the data
1. Confirm your position with Ivanti in writing. Deployment type, licence type, renewal date, what happens to your tenant or support, and any transition offer. 2. Export everything. Incidents, requests, problems, changes, configuration items, knowledge, customers and users, attachments, and your configuration (business object definitions, one-step actions, automation processes, forms, dashboards). Test that the export opens and is complete. 3. Freeze change in Cherwell. No new customisations from here on; every new rule is one more thing to rebuild. 4. Make the platform decision. Use the comparison in this guide to get to a shortlist of one or two, then run focused demos against your top workflows.
After the decision: phase the build
Start with the work your users see every day: incident, service requests and the portal, knowledge, and SLAs. Move change, problem and the CMDB in a second phase. Bring across only the history you will actually use; archive the rest in a searchable read-only store (a database export reported through your BI tool is usually enough). Our ServiceNow to Freshservice migration guide describes the same phased pattern for a different source tool.
If you are on-premises with perpetual licences, running Cherwell unsupported for a short, defined period while you migrate is a legitimate option, but treat it as a risk decision: no vendor fixes, no security updates, and your own team becomes the only support. Write down the exit date and who signs off on the risk.
What you are actually migrating: Cherwell concepts and where they go
Cherwell's strength was codeless configuration: business objects, forms and one-step actions that admins could build without code. That is also what makes leaving hard. Every destination has equivalents, but none of them is a one-to-one copy, and many Cherwell builds were workarounds for things newer platforms do natively.
| Cherwell concept | Ivanti Neurons for ITSM | ServiceNow | Freshservice | JSM |
|---|---|---|---|---|
| Business objects (major, supporting, lookup) | Business objects (closest model) | Tables (extend task or cmdb_ci) | Ticket types, custom objects, custom fields | Work types, request types, custom fields, Assets object types |
| Forms and form arrangements | Forms and layouts | Forms, UI policies | Ticket forms, dynamic sections | Request type forms, portal forms |
| One-step actions | Quick actions, workflows | Flow Designer flows, UI actions | Workflow Automator, scenario automations | Automation rules |
| Automation processes | Workflows | Flows, business rules | Workflow Automator | Automation rules, workflows |
| Expressions and stored values | Expressions, calculations | Scripts, flow data pills | Workflow conditions, placeholders | Smart values in automation |
| Customer portal | Self-service portal | Service Portal, Employee Center | Support portal, service catalog | Help center, portal |
| CMDB items and relationships | CMDB | CMDB (cmdb_ci, cmdb_rel_ci) | CMDB / asset management | Assets (objects and references) |
| Dashboards and widgets | Dashboards | Dashboards, Platform Analytics | Analytics dashboards | Dashboards, reports |
| mApps and blueprints | Ivanti configuration-transfer tooling (confirm scope with Ivanti) | Update sets, scoped apps | Sandbox (Enterprise) | No direct equivalent; configure per project |
Treat this map as a starting point for design conversations, not a field-by-field spec. Our rule of thumb: rebuild the outcome, not the mechanism. If a Cherwell one-step action existed to work around a missing feature, check whether the destination already does it before you rebuild it.
The four realistic Cherwell replacements at a glance
| Ivanti Neurons for ITSM | ServiceNow ITSM | Freshservice | Jira Service Management | |
|---|---|---|---|---|
| Who it fits | Cherwell customers who want to stay with Ivanti and keep a similar configuration model | Larger or fast-growing organisations wanting one platform across IT, HR and operations | Mid-sized internal IT teams wanting ITIL processes with low admin load | Organisations whose engineering and IT teams already work in Jira |
| Deployment | Cloud, on-premises or hybrid (per Ivanti datasheet) | SaaS | SaaS | Cloud; Data Center for self-managed |
| Public pricing | No: quote only | No: quote only | Yes | Yes |
| Admin skill needed | Ivanti configuration skills (closest to Cherwell) | Dedicated platform admin/developer skills, JavaScript for advanced work | IT generalist admin | Jira admin skills |
| Migration path from Cherwell | Vendor-supported path with Ivanti tooling and services | Partner-led project | Partner-led or in-house project | Partner-led or in-house project |
| Main risk | Choosing it only because it is the default | Cost and complexity outgrowing the team | Hitting limits on deep customisation | ITIL depth depends on plan and configuration |
There are other credible ITSM tools. This guide covers these four because Ivanti Neurons is the vendor's own path, and ServiceNow, Freshservice and JSM span the range from enterprise platform to lighter mid-market tools.
Ivanti Neurons for ITSM: the path of least resistance
Ivanti positions Neurons for ITSM as the go-forward product for Cherwell customers. According to Ivanti's Ivanti Neurons for ITSM datasheet, it is built on industry standards with 14 ITIL 4-certified practices and can be deployed in the cloud, on-premises or in a hybrid combination. Ivanti also notes that its AI capabilities are available on SaaS deployments with specific licence tiers, so check which features you would get on the deployment you choose.
Best for
- Teams that want to stay with one vendor and avoid a full re-platform decision under time pressure.
- Cherwell estates that need an on-premises or hybrid option, which neither Freshservice nor ServiceNow offers.
- Organisations that already use other Ivanti products (endpoint management, asset discovery, security) and want them connected to service management.
Wrong choice when
- You were already unhappy with Cherwell's direction and are choosing Ivanti only because it is the default path. A forced migration is a rare chance to re-evaluate; use it.
- You want a large third-party ecosystem of apps and admins to hire from. Compare the talent market in your region before you commit.
- Your main driver is lower admin effort. Moving to a similar configuration model can carry your old complexity across with it.
Pricing: Ivanti does not publish Neurons for ITSM prices; its Ivanti request-a-quote page routes you to a specialist. Ask specifically whether any migration incentive or credit applies to Cherwell customers, and get it in writing with its expiry date.
ServiceNow ITSM: the platform choice
ServiceNow is the default enterprise choice when service management is part of a wider platform plan: IT, HR service delivery, security operations, customer service and custom workflow apps on one data model. Its ServiceNow ITSM pricing page describes three ITSM packages (ITSM Foundation, ITSM Advanced and ITSM Prime) but publishes no prices. Expect a sales-led quote; in our experience it is driven mainly by the number of fulfillers (agents), the package and any add-ons.
Best for
- Organisations with Cherwell used across several departments that want one enterprise service management platform.
- Teams that can fund a platform owner and at least one dedicated admin or developer, internal or through a partner.
- Complex change, CMDB and integration requirements where depth matters more than speed of setup.
Wrong choice when
- You are a mid-sized IT team with a few dozen agents and no appetite for a platform team. You may pay for depth you will not use.
- You need to go live in weeks. A ServiceNow implementation done properly is a project, not a switch-over.
- You need a self-hosted option. ServiceNow is SaaS.
If ServiceNow makes your shortlist, read our Freshservice vs JSM vs ServiceNow comparison for how it compares on admin load for teams under about 500 employees.
Freshservice: the fastest route to a working ITIL desk
Freshservice is a SaaS ITSM tool aimed at internal IT teams. Its Freshservice pricing page (checked on Oct 31, 2026) lists Starter at $19, Growth at $49 and Pro at $99 per agent per month, billed annually, with Enterprise priced on request. Problem, change and release management sit in Pro and above; Growth adds the service catalog and SLA management to Starter. Sandbox and audit logs are Enterprise features.
Best for
- Mid-sized internal IT teams that used Cherwell mainly for incident, request, knowledge and basic change.
- Teams that want a short path to go-live and an admin model an IT generalist can run.
- Organisations that do not need self-hosting.
Wrong choice when
- Your Cherwell instance has heavy custom business objects that drive non-IT processes. Freshservice supports custom objects and workflows, but deep bespoke data models are a better fit for a platform tool.
- You need an on-premises deployment.
- You need sandbox-based change control for configuration but are not budgeting for Enterprise.
For a realistic multi-year cost comparison, see our Freshservice vs JSM vs ServiceNow pricing guide.
Jira Service Management: the choice when engineering already lives in Jira
Jira Service Management (JSM) makes most sense when IT incidents, changes and engineering work need to flow between the same tools. The Atlassian JSM pricing page (checked on Oct 31, 2026, monthly billing at the page's default team size) shows a Free plan for up to 3 agents, Standard at $21.50 per agent per month and Premium at $55.28 per agent per month, with Enterprise available through sales on annual billing. Premium adds advanced incident and problem management and change management features; Assets (configuration management) is included from Standard, with object allowances by plan.
Best for
- Organisations where developers and IT operations already use Jira, so changes, incidents and deployments link naturally.
- Teams that want to start on Standard and move to Premium as ITIL processes mature.
- Teams that need a self-managed option for now (JSM Data Center), with a plan for its own lifecycle. Atlassian has set an end of life for Data Center products; see our JSM Data Center to Cloud guide.
Wrong choice when
- Your IT team does not use Jira and has no Atlassian skills; the configuration model has a learning curve.
- You expect a full ITIL suite out of the box on the cheapest plan. Compare Standard and Premium feature lists against your Cherwell processes.
- Most of your requesters expect an IT-branded experience separate from engineering tools and you are not prepared to configure the portal carefully.
Pricing: what is public and what is not
| Product | Published pricing (checked Oct 31, 2026) | Source |
|---|---|---|
| Freshservice | Starter $19, Growth $49, Pro $99 per agent/month billed annually; Enterprise custom | Freshservice pricing page |
| Jira Service Management | Free up to 3 agents; Standard $21.50, Premium $55.28 per agent/month (monthly billing, default team size shown); Enterprise via sales, annual only | Atlassian JSM pricing page |
| ServiceNow ITSM | Not published. Foundation, Advanced and Prime packages are quote-only | ServiceNow ITSM pricing page |
| Ivanti Neurons for ITSM | Not published. Quote via Ivanti sales | Ivanti request-a-quote page |
We do not estimate ServiceNow or Ivanti prices. Quote-only vendors price on agent count, modules, term and negotiation, and published "typical" figures are rarely comparable. Instead, ask every vendor to price the same scope: the same number of agents, the same processes (incident, request, problem, change, knowledge, CMDB), the same asset counts, the same term and the same implementation help. Then compare three-year totals, including implementation, data migration and your internal admin time.
A late move costs more than licences
The expensive part of a rushed Cherwell exit is usually not the subscription. It is rework: a quickly copied configuration you rebuild a year later. Budget for one clean design pass, even if the go-live is phased.
Which Cherwell replacement fits your situation?
| Your situation | Where we would start |
|---|---|
| Cherwell cloud, under 100 agents, mostly incident/request/knowledge | Freshservice or JSM, phased go-live; full data export first |
| Cherwell on-premises, must stay self-hosted | Ivanti Neurons for ITSM (on-premises or hybrid) |
| Cherwell used by IT, HR and facilities, growth plans, budget for a platform team | ServiceNow, with a partner-led design phase |
| Engineering and IT ops already in Jira; DevOps change is the priority | Jira Service Management, Premium if you need advanced incident, problem and change |
| Heavily customised Cherwell, little time, want least change for users | Ivanti Neurons for ITSM now, with a clean-up plan afterwards |
| Unhappy with Cherwell and want a fresh start, can accept a short interim | Shortlist two of the four and run scripted demos against your top ten workflows |
Cherwell exit checklist
- Written confirmation from Ivanti of your end-of-life position (tenant, licence, support, any offer)
- Full data export taken and test-restored or opened
- Configuration inventory: business objects, one-step actions, automation processes, integrations, dashboards
- Change freeze on Cherwell configuration
- Shortlist of one or two platforms and scripted demos
- Data scope decision: what migrates, what is archived
- Phase 1 scope: incident, request, portal, knowledge, SLAs
- Phase 2 scope: change, problem, CMDB, integrations
- Training and communication plan for agents and requesters
- Decommission and archive plan for Cherwell
Frequently asked questions
When is Cherwell end of life?
Ivanti lists Cherwell Service Management with an end-of-life date of December 31, 2026 on its Product End of Life hub (checked Oct 31, 2026). Cherwell Asset Management has the same date.
What happens to Cherwell after December 31, 2026?
According to Ivanti's CSM End-of-Life FAQ, as republished by Ivanti partners, on-premises perpetual installations keep running without Ivanti support, while cloud tenants are discontinued and inaccessible 30 days after the end-of-life date. Confirm the details for your contract with your Ivanti account team.
What is Ivanti's replacement for Cherwell?
Ivanti's go-forward product is Ivanti Neurons for ITSM. Ivanti describes it as deployable in the cloud, on-premises or hybrid, with 14 ITIL 4-certified practices.
Can we finish a Cherwell migration before the deadline?
For most teams starting now, a full, well-designed migration will not fit into the remaining weeks. Protect your data and contract position first, decide on the platform, and phase the build so incident, request and knowledge go first.
How much do Cherwell replacements cost?
Freshservice and Jira Service Management publish per-agent prices (see the pricing table above, checked Oct 31, 2026). ServiceNow and Ivanti are quote-only, so ask each for a quote against the same scope and compare three-year totals including implementation.
Should we move Cherwell history to the new tool?
Usually only recent or open records and anything you need for reporting or audit. Archive the rest in a searchable read-only store. Moving every closed ticket adds cost and mapping effort for little benefit.
Need a Cherwell exit plan in weeks, not months?
We help IT teams protect their Cherwell data, choose a replacement on fit, and phase the move so the service desk keeps running. Tell us your deployment (cloud or on-premises), agent count and the processes you run in Cherwell today.