Skip to content
DataGrine home

Freshdesk to Zendesk field mapping: every field, where it lands, and what to do when it has no match

In a Freshdesk to Zendesk migration, every ticket goes in through Zendesk’s Ticket Import, which keeps its original created, updated and solved dates and each comment’s time, author and public or private flag. Replies become public comments and private notes become private comments. Contacts become end users and companies become organisations. Statuses, priorities and Type are mapped value by value, and custom fields field by field. A few things have no place in Zendesk, such as Freshdesk Type values beyond Zendesk’s four, and each one has a plan you can make before the first run.

By the DataGrine team · Updated · 5 min read

The short answer

In FreshdeskIn ZendeskHow it is handled
TicketTicketImported with its original created, updated and solved dates
Reply or public notePublic commentOriginal time and author kept
Private notePrivate commentNever shown to the requester
RequesterRequester (end user)Matched on email or external ID
CC addressesCCsTurn on CCs and followers first
Agent and groupAgent and groupMapped one by one
StatusStatus or custom statusCustom statuses included
PriorityPriorityMedium usually to Normal
TypeType, or a drop-down fieldZendesk has four fixed types
TagsTicket tagsWritten on each ticket
Ticket fieldsTicket fieldsField by field, values one by one
Contact and company fieldsUser and organisation fieldsField 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 fieldIn ZendeskGood to know
RequesterRequesterMatched on email or external ID, or created first.
CC addressesCCsWith CCs and followers off, Zendesk silently drops them, so turn the setting on first.
AgentAssigneeThe agent you mapped. Anyone missing falls back to a default you choose.
GroupGroupThe group you mapped.
StatusStatus or custom statusYou map every value; see below.
PriorityPriorityValue by value; see below.
TypeType, or a drop-down fieldZendesk’s Type has four fixed values; see below.
TagsTicket tags
Created dateCreated dateKept by the ticket import, together with the updated and solved dates.
Replies, notes and their timesCommentsEach keeps its own time, author and public or private flag, all in one import that runs no triggers.
AttachmentsFiles on the same commentA type Zendesk does not allow is still kept, renamed to .txt or wrapped in a .zip.
Inline imagesInline imagesFreshdesk image links expire within minutes, so each image is copied and placed back where the author put it.
Due by and first response dueNot carriedSLA 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 typeZendesk fieldGood to know
Single-line textText
Multi-line textMulti-line text
CheckboxCheckbox
Number and decimalNumber and decimal
DateDate
DropdownDrop-downEach 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:

FreshdeskZendesk
Status: OpenOpen
Status: PendingPending
Status: ResolvedSolved
Status: ClosedClosed, or Solved
Custom statusesCustom statuses you create in Zendesk first
Priority: Low, Medium, High, UrgentLow, Normal, High, Urgent
Type: each of your valuesQuestion, 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 FreshdeskWhy it has no placeThe workaround
Type values beyond fourZendesk’s Type has four fixed valuesA drop-down field for the rest
SLA due dates and reporting historyZendesk does not calculate SLAs or metrics for imported ticketsFilter Explore reports to leave out your migration tag
Satisfaction ratingsNot read from FreshdeskKeep the Freshdesk report
Time entriesNot read from FreshdeskKeep a copy before you close Freshdesk
Archived ticketsThey are not migratedExport the Archive view
Spam and TrashFreshdesk’s API leaves them outRestore what you want before the Full migration
Automation rules, canned responses and SLA policiesSettings, not recordsSet 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

Vendor facts checked against these pages on . Vendors change their products; if something here has moved, tell us and we will correct it.

Questions

Common questions on this topic.

Do original dates and authors survive?

Yes. Zendesk’s Ticket Import keeps each ticket’s created, updated and solved dates and each comment’s time, author and public or private flag. A comment a Delta adds to an existing ticket shows the time it was written, so its first line gives its original time and author.

How does Freshdesk priority map to Zendesk?

Value by value. Freshdesk has Low, Medium, High and Urgent; Zendesk has Low, Normal, High and Urgent, so Medium usually goes to Normal.

What happens to Freshdesk Type?

Zendesk’s Type field has four fixed values, question, incident, problem and task. Map each Freshdesk Type to one of them, or to a drop-down field of your own.

Can missing Zendesk fields be created for us?

Yes. Ticket, user and organisation fields can be created from the mapping screen before any run.

Can we change the mapping after the Sample?

The mapping locks once a run completes, a completed Sample included. A failed or cancelled Sample locks nothing. To change a locked mapping, clone the migration and edit the copy.

Let’s move your data forward.

Tell us where you are moving from and to. Run it yourself on the DataGrine platform or have our team run the whole migration for you, end to end.

  • A written mapping document before anything moves
  • A free Sample you review before the Full migration
  • Delta runs at cut-over and rollback per run
  • A Reconciliation report on every run