Platform guides

Cherwell End of Life 2026: What to Do in the Last 10 Weeks

Cherwell end of life is December 31, 2026. See what changes, what Ivanti tools export, your options and a 10-week plan to the deadline. Start now.

Ayush BothraFounding Member, MigrateX

Published Updated 12 min read

An old on-premises server rack in a darkening server room with one light still on, as Cherwell reaches end of life
On this page

Cherwell end of life means Ivanti stops supporting Cherwell Service Management (CSM) on December 31, 2026. Consultancy StrataCom reports that Ivanti announced the date on October 31, 2023, and ServiceNow partner Beyond20 gives the same date (both as of 20 Oct 2026). Ivanti publishes no end of life date on its public site: its renewal policy FAQ sits behind a customer login.

As of 20 October 2026, about 10 weeks remain. If you own a Cherwell service desk, this guide covers what changes on the date, your options, what Ivanti's tools export, and a week-by-week plan to December 31.

Cherwell end of life: the key dates

Cherwell Service Management reaches end of life and end of support on December 31, 2026, and cloud tenants become inaccessible 30 days later. Ivanti's lifecycle notices sit behind its customer hub, so these dates come from Ivanti's public pages and named partners.

DateWhat happensSource (as of 20 Oct 2026)
March 25, 2021Ivanti acquires CherwellIvanti history page
October 31, 2023Ivanti announces the CSM end of life dateStrataCom
July 2024Ivanti stops renewing support for unsupported Cherwell versionsStrataCom
December 31, 2026CSM end of life and end of supportStrataCom; Beyond20; Service Quality
30 days after December 31, 2026Cloud tenants discontinued and inaccessibleService Quality; StrataCom

Your real deadline can come earlier. StrataCom reported in July 2024 that cloud customers on an unsupported version have their environment shut off 30 days after their renewal date, so check both before planning around the year end.

What happens when Cherwell reaches end of support?

At end of support, on-premises perpetual installs keep running without Ivanti support, while Ivanti-hosted cloud tenants become inaccessible 30 days after December 31, 2026. What changes depends on how you run Cherwell, per the FAQ of Ivanti Premier Partner Service Quality and StrataCom's end of life page (both as of 20 Oct 2026).

How you run CherwellUntil December 31, 2026After December 31, 2026
On-premises, perpetual licenseSupported by IvantiKeeps running; Ivanti no longer provides support
Cloud tenant hosted by IvantiNormal accessDiscontinued and inaccessible 30 days after the date
Subscription licenseData accessible while your instance is supported30 days after the upgrade grace period ends to request a standard database export, which you then maintain
Buying more licensesAllowed if the term ends by December 31, 2026Not applicable

What the sources do not say: none describes a read-only mode after the date, and none sets out a security patch policy, so assume no fixes unless Ivanti confirms otherwise in writing. The length of the "upgrade grace period" is not public either; ask your account team.

A database export keeps your records, but it is not a working service desk until relationships, SLA results and knowledge are mapped.

What are the Cherwell replacement options?

The Cherwell replacement options are Ivanti Neurons for ITSM, another ITSM platform, or unsupported on-premises Cherwell as a bridge. You have three paths, and none avoids migration work.

Ivanti Neurons for ITSM. Ivanti names it as the successor to Cherwell ITSM. It says a clean install keeps core CSM tools such as stored expressions, values, prompts and incoming webhooks, that REST APIs keep current integrations working, and that "You're not going to lose any data" (Ivanti Cherwell refresh page, as of 20 Oct 2026). Service Quality says most of its customers chose a fresh start with limited data, and that both systems can run side by side for about six months during the upgrade (as of 20 Oct 2026).

Another ITSM platform. The table gives each vendor's own pricing and plan gating. For ServiceNow, our Cherwell to ServiceNow migration guide and Cherwell to ServiceNow route page cover that move. For Jira Service Management, our Cherwell to Jira Service Management migration guide and Cherwell to Jira Service Management route cover that pair.

Unsupported on-premises Cherwell. Perpetual installs keep running without Ivanti support (Service Quality), and StrataCom advertises extended support for unsupported versions (as of 20 Oct 2026). Treat it as a bridge to a dated cutover, agreed with security and audit.

Cherwell is not the only service desk nearing end of support. System Center 2016 Service Manager reaches end of support on 11 Jan 2027; see our System Center Service Manager end of life guide.

Which Cherwell replacement fits: choose this if

OptionChoose this ifPricing and problem/change gating (vendor page, as of 20 Oct 2026)G2 (as of 20 Oct 2026)
Ivanti Neurons for ITSMYou want the CSM tools Ivanti says carry over, or need on-premises or hybridNot published; cloud, on-premises or hybrid4.0/5, 324 reviews ("Ivanti ITSM")
ServiceNow ITSMYou want CMDB and ITSM on one enterprise platform and accept quote-based pricingCustom quote; problem and change from ITSM Advanced4.5/5, 2,001 reviews
Jira Service ManagementYour engineering teams already use Jira and cloud is acceptableStandard $21.50, Premium $55.28 per agent/month; change management from Premium; Data Center closed to new customers since March 30, 20264.3/5, 986 reviews
FreshserviceYou want published per-agent pricesStarter $19, Growth $49, Pro $99 per agent/month billed annually; problem and change from Pro4.6/5, 1,363 reviews
Other platforms (for example BMC Helix, ManageEngine ServiceDesk Plus, TOPdesk)A requirement rules out the four aboveCheck each vendor's own pageNot compared here
Unsupported on-premises CherwellYou hold perpetual licenses and need a bridge past December 31No Ivanti support; not open to cloud tenantsNot applicable

The verdict: with 10 weeks left, the first decision is not which platform, but whether your cutover lands before December 31 or after it, from a secured export.

What can you export from Cherwell before end of life?

Ivanti's tools export a full .czar backup, single business objects, grid rows and API data, but no export carries the encryption keys or the workflow logic. Every Cherwell exit is a migration, including the move to Neurons for ITSM, because Ivanti describes that path as a clean install. Ivanti documents these ways to get data out (as of 20 Oct 2026).

ToolWhat it exportsLimits Ivanti documents
Data Export Tool, full systemThe whole database to a compressed Cherwell Archive Repository (.czar) file; attachments, automation data, encrypted fields and emails can be excludedEncryption keys are never included; .czar files never contain decrypted data (CSM 2023 docs)
Data Export Tool, one business object or stored searchA single object or saved searchThe page's introduction says .csv or .xml, but its own steps name a .czar file, so test which format you get (CSM 2023 docs)
Grid exportGrid rows to CSV (all rows) or Excel (only rows shown)Desktop Client grids show at most 20,000 rows; only the object's fields or a 1:1 related object's; "Truncate long fields" cuts text at 300 characters unless cleared (CSM 10.4 docs)
REST APISearch results, business object batches, related objects, attachments and activitiesListed in Ivanti's CSM 10.4 API reference

What that means with 10 weeks left:

  • The full backup is your safety net, not your migration file. A .czar file is Cherwell's own archive format. Take one now, store the keys separately as Ivanti recommends, and plan an extract your target can read.
  • Grid exports flatten records. Links between tickets and CIs need the API or a relationship-aware extract.
  • Logic does not export. Ivanti lists 16 incident automation processes in CSM 10.4. One-Step Actions handle the confirmation email, the not-touched-in-3-days reminder, owner and team assignment notices and the new Journal-Note notice; SLA warning and breach emails and the Resolve-to-Closed step run as separate automation processes (Ivanti, as of 20 Oct 2026). All are rebuilt on the target, with business rules, SLA definitions and running SLA timers.

If you stay with Ivanti, Neurons for ITSM imports CSV, XLS and XLSX files, maps them to business objects and can schedule imports. Its 2025 release documentation lists 250 MB for manual upload and 500 MB over FTP, Secure FTP or a shared folder, with file share on-premises only (as of 20 Oct 2026).

Build your reconciliation list from what is most at risk: relationships, historical SLA results, original timestamps, long text cut at 300 characters, and records owned by deactivated users. Anything not mapped on purpose can arrive empty or stamped with the import date.

A 10-week backwards plan to December 31, 2026

The 10-week plan works backwards from December 31, 2026 on one of two tracks: cut over before the deadline, or secure the data now and cut over later. There is no neutral public benchmark for how long a Cherwell migration takes, so this plan runs on decisions, not durations. In the first fortnight, pick a track: Track A, cut over before the deadline, or Track B, secure the data now and cut over later from an export or an on-premises bridge. The phases are the same: discover, map, test migration, cutover with delta sync, reconcile, hypercare.

Weeks leftTrack A: cut over by December 31Track B: secure now, cut over laterDecision gate
10 to 9 (Oct 20 to Nov 1)Confirm license, version support, renewal date and grace period with Ivanti in writing. Take a full .czar backup; store the keys. Inventory records, CIs and integrationsSame confirmation and backup. List the records audit needs reportableTrack and destination chosen
8 to 6 (Nov 2 to Nov 22)Map states, priorities, users and groups. Rebuild workflows and SLAs. First full test migrationExtract every record type, with relationships, in a format your target reads. Reconcile countsMapping signed off, or extracts reconciled
5 to 3 (Nov 23 to Dec 13)Second test migration, cutover rehearsal, freeze window and go/no-go owner agreedOn-premises: agree the bridge with security and audit. Cloud: plan for tenant closureGo/no-go, or bridge approved
2 to 0 (Dec 14 to Dec 31)Freeze, final load with delta sync, reconcile, switch intake channelsFinal full export; Ivanti's written confirmation of remaining accessSign-off, or fallback documented
After (January 2027)Hypercare; read-only path to the old dataCutover from the export or bridge on a dated planCherwell decommissioned

Two cautions. The last bands include US Thanksgiving and the year-end holidays, so check who is available for the freeze window. And if Track A slips, switch to Track B at the go/no-go gate, not in the last week.

For cloud customers, the 30 days after December 31 are for retrieval, not for running the service desk (Service Quality; StrataCom). By our count the window closes around January 30, 2027; confirm the exact date with Ivanti.

Cherwell end of life checklist

The Cherwell end of life checklist runs from written confirmation with Ivanti to retrieving cloud data within 30 days of December 31, 2026.

  1. Confirm with Ivanti, in writing, your license type, version support status, renewal date and any upgrade grace period.
  2. Take a full .czar export now and store the encryption keys separately.
  3. Inventory record types, CIs, custom business objects and integrations.
  4. Choose a track and a destination.
  5. Decide what history moves live, what is archived and what is retired.
  6. Map states, the priority matrix, categories, users and assignment groups.
  7. Rebuild workflows, automation processes and SLA definitions; plan for open tickets with running SLA timers.
  8. Run a full test migration and reconcile counts, relationships and attachments.
  9. Agree a freeze window and a go/no-go owner.
  10. Cut over with delta sync, reconcile, and keep a read-only path to the old data.
  11. Cloud customers: retrieve what you need within 30 days of December 31, 2026.

Facts checked October 20, 2026 from Ivanti history, Ivanti Cherwell refresh, Ivanti CSM documentation, ServiceNow ITSM pricing, Atlassian pricing and Freshworks pricing. No vendor paid for this article. How we research

Cherwell end of life FAQ

When is the Cherwell end of life date?

December 31, 2026. StrataCom reports that Ivanti announced it on October 31, 2023, and Beyond20 and Service Quality give the same date (as of 20 Oct 2026). Ivanti's public pages list Cherwell as discontinued but do not print the date, and its renewal policy FAQ needs a customer login. Confirm the date in your contract with your Ivanti account team.

Is Cherwell being discontinued?

Yes. Ivanti's history page lists Cherwell products under "Cherwell products, now discontinued" and maps Cherwell IT Service Management to Ivanti Neurons for ITSM and Cherwell IT Asset Management to Ivanti Neurons for ITAM (as of 20 Oct 2026). Ivanti acquired Cherwell on March 25, 2021, and partners report that support ends on December 31, 2026.

What happens if we miss December 31, 2026?

It depends on how you run Cherwell. Service Quality and StrataCom say on-premises perpetual installs keep running without Ivanti support, while cloud tenants become inaccessible 30 days after the date (as of 20 Oct 2026). Neither describes a read-only mode or a security patch policy afterwards. If your cutover will miss the date, secure a full export now and set a dated plan.

Can we still export our Cherwell data after end of life?

For subscription customers, Service Quality says data stays accessible while the instance is supported. After the upgrade grace period ends, you have 30 days to request a standard database export, which you then maintain (as of 20 Oct 2026). Cloud tenants close 30 days after December 31. The safer course is to run Ivanti's Data Export Tool yourself before the date and keep the encryption keys.

What is replacing Cherwell?

Ivanti names Ivanti Neurons for ITSM as the successor to Cherwell ITSM, and StrataCom calls it Ivanti's go-forward solution (as of 20 Oct 2026). You can also choose another platform, such as ServiceNow, Jira Service Management or Freshservice. Whichever you choose, workflows, automations, business rules and SLA definitions are rebuilt on the new platform rather than migrated.

How long does a Cherwell migration take?

There is no neutral public benchmark. Beyond20, a ServiceNow partner, says it has moved clients from Cherwell to ServiceNow in 8 to 10 weeks (as of 20 Oct 2026); that is the partner's own claim. Record volumes, custom business objects, integrations, how much history moves and the number of test migrations drive the real figure.

Written by

Ayush Bothra

Founding Member, MigrateX

Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.