Skip to content
DataGrine home

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

In a Zendesk to Intercom migration, each ticket becomes an Intercom conversation or a ticket of the type you choose, users become contacts and organisations become companies. Custom fields map to Intercom attributes: conversation or ticket type attributes for tickets, contact and company attributes for people. Archived tickets come across like any other. Statuses are mapped value by value, and priority goes to Intercom’s own priority field. A few things have no place in Intercom, such as followers, the Type field and multi-select fields, and each one has a workaround you can plan before the first run.

By the DataGrine team · Updated · 9 min read

The short answer

In ZendeskIn IntercomHow it is handled
TicketConversation, or ticket of the type you chooseOne per ticket, created with its original date
SubjectTitleCarried as it is
DescriptionThe opening messageIn Ticket mode it also fills the ticket’s description
Public commentReplyOriginal time and author kept
Private commentInternal noteNever shown to the customer
RequesterContactMatched on email or external ID
CCsParticipantsAdded to the conversation
Assignee and groupTeammate and teamMapped one by one
StatusOpen, snoozed or closed, or a ticket stateYou choose each value
Archived ticket (closed over 120 days)Conversation or ticket, like any otherCarried with its full thread and original dates
PriorityIntercom’s own priority fieldValue by value, as conversations
TypeA custom attributeValue by value
TagsTagsMatched to existing tags, ignoring case
Custom ticket fieldsConversation or ticket type attributesField by field, values one by one
User and user fieldsContact and contact attributesUser or lead, as you choose
Organisation and organisation fieldsCompany and company attributesOrganisation ID as company ID by default

This page is for the admin who plans the mapping. For what moves overall, and what you set up again in Intercom, see Zendesk to Intercom migration. For what to switch off before the first run, see the Zendesk to Intercom migration checklist.

The first decision: conversations or tickets

Before any field is mapped, choose how Zendesk tickets land in Intercom: as conversations, or as tickets of an Intercom ticket type. The choice decides which fields you can map to, so make it first.

  • Conversations. Each ticket arrives as a conversation with its whole thread. Ticket fields map to conversation attributes. Conversation attributes cannot be created through Intercom’s API, so create the ones you need in Intercom before mapping.
  • Tickets. Each ticket starts as a conversation carrying the thread and is then converted into the ticket type you pick. That adds the type’s attributes to the mapping and gives each record a ticket state. Missing ticket type attributes can be created from the mapping screen, but the ticket type itself is created in Intercom first.

Tickets suit work that takes time and needs a type and a state; conversations suit quick questions. If you are unsure, read Intercom tickets vs conversations. The mapping locks for the whole migration once a run completes, a completed Sample included, so settle this before the Sample. A failed or cancelled Sample locks nothing, and to change a locked mapping you clone the migration.

Zendesk ticket fields and where they land

Zendesk ticket fieldIn IntercomGood to know
SubjectTitleThe conversation or ticket title.
DescriptionOpening messageIn Ticket mode it also fills the description, which holds at most 32,766 characters. A longer one is cut there and named as a Vendor limit; the full text stays in the opening message.
RequesterThe contact who opens the conversationIntercom opens every conversation in its contact’s name, so a ticket an agent opened for a customer shows its first message as the customer’s, and the record says so.
CCsParticipantsEveryone copied on the email is added to the conversation.
FollowersNot addedIntercom has no followers on a conversation. The record names them.
AssigneeTeammateTeammates must already exist in Intercom; its API cannot create them. Anyone missing falls back to a default you choose.
GroupTeamThe team is assigned first and the teammate second, so Intercom’s round-robin does not replace the teammate you mapped.
StatusState, or ticket stateYou map every value; see the status table below.
PriorityIntercom’s own priority fieldMapped value by value when you migrate as conversations. An Intercom ticket type has no priority field, so in Ticket mode priority is not mapped.
Type (question, incident, problem, task)A custom attributeIntercom tickets have no built-in Type. It travels only when you map it.
Ticket formThe ticket type you chooseForms are configuration. Create matching ticket types in Intercom first.
TagsTagsMatched to your existing Intercom tags, ignoring case, and reused as they are, never renamed.
Created dateCreated dateEach conversation and each reply keeps its original time. Intercom sets its own last-updated time when the record is written.
Due date (tasks)Not carriedA conversation has no due date. The record keeps the original date.
External IDNot on the conversationIntercom conversations have no external ID. Map it to an attribute to keep it.
Channel (via)Not carriedIntercom’s API creates every migrated conversation as an email conversation.
DataGrine field mapping screen: source fields matched to Intercom fields, each marked Mapped.
The Field Mapping screen, shown here on a Freshdesk to Intercom migration. Each source field is matched to where it lands, and anything without a home is flagged before it moves.

Custom fields, type by type

Zendesk documents twelve ticket field types. Intercom attributes come in fewer types, so most map one to one and a few need a decision. Where the Intercom attribute does not exist yet, it can be created from the mapping screen for contacts, companies and ticket types; conversation attributes are created in Intercom first.

Zendesk field typeIntercom attributeGood to know
Text, and regular expressionTextThe pattern check stays in Zendesk; the value arrives as text.
Multi-line textMulti-line textLine breaks are kept on a multi-line attribute.
CheckboxTrue or false
DateDate
Number and decimalNumber and decimal
Drop-downListEach value is mapped to an Intercom value one by one, with a fallback you choose.
Multi-selectNo direct matchIntercom’s own Zendesk importer documentation says multi-select fields have to become text. Plan a text attribute, or a list holding the one value that matters, and check how it reads on a Sample.
Lookup relationshipNo direct matchThe same note applies: plan a text attribute and check it on a Sample.
Credit cardLeave unmappedZendesk keeps only the last four digits; there is rarely a reason to carry them.

Two limits are worth knowing before you map people’s fields. Intercom refuses a list attribute on contacts or companies with fewer than two or more than 35 options, and the mapping screen tells you so by name before anything is created. A Zendesk drop-down with more values than that is mapped to a text attribute instead.

Statuses and priorities, value by value

Every value inside a field is mapped in writing to where it lands, 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.

Statuses decide whether each conversation ends up open or closed. The state you map each status to is applied exactly, and it is written last, after the replies and the assignment, because each of those reopens an Intercom conversation. In Ticket mode, the category of the ticket state you map to decides open or closed. A sensible starting point, which you can change value by value:

Zendesk statusAs a conversationAs a ticket (state category)
NewOpenSubmitted
OpenOpenIn progress
PendingOpenWaiting on customer
On-holdOpenIn progress
SolvedClosedResolved
ClosedClosedResolved

Map a status to Snoozed only if you want those conversations back: a snoozed conversation wakes after 7 days and reappears as open in the inbox.

Priority has a home of its own. When you migrate as conversations, each Zendesk priority maps to a value of Intercom’s own priority field, which takes Low, Medium, High and Urgent. An Intercom ticket type has no priority field, so in Ticket mode priority is not mapped. Type has no built-in home in Intercom, so it becomes a list attribute you create first, with values that match Zendesk’s.

Zendesk fieldZendesk valuesIn Intercom
PriorityLow, Normal, High, UrgentIntercom’s priority field, value by value, for example Normal to Medium (as conversations)
TypeQuestion, Incident, Problem, TaskA list attribute, for example ‘Zendesk type’, with the same four values

Users to contacts

  • User or lead. Zendesk end users become Intercom users or leads, as you choose in the mapping. An Intercom user needs an email or an external ID; a lead needs neither, but Intercom will not store an external ID on a lead.
  • Matching. Contacts are matched on email or external ID, never on name or phone, so two people who share a name are never merged.
  • No email and no external ID? The contact gets a stable ID from the source, so a later run finds it again instead of creating a second one.
  • Archived in Intercom? A matching archived contact is unarchived and updated, not created again.
  • Dates. Intercom has no writable created date for a contact, so the Zendesk creation date goes into the contact’s signed-up date.
  • Phone numbers. If phone number validation is on in Intercom, numbers it cannot validate are refused. Turn it off for the run.
  • User fields. Each maps to a contact attribute: text, number, decimal, true or false, date or list. Missing ones can be created from the mapping screen.
  • Agents. Zendesk agents are not contacts. They map to Intercom teammates, who must exist before mapping.

More on keeping one person as one contact: avoid duplicate contacts in an Intercom migration.

Organisations to companies

  • The company ID. Intercom identifies a company by its company ID alone, and the ID cannot change later. By default it receives the Zendesk organisation ID, so a re-run updates the same company rather than adding a second. If you choose another field, it must be unique: two organisations sent with the same ID become one company.
  • A company Intercom already holds. A write with an ID Intercom already has updates that company. It is counted as an update, and a rollback leaves it in place.
  • Visible once it has people. Intercom shows a company once at least one contact is attached to it.
  • Organisation fields. Each maps to a company attribute, with the same types as contact attributes. Missing ones can be created from the mapping screen.

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. What you can plan is where the information lives afterwards.

In ZendeskWhy it has no placeThe workaround
Type fieldIntercom tickets have no built-in typeA list attribute, or a ticket type per kind of work
Multi-select and lookup fieldsNo matching attribute typeA text attribute, checked on a Sample
Drop-downs with more than 35 values (people)Intercom refuses longer lists on contacts and companiesA text attribute
Ticket external IDConversations have no external IDMap it to a text attribute
FollowersIntercom has no followersNone in Intercom; the record names them
Due dates on tasksA conversation has no due dateSet reminders again for open tasks; the record keeps the date
Original channelEvery migrated conversation is created as emailKeep a Zendesk export if you report on channel
Inline image positionImage links expireThe image arrives as a file on the same message
Very long descriptionsA ticket description holds 32,766 charactersThe full text stays in the opening message
Satisfaction ratingsIntercom’s API cannot write a past ratingKeep the Zendesk report
SLA history and ticket metricsRead-only in ZendeskKeep the Zendesk report; set up SLA rules again in Intercom
Side conversationsNot part of the ticket thread the migration readsExport any you need before you close Zendesk

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 Intercom, and the Full migration recognises them instead of creating them twice. Pick tickets that test the mapping, then open them in Intercom and check:

  • Each mapped attribute holds the value you expected, including your drop-downs and any multi-select you sent to text.
  • Solved and closed tickets arrived closed, and open ones open, as your status map says.
  • Each conversation shows the Intercom priority you mapped, and Type sits in the attribute you made for it.
  • Tags match your existing Intercom tags, with no near-duplicates.
  • People copied on emails are participants, and private comments are internal notes.
  • Contacts have the right company, and no contact arrived twice.

Then start the Reconciliation report for the run: it compares Zendesk and Intercom line by line and names every record that did not arrive as it was, with the reason. If the mapping needs a change after a completed Sample, clone the migration and fix it in the copy. When it is right, run the Full migration from the Zendesk to Intercom 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 Intercom attributes be created for us?

Yes, for contacts, companies and ticket types: the mapping screen can create them before any run. Conversation attributes cannot be created through Intercom’s API, so create those in Intercom first.

How do Zendesk statuses map to Intercom?

You map each status yourself, to open, snoozed or closed, or in Ticket mode to a ticket state. The state is written last, after the replies and the assignment, so a solved ticket arrives closed.

What happens to Zendesk priority?

When you migrate as conversations, it maps to Intercom’s own priority field, value by value: Low, Normal, High and Urgent each go to the Intercom priority you choose, such as Normal to Medium. An Intercom ticket type has no priority field, so in Ticket mode priority is not mapped.

Do archived Zendesk tickets come across?

Yes. Zendesk archives a ticket 120 days after it closes, and archived tickets are carried like any other closed ticket, with their full thread, attachments and original dates, and mapped with the same rules.

Can Zendesk multi-select fields be migrated to Intercom?

Not to a matching type. Intercom’s own Zendesk importer documentation says multi-select and lookup fields have to become text. Plan a text attribute for them and check a few tickets on a Sample.

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