ServiceNowFreshservice

ServiceNow to Freshservice migration

ITSM specialists move your incidents, problems and change requests into Freshservice, check a sample with you first, and count every record on both sides.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

Last updated September 2026 · 10 object types mapped

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

ServiceNow to Freshservice at a glance

We move incidents, problems, changes, request items, requesters, departments and the knowledge base from ServiceNow into Freshservice, with work notes and comments kept as separate private and public notes. An engineer maps states, priorities and groups with you, runs the import in dependency order, and reconciles counts on both sides before you cut over.

Objects mapped
10
from the live connector
Typical timeline
About 10 business days for up to 100k records
3 phases
Free sample
100 records
checked by your team first
Quote
Fixed
within 24 hours

What moves

What moves from ServiceNow to Freshservice

Every object our connector moves, in the order it is written into Freshservice.

  • 11 included
ServiceNowFreshservice

Tickets

  • AgentsAgents

    Order 1

  • CompaniesDepartments

    Order 2

  • UsersRequesters

    Order 3 · after Agents, Companies

  • IncidentsTickets

    Order 4 · after Agents, Users, Companies

  • ProblemsProblems

    Order 5 · after Agents, Users

  • Change RequestsChanges

    Order 6 · after Agents, Users

  • Request ItemsRequest Items

    Order 7 · after Agents, Users, Companies

  • AttachmentsAttachments

    Files under the 40 MB per-ticket cap are uploaded to the matching note; larger files are re-hosted and linked.

Knowledge Base

  • Knowledge BasesCategories

    Order 7

  • CategoriesFolders

    Order 8 · after Knowledge Bases

  • ArticlesArticles

    Order 9 · after Categories

Looking for another object?From the MigrateX connector catalogue, fetched 22 Sep 2026. Object mapping is live in our connectors; field-level mapping is reviewed with you during scoping.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

ServiceNow to Freshservice migration timeline

Estimated total

About 10 business days

for up to 100k records

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Access and scope

      You1 day

      You create a ServiceNow integration user (basic auth or OAuth) with read access to task (including its work notes and additional comments), sys_user, kb_knowledge and sc_req_item, plus a Freshservice API key. We agree which tables, date ranges and knowledge bases are in scope.

    • Schema and volume export

      MigrateX0.5 day

      We pull record counts, custom fields, choice lists, groups and attachment sizes from both sides and check your instance's rate limit rules.

    • Mapping sign-off

      Both0.5 day

      We send the field, state, priority and group mapping sheet, plus the list of oversize attachments and inactive callers. You approve or amend it.

  2. Migration

    Day 3-7

    • People and structure

      MigrateX1 day

      Departments, requesters, agents and groups are created in Freshservice in dependency order. Custom fields are created to hold ServiceNow numbers and original dates.

    • Sample run

      Both1 day

      A few hundred incidents, problems, changes and request items with notes and attachments, so you can check the result before the bulk pass.

    • Bulk pass

      MigrateX2-3 days

      Tickets, notes and attachments in batches paced to the Freshservice plan limit, with checkpoints by sys_id. Knowledge bases, categories, folders and articles follow.

    • Delta and cutover

      Both0.5 day

      Records created or updated in ServiceNow since the bulk pass are synced. You switch intake to Freshservice; ServiceNow becomes read-only.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Counts per object, per state and per group on both sides, plus a list of every record that needed a placeholder or default mapping.

    • Spot checks

      You1 day

      Your service desk leads open a random sample of migrated tickets, request items and articles and confirm notes, attachments and requesters are right.

    • Fixes and sign-off

      Both1 day

      We correct anything the spot checks raise, re-run the affected batch, and hand over the sys_id map and mapping sheet.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

Known risks

Every known risk on this route, with how we handle it

  • 2 solved
  • 3 handled
  1. 01SolvedMost critical

    Requesters and departments must exist before incidents

    The problem

    A Freshservice ticket needs a requester (requester_id or email) and optionally a department_id. If a ticket is created with an email that has no matching contact, Freshservice adds a new contact for that email with no department, manager, location or custom fields, and the ticket's department is dropped. Every later object (problems, changes, request items) then points at the wrong or an empty requester.

    How we handle it

    We import in dependency order: companies to departments, then sys_user to requesters (with department_ids, reporting_manager_id, location_id), then agents, then groups, and only then incidents. Inactive ServiceNow users who still appear as callers get a placeholder requester so the ticket keeps its history without inflating your active user count.

    Source: Freshservice API documentation, checked 15 Nov 2026

  2. 02Handled

    Freshservice documents no way to backdate tickets or notes

    The problem

    Freshservice does not document a way to set the original created date on a ticket or note. A ticket created today shows today's date, which breaks age reports, SLA history and audit trails for migrated incidents.

    How we handle it

    We add date-type custom fields for original opened, resolved and closed dates, populate them from ServiceNow, and keep the ServiceNow number in a text field so reports and searches still work. SLA timers on migrated tickets are handled by importing resolved and closed records in their final state so no new timers start.

    Source: Freshservice API documentation, checked 15 Nov 2026

  3. 03Handled

    Attachment ceilings differ by orders of magnitude

    The problem

    ServiceNow allows up to 1024 MB per file by default. Freshservice caps the combined attachments on a ticket at 40 MB across the description and every note. Large incident attachments therefore fail on import, and a naive script either aborts the ticket or silently drops the file.

    How we handle it

    We size every attachment during export, re-host attachments over the ticket cap in your own storage (S3 or SharePoint), and insert a link with the original filename and size in the note where the file sat. Everything under the cap is uploaded as multipart form-data against the matching note.

    Source: ServiceNow documentation, checked 15 Nov 2026

  4. 04Handled

    Request items sit under requests, not incidents

    The problem

    A ServiceNow request (sc_request) fans out into one requested item (sc_req_item) per catalog item, each with its own variables and catalog tasks. Freshservice's create-ticket API currently accepts only the incident type, so a flat export either loses the parent request or dumps variables into the description.

    How we handle it

    Each requested item becomes its own Freshservice ticket. The parent REQ number and the catalog item name are stored in custom fields, item variables are rendered as a labelled table in the description, and catalog tasks become private notes in order. Where the Freshservice catalog already exists we can link the item on request.

    Source: ServiceNow documentation, checked 15 Nov 2026

  5. 05Solved

    Paced to each platform's request quotas, on different clocks

    The problem

    ServiceNow enforces per-hour rate limit rules that are specific to each instance, while Freshservice enforces per-minute limits with separate sub-limits for creating tickets and listing requesters. A migration that ignores either side stalls on HTTP 429 mid-run and leaves partial tickets behind.

    How we handle it

    The runner paces requests against the Freshservice plan limit, honours Retry-After on both sides, and checkpoints progress by sys_id so an interrupted batch resumes without duplicates. For 100k+ records we schedule the bulk pass outside your peak hours and run a delta pass at cutover.

    Source: Freshservice API documentation, checked 15 Nov 2026

Technical profile

What makes this route technical

The API limits and data model differences between ServiceNow and Freshservice that shape the plan.

ServiceNow Table API page size
sysparm_limit defaults to 10,000 records per request. ServiceNow warns that unusually large values hurt instance performance, so exports run in smaller pages.

Source: ServiceNow documentation, checked 15 Nov 2026

Reference fields come back as sys_ids
sysparm_display_value defaults to false, so reference fields such as caller and assignment group arrive as sys_ids rather than names. We resolve them against sys_user, sys_user_group and the choice tables during export.

Source: ServiceNow documentation, checked 15 Nov 2026

ServiceNow inbound REST rate limits
Rate limit rules are configured per instance and count requests per hour, per user or role. Exceeding a rule returns HTTP 429 with a Retry-After header. The docs do not state an out-of-the-box limit, so we confirm your instance's rules before scheduling the export.

Source: ServiceNow documentation, checked 15 Nov 2026

ServiceNow attachment ceiling
com.glide.attachment.max_size defaults to 1024 MB per file; allowed types come from glide.attachment.extensions.

Source: ServiceNow documentation, checked 15 Nov 2026

Freshservice attachment cap per ticket
The total size of all attachments on a ticket, across the description and every note, cannot exceed 40 MB.

Source: Freshservice API documentation, checked 15 Nov 2026

Freshservice API rate limit (Pro plan)
400 requests per minute overall on Pro (Starter 100, Growth 200, Enterprise 500), with a sub-limit of 140 ticket creates per minute on Pro. Invalid requests count too, and HTTP 429 comes back with a Retry-After header.

Source: Freshservice API documentation, checked 15 Nov 2026

Historical timestamps
Freshservice does not document a way to set the original created date on a ticket or note. The original ServiceNow opened, resolved and closed dates are preserved in dedicated custom fields instead.

Source: Freshservice API documentation, checked 15 Nov 2026

Facts checked 15 Nov 2026 against ServiceNow and Freshservice documentation. Each fact links its source.

Testimonials

What our customers say

  • “We've done ServiceNow to Freshservice, HaloITSM to Freshservice, even a Freshservice to JSM move. Honestly I was nervous about the ServiceNow one because of the dataset size. But it just... worked. No drama.”

    Charles Manuel

    CEO, FreshIdeas.ai

  • “Our client had 4 years of ticket history in ServiceNow and their IT team was convinced half of it would get lost. MigrateX ran a demo migration and the client's own team verified it. That closed the conversation.”

    Mohamed Firdous

    Founder & Business Head, Assuretek IT Solutions

ServiceNow to Freshservice questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

Do ServiceNow incidents become Freshservice tickets?

Yes. Each incident becomes a ticket of type Incident with the same subject, description, requester, group, agent, status and priority mapped to Freshservice values. The original INC number is kept in a custom field so agents can still search by it.

What happens to work notes and additional comments?

Work notes and additional comments are separate journal fields on every ServiceNow task, and we export each entry on its own rather than as one block of text. Work notes are imported as private notes and additional comments as public notes, in chronological order, with the original author and time noted in each entry.

Are CMDB configuration items and assets included?

Not in the standard scope. We can migrate selected cmdb_ci classes to Freshservice asset types on request; relationships between CIs are not carried over. Most teams rebuild the asset inventory with the Freshservice discovery probe and keep the CI reference on migrated tickets as text.

Do SLAs and timers restart on migrated tickets?

Freshservice calculates SLA due dates from its own created_at, which Freshservice documents no way to backdate. Resolved and closed tickets are imported in their final state so no timer starts. For open tickets we set the status last, and the original opened date lives in a custom field for reporting.

How are request items and catalog tasks handled?

Each requested item (RITM) becomes its own ticket. The parent REQ number and catalog item name go into custom fields, variables are written as a labelled table in the description, and catalog tasks become ordered private notes. Linking to an existing Freshservice catalog item is available on request.

Will the original created and resolved dates be preserved?

Not in the built-in timestamp fields, because Freshservice does not document a way to set the original created date. We create date custom fields for original opened, resolved and closed dates and populate them from ServiceNow, so age and volume reports can be rebuilt against those fields.

Is there downtime during the migration?

No. ServiceNow stays live during the bulk pass because we only read from it. At cutover we run a delta pass for anything created or changed since the bulk run, you switch intake to Freshservice, and ServiceNow becomes read-only. The switch itself takes under an hour.

How do we check every record arrived?

We reconcile record counts per object, status and group on both sides and deliver the sys_id to Freshservice id map. Every record that needed a placeholder requester, a default state or attachment re-hosting is listed in the report, and your leads spot-check a random sample before sign-off.

What does it cost?

Pricing depends on record volume, the number of objects in scope and how much custom mapping is needed. Use the pricing page to get a quote from your counts; there is no per-record charge for notes or attachments.

How long does it take?

About ten business days for up to 100k records: two for preparation and mapping sign-off, five for the sample run, bulk pass and delta, and three for validation. Larger instances or CMDB scope add time mostly in the bulk pass, which is paced by the Freshservice plan's rate limit.

How it compares

Four ways to run ServiceNow to Freshservice

The same data, moved four different ways. This is what changes between them.

Object coverage (incidents, problems, changes, requests, KB)

  • MigrateX

    Every object in the ServiceNow connector, plus the ones you ask for during scoping.

  • Automated migration software

    Tickets and contacts are covered. Problems, changes and request items often are not.

  • Vendor CSV import

    One object per file, and only the fields the export template exposes.

  • In-house scripts

    Whatever you have time to build before the cutover date.

Work notes vs comments fidelity

  • MigrateX

    Each entry is posted separately, private stays private, public stays public.

  • Automated migration software

    Threads usually arrive, but per-entry author and visibility can be flattened.

  • Vendor CSV import

    Notes collapse into one field on the ticket, if they come across at all.

  • In-house scripts

    Possible, but it is the part teams most often run out of time for.

Attachments

  • MigrateX

    Uploaded against the right note, and re-hosted with a link when they exceed the Freshservice cap.

  • Automated migration software

    Supported up to the destination cap. Oversize files are skipped.

  • Vendor CSV import

    Not carried by a CSV import.

  • In-house scripts

    Needs its own download, retry and upload pipeline.

Original IDs cross-referenced

  • MigrateX

    Every source id is stored on the destination record and handed back as a map.

  • Automated migration software

    Often kept as a tag or a single text field.

  • Vendor CSV import

    Lost once the file is imported.

  • In-house scripts

    Only if you design the mapping table up front.

Delta sync before cutover

  • MigrateX

    Included. Anything created or changed during the bulk pass is synced at cutover.

  • Automated migration software

    Usually a paid upgrade on the top tier.

  • Vendor CSV import

    You would re-export and re-import by hand.

  • In-house scripts

    Requires change tracking and idempotent writes on both sides.

Rate-limit handling

  • MigrateX

    Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.

  • Automated migration software

    Backs off, but a long run can still stall and leave partial records.

  • Vendor CSV import

    Not applicable, and the file size limits bite instead.

  • In-house scripts

    The most common reason a home-grown run dies overnight.

Validation report

  • MigrateX

    Counts per object and per status on both sides, with every default and placeholder listed.

  • Automated migration software

    A run log and an error list, rather than a reconciliation.

  • Vendor CSV import

    Row counts in a spreadsheet.

  • In-house scripts

    You write the reconciliation queries yourself.

Rollback plan

  • MigrateX

    Every write is tagged, so a batch can be reversed without touching your own records.

  • Automated migration software

    Some approaches can clear a migration, some cannot.

  • Vendor CSV import

    Manual cleanup of everything the import created.

  • In-house scripts

    Only if you built the tagging in from the start.

Who does the work

  • MigrateX

    A MigrateX engineer runs it and stays on the cutover call.

  • Automated migration software

    You run the software. Support answers tickets.

  • Vendor CSV import

    Your admins, one file at a time.

  • In-house scripts

    Your engineers, instead of your roadmap.

Guides

Guides for a ServiceNow to Freshservice migration

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    SOC 2 Type II

    Independently audited controls over how we handle your data.

  • GDPR compliant

    Data processing agreement available.

  • HIPAA compliant

    Business associate agreement available.

Start your Freshservice move with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.