
ZendeskFreshdesk
Zendesk to Freshdesk migration
Migration specialists move your organizations, tickets and sections into Freshdesk, 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
Zendesk to Freshdesk at a glance
We move your Zendesk history into Freshdesk: tickets with every public reply and internal note, attachments, users, organizations, custom fields and Help Center articles. Zendesk's own export leaves comments out of CSV and stops at 200,000 tickets in XML, so we read everything through the API and pace the load to your Freshdesk plan's limits. Your team keeps working in Zendesk 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 Zendesk to Freshdesk
Every object our connector moves, in the order it is written into Freshdesk.
- 7 included
| Zendesk | maps to | Freshdesk | Status | Order | Migrated after |
|---|---|---|---|---|---|
| Tickets4 | |||||
| Agents | Agents | Included | 1 | - | |
| Organizations | Companies | Included | 2 | Agents | |
| End Users | Contacts | Included | 3 | Agents, Organizations | |
| Tickets | Tickets | Included | 4 | Agents, End Users, Organizations | |
| Knowledge Base3 | |||||
| Categories | Categories | Included | 5 | - | |
| Sections | Folders | Included | 6 | Categories | |
| Articles | Articles | Included | 7 | Sections | |
Tickets
- AgentsAgents
Order 1
- OrganizationsCompanies
Order 2 · after Agents
- End UsersContacts
Order 3 · after Agents, Organizations
- TicketsTickets
Order 4 · after Agents, End Users, Organizations
Knowledge Base
- CategoriesCategories
Order 5
- SectionsFolders
Order 6 · after Categories
- ArticlesArticles
Order 7 · after Sections
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
Zendesk to Freshdesk 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
- 01HandledMost critical
Zendesk threads can outgrow Freshdesk's 20 MB per ticket
The problem
Freshdesk caps all attachments on a ticket at 20 MB in total. A long Zendesk thread with screenshots and logs can carry more than that.
How we handle it
We size every attachment during export. Files that would push a ticket over the cap are stored in your own storage and linked from the note where they sat.
Source: Freshdesk API documentation, checked 13 Nov 2026
- 02Handled
Side conversations have no Freshdesk home
The problem
Side conversations need Zendesk's Collaboration add-on, and their messages are stored as events on the side conversation, not as ticket comments. A comments-only export misses them.
How we handle it
We read each side conversation with its events and post it as a private note on the Freshdesk ticket, with the participants and times kept.
Source: Zendesk developer documentation, checked 13 Nov 2026
- 03Solved
Freshdesk contacts must have a unique email
The problem
A Freshdesk contact's email is unique, and creating a ticket with an unknown email creates a new contact on the fly. Zendesk users with shared or changed emails can split or merge by accident.
How we handle it
We create companies and contacts first, match them by email, and only then load tickets, so every ticket points at the right requester.
Source: Freshdesk API documentation, checked 13 Nov 2026
Technical profile
What makes this route technical
The API limits and data model differences between Zendesk and Freshdesk that shape the plan.
- Exporting from Zendesk: rate limits by plan
- Support API calls per minute: 200 on Suite Team, 400 on Growth and Professional, 700 on Enterprise, 2,500 on Enterprise Plus or with the High Volume API add-on.
Source: Zendesk developer documentation, checked 13 Nov 2026
- Exporting from Zendesk: incremental exports
- The incremental export API allows 10 calls a minute (30 with the High Volume API add-on) and returns up to 1,000 items per page. The ticket export does not carry comments, so we read them per ticket.
Source: Zendesk developer documentation, checked 13 Nov 2026
- Exporting from Zendesk: offset paging stops at 10,000
- Offset pagination is limited to the first 100 pages and 10,000 records. Full exports use cursor pagination.
Source: Zendesk developer documentation, checked 13 Nov 2026
- Why the Zendesk native export is not enough
- Data exports are off by default and not available on Team plans. CSV exports leave out ticket comments, and full XML exports are not available above 200,000 tickets.
Source: Zendesk Help Center, checked 13 Nov 2026
- Importing into Freshdesk: rate limits by plan
- 100 calls a minute on Growth, 400 on Pro and 700 on Enterprise, with ticket creation capped lower (50, 160 and 280 a minute). The limit applies to the whole account.
Source: Freshdesk support documentation, checked 13 Nov 2026
- Importing into Freshdesk: 20 MB per ticket
- All attachments on one Freshdesk ticket together cannot exceed 20 MB. Zendesk allows up to 50 MB per file, so large threads need planning.
Source: Freshdesk API documentation, checked 13 Nov 2026
Facts checked 13 Nov 2026 against Zendesk and Freshdesk documentation. Each fact links its source.
Testimonials
What our customers say
“We kept losing deals because customers were scared of the migration. Now I just loop in MigrateX early and it stops being a blocker. Three clients closed last quarter that definitely would've stalled.”

Lorraine Lee
Regional Sales Director, HAND Global Solutions
“We'd been on Zendesk for years and the thought of moving everything over was honestly terrifying. 40,000+ tickets, all our custom fields, attachments. I kept expecting something to break. Nothing did.”

Subash Sebastian
Associate Director of Reservations, One&Only Resorts
Zendesk to Freshdesk questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
What moves from Zendesk to Freshdesk?
Tickets, agents, contacts, companies, attachments, private and public notes, custom fields on tickets, organizations and contacts, CCs, timestamps, tags, and Help Center articles with their categories and sections, which become Freshdesk categories and folders.
How long does a Zendesk to Freshdesk migration take?
It depends on how much data you have. Zendesk's export limits set the pace: 10 incremental export calls a minute, and up to 700 API calls a minute on Enterprise. After the free 100-record sample, you get a timeline with dates in your fixed quote within 24 hours.
Can we use Zendesk's own data export instead?
Only for a partial copy. Zendesk exports are off by default and not on Team plans, CSV leaves out comments, and full XML exports stop at 200,000 tickets. We export through the API so every comment and attachment comes across.
What happens to side conversations and call recordings?
Side conversations come over as private notes on the Freshdesk ticket. Call recordings transfer as attachments, within Freshdesk's 20 MB per ticket cap; larger files are linked from your own storage.
Is there downtime while we move off Zendesk?
No. Zendesk stays fully operational the whole time. We use delta sync to pick up anything that changes while the migration runs, so nothing falls through the cracks.
Can we migrate just a subset of our Zendesk data?
Yes, we can filter by date range, ticket status, tags, or whatever criteria make sense. You don't have to move everything if you don't want to.
How do you handle security?
Everything is encrypted in transit and at rest, under our SOC 2 Type II controls. Each migration runs in its own isolated environment with scoped API credentials. We can share our full security documentation with your infosec team before you start.
What does a Zendesk to Freshdesk migration cost?
Pricing is per record and depends on what moves. After the scoping call and the free 100-record sample, you get a fixed quote within 24 hours.
How it compares
Four ways to run Zendesk to Freshdesk
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 Zendesk 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 Freshdesk 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 Zendesk to Freshdesk 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 Freshdesk move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.


