Freshservice to ServiceNow Data Migration
Upgrading from Freshservice to ServiceNow? Settle automates the mapping between Freshservice's ITSM model and ServiceNow's ITIL-aligned tables — preserving incident history, asset data, change records, and service catalog items.
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 Freshservice to ServiceNow — whether you're scoping, planning, or mid-program.
Freshservice stores ITSM data in tickets, assets, changes, and problems with custom fields, workflow automators, and a built-in CMDB. ServiceNow uses ITIL-aligned tables — incident, cmdb_ci, change_request, problem — with a more granular field model and Flow Designer automation. Settle translates Freshservice's streamlined ITSM data to ServiceNow's enterprise architecture automatically.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your Freshservice to ServiceNow migration
Settle classifies Freshservice tickets into ServiceNow incidents and service requests based on ticket type, category, and custom field analysis — generating routing rules you approve before migration.
Assets are mapped to ServiceNow CMDB classes — Freshservice asset types translate to cmdb_ci subclasses (cmdb_ci_computer, cmdb_ci_server, cmdb_ci_software_instance) with attribute and relationship preservation.
Service catalog items are profiled and mapped to ServiceNow catalog items with custom fields translated to catalog variables and approval workflows documented for Flow Designer rebuild.
Settle catalogs all workflow automators with field-level dependencies, generating a ServiceNow automation rebuild checklist covering business rules, Flow Designer flows, and SLA definitions.
Get your Freshservice to ServiceNow mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
3–6 months
Estimated cost
$250K–$600K
Team size
3–6 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 Freshservice to ServiceNow
Ticket type routing to ServiceNow tables
Freshservice uses ticket types (Incident, Service Request) within a unified ticket model. ServiceNow separates incidents and service requests into distinct tables with different fields, workflows, and SLA configurations. Freshservice tickets must be classified and routed to the correct ServiceNow table. Settle analyzes ticket type, category, and custom field data to generate the routing rules.
Explore related migrations →Asset module to ServiceNow CMDB
Freshservice's asset management tracks hardware and software assets with asset types, lifecycle status, and relationships. ServiceNow's CMDB uses a class hierarchy (cmdb_ci → cmdb_ci_computer → cmdb_ci_server) with CI relationships and discovery integration. The asset-to-CI translation requires mapping Freshservice asset types to ServiceNow CMDB classes and preserving asset relationships.
Explore related migrations →Service catalog translation
Freshservice's service catalog uses service items with custom fields and approval workflows. ServiceNow's service catalog uses catalog items with variable sets, order guides, and execution plans. The catalog structure is more complex in ServiceNow — each Freshservice service item must map to a ServiceNow catalog item with variables replacing Freshservice's custom fields.
Explore related migrations →Workflow automator to ServiceNow automation
Freshservice's workflow automators use event-condition-action rules for ticket routing, notifications, and escalations. ServiceNow uses business rules, Flow Designer, and SLA definitions. The automation logic doesn't migrate — it must be rebuilt. Settle documents all automator field references and conditions for the ServiceNow implementation team.
Explore related migrations →Agent groups and role mapping
Freshservice uses agent groups with role-based permissions. ServiceNow uses assignment groups, ACLs, and user roles with more granular access control. The group membership and permission model translation affects case routing and data visibility post-migration.
Explore related migrations →Freshservice to ServiceNow field mapping — what data moves
12 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| Ticket (Incident) | → | Incident (incident) |
| Ticket (Service Request) | → | Service Request (sc_request) |
| Problem | → | Problem (problem) |
| Change | → | Change Request (change_request) |
| Release | → | Release (rm_release) |
| Asset | → | CMDB CI (cmdb_ci_*) |
| Asset Relationship | → | CI Relationship (cmdb_rel_ci) |
| Service Catalog Item | → | Catalog Item (sc_cat_item) |
| Requester | → | sys_user / customer_contact |
| Agent Group | → | Assignment Group (sys_user_group) |
| Knowledge Article | → | Knowledge Article (kb_knowledge) |
| Conversation (ticket notes) | → | Work Note / Additional Comments |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual Freshservice to ServiceNow migration
Freshservice to ServiceNow is the most common mid-market-to-enterprise ITSM upgrade. Companies adopt Freshservice for its ease of use and lower cost, then outgrow it when they need ServiceNow's advanced capabilities — enterprise CMDB with discovery, Security Operations, HR Service Delivery, Customer Service Management, or complex change management workflows. This migration is common at the 1,000–5,000 employee stage, after M&A when the parent company standardizes on ServiceNow, or when ITIL maturity requires capabilities Freshservice doesn't offer.
The migration maps Freshservice's streamlined ITSM model to ServiceNow's more granular architecture. Freshservice tickets map to ServiceNow incidents or service requests depending on ticket type. Assets map to CMDB CIs but with a different class hierarchy. Changes, problems, and releases each have structural differences. Freshservice's workflow automators must be rebuilt as ServiceNow business rules and Flow Designer flows.
Companies typically manage this migration during ServiceNow implementation. The ticket classification, asset-to-CMDB mapping, and custom field translation are where most of the manual effort goes.
Consulting-led delivery for migrations in this class typically runs $250K–$600K. 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 Freshservice 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.