ServiceNow to Freshservice Migration 2026: Export, Mapping and Cutover
ServiceNow to Freshservice migration from the export side: archived tables, note visibility, priority mapping, API limits and cutover. Plan your move.
Published Updated 13 min read

On this page
- Why teams move from ServiceNow to Freshservice
- What moves, what gets rebuilt, what's at risk
- ServiceNow to Freshservice field mapping
- Export from ServiceNow, import into Freshservice
- How to migrate ServiceNow to Freshservice in phases
- ServiceNow to Freshservice failure points
- ServiceNow to Freshservice migration checklist
- FAQ
A ServiceNow to Freshservice migration moves your records, not your configuration. Incidents, notes, attachments, people, assets and knowledge travel through the APIs on both sides, while workflows, business rules, SLA definitions and the priority lookup are rebuilt in Freshservice.
If you own a ServiceNow instance and are rightsizing to Freshservice, most of the work sits on the export side: archived tables, note visibility, attachment sizes and sys_id references. If a provider runs the instance for you, read about leaving a ServiceNow MSP first. This guide covers scope, mapping, limits, a phased plan and a checklist. Going the other way? See our Freshservice to ServiceNow migration guide.
Why teams move from ServiceNow to Freshservice
The move usually starts at a renewal, when quoted ServiceNow cost is weighed against published Freshservice plans.
ServiceNow sells ITSM as Foundation, Advanced and Prime, each "Get Custom Quote" (ServiceNow ITSM pricing page, as of 27 Oct 2026). Freshservice lists Starter $19, Growth $49 and Pro $99 per agent per month billed annually, Enterprise on request, with problem and change from Pro; Freddy AI Copilot adds $29 billed annually or $35 monthly on Pro and Enterprise (Freshworks pricing page, as of 27 Oct 2026). Our Freshservice pricing guide prices the other add-ons.
| Date | What happened | Why it matters |
|---|---|---|
| 9 Apr 2026 | ServiceNow said AI is "now in every ServiceNow offering" (press release) | AI is no longer a line to cut |
| 29 Jul 2026 | ServiceNow's Workflow news post (Rahul Tripathi) said it was named a Leader in the 2026 Gartner Magic Quadrant for IT Service Management (ITSM) Platforms | Both platforms cover core ITSM |
| 29 Jul 2026 | A Freshworks press release said it was named a Leader in the 2026 Gartner Magic Quadrant for IT Service Management Platforms | The choice turns on fit and cost |
| 31 Dec 2026 | Freshservice AI Agent Studio stops being a free promotion on Growth, Pro and Enterprise (Freshservice support) | Budget for it from 2027 |
Sources: vendor pages named in each row, as of 27 Oct 2026.
Neither placement tells you whether Freshservice covers your CMDB depth. On G2, ServiceNow ITSM scores 4.5 out of 5 from 2,010 reviews, with Learning Curve (72 mentions) and Expensive (60) the top cons, and Freshservice scores 4.6 from 1,363 reviews (G2, as of 27 Oct 2026). Our ServiceNow vs Freshservice comparison covers capabilities.
What moves, what gets rebuilt, what's at risk
Records move as data, configuration is rebuilt, and anything tied to a ServiceNow reference or lookup is at risk.
| Moves (as data) | Rebuilt in Freshservice | At risk |
|---|---|---|
| Incidents with public and private notes | Business rules, client scripts and flows (as Workflow Automator rules) | Priority values copied as raw numbers |
| Requesters, agents, groups, departments, locations | SLA definitions (as SLA policies) | Requested items, because the ticket API accepts only type "incident" |
| Assets and CIs, one asset type per CSV import | Priority lookup rules (as the priority matrix) | Attachments above 40 MB per ticket |
| Problems and changes, through their own endpoints | Catalog items and record producers | CI relationships, which need a separate load |
| Knowledge articles | Notifications, approvals, reports and dashboards | Archived incidents in ar_ tables, which hold no reference fields |
| Attachments within Freshservice limits | Change models and assignment rules | Original created dates and running SLA timers |
Sources: ServiceNow and Freshservice docs named below, as of 27 Oct 2026.
ServiceNow to Freshservice field mapping
ServiceNow to Freshservice data migration succeeds or fails on value-level mapping, so export custom states, choice lists and lookup rules first.
| ServiceNow (source) | Freshservice (target) | Watch-out |
|---|---|---|
| Incident state New, In Progress | Open (API value 2), or a custom status | Custom status keeps In Progress visible |
| On Hold (four reasons) | Pending (3), or a custom status per reason | Decide which reasons pause the SLA timer |
| Resolved / Closed / Canceled | Resolved (4) / Closed (5), plus a field for Canceled | No default Canceled status |
| Priority 1 Critical, 2 High, 3 Moderate, 4 Low | Urgent (4), High (3), Medium (2), Low (1) | Map by label, never by number |
| Additional comments | Public note | Requesters see it on the portal |
| Work notes | Private note (private: true) | Must stay private |
| Problem, Change Request, Caused by Change | Linked problem and change | Load problems and changes first |
| Configuration item | Associated asset | Load assets first |
| Change type Standard, Normal, Emergency | Minor, Standard, Major, Emergency | Agree a rule for Normal |
Sources: ServiceNow incident state, priority lookup and Change Management API docs (Brazil, updated 10 Sep 2026); Freshservice API docs, statuses and change types articles; as of 27 Oct 2026.
States and the priority matrix
ServiceNow has six incident states and four On Hold reasons (ServiceNow docs, as of 27 Oct 2026). Freshservice's SLA timer for Pending and custom statuses "can be toggled on or off" (Freshservice support, modified 18 Feb 2025). ServiceNow sets a read-only priority from impact and urgency; Freshservice uses "Priority = Impact x Urgency", an option "only available for incident tickets" (ServiceNow docs; Freshservice priority matrix article, as of 27 Oct 2026). Rebuild the matrix before the test load.
Users, groups and note visibility
ServiceNow's docs say "All users who can view incidents see additional comments" (ServiceNow docs, Brazil, as of 27 Oct 2026). In Freshservice, public notes "will be visible to the requester when they're viewing the ticket on the portal", and private notes are "only visible to agents logged in to your service desk" (Freshservice support, modified 18 Sep 2019 and 16 May 2024). Send additional comments to public notes, not replies, which are also emailed to the requester.
Load people first: requester imports are CSV only, with locations created beforehand (Freshservice support, modified 17 Apr 2025).
CIs and relationships
ServiceNow keeps relationships in CI Relationship [cmdb_rel_ci] as a parent CI, a child CI and a type such as Depends on / Used by (ServiceNow CMDB docs, Brazil, as of 27 Oct 2026). Map each CI class to a Freshservice asset type, since imports take "assets of one asset type in one go" (Freshservice support, modified 2 Apr 2026). Load relationships with "Create Relationships in bulk" once both ends exist (Freshservice API docs, as of 27 Oct 2026).
Catalog and knowledge
Catalog items and record producers are rebuilt; Freshservice says "The option to export Service Catalog items directly from the Service Catalog is not available" (Freshservice support, modified 17 Sep 2026). Knowledge moves into categories, folders and articles; set each folder's visibility before loading.
Export from ServiceNow, import into Freshservice
Run the migration API to API: ServiceNow's UI exports stop at 10,000 records per format, and Freshservice documents no self-service ticket import.
| Limit | ServiceNow (export) | Freshservice (import) |
|---|---|---|
| Records per call or file | Table API sysparm_limit default 10,000; UI export 10,000 per format | Bulk API 50 records per request (partners only) |
| Throughput | Large sysparm_limit values "can impact system performance" | 100 / 200 / 400 / 500 calls per minute by plan; migration token 700 per minute |
| Attachments | 1,024 MB default per file (com.glide.attachment.max_size); one file per request | 40 MB total per ticket (API); 40 MB per entity (Bulk API) |
| UI export | Excel stops at 500,000 cells | Ticket export 10,000 per export, without conversations or internal notes |
Sources: ServiceNow docs (Brazil, updated 10 Sep 2026); Freshservice API docs and support articles; as of 27 Oct 2026.
Four rules for the ServiceNow export
- Request both values. Page with sysparm_offset and set sysparm_display_value=all ("Returns both actual and display values"), so each reference keeps its sys_id and name (ServiceNow Table API docs, as of 27 Oct 2026).
- Export archives separately. Archived incidents sit in ar_ tables such as ar_incident, stored flat with "no reference fields to other tables"; sys_archive_log holds an XML copy of each (ServiceNow archiving docs, Brazil, as of 27 Oct 2026). Our guide on whether to migrate ticket history helps decide if they move.
- Carry the dates as data. Freshservice's API describes created_at only as "Ticket creation timestamp" (Freshservice API docs, as of 27 Oct 2026), so store the ServiceNow number and created and resolved dates in custom fields.
- Pre-scan attachment sizes. Flag every ticket whose files total more than 40 MB before the load, not after.
A sysparm_query on the last-updated date gives the cutover delta. Our ServiceNow migration guide covers inventory.
What Freshservice documents for the import
The Bulk API is written for migration partners: tickets and notes only, 50 per request, 10 requests per minute per endpoint, marked "[To be confirmed post load testing]"; workspaces and users must exist first (Freshservice support, modified 24 Nov 2025). A migration token, requested with the account ID, an approximate ticket count and future dates, raises the limit to 700 calls per minute (Freshservice support, modified 21 Mar 2025).
How to migrate ServiceNow to Freshservice in phases
Run the move as a controlled change with exit criteria per phase; Freshworks describes demo, full and delta runs, the demo using "sample data to test mapping rules" (Freshworks migration guide, as of 27 Oct 2026).
- Discover. Count records per table, including ar_ tables, and inventory custom fields, CI classes, flows and SLA definitions.
- Map. Sign off value-level mapping and decide how requested items land.
- Test migration. Load a sample into a non-production account; the sandbox is Enterprise only (Freshworks pricing page, as of 27 Oct 2026). Our test migration checklist sets pass/fail criteria.
- Cutover with delta sync. Pause automations, run the full load, freeze ServiceNow, run the delta, then hold a go/no-go check before switching intake.
- Reconcile. Compare counts, priorities, note visibility, attachments and asset links. Bulk API errors "cannot be retried automatically" (Freshservice Bulk API article, as of 27 Oct 2026).
- Hypercare. Watch rebuilt SLA policies and workflows. Freshworks advises keeping "read-only access to archived data for audit purposes" (Freshworks migration guide, as of 27 Oct 2026).
ServiceNow to Freshservice failure points
Each failure follows from a documented platform difference.
- Inverted priorities. The numeric scales run in opposite directions, so a raw copy turns every Critical into a Low.
- Requested items forced into incidents. They need the Create a Service Request endpoint and matching catalog items, or an archive decision.
- Attachments dropped. A Bulk API attachment over 40 MB is rejected while its ticket is still created (Freshservice Bulk API article, as of 27 Oct 2026).
- Automations firing on old tickets. The Bulk API guide says assignment, cc_emails and association emails are not sent during a bulk load, but Slack and Teams "Will not be muted" and workflows keep running; the migration token article still lists suppression as a future enhancement (Freshservice support, as of 27 Oct 2026).
- Archived references lost. ar_ records hold display values, not sys_ids, so links are matched by name.
- SLA history reset. ServiceNow's SLA repair "removes the SLA record, then recreates and recalculates it" (ServiceNow SLA docs, Brazil, as of 27 Oct 2026), and Freshservice SLA policies run on their own time-priority matrix (Freshservice support, modified 18 Nov 2025). Export SLA outcomes for reporting.
ServiceNow to Freshservice migration checklist
- Confirm your Freshservice plan covers every module you migrate into.
- Count records per table, including ar_ tables, and attachment size per ticket.
- Export choice lists, priority lookup rules and On Hold reasons.
- Inventory business rules, client scripts, flows, SLA definitions and notifications.
- Create workspaces, departments, locations, custom fields, statuses and asset types.
- Import requesters, agents and groups.
- Rebuild the priority matrix and SLA policies.
- Sign off mapping: priority by label, note visibility, change types.
- Decide how requested items and archived records land.
- Pause Slack and Teams alerts, business rules and workflows for the load.
- Run a test migration and reconcile a sample by hand.
- Run the full load and delta, reconcile, and keep ServiceNow read-only until sign-off.
For one project on this route at scale, see how Covia moved 1.03M+ records and 9 years of service desk history from ServiceNow to Freshservice. Metro Systems, an IT services partner, moved 19,970 records on the same route in 136 minutes.
Facts checked October 27, 2026 from ServiceNow Table API, Freshservice API docs, Freshservice Bulk API guide, Freshworks pricing and Freshworks migration guide. No vendor paid for this article. How we research
FAQ
How long does a ServiceNow to Freshservice migration take?
There is no neutral public benchmark. Freshworks says these migrations "typically range from 4-12 weeks", with simple setups in 4 to 6 weeks and complex ones in 8 to 12 (Freshworks migration guide, page dated 3 Nov 2025, as of 27 Oct 2026), a vendor estimate. Duration depends on record volume, archived tables, attachments, CMDB depth, rebuild scope, API throughput and sign-off speed.
Can I import ServiceNow tickets into Freshservice with a CSV file?
Not on your own. Freshservice documents CSV imports for requesters and assets but no self-service ticket import, and its two migration articles are for partners using the APIs (Freshservice support, as of 27 Oct 2026). In a 2021 community thread, a Freshservice Community Manager wrote: "We would have to perform a CSV migration from our end in order to migrate the tickets." Confirm today's option with Freshworks. Our guide to importing tickets into Freshservice covers the CSV, API and bulk limits.
Do SLAs and workflows migrate from ServiceNow?
No. SLA definitions, business rules, flows, client scripts, notifications and running SLA timers are rebuilt in Freshservice, not migrated. Freshservice SLA policies set due-by times from a time-priority matrix in business or calendar hours (Freshservice support, as of 27 Oct 2026). Rebuild them before the test migration and keep past SLA results in an export.
Which Freshservice plan do I need for problem and change records?
Pro. Freshservice puts the service catalog and SLA management on Growth, problem, change and release management on Pro at $99 per agent per month billed annually, and the sandbox on Enterprise (Freshworks pricing page, as of 27 Oct 2026). Teams keeping problem and change history need Pro or above, or an archive outside Freshservice.
Will private work notes stay private in Freshservice?
Only if every note is loaded with the private flag. Freshservice private notes are "only visible to agents logged in to your service desk", while public notes show on the requester's portal (Freshservice support, as of 27 Oct 2026). Map work notes to private notes and additional comments to public notes, then check sample tickets from a requester's login during the test migration.
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.


