Freshdesk to Freshservice Migration: Keep Your IT Ticket History
Freshdesk to Freshservice migration: keep IT ticket threads, authors, private notes and files, with original dates in custom fields. Free 100-record test.
Published 6 min read

On this page
- What counts as ticket history in a Freshdesk to Freshservice migration?
- Why do migrated tickets show the import date in Freshservice?
- What fires in Freshservice while history loads?
- What should you check on the Freshservice sample?
- Freshdesk to Freshservice migration FAQ
- Move 100 IT tickets from Freshdesk first
A Freshdesk to Freshservice migration can keep IT ticket history. The full thread, each entry's author, private notes, attachments and the old ticket number all load through the Freshservice API. Freshservice documents no way to set the original created date, so original dates are kept in dedicated custom fields.
This guide is for IT managers moving the IT side of a Freshdesk account into Freshservice. How ticket types split into incidents and service requests, and how contacts become requesters, is on the Freshdesk to Freshservice migration page. Still choosing? Read Freshdesk vs Freshservice first.
What counts as ticket history in a Freshdesk to Freshservice migration?
Six things, and each reaches Freshservice a different way, and one of them, the created date, does not go into the built-in field at all.
Where each part of the history lands, with the vendor statement behind it:
| Part of the history | In Freshservice | What the vendor documentation says |
|---|---|---|
| The thread | Notes on the ticket, in order | Freshdesk replies and notes are read from each ticket's conversations endpoint |
| Who wrote each entry | The note's user_id | Freshservice: user_id is the "ID of the agent/user who is adding the note" |
| Private or public | The note's private flag | Freshservice: "The default value is true", so public replies must be set to public |
| Attachments | Files on the ticket and its notes | Freshservice: a ticket's attachments "cannot exceed 40 MB" in total |
| Original dates | Custom date fields | Freshservice documents no way to set the original created date |
| Old ticket number | A text custom field | Not a vendor feature. We store it so agents can search by it |
Why do migrated tickets show the import date in Freshservice?
Because Freshservice documents no way to set the original created date on a ticket or a note. Neither its API documentation nor its article on the Bulk Migration APIs describes one. A migrated ticket's built-in created date is therefore the day it was loaded.
The original dates are still kept, in fields you can report on:
- Three custom date fields on the Freshservice ticket form: original created, original resolved and original closed.
- A text field with the Freshdesk ticket number, so agents can search by the number a user quotes.
- The original author and time at the top of each note's body.
Build ticket-age and trend reports for migrated tickets on the custom date fields. Tickets raised in Freshservice after cutover use the built-in fields as normal.
What fires in Freshservice while history loads?
More than most teams expect, according to Freshservice's own migration articles. Left alone, a load of old tickets can email requesters and run today's workflows against tickets that closed years ago.
- Workflows and business rules keep running. Freshservice's Bulk APIs article says "workflows and other configured automations will continue to operate during the migration" and "currently, there is no option to disable these automations". It recommends muting them first, along with Slack and Teams.
- Notifications. The same article says some email notifications are suppressed during a bulk import. For migrations on the public API, Freshservice's partner article says "a large number of notifications and emails are triggered", and lists not sending them as a future enhancement.
So your Freshservice admin mutes workflows and notifications before the first ticket loads and switches them back on at cutover.
What should you check on the Freshservice sample?
Read the migrated tickets the way an agent would in six months.
- A long thread reads in the right order, start to finish.
- Each note names its original author and time.
- Private notes are private. Open the ticket in the portal as a requester and confirm.
- The original created, resolved and closed dates are in the custom fields, and a report can group by them.
- Searching the old Freshdesk ticket number finds the ticket.
- Every attachment opens.
- The ticket is in the right workspace, and no workflow or email fired.
For scale, AOM Infusion moved 28,000+ Freshdesk tickets to Freshservice with MigrateX in 5 weeks, from kickoff to handover. Read the AOM Infusion story. What else is in scope for each side is on the Freshdesk and Freshservice platform pages.
Facts checked November 15, 2026 from Freshservice: Service Desk API for Developers, Freshservice: How to migrate into Freshservice via Bulk APIs, Freshservice: Migration Process via Public APIs for Data Migration Partners, Freshdesk API and Freshdesk API rate limits. No vendor paid for this article. How we research
Freshdesk to Freshservice migration FAQ
Can a migrated note show the agent who wrote it?
Yes, where that agent exists in Freshservice. The Freshservice API lets a note be created with a user_id, described as the ID of the agent or user adding the note. For agents who are not moving, the original name is written at the top of the note, so the thread still reads correctly.
Will Freshdesk attachments fit in Freshservice?
Yes. Freshdesk caps the attachments on one ticket at 20 MB in total. Freshservice's limit is 40 MB across a ticket and all its notes, so a Freshdesk thread stays inside it. Each file is attached to the note it came from, not gathered at the top of the ticket.
Which Freshservice workspace do migrated tickets go into?
The primary workspace, unless one is named. Freshservice's API documentation says a ticket created without a workspace_id defaults to the primary workspace, and that the workspace "cannot be updated through the Update operation", only moved. If IT has its own workspace, name it before the sample.
Does Freshservice have a bulk import for ticket history?
Yes, for its data migration partners. Freshservice documents Bulk Migration APIs that take up to 50 tickets or notes per request, and its article still marks their rate limits as to be confirmed after load testing, as of November 2026. The standard API is limited per minute by plan and "on an account wide basis", so a live integration shares the allowance.
What if a ticket's requester is not in Freshservice yet?
Freshservice creates one. A ticket created with an email address that matches no existing contact adds a new contact for that email. To avoid half-empty requester records, people are loaded before tickets, with their names, departments and other details, so each ticket attaches to a complete requester.
Move 100 IT tickets from Freshdesk first
MigrateX is an AI migration platform with ITSM engineers checking every mapping, and it is SOC 2 Type II, GDPR and HIPAA compliant. Send us your IT ticket count and how you tell IT tickets from customer tickets. You get 100 of them in Freshservice, free, and a fixed quote within 24 hours. Book a scoping call. Leaving Freshservice later is covered in Freshservice to HaloITSM: tickets, assets and SLAs.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


