Cherwell Service Management brings together the practical considerations that affect this decision, from condition and timing to the available evidence.
The exact-match query cherwell service management now describes a legacy product line rather than an actively sold platform. Ivanti's own history page states that Cherwell is part of Ivanti and that the Cherwell products are discontinued. That single fact reshapes every buying decision: the practical question is no longer which edition to license, but what to do with an existing deployment, a renewal quote, or a shortlist that still names Cherwell.
This guide works through the entity itself, the acquisition timeline, the end-of-life implications, and the decision sequence for teams in Malaysia and elsewhere who still encounter the name in procurement documents.
What Is Cherwell Service Management?
Cherwell Service Management, usually shortened to CSM, is an IT service management platform built around ITIL-aligned processes. Ivanti's product documentation describes CSM as providing incident, request, change, and related service workflows, with a no-code configuration layer that lets administrators build custom applications without writing code. The same documentation names the CSM Desktop Client, the CSM Browser Client, and the Cherwell Virtual Agent as the main ways users reach the system.
Three characteristics defined the product in its active years:
- Configurability over custom development. The platform was marketed on codeless configuration, so process changes did not require a development project.
- Scope beyond IT. Cherwell's own materials extended the same engine to HR, facilities, project and portfolio management, and security workflows under an enterprise service management banner.
- Deployment choice. Partner documentation describes both on-premises and hosted options, with SaaS and on-premises licensing models available.
Wikipedia's entry on Cherwell Software records the company's founding in Colorado Springs, Colorado, its venture backing from Insight Venture Partners and later KKR, and its acquisition by Ivanti. The same entry notes that in January 2013 the Service Desk Institute accredited Cherwell service management, which is the kind of third-party validation that mattered to buyers evaluating ITSM vendors at the time.
Cherwell Service Management After the Ivanti Acquisition
The acquisition changed the product's status rather than its feature set. Ivanti's Cherwell history page states plainly that Cherwell products are now discontinued and directs readers toward Ivanti Neurons for ITSM and Ivanti Neurons for ITAM as the current offerings. The page also references Spend Intelligence and IoT edge capabilities as part of the wider Ivanti portfolio.
For anyone searching cherwell service management today, that discontinuation notice is the most consequential piece of information on the internet about the product. It means.
- New licences are not the normal path, so a fresh implementation is unlikely to be the right recommendation.
- Existing deployments still run, and the operational questions around them remain real.
- Migration planning becomes the primary workstream, whether the destination is Ivanti Neurons or another ITSM platform entirely.
- Renewal and support terms deserve scrutiny, because a discontinued product line changes the leverage on both sides of a contract.
Ivanti's own documentation bundle for CSM 10.4 remains accessible, which matters for teams still administering an installed system. Documentation availability is not the same as active development, and the two should not be conflated during a renewal conversation.
What the End-of-Life Discussion Actually Covers
Third-party coverage of Cherwell end of life, including Invgate's analysis, frames the topic around migration planning and ITSM tool selection rather than around the product's remaining features. That framing is consistent with Ivanti's own positioning. The practical content of an end-of-life discussion is usually narrower than teams expect: it covers support timelines, data extraction, integration dependencies, and the cost of running two systems in parallel during a transition.
Data extraction deserves early attention. A CSM deployment typically holds years of incident history, configuration items, knowledge articles, and workflow definitions. The configuration layer is the harder asset to move, because codeless customisations rarely translate one-to-one into a different platform's data model. Teams that inventory their customisations before selecting a destination avoid discovering the gap mid-migration.
Practical Considerations for Cherwell Service Management Users
Four constraints shape most decisions about a legacy CSM estate.
Integration surface. CSM exposed a REST API and connected to collaboration tools such as Slack, according to Ivanti's documentation. Any replacement needs to cover the same integration points, or the migration quietly breaks automations that nobody documented.
Process depth. A team using CSM for straightforward incident and request handling has a simpler migration than a team running change management, a configuration management database, and project portfolio workflows on the same platform. The more of the ITIL stack is in active use, the more the destination platform's coverage matters.
Reporting continuity. Dashboards and reports built on CSM data rarely survive a platform change intact. Deciding which reports are genuinely used, rather than merely available, reduces the rebuild effort.
Timing pressure. End-of-life coverage tends to create urgency, and urgency is a poor basis for platform selection. A migration planned over a realistic window costs less than one compressed by a support deadline.
Where the Name Still Appears
Cherwell Service Management still surfaces in three places. Procurement and vendor comparison documents sometimes list it as an incumbent. Job descriptions occasionally name it as a desirable skill, which reflects installed bases rather than new sales. Partner and marketplace listings persist online long after the underlying commercial relationship changes, so a page describing Cherwell as a current offering is not evidence that it is one.
That last point is worth stating directly: a partner page, a marketplace listing, or a review-site profile can remain live and well-optimised while describing a product that is no longer sold. Checking the vendor's own current product pages resolves the ambiguity faster than comparing third-party listings.
Making an Informed Choice About Cherwell Service Management
The decision depends on which side of the product's lifecycle a team sits on.
| Situation | What the evidence supports |
|---|---|
| Evaluating ITSM platforms for a new implementation | Ivanti lists Cherwell products as discontinued and points to Ivanti Neurons for ITSM and ITAM. A shortlist built on current vendor offerings is the more defensible starting point. |
| Running an existing CSM deployment | Documentation for CSM 10.4 remains available, so administration can continue while migration options are assessed. |
| Facing a renewal or support decision | Discontinuation changes the negotiating position. Support scope and term length are the terms to examine first. |
| Planning a migration | Inventory customisations, integrations, and reports before selecting a destination platform, because the configuration layer is the least portable asset. |
For organisations that treat ITSM as one component of a wider operating system, the migration question connects to a broader one about how service data, automation, and reporting fit together. That is the framing Blackstone Intelligence applies to client work in Sarawak, where websites, SEO, AI agents, dashboards, and workflows are treated as connected systems rather than isolated deliverables. Related project work includes the SDSC at University Technology Sarawak and Camel Active Malaysia, which illustrate the same delivery approach rather than an ITSM migration specifically.
Two limits are worth naming. First, no public evidence establishes a firm end-of-support date for every CSM version, so any specific deadline should be confirmed with the vendor rather than assumed from third-party summaries. Second, migration cost depends heavily on how much of the platform a team actually uses, which is why the inventory step comes before the selection step.
Questions That Come Up During Evaluation
Is Cherwell Service Management still available to buy? Ivanti's Cherwell history page describes the Cherwell products as discontinued, so a new purchase is not the expected path.
What replaced it? Ivanti directs readers to Ivanti Neurons for ITSM and Ivanti Neurons for ITAM.
Can an existing deployment keep running? Yes. Documentation for CSM 10.4 remains published, and installed systems continue to operate independently of the vendor's current catalogue.
Does the Service Desk Institute accreditation still apply? Wikipedia records that accreditation from January 2013. It reflects the product's standing at that time and does not indicate current certification status.
How long does a migration take? No public source provides a reliable figure, because duration depends on customisation depth, data volume, and integration count. Teams should size the work from their own inventory rather than from a generic estimate.
The clearest next step for most teams is to separate the two questions that the name Cherwell Service Management tends to merge: whether the product is still a viable platform, and what to do about the deployment already in place. The first has a documented answer. The second requires an inventory of what the system actually does today.