ServiceNow to Freshservice migration: what moves, what breaks, and a 90-day plan
Short answer
Migrating from ServiceNow to Freshservice makes sense when ServiceNow's cost, complexity, or admin overhead no longer justifies the ROI — typically for teams under 200 employees without ESM ambitions. What moves cleanly: tickets, users, groups, attachments, knowledge base articles (with HTML conversion). What breaks: workflows, Flow Designer automations, complex CMDB CI relationships, custom UI policies, and ServiceNow-specific integrations. Timeline: 90 days from discovery to hypercare with a phased approach. Use Help Desk Migration for bulk data transfer, or ServiceNow's CSV export + Freshservice API for custom migration. Don't migrate if you depend on ServiceNow's HR Service Delivery, complex change CABs, or enterprise reporting that Freshservice can't replicate.
When to migrate and when NOT to
Migrate from ServiceNow to Freshservice if:
- Cost is unsustainable. ServiceNow annual costs (licenses + admin + managed services) exceed $100k and your team is under 100 agents. Freshservice delivers 80% of the functionality at 30% of the cost.
- You lack dedicated ServiceNow admin resources. ServiceNow requires full-time admin expertise (or expensive managed services). Freshservice can be managed part-time by an IT generalist.
- You're using only core ITSM. If you're running incident, request, and basic change management without leveraging ServiceNow's CMDB, ESM modules, or custom applications, you're overpaying for unused complexity.
- Implementation and upgrades are painful. ServiceNow's release cycles, instance upgrades, and customization maintenance require ongoing investment. Freshservice is cloud-native with automatic upgrades.
- Your IT org is shrinking or simplifying. Post-merger consolidation, budget cuts, or a shift away from enterprise IT complexity make Freshservice's simplicity attractive.
Do NOT migrate if:
- You rely on HR Service Delivery or multi-department ESM. ServiceNow's HR onboarding/offboarding workflows, employee case management, and ESM modules are more mature than Freshservice's multi-department support.
- Your CMDB is mission-critical. If change management, incident resolution, and capacity planning depend on ServiceNow's CMDB with rich CI relationships and integrations, Freshservice's asset management won't match the depth.
- You have complex approval workflows and CAB processes. ServiceNow's Flow Designer, approval engines, and change CAB scheduling are more flexible than Freshservice's visual automation.
- You're heavily integrated with ServiceNow ITOM/ITAM/GRC modules. If your ITSM platform is the hub for IT operations, governance, and compliance, migrating away creates integration debt.
- Your organization is growing toward enterprise scale. If you're 500+ employees today and planning ESM expansion, stay with ServiceNow or consider it a long-term investment. Migrating now and migrating back later is expensive.
What moves cleanly vs what breaks
This table summarizes what migrates from ServiceNow to Freshservice, how cleanly data transfers, and what manual work you'll face.
| Data type | Migration outcome | Notes |
|---|---|---|
| Tickets / Incidents | ✓ Moves cleanly | Export from ServiceNow as CSV (incident table), map fields (status, priority, category, assignment group), import to Freshservice via CSV or API. Ticket numbers won't preserve (Freshservice generates new IDs); add old ticket# as custom field for reference. |
| Ticket history & comments | ✓ Moves cleanly | Export work notes and comments from ServiceNow, import as Freshservice ticket notes. Timestamps and user attribution transfer. Formatting (bold, lists) may need cleanup if ServiceNow used rich text. |
| Attachments | ⚠ Partial | Attachments export via ServiceNow API (not CSV). Use Help Desk Migration or custom script to download attachments and re-upload to Freshservice tickets. Large volumes (10k+ attachments) are slow; prioritize recent tickets. |
| Users & requesters | ✓ Moves cleanly | Export user table (name, email, department, manager) from ServiceNow, import to Freshservice. If you're using SSO (Okta, Azure AD), users auto-provision on first login. Passwords don't migrate (SSO handles auth). |
| Groups / assignment groups | ✓ Moves cleanly | Recreate assignment groups in Freshservice manually (group names, members, escalation rules). Group memberships from ServiceNow can be exported and scripted, but Freshservice groups are simpler (no complex role hierarchies). |
| SLAs | ⚠ Rebuild required | SLA definitions (response time, resolution time, business hours) must be recreated in Freshservice. Export ServiceNow SLA targets as reference, configure new SLAs in Freshservice SLA Management. Historical SLA compliance data (met/breached) migrates as ticket metadata but won't populate Freshservice SLA reports retroactively. |
| Automations / business rules | ✗ Rebuild required | ServiceNow business rules, UI policies, and Flow Designer workflows don't transfer. Audit your ServiceNow instance for active automations, document logic, rebuild in Freshservice Automation (visual workflow builder). Freshservice automations are simpler — complex logic (JavaScript in ServiceNow) may not have direct equivalents. |
| CMDB / Assets | ⚠ Partial | Basic asset data (hardware, software, owner, location) exports from ServiceNow CMDB and imports to Freshservice Asset Management. What breaks: complex CI relationships (depends on, hosted on, uses), discovery sources, and integrations. If your CMDB is critical, plan to rebuild relationships or use Freshservice's automated discovery to repopulate assets from scratch. |
| Knowledge base | ✓ Moves cleanly | Export ServiceNow KB articles as HTML, import to Freshservice Knowledge Base via API or CSV. Formatting, images, and internal links transfer with minor cleanup. Categories and article permissions (visibility rules) must be recreated manually. |
| Service catalog | ⚠ Rebuild required | Service catalog items (request types, forms, approval workflows) must be recreated in Freshservice. Export ServiceNow catalog definitions as documentation, rebuild request forms in Freshservice. Freshservice service catalog is visual (drag-drop form builder); ServiceNow custom forms with catalog client scripts won't transfer directly. |
| Integrations | ✗ Rebuild required | ServiceNow integrations (SIEM, monitoring tools, SSO, Slack, ServiceNow IntegrationHub flows) must be disconnected and reconnected to Freshservice. Freshservice supports 400+ marketplace apps; if your integration isn't listed, use Freshservice API or webhooks. Budget 1-2 weeks per major integration. |
| Reports & dashboards | ✗ Rebuild required | ServiceNow reports (incident trends, SLA compliance, agent performance) don't migrate. Freshservice includes pre-built reports; recreate custom reports using Freshservice Analytics. ServiceNow Performance Analytics dashboards have no direct equivalent; use Freshservice scheduled reports or export to Power BI/Tableau. |
Migration approaches: tools and methods
Three approaches to migrate data from ServiceNow to Freshservice, with trade-offs:
1. Help Desk Migration (third-party tool)
How it works: Cloud service that connects to ServiceNow and Freshservice APIs, maps fields, and transfers tickets, users, attachments, and knowledge base articles in bulk.
Pros: Fast (bulk migration in hours to days), handles attachments automatically, provides field mapping UI, no scripting required.
Cons: Costs $199-$1,499 depending on record count. Limited control over data transformation. May not support custom ServiceNow tables or complex CI relationships. Best for straightforward migrations (tickets, users, knowledge base) without heavy customization.
When to use: Mid-sized migrations (5k-50k tickets), limited custom fields, tight timeline (4-6 weeks).
2. CSV export + Freshservice bulk import
How it works: Export ServiceNow tables (incident, user, asset) as CSV, map columns to Freshservice fields in Excel/scripts, import via Freshservice Admin > Import.
Pros: Free (no third-party costs). Full control over data mapping and cleanup. Can filter/transform data before import (e.g., exclude closed tickets older than 2 years).
Cons: Manual effort (data mapping, CSV formatting, validation). Attachments don't export via CSV (requires API scripts). Large datasets (50k+ tickets) hit CSV size limits; need batch imports.
When to use: Small migrations (under 10k tickets), custom data transformation needed, budget-constrained projects.
3. Custom API migration (scripted)
How it works: Write Python/Node.js scripts to pull data from ServiceNow REST API, transform, and push to Freshservice API. Full control over data mapping, error handling, and validation.
Pros: Handles complex migrations (custom tables, CI relationships, attachments). Can run incremental migrations (migrate in batches, validate, iterate). Reusable for future data syncs or rollback scenarios.
Cons: Requires developer time (2-4 weeks to build, test, debug scripts). API rate limits on both platforms require throttling. Higher cost (developer time vs third-party tool).
When to use: Large migrations (50k+ tickets), custom ServiceNow tables or fields, CMDB with complex relationships, need for parallel run or phased cutover.
Recommendation:
For most mid-sized teams (10-50 agents, 10k-30k tickets), Help Desk Migration offers the best speed-to-cost ratio. For teams under 10k tickets with simple data, CSV export is sufficient. For enterprises with custom CMDB, complex workflows, or 50k+ tickets, invest in custom API migration — you'll need the control and error handling.
Phased 90-day migration plan
A realistic timeline from kickoff to cutover, with buffer for UAT and hypercare. Adjust durations based on data volume and org complexity.
Phase 1: Discovery & Design (Weeks 1-3)
Objectives: Audit ServiceNow configuration, define Freshservice target state, plan data mapping.
- Export ServiceNow configuration: active business rules, workflows, SLA definitions, assignment groups, service catalog items, integrations.
- Audit ticket data: volume (open/closed), custom fields in use, attachment size, oldest ticket to migrate.
- Define Freshservice configuration: incident/request workflows, SLA targets, automation rules, agent roles, service catalog.
- Document field mapping: ServiceNow status → Freshservice status, priority schemes, categories, custom fields.
- Choose migration approach (Help Desk Migration, CSV, or API scripts).
Deliverable:
Migration plan document with field mapping, timeline, and cutover plan.
Phase 2: Freshservice Configuration & Data Mapping (Weeks 4-7)
Objectives: Configure Freshservice instance, rebuild workflows, prepare migration scripts/tools.
- Set up Freshservice instance: agent accounts, groups, roles, email routing, SSO integration.
- Configure incident/request workflows: statuses, priorities, SLAs, escalation rules.
- Rebuild service catalog: request forms, approval workflows (simplified from ServiceNow).
- Configure automations: assignment rules, notification templates, SLA breach alerts.
- Prepare migration scripts or Help Desk Migration configuration: field mapping, data filters (exclude tickets older than X years).
- Set up knowledge base: categories, article templates.
Deliverable:
Freshservice instance configured, migration tool ready for test run.
Phase 3: Test Migration & UAT (Weeks 8-9)
Objectives: Migrate subset of data, validate accuracy, test workflows, train agents.
- Run test migration: migrate 500-1,000 sample tickets (mix of open/closed, high/low priority, with attachments).
- Validate data: check ticket statuses, assignments, SLA calculations, attachment integrity, user mappings.
- Test workflows: create test tickets in Freshservice, verify assignment rules, SLA timers, notifications, escalations.
- Train agent team: Freshservice UI walkthrough, queue management, ticket updates, knowledge base search.
- Document issues: data mapping errors, missing automations, performance gaps vs ServiceNow.
Deliverable:
UAT sign-off, issues resolved, agents trained.
Phase 4: Final Migration & Cutover (Week 10)
Objectives: Migrate full dataset, switch production traffic to Freshservice, decommission ServiceNow access.
- Freeze ServiceNow (read-only): stop new ticket creation 48 hours before cutover. Redirect users to "maintenance mode" message.
- Run final migration: export all ServiceNow data (open tickets, users, assets, knowledge base), import to Freshservice. Typical runtime: 12-24 hours for 20k-50k tickets.
- Validate migration: spot-check 100+ tickets, verify open ticket assignments, test knowledge base search.
- Cutover: switch email routing to Freshservice, update service desk portal URL, enable Freshservice for end users.
- Communicate to organization: "Service desk is now on Freshservice. New portal URL: [link]. Old ServiceNow tickets are available for 30 days (read-only)."
Deliverable:
Freshservice live in production, ServiceNow decommissioned.
Phase 5: Hypercare & Optimization (Weeks 11-13)
Objectives: Monitor performance, fix issues, tune automations, gather feedback.
- Daily standup with IT team: review open issues, ticket backlogs, agent feedback.
- Fix automation gaps: adjust assignment rules, SLA targets, notification frequency based on real ticket flow.
- Monitor SLA compliance: compare Freshservice SLA metrics to ServiceNow baseline, tune business hours and targets.
- Knowledge base optimization: identify top ticket categories without KB articles, publish new articles.
- Decommission ServiceNow: export final archive (CSV + attachments), cancel ServiceNow subscription.
Deliverable:
Stable Freshservice operation, agent adoption, ServiceNow fully decommissioned.
Cost drivers (no estimates, just categories)
Budget for these cost categories when planning the migration. Actual costs vary by data volume, org size, and internal vs consultant labor.
- Migration tooling — Help Desk Migration ($199-$1,499), or developer time for custom API scripts.
- Freshservice licenses — Pay for Freshservice subscriptions during parallel run (if running both platforms simultaneously for 2-4 weeks). Most teams start Freshservice subscriptions 1 month before cutover.
- Consulting / implementation services — Process design, Freshservice configuration, data migration execution, UAT coordination, training. Scope depends on whether you self-implement or hire ITSM consultants.
- Agent training — Time spent training IT team on Freshservice UI, workflows, and new processes. Budget 2-4 hours per agent (group training + hands-on practice).
- Integrations — Reconnecting SSO, Slack, monitoring tools, HR systems to Freshservice. Some integrations are plug-and-play (Okta, Azure AD); custom integrations require developer time.
- Opportunity cost — IT team focus on migration reduces capacity for BAU work. Plan for reduced service desk capacity during Weeks 9-11 (UAT, cutover, hypercare).
Common failure points
Migrations fail or stall when these risks aren't addressed upfront:
1. Migrating stale or low-quality data
Don't migrate every ticket from the past 5 years. Old, closed tickets with no historical value clutter Freshservice and slow migration. Fix: Archive tickets older than 2 years, migrate only open tickets + closed tickets from the past 12-24 months.
2. Underestimating workflow rebuild effort
ServiceNow workflows with complex approval chains, conditional logic, and integrations won't map 1:1 to Freshservice. Teams assume automation "just migrates" and hit delays in Week 4-6. Fix: Audit active ServiceNow workflows in Week 1, simplify before rebuilding in Freshservice.
3. Poor change management and user communication
End users and agents resist the new platform if they're not prepared. Surprise cutover with no training = ticket backlog and frustrated users. Fix: Communicate early (Week 1), train agents (Week 8), send end-user "what's changing" emails 2 weeks before cutover.
4. No rollback plan
If the cutover fails (data issues, critical automation missing, integrations broken), what's the rollback procedure? Without a plan, you're stuck troubleshooting in production. Fix: Keep ServiceNow read-only (not decommissioned) for 2-4 weeks post-cutover. Prepare "revert to ServiceNow" runbook if Freshservice fails.
5. Integration gaps discovered post-cutover
ServiceNow integrations (monitoring alerts → incidents, Slack notifications, SSO) break after cutover because they weren't tested pre-migration. Fix: Inventory all ServiceNow integrations in Week 1, test Freshservice equivalents in Week 8 (UAT), have fallback manual processes ready.
Pre-migration checklist
Confirm these items before starting the migration:
Discovery & planning
- ServiceNow data audit complete: ticket volume, custom fields, attachment size, CMDB CI count.
- Field mapping documented: ServiceNow statuses → Freshservice statuses, priorities, categories.
- Workflow inventory: list of active business rules, automations, approval workflows to rebuild.
- Migration tool chosen: Help Desk Migration, CSV export, or custom API scripts.
- Cutover date set: coordinated with business (avoid month-end, quarter-end, or major releases).
Freshservice configuration
- Freshservice instance provisioned: agents created, groups configured, SSO integrated.
- Workflows configured: incident/request statuses, SLAs, escalation rules tested.
- Service catalog rebuilt: request forms, approval workflows, self-service options.
- Knowledge base structure ready: categories created, sample articles published.
- Integrations connected: SSO, Slack, email routing, monitoring tools (test in UAT).
Training & communication
- Agent training scheduled: Freshservice UI, ticket management, SLA tracking.
- End-user communication sent: new portal URL, what's changing, go-live date.
- Hypercare team identified: on-call support for Week 1 post-cutover.
Migration execution
- Test migration completed: 500-1,000 sample tickets migrated, validated, issues fixed.
- Final migration window scheduled: ServiceNow frozen, data export started.
- Rollback plan documented: steps to revert to ServiceNow if cutover fails.
Frequently asked questions
How long does a ServiceNow to Freshservice migration take?
Plan 90 days from kickoff to cutover: 2-3 weeks discovery and design, 3-4 weeks data mapping and Freshservice configuration, 2 weeks test migration and UAT, 1 week final migration and cutover, 2-3 weeks hypercare. Parallel run (both systems live) adds 2-4 weeks. Faster migrations (6-8 weeks) are possible if you're only migrating core incident data and users, skipping CMDB and complex workflows.
Will I lose ticket history when migrating from ServiceNow?
No. Ticket history, comments, and attachments migrate via CSV export from ServiceNow and bulk import to Freshservice. Expect data mapping work (statuses, priorities, custom fields). Ticket relationships (parent/child, related incidents) may not transfer cleanly — budget time to rebuild critical links manually.
What doesn't migrate from ServiceNow to Freshservice?
Workflows and business rules (rebuild in Freshservice automation builder), custom UI policies and client scripts (Freshservice uses different UX), Flow Designer automations (rebuild as Freshservice workflows), complex CMDB CI relationships (Freshservice CMDB is simpler), ServiceNow custom applications (no equivalent in Freshservice), and ServiceNow integrations via IntegrationHub (reconnect via Freshservice marketplace apps or API).
Should I migrate the CMDB from ServiceNow?
Depends on CMDB maturity. If your ServiceNow CMDB has accurate CI data, clean relationships, and is actively used by change/incident teams, migrate it. If the CMDB is stale, incomplete, or unmaintained, start fresh in Freshservice with automated asset discovery. Migrating a messy CMDB wastes time and carries bad data forward.
Can I run ServiceNow and Freshservice in parallel?
Yes, but it's painful. Parallel run means agents check both systems for tickets, data syncs manually, and users get confused about which portal to use. We recommend a short parallel run (1-2 weeks max) for validation only: new tickets go to Freshservice, old ServiceNow tickets remain read-only. Don't try to sync ticket updates bidirectionally — it creates data conflicts.
What if the migration fails?
Keep ServiceNow read-only (not decommissioned) for 2-4 weeks post-cutover. If Freshservice has critical issues (data loss, broken integrations, SLA failures), you can revert: redirect email routing back to ServiceNow, reactivate agent access, communicate rollback to users. Test the rollback procedure during UAT so you're not figuring it out in a crisis.
Need help with your ServiceNow to Freshservice migration?
We plan and execute ITSM migrations. Bring us your ServiceNow instance audit, your Freshservice requirements, and your timeline — we'll handle data migration, workflow rebuild, UAT, and cutover.