The short answer
| In Intercom | In Zendesk | How it is handled |
|---|---|---|
| Conversation | Ticket | Imported with its original created, updated and solved dates |
| Intercom ticket | Ticket | Its ticket attributes map to ticket fields |
| Customer message | Public comment | From the contact, at its original time |
| Teammate reply | Public comment | From the agent you mapped, at its original time |
| Internal note | Private comment | Never shown to the requester |
| Contact (user or lead) | End user | Matched on email or external ID |
| Company | Organisation | External ID made from the source |
| Teammate and team | Agent and group | Mapped one by one |
| State or ticket state | Status | You choose each value |
| Priority | Priority | Value by value |
| Tags | Ticket tags | Written on each ticket |
| Conversation and ticket attributes | Ticket fields | Field by field, values one by one |
| Contact and company attributes | User and organisation fields | Field 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 Intercom | In Zendesk | Good to know |
|---|---|---|
| Created date | Created date | Kept by the ticket import, together with the updated and solved dates. |
| Contact | Requester | Matched on email or external ID, or created first, so the ticket belongs to the right person. |
| Each message | A comment | Its own time, author and public or private flag, all in one import that runs no triggers. |
| Teammate assignee | Assignee | The agent you mapped. Anyone missing falls back to a default you choose. |
| Team assignee | Group | The group you mapped. |
| State (open, snoozed, closed) | Status | You map every value; see the table below. |
| Ticket state | Status | For Intercom tickets, each state is mapped the same way. |
| Priority | Priority | Value by value; see below. |
| Tags | Ticket tags | |
| Conversation and ticket type attributes | Ticket fields | Field by field. Zendesk ticket fields belong to the whole account; ticket forms decide which ones agents see. |
| Attachments | Files on the same comment | A type Zendesk does not allow is still kept, renamed to .txt or wrapped in a .zip. |
| Inline images | Inline images | Intercom image links expire, so each image is copied and placed back where the author put it. |
| Conversation rating | Not carried | Zendesk 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 Intercom | In Zendesk |
|---|---|
| Open | Open |
| Snoozed | Pending or On-hold |
| Closed | Solved, or Closed if nothing more will change |
| Ticket state: Submitted | New or Open |
| Ticket state: In progress | Open |
| Ticket state: Waiting on customer | Pending |
| Ticket state: Resolved | Solved |
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 Intercom | Why it has no place | The workaround |
|---|---|---|
| Conversation ratings | Zendesk lets only the requester create a rating, on a solved ticket | Keep your Intercom report |
| Messages beyond the latest 500 | Intercom hands over at most 500 parts of a conversation | Copy the start of a very long conversation by hand if you need it |
| Companies with no people | Intercom lists a company only once it has a person | Add a person first, or create it in Zendesk |
| Blocked people and their conversations | Intercom’s API hides them | Unblock them before the run |
| Files Intercom blocked when they were sent | Intercom kept only a note | None: the file never reached Intercom |
| Reporting history | Zendesk does not calculate SLAs or metrics for imported tickets | Filter Explore reports to leave out your migration tag |
| Workflows, saved replies and SLA rules | Settings, not records | Set 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
- Zendesk Developers - Ticket Import
- Zendesk Developers - Ticket fields
- Zendesk Help - CCs and followers
- Zendesk Help - Migrating data into Zendesk
Vendor facts checked against these pages on . Vendors change their products; if something here has moved, tell us and we will correct it.