FreshdeskFreshservice

Freshdesk to Freshservice migration

ITSM specialists move your tickets and articles 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 October 2026 · 7 object types mapped

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

Freshdesk to Freshservice at a glance

We move IT tickets, conversations, contacts, companies, agents and the knowledge base from Freshdesk into Freshservice, splitting tickets into incidents and service requests during the move. An engineer agrees the type, department and field mapping with you, imports in dependency order, and reconciles counts on both sides before you cut over. Customer support can stay on Freshdesk.

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

What moves

What moves from Freshdesk to Freshservice

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

  • 8 included
FreshdeskFreshservice

Tickets

  • AgentsAgents

    Order 1

  • CompaniesDepartments

    Order 2 · after Agents

  • ContactsRequesters

    Order 3 · after Agents, Companies

  • TicketsTickets

    Order 4 · after Agents, Contacts, Companies

  • AttachmentsAttachments

    Uploaded to the matching note. Files that would push a ticket past the 40 MB cap are re-hosted and linked.

Knowledge Base

  • CategoriesCategories

    Order 7

  • FoldersFolders

    Order 8 · after Categories

  • ArticlesArticles

    Order 9 · after Folders

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

Freshdesk to Freshservice migration timeline

Estimated total

About 8 business days

for up to 100k tickets

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

    Day 1-2

    • Access and scope

      You0.5 day

      You share a Freshdesk admin API key and a Freshservice API key. We agree which groups, companies, date ranges and solution categories move, and which stay on Freshdesk.

    • Schema and volume export

      MigrateX0.5 day

      We pull ticket counts by type, status and group, custom fields, agents, companies, folder depth and attachment sizes from Freshdesk.

    • Mapping sign-off

      Both1 day

      We send the mapping sheet: Type to incident or service request, companies to departments, custom statuses, fields and agents. You approve or amend it.

  2. Migration

    Day 3-6

    • People and structure

      MigrateX0.5 day

      Departments, requesters, agents and groups are created in Freshservice, plus custom fields for the Freshdesk ticket id and original dates.

    • Sample run

      Both1 day

      A few hundred tickets of every type with notes and attachments, plus a handful of articles, so you can check the result before the bulk pass.

    • Bulk pass

      MigrateX1-2 days

      Tickets, notes and attachments in date windows paced to both plan limits, checkpointed by ticket id. Solution categories, folders and articles follow.

    • Delta and cutover

      Both0.5 day

      Tickets created or updated in Freshdesk since the bulk pass are synced. You point IT intake at Freshservice; the IT side of Freshdesk becomes read-only.

  3. Validation

    Day 7-8

    • Reconciliation report

      MigrateX0.5 day

      Counts per object, type, status and group on both sides, plus every record that needed a default mapping or re-hosted attachment.

    • Spot checks

      You1 day

      Your IT leads open a random sample of migrated tickets and articles and confirm notes, attachments, requesters and types are right.

    • Fixes and sign-off

      Both0.5 day

      We correct anything the spot checks raise, re-run the affected batch, and hand over the 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

  • 1 handled
  1. 01Handled

    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. Migrated tickets show the import date, which breaks age reports and SLA history for anything that moved.

    How we handle it

    We create date custom fields for original created, resolved and closed dates and keep the Freshdesk ticket id in a text field. Resolved and closed tickets are imported in their final state so no SLA timer starts on them.

    Source: Freshservice API documentation, checked 15 Nov 2026

Technical profile

What makes this route technical

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

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

Source: Freshservice API documentation, checked 15 Nov 2026

Freshservice API rate limit
100 requests per minute on Starter, 200 on Growth, 400 on Pro and 500 on Enterprise, with a separate sub-limit for ticket creates. HTTP 429 comes back with a Retry-After header.

Source: Freshservice API documentation, checked 15 Nov 2026

Freshservice ticket types
The Freshservice create-ticket API accepts only the Incident type. Service requests are raised through a separate service catalog call, so every Freshdesk ticket has to be assigned to one side before import.

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. Original Freshdesk created, resolved and closed dates are kept in dedicated custom fields instead.

Source: Freshservice API documentation, checked 15 Nov 2026

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

Freshdesk to Freshservice questions

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

What is the difference between Freshdesk and Freshservice?

Both are Freshworks products. Freshdesk is a help desk for customer support, with one ticket object and a free-text Type label. Freshservice is an IT service management platform, with incidents and service requests as different records, plus problems, changes, releases, assets and a service catalog. Choose Freshdesk when customers raise tickets, and Freshservice when employees do.

Can I keep both?

Yes, and many teams do. Customer support stays on Freshdesk and only IT moves to Freshservice. We scope the migration by group, company or email domain so only IT tickets, requesters and articles move, and the support side of Freshdesk is left untouched. Freshworks' own integration can link the two for new tickets, but it does not move history.

Does Freshworks migrate Freshdesk tickets to Freshservice for me?

Not typically. Both products share a vendor but not a data model, and there is no built-in importer that moves historical Freshdesk tickets, conversations and articles into Freshservice. The move runs through both APIs, which is the work we do.

How do Freshdesk ticket types become incidents and service requests?

We list every Type value with its ticket count and agree a rule for each one with you. Break-fix types become incidents, request types become service requests, and empty or unclear types go to a default you choose. The original Type is kept in a custom field so nothing is lost.

What happens to contacts and companies?

In-scope contacts become requesters and in-scope companies become departments. External customers who never raised an IT ticket are left out so your requester list stays clean. Contacts linked to several companies get the matching departments.

Are private notes kept private?

Yes. Freshdesk private notes become private notes in Freshservice. Public replies and customer messages become public notes. Each note carries the original author and time at the top, because Freshservice sets its own creation time on import.

What does not move?

Automations, scenario automations, SLA policies, business hours and portal branding are rebuilt in Freshservice rather than migrated. Satisfaction ratings and canned responses have no direct home; we can keep ratings as notes or fields and export canned responses for you to review. We hand over a list of everything rebuilt.

Will the original ticket dates be preserved?

Not in the built-in timestamp fields, because Freshservice does not document a way to set the original created date. We store original created, resolved and closed dates in custom fields, and keep the Freshdesk ticket id so agents can still search by it.

Is there downtime?

No. Freshdesk stays live during the bulk pass because we only read from it. At cutover we sync anything created or changed since, you point IT intake at Freshservice, and the IT side of Freshdesk becomes read-only.

How long does it take?

About eight business days for up to 100k tickets: two for scoping and mapping, four for the sample run, bulk pass and delta, and two for validation. The bulk pass is paced by the Freshdesk ticket list limit and the Freshservice plan limit, so larger accounts mostly add time there.

How it compares

Four ways to run Freshdesk 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 Freshdesk 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 Freshdesk 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.