The short answer
| In Zendesk | In Freshdesk | How it is handled |
|---|---|---|
| Ticket | Ticket | Original date kept in a text field such as ‘created at zendesk’ |
| Archived ticket (closed over 120 days) | Ticket | Carried like any other closed ticket |
| Public comment by an agent | Public note | Opens with its original time in UTC and author |
| Public comment by an end user | Note from that customer | Shown as the customer’s own message |
| Private comment | Private note | Never shown to the customer |
| Requester and CCs | Requester and CC addresses | Matched on email or external ID |
| Assignee and group | Agent and group | Agents must exist; groups can be created |
| Status | Status | Custom statuses included |
| Priority | Priority | Normal usually to Medium |
| Type | Type | Add the values first |
| Tags | Tags | Up to 32 characters, no comma |
| Custom ticket fields | Ticket fields | Field by field, values one by one |
| User and organisation fields | Contact and company 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 Freshdesk, see Zendesk to Freshdesk migration. For what to switch off in Freshdesk before the first run, see Freshdesk migration without emailing customers.
Where the original dates go
Freshdesk does not accept a creation date through its API, so its own Created date on a migrated ticket is the migration day. The original date is kept in a ticket text field named after the source, such as ‘created at zendesk’, which ‘Create all missing fields’ in Field Mapping adds. Without that field, it is written on the description’s first line. Solved and closed times become the time the status is written, so build historical reports on the original-date field.
How each comment is written
Freshdesk’s reply action emails the requester and everyone in CC, so DataGrine never uses it. Each Zendesk comment is written as a note under its author instead:
- Agent public comments become public notes from the agent you mapped.
- End-user comments become notes from that customer.
- Private comments become private notes.
- Each note opens with two lines: its original time in UTC and author, then the Cc addresses Zendesk recorded on an email comment. Bcc is never written on a note your customer can see.
A public note can still make Freshdesk email the requester ‘Ticket Updated’ while that notification is on, so switch the requester and CC notifications off before the Sample.
Zendesk ticket fields and where they land
| Zendesk ticket field | In Freshdesk | Good to know |
|---|---|---|
| Requester | Requester | Matched on email or external ID, or created first. |
| CCs | CC addresses | Freshdesk records CC only as email addresses, so a participant with none is named as a Vendor limit. |
| Assignee | Agent | Agents must exist in Freshdesk, with the same email address. Anyone missing goes to the default agent you choose, with the original name on each note. |
| Group | Group | Groups Freshdesk lacks can be created with their members. |
| Status | Status | Each Zendesk status, custom ones included, maps to a Freshdesk status; see below. |
| Priority | Priority | Value by value; see below. |
| Type | Type | Add each value to Freshdesk first, with the same spelling. |
| Tags | Tags | Freshdesk allows 32 characters and no comma, so a longer tag is shortened and named, not dropped. |
| Created date | A text field such as ‘created at zendesk’ | Freshdesk’s own Created date is the migration day. |
| Attachments | Attachments | On the ticket and each note, up to 20 MB per message. Private attachments are fetched through your connection. |
| Inline images | Inline images | Placed where the author put them. Freshdesk also lists them under attachments; it is one file. |
| Satisfaction rating | Not carried | Ratings are not read from Zendesk. |
Custom fields, type by type
Freshdesk refuses a whole record over one value that is not on a field’s choice list, so DataGrine checks each value against your lists first, leaves out one that does not fit and reports it. Missing ticket, contact and company fields can be created from the mapping screen before any run.
| Zendesk field type | Freshdesk field | Good to know |
|---|---|---|
| Text, and regular expression | Single-line text | Freshdesk text fields hold 255 characters. The pattern check stays in Zendesk. |
| Multi-line text | Multi-line text | |
| Checkbox | Checkbox | |
| Date | Date | |
| Number and decimal | Number and decimal | |
| Drop-down | Dropdown | Each value is mapped to a Freshdesk value one by one, with a fallback you choose. |
| Multi-select and lookup | No direct match | Freshdesk’s API lists no multi-select or lookup field type. Plan a text field and check how it reads on a Sample. |
| Credit card | Leave unmapped | Zendesk keeps only the last four digits; there is rarely a reason to carry them. |
Statuses, priorities and Type, value by value
Every value is mapped in writing, with a fallback you choose; a value with no match and no fallback is left off and named as a Setup gap. A status the migration sets to Resolved or Closed sends no mail. A sensible starting point:
| Zendesk | Freshdesk |
|---|---|
| Status: New | Open |
| Status: Open | Open |
| Status: Pending | Pending |
| Status: On-hold | Pending, or a custom status you add |
| Status: Solved | Resolved |
| Status: Closed | Closed |
| Priority: Low, Normal, High, Urgent | Low, Medium, High, Urgent |
| Type: Question, Incident, Problem, Task | The same values, added to Freshdesk’s Type field first |
Freshdesk refuses a Type it does not have, and the match is case-sensitive. A Type that differs only in capitals is written in Freshdesk’s spelling; any other is left off as a Setup gap, so the ticket still migrates.
Users and organisations
- Matching. End users become contacts, matched on email or external ID, never on name or phone.
- Language and time zone. Freshdesk accepts only the values on its own lists. One it does not list is left off and named, and the contact still migrates.
- Activation email. Check Freshdesk’s user activation email is off, or every migrated contact can be invited to sign in to your portal.
- Organisations. They become companies. A company whose domain is already in Freshdesk is linked to it and left as it is; a different company with the same name is added with ‘(migrated ...)’ after its name.
- Fields. User fields map to contact fields and organisation fields to company fields, value by value against your choice lists.
Guide articles in Solutions
- Structure. Categories, sections and articles become Solutions categories, folders and articles.
- State and languages. Articles keep their draft or published state, with translations. A published article in a folder visible to all users shows on your portal as soon as it arrives.
- Links. Links between articles point at the new articles.
- Who can see an article is never migrated. Set folder visibility again in Freshdesk.
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 Zendesk | Why it has no place | The workaround |
|---|---|---|
| Original created date | Freshdesk’s API takes no creation date | A text field such as ‘created at zendesk’ |
| Multi-select and lookup fields | No matching Freshdesk field type | A text field, checked on a Sample |
| A value not on a Freshdesk choice list | Freshdesk would refuse the whole record | Add the value first, or map it to one that exists |
| A CC with no email address | Freshdesk records CC only as addresses | None; the ticket names who was left off |
| Side conversations | Not part of the ticket thread the migration reads | Export any you need before you close Zendesk |
| Satisfaction ratings, SLA history and metrics | Not read from Zendesk | Keep the Zendesk reports |
| SLA due dates | Not carried | Freshdesk applies its own SLA policies |
| Suspended tickets | Held emails, not tickets yet | Recover the ones you want before the Full migration |
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 users and organisations they use. Sample records are real records in Freshdesk, and the Full migration recognises them instead of creating them twice. Include an archived ticket or two, then open them in Freshdesk and check:
- The original-date field holds the Zendesk date, and each note opens with its original time and author.
- Each ticket has the status, priority and Type your map says.
- Private comments are private notes, and inline images sit where the author put them.
- Values on choice-list fields are there, and anything left out is named on the record.
- Nobody received an email. If someone did, switch that notification off before the Full.
Then start the Reconciliation report for the run: it compares Zendesk and Freshdesk 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 Zendesk to Freshdesk 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 fields
- Zendesk Help - About ticket archiving
- Freshdesk API reference
- Freshdesk Support - Configuring email notifications
Vendor facts checked against these pages on . Vendors change their products; if something here has moved, tell us and we will correct it.