Skip to content
DataGrine home

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

In an Intercom to Zendesk migration, every conversation and ticket becomes a Zendesk ticket through Zendesk’s Ticket Import, with its original dates. Customer messages and teammate replies become public comments and internal notes become private comments, each with its own time and author. Contacts become end users and companies become organisations. Attributes map to Zendesk ticket, user and organisation fields, and states and priorities are mapped value by value. A few things have no place in Zendesk, such as conversation ratings, and each one has a plan you can make before the first run.

By the DataGrine team · Updated · 6 min read

The short answer

In IntercomIn ZendeskHow it is handled
ConversationTicketImported with its original created, updated and solved dates
Intercom ticketTicketIts ticket attributes map to ticket fields
Customer messagePublic commentFrom the contact, at its original time
Teammate replyPublic commentFrom the agent you mapped, at its original time
Internal notePrivate commentNever shown to the requester
Contact (user or lead)End userMatched on email or external ID
CompanyOrganisationExternal ID made from the source
Teammate and teamAgent and groupMapped one by one
State or ticket stateStatusYou choose each value
PriorityPriorityValue by value
TagsTicket tagsWritten on each ticket
Conversation and ticket attributesTicket fieldsField by field, values one by one
Contact and company attributesUser 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 Intercom to Zendesk migration. For what to switch off before the first run, see the helpdesk migration checklist for an Intercom 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 teammate and team, 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. 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.

Intercom conversation fields and where they land

In IntercomIn ZendeskGood to know
Created dateCreated dateKept by the ticket import, together with the updated and solved dates.
ContactRequesterMatched on email or external ID, or created first, so the ticket belongs to the right person.
Each messageA commentIts own time, author and public or private flag, all in one import that runs no triggers.
Teammate assigneeAssigneeThe agent you mapped. Anyone missing falls back to a default you choose.
Team assigneeGroupThe group you mapped.
State (open, snoozed, closed)StatusYou map every value; see the table below.
Ticket stateStatusFor Intercom tickets, each state is mapped the same way.
PriorityPriorityValue by value; see below.
TagsTicket tags
Conversation and ticket type attributesTicket fieldsField by field. Zendesk ticket fields belong to the whole account; ticket forms decide which ones agents see.
AttachmentsFiles on the same commentA type Zendesk does not allow is still kept, renamed to .txt or wrapped in a .zip.
Inline imagesInline imagesIntercom image links expire, so each image is copied and placed back where the author put it.
Conversation ratingNot carriedZendesk lets only the requester create a satisfaction rating, on a solved ticket.

Attributes and list values

Every attribute you map lands in a Zendesk field, and every value inside a list 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.

  • Conversation and ticket attributes map to ticket fields. Zendesk documents text, multi-line text, checkbox, date, number, decimal, regular expression, drop-down, multi-select, lookup and credit card field types.
  • List attributes map to drop-down fields, value by value.
  • Contact attributes map to user fields, and company attributes to organisation fields.
  • Users and leads both become Zendesk end users, who have no user or lead role of their own.

States and priorities, value by value

States 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, and that cannot be turned off. A sensible starting point, which you can change value by value:

In IntercomIn Zendesk
OpenOpen
SnoozedPending or On-hold
ClosedSolved, or Closed if nothing more will change
Ticket state: SubmittedNew or Open
Ticket state: In progressOpen
Ticket state: Waiting on customerPending
Ticket state: ResolvedSolved

Priority maps to Zendesk’s own Priority field. Intercom has Low, Medium, High and Urgent; Zendesk has Low, Normal, High and Urgent, so Medium usually goes to Normal. A conversation with no priority has none to carry.

Contacts to end users

  • Matching. Contacts are matched on email or external ID, never on name or phone, so two people who share a name are never merged.
  • Already an agent? A contact who matches a Zendesk agent or admin, by email or external ID, is linked to that user and nothing is written to their profile, so their tickets reach the right person. 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, or the extra memberships are not carried. It is not available on the Team plan.
  • Language. A language is written in the account’s own spelling. One the account has not enabled is not sent, and the record says so.

Companies to organisations

  • External ID. Each organisation carries an External ID made from the source platform and the source ID, so a later run finds the same organisation.
  • Same name, different company. A different organisation with the same name is added with ‘(migrated ...)’ after its name.
  • 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 to it first, or create it in Zendesk by hand.

Help Center articles in Guide

  • Sections. A Guide article can live only in a section. An article that sits directly in an Intercom collection is placed in a section DataGrine creates in that category, and the record names it.
  • 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 IntercomWhy it has no placeThe workaround
Conversation ratingsZendesk lets only the requester create a rating, on a solved ticketKeep your Intercom report
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
Companies with no peopleIntercom lists a company only once it has a personAdd a person first, or create it in Zendesk
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
Reporting historyZendesk does not calculate SLAs or metrics for imported ticketsFilter Explore reports to leave out your migration tag
Workflows, saved replies and SLA rulesSettings, 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 conversations (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 mapped field holds the value you expected, including your list values.
  • Each ticket has the status your state map says, and the priority you mapped.
  • Internal notes are private comments, and every comment has the right author and time.
  • Contacts belong to the right organisation, and nobody arrived twice.
  • Nobody received an email.

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

Can missing Zendesk fields be created for us?

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

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.

What happens to Intercom priority?

It maps to Zendesk’s own Priority field, value by value. Medium usually goes to Normal.

Do Intercom internal notes stay internal?

Yes. They become private comments, which Zendesk never shows to the requester.

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