ServiceNow Migration 2026: Map, Cut Over and Reconcile Your History
ServiceNow migration guide for 2026: extraction limits, what moves, field mapping, cutover with delta sync and a 13-step checklist. Plan yours now.
Published Updated 14 min read

On this page
- Why teams start a ServiceNow migration in 2026
- Before you start: scope and inventory for a ServiceNow data migration
- What moves, what gets rebuilt, what's at risk in a ServiceNow migration
- ServiceNow migration field mapping essentials
- The ServiceNow migration plan in phases
- Common ServiceNow migration failure points
- ServiceNow migration checklist
- ServiceNow migration FAQ
A ServiceNow migration moves your service history into or out of ServiceNow: incidents, service requests, problems, changes, knowledge articles, configuration items (CIs) and the links between them. Workflows, business rules, SLA definitions and running SLA timers do not move. They are rebuilt on the target.
If a platform decision has been made and someone has to bring years of tickets across, this guide covers both directions and the parts that decide the outcome: extraction limits, mapping, cutover with delta sync and reconciliation.
Why teams start a ServiceNow migration in 2026
Most ServiceNow migrations in 2026 start with a dated vendor decision or with renewal pressure.
| Trigger | Direction | What the source says (as of 23 Oct 2026) |
|---|---|---|
| Atlassian Data Center end of life | Into ServiceNow, or to other platforms | No new-customer sales after March 30, 2026; no purchases or expansions after March 30, 2028; Data Center products, Jira Service Management included, become read-only on March 28, 2029 (Atlassian) |
| Cherwell discontinued | Into ServiceNow, or to other platforms | Ivanti lists Cherwell under "Cherwell products, now discontinued" and names Ivanti Neurons for ITSM as the successor (Ivanti) |
| Flow by ServiceNow | Into ServiceNow | ServiceNow announced Flow, a conversational AI service desk, on October 1, 2026, in controlled availability with general availability for North America and EMEA expected in Q4 2026 (ServiceNow press release) |
| Analyst position | Into ServiceNow | ServiceNow said in a Workflow news post of July 29, 2026 that it was named a Leader in the 2026 Gartner Magic Quadrant for IT Service Management (ITSM) Platforms, a report dated July 27, 2026 (ServiceNow) |
| Cost and complexity | Out of ServiceNow | G2 reviewers rate ServiceNow ITSM 4.5/5 from 2,006 reviews; the most-mentioned cons are learning curve (72), expensive (60) and complexity (56) (G2) |
Ivanti's public pages give no Cherwell end date. StrataCom, an ITSM consultancy, reports that Ivanti set December 31, 2026 (StrataCom, as of 23 Oct 2026). Confirm the date in your contract.
A Magic Quadrant placement is an analyst's view of a vendor, not of your migration: it changes nothing about what moves or what is rebuilt. Flow's launch release does not mention importing history, so teams trialing it still have to decide where old tickets live. Our guide to Flow by ServiceNow's ticket storage covers that choice. Pair-specific guidance is in our Jira to ServiceNow migration guide and, for the reverse move, our ServiceNow to Freshservice migration guide.
Before you start: scope and inventory for a ServiceNow data migration
What "ServiceNow migration" can mean
The phrase covers four different jobs.
- Data migration between platforms. Records move from Jira Service Management, Cherwell, Freshservice, BMC Remedy or another tool into or out of ServiceNow. Our route guides also cover Cherwell to ServiceNow and Freshservice to ServiceNow.
- Instance to instance. Update sets move configuration between ServiceNow instances, but they "exclude task or process data" such as submitted orders and catalog tasks (ServiceNow docs, as of 23 Oct 2026). Records between instances are a data migration in their own right.
- Platform Analytics Migration Center. Inside one instance, ServiceNow moves Core UI dashboards, reports, interactive filters and Performance Analytics widgets to Platform Analytics (ServiceNow docs, as of 23 Oct 2026). A reporting upgrade, not a history move.
- Cloud workload migration. Servers and applications move to the cloud.
Moving from Freshservice? Our Freshservice to ServiceNow migration guide covers that pair.
Inventory what you have
Count every record type before planning: incidents, requests and requested items, problems, changes, knowledge articles, CIs and relationships, users, groups, attachments and journal entries, per state and in total.
Then decide, with your audit and compliance owners, how much history moves: all of it, everything after a cut-off, or a cut-off plus a read-only archive. Our guide to what an ITSM migration costs covers how history depth feeds the budget.
Leaving ServiceNow? Plan extraction by API
List exports are built for reports, not full history. ServiceNow's documented defaults (ServiceNow export limits docs, as of 23 Oct 2026):
| Extraction path | Documented default | What it means for a migration |
|---|---|---|
| List export to XML, CSV or JSON | 10,000 records per export | A 30,000-record list returns 10,000 rows; ServiceNow advises breaking large exports into smaller increments |
| List export to Excel | 10,000 records; the export stops above 500,000 cells | Wide tables hit the cell cap before the record cap |
| List export to PDF | 1,000 rows, 25 columns | Not a migration format |
| Table API (sysparm_limit) | 10,000 records per request; page with sysparm_offset | The route for full history; sysparm_display_value=all returns stored and display values, because choice codes mean nothing outside ServiceNow |
| Attachment API | One file per request; 1,024 MB default maximum size | Plan attachment extraction as its own job |
Then check System Archiving. Archive rules move old records into ar_ tables, such as ar_incident, and ServiceNow says archived data "is stored as a flat file with no reference fields to other tables," and that the sys_archive_log table is the only place pairing each reference's sys_id with its display value (ServiceNow docs, as of 23 Oct 2026). If your counts come only from the incident table, your oldest history is missing from them.
What moves, what gets rebuilt, what's at risk in a ServiceNow migration
Records and their history move as data; the logic that acted on them is rebuilt. Agree this table with stakeholders before anyone writes a transform map.
| What moves (as data) | What gets rebuilt (not migrated) | What's at risk |
|---|---|---|
| Incident, request, problem and change records with their field values | Flows, workflows and business rules | SLA history, because repair can only use the task history you import |
| Journal entries, kept as additional comments or work notes | SLA definitions, schedules and running SLA timers | Internal notes landing in customer-visible comments |
| Attachments, one file per API request, up to a 1,024 MB default maximum (ServiceNow Attachment API docs, as of 23 Oct 2026) | Priority lookup rules and assignment rules | Files over the target's size limit or blocked by its allowed extensions |
| Knowledge articles from Word: headings, lists, tables and images are kept, links only from .docx (ServiceNow docs, as of 23 Oct 2026) | Notifications, templates and macros | Heading numbers, table borders and custom heading styles, which are dropped |
| CIs, loaded through the Identification and Reconciliation Engine (IRE) | Catalog items and record producers | Duplicate CIs when loads bypass IRE |
| CI relationships (parent, child, type) | CMDB health and data-certification rules | Incident, problem, change and CI links dropped in mapping |
| Users, groups and locations as reference data | Integrations and inbound email actions | References pointing at old sys_ids |
The middle column belongs in the project plan, not the migration scope. The right column is where reconciliation should focus, because these losses rarely raise an error. For how CIs and relationships are modeled on the target, see our ServiceNow CMDB guide.
ServiceNow migration field mapping essentials
Inbound data usually lands through import sets and transform maps, where "a transform map is a set of field maps that determine the relationships between fields" (ServiceNow docs, as of 23 Oct 2026). These mappings go wrong most often.
| Area | ServiceNow target (ServiceNow docs, as of 23 Oct 2026) | What to watch |
|---|---|---|
| States | Incident states New, In Progress, On Hold, Resolved, Closed, Canceled; On Hold reasons Awaiting Caller, Awaiting Change, Awaiting Problem, Awaiting Vendor | Map every source status. "Waiting for customer" needs an On Hold reason, not just a state |
| Priority matrix | Priority is derived from impact and urgency through lookup rules and is read-only by default | Import impact and urgency, then sample-check computed priority against the source |
| Users and groups | User, group and location tables | Load first. If a referenced sys_id does not exist, it "could potentially appear in the target record as the DisplayValue" |
| Public vs internal notes | Additional comments, which "all users who can view incidents see", and work notes | Never merge them. Keep the original author and timestamp in the entry text if the target cannot set them |
| Attachments | Attachment API, one file per request; size set by com.glide.attachment.max_size, types by glide.attachment.extensions | Check file sizes and extensions before the load, not after |
| Links and CIs | CI relationships in the CI Relationship [cmdb_rel_ci] table as parent, child and relationship type; IRE "can also" process import set data | Load CIs through IRE, then relationships, then task-to-CI links |
Two settings decide whether re-runs are safe. The first is coalesce: a match updates the record, no match inserts one; with no coalesce defined, "all imported rows are treated as new records," and when several records match, "only the first matching record in the target table is updated" (ServiceNow docs, as of 23 Oct 2026). Store the source ticket ID in a dedicated field and coalesce on it.
The second is identity. The Table API says sys_ fields are system generated and generally cannot be updated (ServiceNow docs, as of 23 Oct 2026). Expect new sys_ids on the target, keep a source-to-target ID map, and remap references from it.
The ServiceNow migration plan in phases
A ServiceNow migration plan has six phases: discover, map, test migration, cutover with delta sync, reconcile and hypercare. Each phase ends with something a named owner signs.
- Discover. Finish the inventory (archive tables included), the history-depth decision and owners per record type.
- Map. Produce field and value mappings for states, priority, categories, assignment groups and notes visibility, signed by process owners. Build the rebuild list in parallel.
- Test migration. Run a full load into sub-production, not a sample, and reconcile it as you will in production. Run SLA repair on imported tickets and compare with the source. Our test migration checklist lists what a test should prove.
- Cutover with delta sync. Load bulk history before the freeze. In the freeze window, re-run the load for records changed since (filter on sys_updated_on); the coalesce key makes it update, not duplicate. Hold go/no-go against agreed reconciliation thresholds.
- Reconcile. Compare counts per record type and state, sampled field values, attachments, relationships and journal entries. If a partner provides your ServiceNow migration services, agree the reconciliation report format before work starts. Deciding whether to use a partner at all? See data migration companies vs in-house.
- Hypercare. Watch for wrong assignment groups, priority mismatches and missing attachments. Keep the source read-only.
Common ServiceNow migration failure points
These failures rarely stop a load. The migration looks finished, and the damage shows up in reconciliation or hypercare.
- No coalesce, or coalescing on a non-unique field. Without coalesce every re-run inserts duplicates; with a non-unique key only the first match is updated (ServiceNow docs, as of 23 Oct 2026).
- Truncated extracts. A list export stops at 10,000 records by default. Compare extracted row counts with source counts.
- Archived history left behind. Records in ar_ tables are not in the live table counts, and their references are frozen as text.
- Source sys_ids reused as keys. References point at records that do not exist on the target.
- SLA definitions firing on historical records. If definitions are active during the load, test whether they attach to imported tickets.
- Dot-walked SLA conditions. SLA repair "considers only the final state of the dot-walk fields," not their history (ServiceNow SLA repair docs, as of 23 Oct 2026).
ServiceNow migration checklist
Use these 13 steps in either direction, into or out of ServiceNow.
- Confirm direction, record types, source and target.
- Count every record type, by state, in the source, including archive tables.
- Get the history-depth decision signed by your audit or compliance owner.
- Write the rebuild list: workflows, business rules, SLA definitions, notifications, priority rules. Our ServiceNow implementation guide covers that build work.
- Extract through the API, with stored and display values, and compare row counts with source counts.
- Load users, groups and locations before any ticket data.
- Get state, On Hold reason and priority mappings signed off.
- Choose a unique coalesce key for every target table and keep a source-to-target ID map.
- Map public comments to additional comments and internal notes to work notes.
- Check attachment sizes and file types against the target's limits.
- Load CIs through IRE, then relationships, then task-to-CI links.
- Run a full test migration on sub-production and produce a reconciliation report.
- Write the cutover runbook: freeze window, delta sync, go/no-go criteria, rollback and hypercare owners.
Facts checked October 23, 2026 from ServiceNow export limits docs, ServiceNow Table API, ServiceNow SLA repair docs, Atlassian Data Center end of life and ServiceNow newsroom. No vendor paid for this article. How we research
ServiceNow migration FAQ
How do you migrate incidents into ServiceNow?
Load users, groups and locations first. Then stage incidents in an import set and map them to the Incident table with a transform map, coalescing on the source ticket ID so you can re-run the load for delta sync. Keep work notes and additional comments separate, upload attachments one file per request, and import impact and urgency so ServiceNow calculates priority.
How does a ServiceNow to Jira migration work?
Extract through the ServiceNow Table API, with display values as well as stored codes. On the Atlassian side, CSV import maps status only to statuses that already exist in the workflow, recommends 1,500 work items per file, and makes all imported Jira Service Management comments public (Atlassian, as of 23 Oct 2026). Atlassian also says CSV "isn't a recommended migration method due to its limitations," so plan an API load for internal notes. See our ServiceNow to Jira Service Management migration page for the full route.
Can update sets migrate data between ServiceNow instances?
No. ServiceNow's documentation says update sets capture configuration, such as catalog item definitions and variables, but "exclude task or process data" (ServiceNow docs, as of 23 Oct 2026). Incidents, problems and changes are task records. Moving records between instances is a data migration: extract, map, load with coalesce keys, remap sys_id references and reconcile.
Does SLA history carry over in a ServiceNow migration?
Not automatically. SLA definitions, schedules and running timers are rebuilt on the target. ServiceNow's SLA repair "removes the SLA record, then recreates and recalculates it from the start," using the history from the task (ServiceNow docs, as of 23 Oct 2026). If you import only each ticket's final state, repair has little to work from. Decide early whether you rebuild SLA results, import them as reference data, or keep them in an archive.
How long does a ServiceNow migration take?
There is no neutral public benchmark. Freshworks says ServiceNow to Freshservice migrations "typically range from 4-12 weeks" (Freshworks, as of 23 Oct 2026), the target vendor's own estimate. Record volumes, history depth, archive tables, attachments, API paging, the number of test migrations and your freeze window drive the real figure. For one real case, Metro Systems moved 19,970 ServiceNow records to Freshservice in 136 minutes.
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. GARTNER and MAGIC QUADRANT are registered trademarks of Gartner, Inc. and/or its affiliates in the U.S. and internationally.
Written by
Ayush BothraFounding 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.


