Skip to content
DataGrine home

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

In an Intercom to Freshdesk migration, every conversation and ticket becomes a Freshdesk ticket. Teammate replies become public notes, customer messages notes from that customer and internal notes private notes, each opening with its original time and author, so nothing goes through Freshdesk’s reply action. Freshdesk takes no creation date through its API, so the original date is kept in a field. Attributes map to Freshdesk ticket, contact and company fields, value by value against your choice lists, and states and priorities are mapped the same way.

By the DataGrine team · Updated · 6 min read

The short answer

In IntercomIn FreshdeskHow it is handled
Conversation or ticketTicketOriginal date kept in a text field such as ‘created at intercom’
Teammate replyPublic noteOpens with its original time in UTC and author
Customer messageNote from that customerShown as the customer’s own message
Internal notePrivate noteNever shown to the customer
ContactContactMatched on email or external ID
CompanyCompanyLinked by domain, or added
Teammate and teamAgent and groupAgents must exist; groups can be created
State or ticket stateStatusYou choose each value
PriorityPriorityValue by value
TagsTagsUp to 32 characters, no comma
AttributesTicket, contact and company fieldsValue by value against your choice lists

This page is for the admin who plans the mapping. For what moves overall, and what you set up again in Freshdesk, see Intercom 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 intercom’, 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 any historical report on that field rather than on Freshdesk’s Created date, and create the field before the Sample.

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:

  • Teammate replies become public notes from the agent you mapped.
  • Customer messages become notes from that customer, shown as the customer’s own message.
  • Internal notes become private notes.
  • Each note opens with a line giving its original time in UTC and its author, then, where Intercom recorded them, who it went to. 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.

Intercom conversation fields and where they land

In IntercomIn FreshdeskGood to know
Created dateA text field such as ‘created at intercom’Freshdesk’s own Created date is the migration day.
ContactRequesterMatched on email or external ID, or created first.
Teammate assigneeAgentAgents 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.
Team assigneeGroupGroups Freshdesk lacks can be created with their members.
State or ticket stateStatusYou map every value; see the table below.
PriorityPriorityValue by value; see below.
TagsTagsFreshdesk allows 32 characters and no comma, so a longer tag is shortened and named, not dropped.
Conversation and ticket type attributesTicket fieldsField by field. Text fields hold 255 characters.
AttachmentsAttachmentsOn the ticket or note they belong to, up to 20 MB per message (Freshdesk’s limit). A file that does not make it is named on the record.
Inline imagesInline imagesIntercom image links expire, so each image is copied to the ticket and placed where the author put it. Freshdesk also lists it under attachments; it is one file.

Attributes 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 your 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; a value with no match and no fallback is left off and named as a Setup gap.

  • Missing fields. Ticket, contact and company fields can be created from the mapping screen before any run.
  • Type. 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; add any other value to the Type field first.
  • Dependent fields. Freshdesk cannot set a lower level without the level above it, so if you map to a dependent field, map every level.

States and priorities, value by value

A status the migration sets to Resolved or Closed sends no mail. A sensible starting point, which you can change value by value:

In IntercomIn Freshdesk
OpenOpen
SnoozedPending
ClosedResolved or Closed
Ticket state: SubmittedOpen
Ticket state: In progressOpen
Ticket state: Waiting on customerPending
Ticket state: ResolvedResolved

Priority maps to Freshdesk’s Priority field, value by value: Low, Medium, High and Urgent.

Contacts and companies

  • Matching. Contacts are matched on email or external ID, never on name or phone, so two people who share a name are never merged.
  • 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.
  • 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.
  • Industry. An industry Freshdesk does not list is left off and named.
  • Companies with no people. Intercom lists a company only once at least one person belongs to it, so a company with nobody in it is never seen. Add a person first, or create it in Freshdesk by hand.

Help Center articles in Solutions

  • Structure. Collections become Solutions categories and folders, with articles in their folders. A Freshdesk article lives only in a folder, so an Intercom article that sits directly in a collection gets a folder made for it in the same category.
  • State. Articles keep their draft or published state. A published article in a folder visible to all users shows on your portal as soon as it arrives.
  • 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 IntercomWhy it has no placeThe workaround
Original created dateFreshdesk’s API takes no creation dateA text field such as ‘created at intercom’
Resolved and closed timesThey become the time the status is writtenReport on the original-date field
A value not on a Freshdesk choice listFreshdesk would refuse the whole recordAdd the value first, or map it to one that exists
A CC with no email addressFreshdesk records CC only as addressesNone; the ticket names who was left off
Messages beyond the latest 500Intercom hands over at most 500 parts of a conversationCopy the start of a very long conversation by hand if you need it
Blocked people and their conversationsIntercom’s API hides themUnblock them before the run
Files Intercom blocked when they were sentIntercom kept only a noteNone: the file never reached Intercom
Workflows, saved replies and SLA rulesSettings, not recordsSet them up again as automation rules, canned responses and SLA policies

Check the mapping on a free Sample

The Sample is free: 20, 100, 500 or 1,000 of your own conversations (100 by default), with the contacts and companies they use. Sample records are real records in Freshdesk, and the Full migration recognises them instead of creating them twice. Open them in Freshdesk and check:

  • The original-date field holds the Intercom date, and each note opens with its original time and author.
  • Each ticket has the status and priority your map says.
  • Internal notes are private notes, and inline images sit where the author put them.
  • Values you expected 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 Intercom 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 Intercom 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.

Why does Freshdesk show the migration day as the Created date?

Freshdesk does not accept a creation date through its API. The original date is kept in a text field such as ‘created at intercom’, which the mapping screen can create, and every note starts with its original time in UTC.

Will Freshdesk email our customers?

Not through DataGrine: every past reply is written as a note, never through the reply action. Freshdesk’s own notifications still fire unless you switch them off, so turn off the requester and CC notifications before the Sample.

What happens to Intercom priority?

It maps to Freshdesk’s Priority field, value by value: Low, Medium, High and Urgent.

What if an Intercom value is not on a Freshdesk choice list?

It is left out and reported, and the record still migrates. Add the value to the Freshdesk field before the run, or map it to one that exists.

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