Cherwell Service Management reaches its official end of life on December 31, 2026 — less than two months away. If your service desk still runs on Cherwell, the question in front of you now is not whether to move but how much you can finish before the date: what to migrate, what to archive, and where to land.
This article covers what the end-of-life date actually changes for cloud and on-premise teams, how to build a migration plan that fits the time you have left, and what to weigh when you choose the platform that replaces Cherwell.
Cherwell End of Life (EoL): What It Means And What to Do Next
Is Cherwell being discontinued?
Yes. Ivanti has confirmed that Cherwell Service Management reaches end of life on December 31, 2026, after which it will no longer receive updates, patches, or technical support. The announcement, made on October 31, 2023, caught many customers off guard — especially those who had been told the platform would be supported until the last Cherwell customer had left it.
Communication since then has been thin, and much of the frustration customers have voiced comes from feeling pushed toward Ivanti Neurons, the vendor’s own platform, on a timeline they did not choose.
When will the Cherwell end of life happen?
The official end-of-life date is December 31, 2026. It helps to separate two terms that get used loosely: end of life is the point where Ivanti stops developing and maintaining the product altogether, while end of support is when a given version stops receiving technical assistance and fixes. Individual Cherwell versions reach end of support on their own schedules ahead of the final date.
Timeline for Cherwell's end of support
Ivanti currently supports only its two most recent releases, and both run out at the same time as the product itself.
Below is the CSM Version Matrix with the current release dates, support timelines, and technical assistance windows:
[*]: This date is 1.5 years after the release of that specific version of CSM.
Any release earlier than these is already outside its support window, where Ivanti provides best-effort help only — no new bug fixes and no escalations. Moving to a still-supported version buys a few months at most, so the effort is better put toward leaving Cherwell for good.
What happens to Cherwell after December 31, 2026
The end-of-life date lands differently depending on how you run Cherwell, and Ivanti’s guidance spells out both cases.
If you run Cherwell in Ivanti’s cloud, your hosted tenant is decommissioned roughly 30 days after December 31, 2026, and the environment and the data inside it become inaccessible once that happens. Plan to request a full export well before then; cloud exports can take one to three weeks to be delivered, so this is not something to leave until January.
If you run Cherwell on-premise, your installation will keep running past the date — but with no updates, no patches, and no vendor support. In practice that means unpatched software sitting on a database of sensitive records, a security exposure that grows the longer it stays live.
Recommended reading
Read Article
Looking for a Cherwell Alternative? Options to Replace it
Crafting an effective Cherwell migration plan
With the deadline this close, the migration plan is the first thing to put in place. You will not get a drawn-out, multi-quarter project — the work has to be scoped to the weeks that remain. These steps keep it focused:
- Export your data and decide what moves with you. Request your Cherwell database from Ivanti now, since exports can take one to three weeks, and split your records into what the new platform actually needs on day one and what can go to a separate archive. Keep years of history out of the migration itself.
- Map a tight timeline to December 31, 2026. Set milestones for evaluation, data migration, testing, and training, and build in room for the problems that always surface — on a two-month runway there is little slack.
- Evaluate replacement platforms quickly. Shortlist tools that match your deployment model, integration needs, and process maturity, and make the call fast rather than perfect.
- Plan the data and configuration move. Account for custom configurations, workflows, and integrated systems, and confirm the new platform can take them without losing functionality or security along the way.
- Test and validate before you cut over. Run configurations, workflows, and integrations in a controlled environment so issues surface before go-live, not after.
- Prepare your team. Even a short, focused round of training on the new platform protects productivity in the first weeks and reduces pushback.
Key considerations when selecting a new ITSM solution
Cherwell’s end of life arrives in a mature market: there are plenty of capable platforms to replace it, so the real work is narrowing that field to the one that fits your team. A handful of criteria do most of that work.
Deployment comes first: decide whether cloud or on-premise fits your security posture and the control you need over maintenance and updates. Check that the platform genuinely supports ITIL practices, so you can keep or improve the processes you already run. Make sure it will scale as you add agents, departments, and integrations. And confirm it connects cleanly to the systems around it — Asset Management, monitoring, and the rest of your stack — testing those links during the move, not after.
Recommended reading
Read Article
5 Key Steps to Switch Service Desk Provider
Moving from Cherwell to InvGate Service Management
InvGate Service Management gives Cherwell teams enterprise-grade capability without the complexity that usually comes with it — the workflows, automation, and reporting a mature service desk needs, built and adjusted by your own IT team without code. It runs in the cloud or on-premise, so the deployment choice stays yours, and it is worth seeing exactly how the two line up on features, cost, and migration effort before you decide.
On the move itself, InvGate starts by analyzing your current Cherwell environment and migration goals, then handles configuration and go-live alongside a dedicated specialist, so the transition stays controlled from assessment through launch.
Recommended reading
Read Article
9 Help Desk Migration Mistakes You Need to Avoid
Background on the acquisition of Cherwell Software by Ivanti
Cherwell’s end of life traces back to Ivanti’s 2021 acquisition of Cherwell Software, after which the vendor concentrated its roadmap on Ivanti Neurons and began moving customers toward it. Retiring Cherwell lets Ivanti put its resources behind that single platform — useful context for the date, though the practical question for most teams is simply where to go next.
With the deadline close, the teams that move first will have the most room to do it well. You can start a 30-day free trial to see how your processes map onto a new platform, or talk to our team about scoping a migration on your timeline.
Recommended reading
Read Article
Ivanti Neurons Alternative: Features, UI, Integrations, and Support
Cherwell end of life FAQ
What happens to Cherwell cloud data after December 31, 2026?
Ivanti-hosted cloud tenants are decommissioned about 30 days after the end-of-life date, and the data in them becomes inaccessible once that happens. Request a full export from Ivanti before the window closes — cloud exports can take one to three weeks to be delivered.
Can I keep running Cherwell on-premises after end of life?
Technically yes — an on-premise install will keep running past December 31, 2026. But Ivanti stops all patches, updates, and support, so you would be running unpatched software on sensitive data, which is not a position to hold for long.
What is Ivanti replacing Cherwell with?
Ivanti is directing Cherwell customers to Ivanti Neurons for ITSM, its own service management platform. The two differ enough in cost, deployment, and day-to-day use that it is worth weighing them closely rather than accepting the default path.
How long does a Cherwell migration take?
It depends on your data volume, customizations, and integrations: a clean, lightly customized environment can move in a few weeks, while complex deployments run several months. With the deadline near, scope tightly and start now.
What are the best Cherwell alternatives?
InvGate Service Management is a strong fit for teams leaving Cherwell, since it covers enterprise-grade ITSM in the cloud or on-premise without a heavy build. Other options worth a look include ServiceNow, Freshservice, Jira Service Management, and ManageEngine ServiceDesk Plus, each landing at a different point on price and complexity. The practical move is to shortlist the ones that fit your deployment model and budget and compare them head to head.
