The short answer
| In Freshdesk | In Zendesk | How it is handled |
|---|---|---|
| Ticket | Ticket | Imported with its original created, updated and solved dates |
| Reply or public note | Public comment | Original time and author kept |
| Private note | Private comment | Never shown to the requester |
| Requester | Requester (end user) | Matched on email or external ID |
| CC addresses | CCs | Turn on CCs and followers first |
| Agent and group | Agent and group | Mapped one by one |
| Status | Status or custom status | Custom statuses included |
| Priority | Priority | Medium usually to Normal |
| Type | Type, or a drop-down field | Zendesk has four fixed types |
| Tags | Ticket tags | Written on each ticket |
| Ticket fields | Ticket fields | Field by field, values one by one |
| Contact and company fields | User and organisation fields | Field by field |
This page is for the admin who plans the mapping. For what moves overall, and what you set up again in Zendesk, see Freshdesk to Zendesk migration. For what to switch off before the first run, see the helpdesk migration checklist for a Freshdesk to Zendesk move.
Before you map: what must exist in Zendesk
- Agents and groups. A ticket can only be assigned to an agent and group that already exist in Zendesk. Add them first, then map each Freshdesk agent and group, and send people who have left to one active agent.
- Fields. Missing ticket, user and organisation fields can be created from the mapping screen before any run.
- Values and custom statuses. A value map can only choose values that already exist in Zendesk, so add the drop-down values and custom statuses you want to keep first.
- Help centre languages. A translation in a language your help centre lacks is skipped, so add each language first.
The mapping locks for the whole migration once a run completes, a completed Sample included. A failed or cancelled Sample locks nothing, and to change a locked mapping you clone the migration.
Freshdesk ticket fields and where they land
| Freshdesk ticket field | In Zendesk | Good to know |
|---|---|---|
| Requester | Requester | Matched on email or external ID, or created first. |
| CC addresses | CCs | With CCs and followers off, Zendesk silently drops them, so turn the setting on first. |
| Agent | Assignee | The agent you mapped. Anyone missing falls back to a default you choose. |
| Group | Group | The group you mapped. |
| Status | Status or custom status | You map every value; see below. |
| Priority | Priority | Value by value; see below. |
| Type | Type, or a drop-down field | Zendesk’s Type has four fixed values; see below. |
| Tags | Ticket tags | |
| Created date | Created date | Kept by the ticket import, together with the updated and solved dates. |
| Replies, notes and their times | Comments | Each keeps its own time, author and public or private flag, all in one import that runs no triggers. |
| Attachments | Files on the same comment | A type Zendesk does not allow is still kept, renamed to .txt or wrapped in a .zip. |
| Inline images | Inline images | Freshdesk image links expire within minutes, so each image is copied and placed back where the author put it. |
| Due by and first response due | Not carried | SLA due dates are not carried, and Zendesk does not apply SLAs to imported tickets. |
Custom fields, type by type
Every field you map lands in a Zendesk field, and every value inside a dropdown is mapped in writing to a Zendesk value, with a fallback you choose. A value with no match and no fallback is left off and named as a Setup gap, never swapped for a guess.
| Freshdesk field type | Zendesk field | Good to know |
|---|---|---|
| Single-line text | Text | |
| Multi-line text | Multi-line text | |
| Checkbox | Checkbox | |
| Number and decimal | Number and decimal | |
| Date | Date | |
| Dropdown | Drop-down | Each value is mapped to a Zendesk value one by one, with a fallback you choose. |
Statuses, priorities and Type, value by value
Statuses decide whether each ticket arrives open, pending or solved. Zendesk refuses every change to a closed ticket, so if a later Delta brings new messages for one, they are imported on a follow-up ticket linked to the original. Zendesk also closes solved tickets on its own after a while. A sensible starting point:
| Freshdesk | Zendesk |
|---|---|
| Status: Open | Open |
| Status: Pending | Pending |
| Status: Resolved | Solved |
| Status: Closed | Closed, or Solved |
| Custom statuses | Custom statuses you create in Zendesk first |
| Priority: Low, Medium, High, Urgent | Low, Normal, High, Urgent |
| Type: each of your values | Question, Incident, Problem or Task, or a drop-down field of your own |
Contacts and companies
- Matching. Contacts become end users, matched on email or external ID, never on name or phone.
- Already an agent? A contact who matches a Zendesk agent or admin is linked to that user and nothing is written to their profile. The record says so.
- No welcome email. DataGrine tells Zendesk to skip the verification email for every user it creates.
- More than one company. If your contacts belong to more than one company, turn on Allow users to belong to multiple organizations first. It is not available on the Team plan.
- Companies become organisations, each with an External ID made from the source, so a later run finds it. A different organisation with the same name is added with ‘(migrated ...)’ after its name.
Solutions articles in Guide
- Sections. A Guide article can live only in a section, and each Freshdesk article is placed in one.
- Languages. Translations travel for the languages your help centre has.
- Subscribers. Articles are created with subscriber emails switched off.
- Who can see an article is never migrated. Set user segments again in Guide.
What cannot map, and the honest workaround
Nothing here disappears silently. Each of these is named on its record and counted in the Reconciliation report, as a Vendor limit, a Setup gap or Not carried.
| In Freshdesk | Why it has no place | The workaround |
|---|---|---|
| Type values beyond four | Zendesk’s Type has four fixed values | A drop-down field for the rest |
| SLA due dates and reporting history | Zendesk does not calculate SLAs or metrics for imported tickets | Filter Explore reports to leave out your migration tag |
| Satisfaction ratings | Not read from Freshdesk | Keep the Freshdesk report |
| Time entries | Not read from Freshdesk | Keep a copy before you close Freshdesk |
| Archived tickets | They are not migrated | Export the Archive view |
| Spam and Trash | Freshdesk’s API leaves them out | Restore what you want before the Full migration |
| Automation rules, canned responses and SLA policies | Settings, not records | Set them up again as triggers, automations, macros and SLA policies |
Check the mapping on a free Sample
The Sample is free: 20, 100, 500 or 1,000 of your own tickets (100 by default), with the contacts and companies they use. Sample records are real records in Zendesk, and the Full migration recognises them instead of creating them twice. Open them in Zendesk and check:
- Each ticket shows its original created date, and each comment the right author and time.
- Each ticket has the status, priority and Type your map says.
- Private notes are private comments, and people copied on tickets are CCs.
- Contacts belong to the right organisation, and nobody arrived twice.
- Nobody received an email.
Then start the Reconciliation report for the run: it compares Freshdesk and Zendesk line by line and names every record that did not arrive as it was, with the reason. When the mapping is right, run the Full migration from the Freshdesk to Zendesk migration page.
Next step
Check a Sample migration of your own records in the new helpdesk before anything else moves, then run the full migration and a delta at cut-over.
Sources
- Zendesk Developers - Ticket Import
- Zendesk Developers - Tickets
- Freshdesk API reference
- Freshdesk Support - Ticket archiving
Vendor facts checked against these pages on . Vendors change their products; if something here has moved, tell us and we will correct it.