How to Migrate from Freshdesk to Zendesk
The objects line up almost exactly. What does not is the automation layer: Freshdesk's Dispatch'r, Supervisor and Observer rules all collapse into Zendesk triggers and automations, and the collapse is not mechanical.
- Difficulty
- Moderate
- Typical duration
- 3–6 weeks
- Downtime
- None — run both inboxes in parallel, then switch mail routing
- Native importer
- Partial — Zendesk API, or a third-party migration tool
| Freshdesk | maps to | Zendesk | What to watch |
|---|---|---|---|
| Ticket | Ticket | Direct. Map statuses explicitly — Freshdesk's Resolved/Closed pair does not align exactly with Zendesk's Solved/Closed semantics. | |
| Contact | End user | Clean on email. Zendesk supports multiple identities per user, which is a small upgrade over Freshdesk's primary-plus-secondary model. | |
| Company | Organization | Direct, and Zendesk organizations do more — they can drive routing, SLA policies and shared ticket visibility. | |
| Group | Group | Same concept. Create before importing tickets so assignment resolves. | |
| Dispatch'r | Trigger (on create) | Freshdesk's creation-time rules become Zendesk triggers scoped to ticket creation. | |
| Observer | Trigger (on update) | Update-time rules also become triggers. Two Freshdesk rule types merging into one Zendesk type means conditions must be tightened or rules will over-fire. | |
| Supervisor | Automation | Time-based rules. Zendesk automations run hourly; verify anything with tight SLA timing behaves the same. | |
| Solution article | Guide article | Separate import. Freshdesk's category/folder structure maps to Zendesk's category/section hierarchy. |
What transfers cleanly
- Tickets with their full public and private conversation threads.
- Contacts and companies with custom fields, once matching Zendesk fields exist.
- Ticket custom field values, where fields are pre-created with matching option sets.
- Attachments on tickets and replies.
- Agent assignment, where Freshdesk agents have Zendesk seats with matching emails.
What doesn't come across
- Business rules. Freshdesk's three rule types collapse into Zendesk's two. This is a redesign — merged rules that keep their original conditions will fire more often than intended.
- Freshdesk Analytics. Rebuild in Zendesk Explore, which is more capable but structured differently.
- Scenario automations. Zendesk macros can set fields, so these map reasonably — but they need rebuilding by hand.
- Freshdesk apps and integrations. Check each has a Zendesk marketplace equivalent before committing.
- Freshcaller recordings. Call audio stays in Freshworks. Export what you must retain before cancelling.
- Ticket forms and dynamic sections. Zendesk has ticket forms with conditional fields, but the configuration model differs enough to require rebuilding.
Migration order that works
- Inventory every Dispatch'r, Observer, Supervisor, scenario automation and canned response, and mark which still fire.
- Classify each rule by when it should run — Zendesk needs that distinction expressed in trigger conditions, not rule type.
- Create Zendesk groups, agents, organizations, custom fields, ticket forms and SLA policies before importing.
- Map Freshdesk statuses to Zendesk statuses explicitly, particularly Resolved versus Solved.
- Import organizations and end users first, then tickets with their threads, then attachments.
- Import Solutions articles into Guide as a separate pass, with a redirect map from old URLs.
- Run both systems in parallel with mail routing still on Freshdesk, then switch once rules are verified.
Teams move from Freshdesk to Zendesk when they need more: more granular routing, organization-level SLA policies, a bigger app ecosystem, or reporting that Freshdesk Analytics cannot reach. The object mapping is almost boringly direct, which is good, because the automation layer is where the attention needs to go.
Three rule types become two
Freshdesk separates business rules by when they run. Dispatch'r fires at ticket creation, Observer fires on update, Supervisor runs on a schedule.
Zendesk has two: triggers, which handle both creation and update, and automations, which are time-based.
That merge is the trap. Take a Dispatch'r rule, rebuild it as a Zendesk trigger with the same conditions, and it will now also fire every time the ticket is updated — because nothing in the conditions says "only on creation". Auto-assignment rules that ran once now reassign continuously. Notification rules that greeted a customer once now greet them on every reply.
The fix is straightforward once you know: add explicit conditions constraining when each trigger applies. But it has to be done deliberately for every migrated rule, and it needs testing on real tickets before mail routing switches.
Organizations are an upgrade worth using
Freshdesk companies are essentially a grouping label. Zendesk organizations do considerably more — they can drive routing, carry their own SLA policies, and let colleagues at the same company see each other's tickets.
Do not just import companies and move on. This is a chance to build account-level support behaviour you could not previously have, particularly if you support businesses rather than consumers.
Check the timing on SLA rules
Freshdesk Supervisors and Zendesk automations both run on a schedule rather than instantly, but not the same schedule. Anything tied to a contractual SLA — escalate at four hours, breach warning at eight — needs verifying against real tickets rather than assumed equivalent.
This is the kind of difference that goes unnoticed for a month and then surfaces in a customer escalation.
Audit before you rebuild
Support instances accumulate rules. Pull the full list with last-fired dates and rebuild only what is live. In a Freshdesk account more than two years old, the dormant share is usually substantial, and every dormant rule you decline to migrate is time saved twice — once in the rebuild, once in the testing.
Redirect the help centre
Solutions articles import into Guide fine, but the URLs change. Established help centres earn meaningful search traffic. Map old URLs to new before switching DNS.