Cherwell migration

Moving off Cherwell?

Cherwell Service Management stores incidents, service requests, changes, problems, customers and CIs as business objects, and runs much of its logic as One-Step Actions. Ivanti is retiring Cherwell CSM, and we move its history to ServiceNow or Freshservice.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Read how we handle your data

What moves

What moves from Cherwell?

The objects we carry across by default. Your exact scope is agreed on the scoping call.

  • Incidents
  • Service Requests
  • Changes
  • Problems
  • Customers
  • Teams
  • Configuration Items
  • Knowledge Articles

What does not move

What does not move from Cherwell as-is

Configuration, not data. We list each item in scope so your team can rebuild it in the target.

  • One-Step Actions and automation processes: rebuilt as workflows in the target
  • Business object forms and field validation
  • SLA definitions and running SLA timers

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Migration paths

Where can I move to or from Cherwell?

Routes we run from and into Cherwell. Open a route to see what migrates, or ask us about one that is not listed yet.

From Cherwell

191 connectors, all live

Every connector is live, so Cherwell can be paired with any of them. Some of the ITSM platforms:

  • BMC Helix ITSM
  • Ivanti Neurons for ITSM
  • ManageEngine ServiceDesk Plus
  • HaloITSM
  • TOPdesk
  • SysAid
  • SolarWinds Service Desk
  • IBM Control Desk
See all 191 connectors

Platform not listed?

We build new connectors in 2 to 3 days. Tell us what you run and we scope the route with you.

Timeline

Your Cherwell migration, step by step

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      A 30 minute call with the engineer who will run the migration, to agree the objects, date ranges and volumes in scope.

    • Connect both platforms

      You0.5 day

      You create scoped API credentials on the source and the destination. Nothing is written until you sign off the mapping.

    • Field mapping review

      Both1 day

      We walk through every field, status and group mapping with your team and note the ones that need a decision.

  2. Migration

    Day 3-7

    • Free sample migration of 100 records

      MigrateX1 day

      A sample of your real records is migrated end to end so you can see the result before the full run.

    • You review the sample

      You1 day

      Your team opens the migrated records and tells us what to adjust. We rerun the sample until it is right.

    • Full migration

      MigrateX2-3 days

      The bulk pass runs in dependency order, paced to the destination rate limit. Your team keeps working normally.

    • Delta sync

      MigrateX0.5 day

      Everything created or changed during the bulk pass is synced at cutover so nothing falls between the two systems.

  3. Validation

    Day 8-10

    • Validation report

      MigrateX1 day

      Record counts per object and per status on both sides, plus every record that needed a default or a placeholder.

    • Spot checks and sign-off

      You1-2 days

      Your leads check a random sample and sign off. We stay available for two weeks after go-live.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

See how it works in detail

Data model

How Cherwell stores your data

What shapes the export, checked against the vendor's own documentation.

  • Major and supporting business objects

    Incident, Problem, Change, Customer, Configuration Item and Knowledge Article are major business objects. Tasks, journals and approvals are supporting objects that exist only under a major one, so they move with their parent.

    Source: Ivanti documentation

  • A CMDB of CI types

    A Configuration Item is a group object made of different CI types. We map each CI type to a class or asset type in the target.

    Source: Ivanti documentation

  • Logic in One-Step Actions

    A One-Step Action is a series of actions, run from toolbars, records, the portal, dashboards and automation processes. These are Cherwell's own automation, so they are rebuilt in the target.

    Source: Ivanti documentation

Cherwell migration questions

Still unsure? Ask us on the scoping call.

What does a Cherwell migration cost?

Cherwell migration cost depends on how many business objects are in scope, the records and journals under each one, the attachments, and how heavily your tenant is customised, since every Cherwell tenant has its own objects and fields. Rebuilding One-Step Actions in the new platform is separate work for whoever configures it. MigrateX migrates 100 of your records free, then sends a fixed quote within 24 hours.

Is there still time to migrate before Cherwell end of life on 31 December 2026?

For the data, usually yes: our default plan is about 10 business days end to end. The tighter constraints are how ready the new platform is to receive records, and your change freeze. Start with the free 100-record sample now. If cutover cannot land before the date, we move open and recent records first and load the rest later.

What happens to our Cherwell data after end of life?

Ivanti stops product updates and official support after 31 December 2026, and a Cherwell licence expires at midnight at the start of its expiry date, so 30 December 2026 is the last day of normal licensed access. Ivanti's public pages do not say what happens to hosted tenants or on-premises installs after that, so take a full export before the date and confirm your contract terms with Ivanti.

Can One-Step Actions be migrated?

Not as they are. One-Step Actions and automation processes are Cherwell's own automation, so they are rebuilt as workflows in the target platform. MigrateX lists every One-Step Action and automation process in scope, so your team or implementation partner can rebuild the ones you still need and retire the rest before cutover.

Do custom business objects and fields move?

Yes. Every Cherwell tenant is customised, so MigrateX reads your own schema first: each business object, its fields and its relationships. Custom major objects and custom fields are then mapped with you to tables and fields in the target, before any data moves. The field mapping is part of what you keep at handover.

What happens to journals and tasks?

They move with their parent record. Journals and tasks are supporting objects in Cherwell, so they travel with the incident, request or change they belong to, in their original order and with their authors and dates. Incidents carry several journal types, such as notes, mail history and SLM history, and each type gets its own rule in the target.

Do configuration items and their relationships move?

Yes. A Cherwell Configuration Item is a group object made of different CI types, and MigrateX maps each CI type to a class or asset type in the target. On the ServiceNow route, relationships between CIs, and the links from incidents, problems and changes to CIs, are loaded once the CIs are in place, and the counts are checked class by class.

Should we move to Ivanti Neurons or another platform?

That is your call. Ivanti names Ivanti Neurons for ITSM as the successor to Cherwell, and it is still a new install, so your data has to move either way. MigrateX runs Cherwell to ServiceNow and Cherwell to Freshservice today, and our Cherwell end-of-life guide compares the options. Whichever platform you choose, the automation is rebuilt.

Guides

Guides for a Cherwell migration

Start with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.