Cherwell to ServiceNow Data Migration
Moving from Cherwell to ServiceNow? Settle automates the mapping between Cherwell's business object model and ServiceNow's ITIL tables — preserving incident history, change records, CMDB data, and automation context.
Working with enterprise teams on active migration programs
Days
to production-ready mappings
Roughly half
the cost of consulting-led delivery
Every row
validated before go-live
Enterprise migrations routinely run months behind schedule. Yours doesn't have to.
This guide is for VPs of IT, data architects, and migration leads at companies moving data from Cherwell to ServiceNow — whether you're scoping, planning, or mid-program.
Cherwell (now Ivanti Neurons for ITSM) stores data in configurable business objects — Incident, Change, Problem, Customer — with custom fields, relationships, and one-step automation rules. ServiceNow uses ITIL-aligned database tables with a different field model and Flow Designer automation. Settle translates Cherwell's business object architecture to ServiceNow's table model automatically.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your Cherwell to ServiceNow migration
Settle profiles Cherwell's business objects and maps each to the corresponding ServiceNow table — Incident to incident, Change to change_request — with field-level type translation including Cherwell's Text, DateTime, Logical, and Relationship fields.
CMDB CI types are mapped to ServiceNow's CMDB class hierarchy with attribute translation and relationship type alignment.
One-step actions and automation rules are cataloged with field-level dependencies — generating a Flow Designer rebuild document for the ServiceNow team.
Settle handles the user and team migration — Cherwell Customers to sys_user records, Teams to assignment groups, with membership and role translation.
Get your Cherwell to ServiceNow mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
6–12 months
Estimated cost
$600K–$1.5M
Team size
4–8 consultants
Typically requires
×Manual field mapping in spreadsheets
×Custom ABAP/SQL extraction scripts
×3–5 mock migration cycles
×Dedicated source system consultants
×Manual reconciliation testing
With Settle
Enterprise benchmarksTimeline
Days
Estimated cost
A fraction of consulting cost
Team size
1–2 internal resources
Included
✓Schema profiling & analysis
✓AI-generated field mappings
✓Transformation SQL
✓Validation & readiness reports
✓Production-ready load files
Common challenges migrating from Cherwell to ServiceNow
Business objects to ServiceNow tables
Cherwell business objects are highly configurable — fields, grids, relationships, and forms can all be modified. ServiceNow tables have a more structured extension model. Each Cherwell business object must map to a ServiceNow table with field-level type translation. Custom business objects need ServiceNow custom tables or extended standard tables.
Explore related migrations →CMDB model differences
Cherwell's CMDB uses configurable CI types with custom attributes and relationship types. ServiceNow's CMDB uses a class hierarchy with different CI categorization. The CI type-to-class mapping, attribute translation, and relationship model alignment require analysis of both CMDB structures.
Explore related migrations →One-step actions to ServiceNow automation
Cherwell's one-step actions combine field updates, email notifications, and business logic in configurable automation rules. ServiceNow uses business rules, Flow Designer flows, and notifications as separate mechanisms. Settle documents which fields each one-step action references for the ServiceNow rebuild.
Explore related migrations →Cherwell-specific features without ServiceNow equivalents
Cherwell's mApp (Mergeable Application) extensibility model, dashboard widgets, and some CSM features don't have direct ServiceNow equivalents. Data associated with these features needs to be either mapped to ServiceNow alternatives, archived, or reimagined using ServiceNow's platform capabilities.
Explore related migrations →Cherwell to ServiceNow field mapping — what data moves
11 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| Incident | → | Incident (incident) |
| Service Request | → | Request (sc_request) |
| Change | → | Change Request (change_request) |
| Problem | → | Problem (problem) |
| Task | → | Task (sn_task) |
| Configuration Item | → | CMDB CI (cmdb_ci_*) |
| Customer | → | sys_user / customer_contact |
| Team | → | Assignment Group (sys_user_group) |
| Knowledge Article | → | Knowledge Article (kb_knowledge) |
| Journal (Work Notes) | → | Work Note / Comment |
| Custom Business Objects | → | Custom Tables |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual Cherwell to ServiceNow migration
Cherwell to ServiceNow migrations accelerated after Ivanti acquired Cherwell in 2021 and began transitioning customers to Ivanti Neurons. Many Cherwell customers decided to evaluate the market rather than accept a forced platform change, and ServiceNow's market dominance makes it the most common destination. This migration is also driven by companies that outgrew Cherwell's mid-market capabilities and need ServiceNow's enterprise features — advanced CMDB, security operations, HR service delivery, and AI-powered virtual agent.
The technical challenge is mapping Cherwell's configurable business object model to ServiceNow's table architecture. Cherwell uses business objects (Incident, Change, Problem, Customer, Configuration Item) with custom fields and relationship definitions that can be modified through a visual designer. ServiceNow uses database tables with dictionary entries and a more rigid but powerful extensibility model. Cherwell's one-step actions and automation rules must be translated to ServiceNow business rules and Flow Designer.
Companies typically manage this migration during ServiceNow implementation. The business object-to-table mapping, custom field translation, and automation rule documentation are the most labor-intensive parts.
Consulting-led delivery for migrations in this class typically runs $600K–$1.5M. Settle prices it fixed and scoped — read the full cost breakdown.
Frequently asked questions
Related migration paths
Exceptions surface before the first load, not after the third.
Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.
Ready to migrate from Cherwell to ServiceNow?
Tell us about your migration and we'll show you how Settle can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.