FreshserviceServiceNow

Freshservice to ServiceNow migration

ITSM specialists move your requesters, tickets and problems into ServiceNow, 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 October 2026 · 10 object types mapped

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

Freshservice to ServiceNow at a glance

We move tickets, problems, changes, service requests, requesters, departments and solution articles from Freshservice into ServiceNow, with private notes and public replies kept as work notes and comments. An engineer loads everything through staging tables and transform maps with notifications off, keeps the original dates, 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 Freshservice to ServiceNow

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

  • 12 included
FreshserviceServiceNow

Tickets

  • AgentsAgents

    Order 1

  • DepartmentsCompanies

    Order 2 · after Agents

  • RequestersUsers

    Order 3 · after Agents, Departments

  • TicketsIncidents

    Order 4 · after Agents, Requesters, Departments

  • ProblemsProblems

    Order 5

  • ChangesChange Requests

    Order 6

  • Request ItemsRequest Items

    Order 7 · after Agents, Requesters, Departments

  • Private Notes and RepliesWork Notes and Comments

    Private notes go to work notes, public replies to additional comments, in original order.

  • AttachmentsAttachments

    Uploaded through the Attachment API against the matching record. Freshservice's 40 MB ticket cap keeps every file within ServiceNow's default limit.

Knowledge Base

  • CategoriesKnowledge Bases

    Order 7

  • FoldersCategories

    Order 8

  • ArticlesArticles

    Order 9

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

Freshservice to ServiceNow 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 share a Freshservice admin API key and create a ServiceNow integration user with the import_transformer and itil roles, plus access to the target tables. We agree which workspaces, date ranges and objects are in scope.

    • Volume and schema export

      MigrateX0.5 day

      We pull record counts per workspace and status, custom fields, groups and attachment sizes from Freshservice, and read your ServiceNow choice lists, priority lookup rules and rate limit rules.

    • Mapping sign-off

      Both0.5 day

      We send the mapping sheet: status to state, priority to impact and urgency, groups, workspaces, service items to catalog items. You approve or amend it.

  2. Migration

    Day 3-7

    • Staging tables and transform maps

      MigrateX1 day

      We build one staging table and transform map per object in a sub-production instance, with business rules and notifications off for the import, then promote them to production.

    • Sample run

      Both1 day

      A few hundred tickets, problems, changes and service requests with notes and attachments, plus the users and companies they depend on, so you can check the result before the bulk pass.

    • Bulk pass

      MigrateX2-3 days

      Users, companies, incidents, problems, changes, requested items, journal entries and attachments in dependency order, paced to both rate limits and checkpointed by Freshservice id. Knowledge bases, categories and articles follow.

    • Delta and cutover

      Both0.5 day

      Tickets created or updated in Freshservice since the bulk pass are synced. You switch intake to ServiceNow and turn notifications back on.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Counts per object, state and group on both sides, plus every record that used a default mapping or a generic catalog item.

    • Spot checks

      You1 day

      Your service desk leads open a random sample of incidents, requested items and articles and confirm dates, journals, attachments and callers are right.

    • Fixes and sign-off

      Both1 day

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

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

    Freshservice hides older tickets by default

    The problem

    List All Tickets returns only the last 30 days unless told otherwise, and embedded conversations stop at ten per ticket. An export that uses the defaults looks complete in testing but misses most of your history and the long threads on hard tickets.

    How we handle it

    We page tickets with updated_since set to the start of your history, 100 per page, and pull every ticket's conversations through the dedicated list endpoint. Export counts are checked against Freshservice's own totals per status and per workspace before anything is written to ServiceNow.

    Source: Freshservice API documentation, checked 15 Nov 2026

  2. 02HandledMost critical

    Notes and replies become two different journals

    The problem

    Freshservice keeps public replies and private notes in one conversation list with a private flag. ServiceNow keeps customer-visible Additional comments and internal Work notes as two separate journal fields on the task. Mixing them up exposes internal notes to requesters on the portal.

    How we handle it

    Private notes become work notes and public replies become additional comments, posted in their original order. The original author and time stay on each entry; where your instance does not accept a backdated journal time, they are written at the top of the entry text.

    Source: ServiceNow documentation, checked 15 Nov 2026

  3. 03Handled

    ServiceNow computes priority, Freshservice sets it

    The problem

    Freshservice priority is a single value from Low to Urgent. On a ServiceNow incident, priority is read-only and calculated from impact and urgency through the priority lookup rules.

    How we handle it

    We agree an impact and urgency pair for each Freshservice priority that produces the right ServiceNow priority under your lookup rules, for example Urgent to impact 1 and urgency 1. Freshservice statuses, including custom ones, are mapped to incident states in the same sign-off sheet.

    Source: ServiceNow documentation, checked 15 Nov 2026

  4. 04Handled

    Service requests need a catalog item on the other side

    The problem

    A Freshservice service request holds one or more requested items, each tied to a service item with its own form fields. In ServiceNow the request becomes sc_request with one sc_req_item per item, and each item must point at a catalog item (sc_cat_item) that already exists.

    How we handle it

    We match Freshservice service items to your ServiceNow catalog items by name with you. Matched items keep their answers as labelled text on the requested item; unmatched ones land on a generic catalog item with the original item name kept, so no request is dropped.

    Source: ServiceNow documentation, checked 15 Nov 2026

  5. 05Solved

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

    The problem

    Freshservice limits per minute with a separate cap for listing tickets. ServiceNow limits per hour with rules unique to your instance. A run that ignores either side stalls on HTTP 429 and leaves half-written records.

    How we handle it

    The export is paced to your Freshservice plan's ticket list limit and the import to your instance's rules. Both sides honour Retry-After, and progress is checkpointed by Freshservice id so an interrupted batch resumes without duplicates.

    Source: Freshservice API documentation, checked 15 Nov 2026

Technical profile

What makes this route technical

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

Freshservice API rate limit
400 requests per minute overall on Pro (Starter 100, Growth 200, Enterprise 500). List All Tickets has its own sub-limit of 120 calls per minute on Pro, and HTTP 429 comes back with a Retry-After header.

Source: Freshservice API documentation, checked 15 Nov 2026

Freshservice page size
List endpoints return 30 records per page by default and at most 100. Asking for more than 100 returns an error, so a full export is many small pages.

Source: Freshservice API documentation, checked 15 Nov 2026

Default ticket list window
List All Tickets returns only tickets created in the past 30 days unless you pass updated_since. A full-history export must set that filter explicitly.

Source: Freshservice API documentation, checked 15 Nov 2026

Freshservice attachment cap per ticket
The combined attachments on a Freshservice ticket cannot exceed 40 MB, so every file you export fits well inside ServiceNow's default ceiling.

Source: Freshservice API documentation, checked 15 Nov 2026

ServiceNow attachment ceiling
com.glide.attachment.max_size defaults to 1024 MB per file. Allowed file types come from glide.attachment.extensions, which some instances restrict.

Source: ServiceNow documentation, checked 15 Nov 2026

ServiceNow import path
POST /api/now/import/{stagingTableName} writes a row to a staging table and runs its transform map synchronously. The insertMultiple variant takes many rows per call but transforms asynchronously by default.

Source: ServiceNow documentation, checked 15 Nov 2026

ServiceNow inbound REST rate limits
Rate limit rules are set per instance and count requests per hour, per user or role. Exceeding a rule returns HTTP 429 with a Retry-After header. There is no documented default, so we read your instance's rules before the bulk pass.

Source: ServiceNow documentation, checked 15 Nov 2026

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

Freshservice to ServiceNow questions

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

Do Freshservice tickets become ServiceNow incidents?

Yes. Each Freshservice incident becomes a record in the incident table with its subject, description, caller, assignment group, agent and state mapped to your values. The Freshservice display id is kept in a searchable field so agents can still find old references.

Will the original created and resolved dates be kept?

Yes. ServiceNow's opened_at, resolved_at and closed_at are normal fields, so we write the Freshservice dates straight into them. This is one place where moving into ServiceNow is easier than the reverse, because Freshservice does not allow backdating.

Will requesters get flooded with emails during the import?

No. We load through import sets with business rules turned off on the transform maps, and your admin pauses outbound email for the import window. A sample run confirms nothing is sent before the bulk pass starts.

What happens to private notes and public replies?

Private notes become work notes and public replies become additional comments, in their original order. Each entry keeps its original author and time, on the entry itself where your instance allows it or at the top of the entry text otherwise.

How is priority handled when ServiceNow calculates it?

ServiceNow derives incident priority from impact and urgency. We agree a pair for each Freshservice priority that gives the right result under your lookup rules, so Urgent tickets arrive as Critical and Low tickets as Low or Planning.

How are service requests migrated?

Each Freshservice service request becomes a ServiceNow request with one requested item per item. Items are linked to matching catalog items where they exist; the rest use a generic catalog item with the original name and answers kept on the record.

Can you move assets into the CMDB?

On request. We map Freshservice asset types to the cmdb_ci classes you choose and load the asset fields, then link incidents to the matching configuration item. Most teams also run ServiceNow discovery afterwards to fill in what Freshservice never tracked.

We use several Freshservice workspaces. Does that work?

Yes. We export each workspace separately and map it to the structure you pick in ServiceNow, usually a set of assignment groups or a category. HR or facilities workspaces can go to their own target tables on request.

Is there downtime during the migration?

No. Freshservice stays live during the bulk pass because we only read from it. At cutover we sync anything created or changed since, you switch intake to ServiceNow, and Freshservice becomes read-only.

How long does it take?

About ten business days for up to 100k records: two for preparation and mapping sign-off, five for transform maps, the sample run, bulk pass and delta, and three for validation. Large volumes add time mostly in the bulk pass, which is paced by both platforms' rate limits.

How it compares

Four ways to run Freshservice to ServiceNow

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 Freshservice 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 ServiceNow 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 Freshservice to ServiceNow migration

Related routes

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 ServiceNow move with 100 of your records.

Scope my migration

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