Skip to content
DataGrine home

Freshdesk to Freshdesk field mapping: every field, where it lands, and what to check when accounts differ

In a Freshdesk to Freshdesk migration, the two accounts speak the same language, so most fields map to the same field. What differs is each account’s own setup: the choice lists, Type values, agents, groups and custom fields the target holds. Freshdesk takes no creation date through its API, so the original date is kept in a field, and every reply is written as a note that opens with its original time, sender and recipients, so nothing goes through the reply action.

By the DataGrine team · Updated · 6 min read

The short answer

In the source accountIn the target accountHow it is handled
TicketTicketOriginal date kept in a text field such as ‘created at freshdesk’
Agent reply or public notePublic noteOpens with its original time, sender and recipients
Customer replyNote from that customerShown as the customer’s own message
Private notePrivate noteNever shown to the customer
ContactContactMatched on email or external ID; other emails too
CompanyCompanyLinked by domain, or added
AgentAgentMust exist in the target
GroupGroupCan be created with its members
Status, priority and TypeStatus, priority and TypeValue by value
TagsTagsUp to 32 characters, no comma
Custom fieldsCustom fieldsMissing ones can be created first
SolutionsSolutionsSame tree, with translations and SEO settings

This page is for the admin who plans the mapping. For what moves overall, see Freshdesk to Freshdesk migration. For what to switch off in the target account 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 the Created date of 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 freshdesk’, which ‘Create all missing fields’ in Field Mapping adds. Without that field, it is written on the description’s first line. Resolved and closed times become the time the status is written, so build historical reports on the original-date field.

How each message is written

Freshdesk’s reply action emails the requester and everyone in CC, so DataGrine never uses it. Every message is written as a note under its author instead:

  • Agent replies and public notes become public notes from the agent you mapped.
  • Customer replies become notes from that customer.
  • Private notes stay private notes.
  • The first line gives the original time in UTC and the author, for example ‘Originally sent 2026-01-31 09:15 UTC by Name’.
  • The second line names who it went to: To and Cc. On a private note it reads ‘Notified’ and can name Bcc, which is never written on a note your customer can see.

A public note can still make the target email the requester ‘Ticket Updated’ while that notification is on, so switch the requester and CC notifications off in the target before the Sample.

Ticket fields and where they land

Source ticket fieldIn the targetGood to know
RequesterRequesterMatched on email or external ID, or created first.
CompanyCompanyThe company the ticket belongs to, linked by domain or added.
CC addressesCC addressesCarried on the ticket.
AgentAgentAgents must exist in the target, with the same email address. Anyone missing goes to the default agent you choose, with the original name on each note.
GroupGroupGroups the target lacks can be created with their members.
StatusStatusValue by value; a custom status must exist in the target to be chosen.
PriorityPriorityLow, Medium, High and Urgent, value by value.
TypeTypeA Type the target does not list is left off and named. Add it first, with the same spelling.
SourceSourceEmail, portal, phone, chat, feedback widget and outbound email pass through. Freshdesk takes no other channel on a new ticket, so another one is not written and the record says so.
TagsTagsFreshdesk allows 32 characters and no comma, so a longer tag is shortened and named, not dropped. A run tag can be added to every migrated ticket.
Created dateA text field such as ‘created at freshdesk’The target’s own Created date is the migration day.
Due by and first response dueNot carriedThe target applies its own SLA policies to every migrated ticket.
AttachmentsAttachmentsOn the ticket and on each note, up to 20 MB per message. A file that does not make it is named on the record with the reason.
Inline imagesInline imagesUploaded to the ticket and placed where the author put them. Freshdesk also lists them under attachments; it is one file.

Custom fields and choice lists

Freshdesk refuses a whole record over one value that is not on a field’s choice list. DataGrine checks each value against the target’s lists first, leaves out one that does not fit and reports it, so the record still migrates. Every value is mapped in writing, with a fallback you choose.

  • Missing fields. Ticket, contact and company fields the target lacks can be created from the mapping screen before any run.
  • Text fields hold 255 characters.
  • Dependent fields. Freshdesk cannot set a lower level without the level above it, so map every level of a dependent field.
  • Two accounts, one list. When you merge accounts, add the source’s dropdown values to the target’s fields first, or map each one to a value the target already has.

Contacts and companies

  • Matching. Contacts are matched on email or external ID, never on name or phone, and their other emails travel too.
  • Language and time zone. A value the target does not list is left off and named, and the contact still migrates.
  • Activation email. Check the target’s user activation email is off, or every migrated contact can be invited to sign in to your portal.
  • Companies. A company whose domain is already in the target is linked to it and left as it is. A different company with the same name is added with ‘(migrated ...)’ after its name.
  • Industry. An industry the target does not list is left off and named.

Solutions

  • Structure. Categories, folders and sub-folders arrive in the same tree.
  • Articles. They keep their draft or published state, translations and SEO settings, and links between articles are rewritten to the new articles.
  • Restricted folders are never widened. A folder visible to selected companies, contact segments, company segments or bots arrives visible to agents only, and the record says so. Set its visibility again in the target.
  • Published articles in a folder visible to all users show on the target portal as soon as they arrive.

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 the source accountWhy it has no placeThe workaround
Original created dateFreshdesk’s API takes no creation dateA text field such as ‘created at freshdesk’
A Type, Industry, language or time zone the target does not listFreshdesk would refuse the whole recordAdd the value to the target first
Folder audiencesNever migratedSet folder visibility again in the target
A channel the target will not take on a new ticketFreshdesk accepts only a few channels on a new ticketNone; the record says so
SLA due datesNot carriedThe target applies its own SLA policies
Satisfaction ratings and time entriesNot read from the sourceKeep the source reports
Archived ticketsThey are not migratedExport the source’s Archive view
Spam and TrashFreshdesk’s API leaves them outRestore what 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 contacts and companies they use. Sample records are real records in the target, and the Full migration recognises them instead of creating them twice. Open them in the target and check:

  • The original-date field holds the source date, and each note opens with its original time, sender and recipients.
  • Each ticket has the status, priority, Type, agent and group your map says.
  • Private notes stay private, and inline images sit where the author put them.
  • Contacts and companies were linked to the ones the target already held, not added twice.
  • Nobody received an email. If someone did, switch that notification off before the Full.

Then start the Reconciliation report for the run: it compares the two accounts 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 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

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 the two accounts need the same fields?

No. Each source field is mapped to a field in the target, and fields the target lacks can be created from the mapping screen. Choice-list values need to exist in the target, or be mapped to one that does.

Where is each ticket’s original date?

In a text field named after the source, such as ‘created at freshdesk’, which the mapping screen can create. Freshdesk’s own Created date is the migration day.

Do restricted Solutions folders stay restricted?

They are never widened. A folder visible to selected companies, segments or bots arrives visible to agents only, and the record says so, so you can set its visibility again in the target.

Are archived tickets migrated?

No. Freshdesk archives a closed ticket after 120 days without activity, and archived tickets are not migrated. Export the source account’s Archive view first if you need them.

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