
FreshdeskZendesk
Freshdesk to Zendesk migration
Migration specialists move your tickets and articles into Zendesk, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 7 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Freshdesk to Zendesk at a glance
We move your Freshdesk history into Zendesk: tickets with every reply and note, attachments, contacts, companies, custom fields and knowledge base articles. Freshdesk's ticket list only returns the last 30 days by default, so we page through your full history by date, then load it through Zendesk's Ticket Import API, which keeps the original created, updated and solved dates. Your team keeps working in Freshdesk until cutover.
- Objects mapped
- 7
- from the live connector
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
What moves
What moves from Freshdesk to Zendesk
Every object our connector moves, in the order it is written into Zendesk.
- 7 included
| Freshdesk | maps to | Zendesk | Status | Order | Migrated after |
|---|---|---|---|---|---|
| Tickets4 | |||||
| Agents | Agents | Included | 1 | - | |
| Companies | Organizations | Included | 2 | Agents | |
| Contacts | End Users | Included | 3 | Agents, Companies | |
| Tickets | Tickets | Included | 4 | Agents, Contacts, Companies | |
| Knowledge Base3 | |||||
| Categories | Categories | Included | 5 | - | |
| Folders | Sections | Included | 6 | Categories | |
| Articles | Articles | Included | 7 | Folders | |
Tickets
- AgentsAgents
Order 1
- CompaniesOrganizations
Order 2 · after Agents
- ContactsEnd Users
Order 3 · after Agents, Companies
- TicketsTickets
Order 4 · after Agents, Contacts, Companies
Knowledge Base
- CategoriesCategories
Order 5
- FoldersSections
Order 6 · after Categories
- ArticlesArticles
Order 7 · 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 migrationTimeline
Freshdesk to Zendesk migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayA 30 minute call with the engineer who will run the migration, to agree the objects, date ranges and volumes in scope.
Connect both platforms
You0.5 dayYou create scoped API credentials on the source and the destination. Nothing is written until you sign off the mapping.
Field mapping review
Both1 dayWe walk through every field, status and group mapping with your team and note the ones that need a decision.
Migration
Day 3-7
Free sample migration of 100 records
MigrateX1 dayA sample of your real records is migrated end to end so you can see the result before the full run.
You review the sample
You1 dayYour team opens the migrated records and tells us what to adjust. We rerun the sample until it is right.
Full migration
MigrateX2-3 daysThe bulk pass runs in dependency order, paced to the destination rate limit. Your team keeps working normally.
Delta sync
MigrateX0.5 dayEverything created or changed during the bulk pass is synced at cutover so nothing falls between the two systems.
Validation
Day 8-10
Validation report
MigrateX1 dayRecord counts per object and per status on both sides, plus every record that needed a default or a placeholder.
Spot checks and sign-off
You1-2 daysYour leads check a random sample and sign off. We stay available for two weeks after go-live.
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 solved
- 2 handled
- 01SolvedMost critical
Older Freshdesk tickets are not in the default list
The problem
Freshdesk's list endpoint returns only the last 30 days by default and stops at 30,000 tickets. A simple export quietly leaves years of history behind.
How we handle it
We page through history in date windows with updated_since, then reconcile ticket counts against Freshdesk before anything is imported.
Source: Freshdesk API documentation, checked 13 Nov 2026
- 02Handled
Imported tickets skip Zendesk triggers and SLAs
The problem
Through the Ticket Import API, triggers do not run on imported tickets that are not closed, no CC notifications go out, and metrics and SLAs are not supported.
How we handle it
Closed history goes through the Ticket Import API with its original dates and no notifications. Open tickets are agreed with you at mapping sign-off, so your SLA policies apply where you want them.
Source: Zendesk developer documentation, checked 13 Nov 2026
- 03Handled
Help Center will not keep original article dates
The problem
Zendesk sets created_at and updated_at on Help Center articles itself, and each article needs a permission group and a user segment.
How we handle it
We map Freshdesk categories and folders to Help Center categories and sections, set the permission group and segment you choose, and record each article's original dates in the migration report.
Source: Zendesk developer documentation, checked 13 Nov 2026
Technical profile
What makes this route technical
The API limits and data model differences between Freshdesk and Zendesk that shape the plan.
- Exporting from Freshdesk: lists look back 30 days
- Listing tickets returns only tickets created in the past 30 days by default, and at most 300 pages (30,000 tickets). Older history needs the updated_since filter.
Source: Freshdesk API documentation, checked 13 Nov 2026
- Exporting from Freshdesk: rate limits by plan
- 100 calls a minute on Growth, 400 on Pro and 700 on Enterprise. Listing tickets has its own lower limit: 40, 100 and 200 a minute.
Source: Freshdesk support documentation, checked 13 Nov 2026
- Why the Freshdesk ticket export is not enough
- The ticket export from the list view leaves out full conversations and archived tickets. Those come from the account export or the API.
Source: Freshdesk support documentation, checked 13 Nov 2026
- Importing into Zendesk: original dates kept
- The Ticket Import API can set created_at, updated_at and solved_at, and takes up to 100 tickets per bulk call. Metrics and SLAs are not supported on imported tickets.
Source: Zendesk developer documentation, checked 13 Nov 2026
- Importing into Zendesk: 50 MB per file
- Each attachment upload can be up to 50 MB.
Source: Zendesk developer documentation, checked 13 Nov 2026
- Importing into Zendesk: Help Center article dates
- created_at and updated_at on Help Center articles are read-only, and every article needs a permission group and a user segment.
Source: Zendesk developer documentation, checked 13 Nov 2026
Facts checked 13 Nov 2026 against Freshdesk and Zendesk documentation. Each fact links its source.
Freshdesk to Zendesk questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
Will old Freshdesk tickets be missed?
Not with us. Freshdesk's ticket list only returns the last 30 days by default and stops at 30,000 tickets, so we page through your full history by date and reconcile the counts before import.
Do our original ticket dates survive in Zendesk?
Yes. Zendesk's Ticket Import API lets us set created_at, updated_at and solved_at, so ticket history keeps its real dates. Help Center articles are the exception: Zendesk sets their dates itself, so we record the originals in the migration report.
What happens to our Freshdesk automations and canned responses?
Canned responses become Zendesk macros. For automation rules, we document each one and map it to the right Zendesk trigger or automation. We review the mapping with you before we run it.
Which Freshdesk data lands in Zendesk?
Tickets, agents, contacts, companies, attachments, private and public notes, custom fields on tickets, companies and contacts, CCs, timestamps, tags, and knowledge base articles with their categories and folders, which become Help Center categories and sections.
How long does a Freshdesk to Zendesk migration take?
It depends on data volume. Freshdesk's API limits set the pace of the export: listing tickets is capped at 40 to 200 calls a minute by plan. The free 100-record sample comes first, then a fixed quote within 24 hours that sets out the timeline with dates.
Does Freshdesk stay live during the move?
Yes. Freshdesk stays live the entire time. Delta sync catches anything that changes during the migration, so changes made during the migration come across too.
Can we move only part of our Freshdesk history?
Yes. Filter by date range, ticket status, tags, whatever makes sense. You're in control of what moves and what stays.
How secure is the migration?
Encrypted in transit and at rest, under our SOC 2 Type II controls. Each migration runs in an isolated environment with scoped credentials. Happy to share our security docs with your infosec team before you start.
What does a Freshdesk to Zendesk migration cost?
We price per record, based on what moves from Freshdesk. Once the scoping call and the free 100-record sample are done, your fixed quote arrives within 24 hours.
How it compares
Four ways to run Freshdesk to Zendesk
The same data, moved four different ways. This is what changes between them.
Object coverage (cases, emails, comments, files, Knowledge)
MigrateX
Every object in the Freshdesk connector, plus the ones you ask for during scoping.
Automated migration software
Tickets and contacts are covered. Linked records, files and knowledge 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.
Public replies vs internal notes
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 Zendesk 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 Zendesk migration
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
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 Zendesk move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.

