ZendeskIntercom

Zendesk to Intercom migration

Migration specialists move your tickets, public comments and private comments into Intercom, check a sample with you first, and count every record on both sides.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

Last updated November 2026 · 12 object types mapped

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Zendesk to Intercom at a glance

A Zendesk to Intercom migration turns each ticket into an Intercom conversation or an Intercom ticket, end users into contacts and organizations into companies. The hard part is the landing: Intercom starts a conversation only from a contact, so tickets opened by agents need a convention. Zendesk stays live until the final delta sync.

Objects mapped
12
in this route's mapping
Typical timeline
About 10 business days end to end
3 phases
Free sample
100 records
checked by your team first
Quote
Fixed
within 24 hours
Who it is for
Support teams moving from Zendesk's ticket queues to Intercom's inbox, often to work with the Fin AI Agent in the same place.
What does not move
Zendesk triggers, automations, macros, SLA policies, views and apps stay behind, listed for your admin to rebuild in Intercom.
What sets the scope
Ticket and comment volume, how many tickets agents opened themselves, custom field count, side conversations, organizations without users, and Help Center size.

What moves

What moves from Zendesk to Intercom

Tickets become Intercom conversations or tickets, end users contacts, organizations companies and agents admins, with comments as conversation parts, private comments as notes and Help Center articles as Intercom articles.

  • 12 included
ZendeskIntercom
  • End usersContacts

    Created as users, or as leads if the person never signed up. The Zendesk user id is kept as external_id.

  • OrganizationsCompanies

    Created by company_id through the API, then linked to its contacts.

  • TicketsConversations, or Intercom tickets

    Tickets that began as customer messages become conversations. Tickets that need a state become Intercom tickets. The rule is agreed per ticket group, and the Zendesk ticket id goes to a data attribute.

  • Public commentsConversation parts

    Customer comments load as contact replies and agent comments as admin replies, each with its original time.

  • Private commentsConversation parts (notes)

    Internal notes for admins, so they never reach the customer.

  • Ticket statusesConversation or ticket states

    Mapped one by one. Intercom ticket states are submitted, in progress, waiting on customer, on hold and resolved.

  • Ticket custom fieldsConversation or ticket data attributes

    Attributes are created first, from the approved mapping.

  • User and organization fieldsContact and company data attributes

    Each must exist in the workspace before values are sent.

  • TagsTags

    Created with the tags endpoint, then attached to the conversation or contact.

  • Agents and groupsAdmins and teams

    Agent replies are written as an admin, so agents are matched to admins first.

  • Help Center articlesArticles

    The author must be a teammate. Published articles load as published and drafts as drafts.

  • Categories and sectionsCollections and sections

    Created before the articles, because an article points to its collection.

Looking for another object?Field-level mapping is reviewed with you during scoping.

What does not move

What does not move from Zendesk to Intercom as-is

Triggers, automations, macros, SLA policies and views are configuration with no Intercom import path, so each is documented and rebuilt as Workflows and macros.

Side conversationsOn request
In Intercom: Internal note on the parentPosted as a note on the parent conversation, with participants and times in its text.
Satisfaction ratingsOn request
No matching Intercom object is documented. Scores can be kept in a data attribute, agreed at mapping.
MacrosNot migrated
Rebuilt by hand in Intercom from the list we hand over.
Triggers and automationsNot migrated
In Intercom: WorkflowsEach rule is documented with what it does today, for your team to rebuild as a Workflow.
SLA policies, views and metrics historyNot migrated
Not moved. Your team rebuilds SLA targets and views in Intercom.
Help Center themes and article URLsNot migrated
The theme is not moved. Redirects from old article addresses can be set.
Apps, integrations and Talk call dataNot migrated
Installed again in Intercom. Call recordings are sent across as attachments when you ask for them.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

Zendesk to Intercom migration timeline

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      We agree which tickets become conversations and which become Intercom tickets, how agent-opened tickets are posted, and what happens to side conversations and organizations without users.

    • Connect Zendesk and Intercom

      You0.5 day

      You approve a Zendesk connection with read access and give us an Intercom access token that can write. Your Intercom Workflows are paused at this point.

    • Attribute and state review

      Both1 day

      Ticket, user and organization fields to data attributes, statuses to conversation and ticket states, groups to teams. You approve the mapping before any attribute is created.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      100 of your records, picked for agent-opened tickets, the longest threads and the largest files, loaded into Intercom through a test contact.

    • You review the sample

      You1 day

      Your team opens the result in the Intercom inbox and checks message order, notes, authors, dates, and that no one was emailed.

    • Full load

      MigrateX2-3 days

      Attributes, contacts and companies first, then conversations and tickets with their replies, then Help Center collections and articles.

    • Delta sync

      MigrateX0.5 day

      Tickets changed in Zendesk since the full load are brought across and matched on the Zendesk ticket id stored in a data attribute.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Tickets against conversations and Intercom tickets by status and year, comments against parts, attachments against files, and every ticket that followed the agent-opened rule.

    • Spot checks and sign-off

      You1-2 days

      Your leads check a random sample, Workflows are switched back on, and Zendesk stays read-only until you agree.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

Known risks

Every known risk on this route, with how we handle it

  • 1 solved
  • 5 handled
  1. 01HandledMost critical

    Tickets opened by an agent have no contact to start from

    The problem

    Intercom's create-conversation call accepts a contact as the sender and no one else. A Zendesk ticket that an agent created for a customer, such as an outbound email or a phone follow-up, has no customer message to open the thread.

    How we handle it

    We agree one convention per ticket group at mapping: the first agent message is posted as if sent by the requester, or the ticket is loaded as an Intercom ticket. The sample run includes some of these tickets.

    Source: Intercom developer documentation, checked 15 Nov 2026

  2. 02Solved

    Each Zendesk ticket becomes a conversation or an Intercom ticket

    The problem

    Intercom has both objects, and they report differently. Tickets with a state and a ticket type suit work that needs tracking, while conversations suit threads that began as customer messages.

    How we handle it

    The choice is made per group of tickets before the sample: by form, by channel or by status. Zendesk statuses are mapped one by one onto conversation states, or onto the Intercom ticket states.

    Source: Intercom developer documentation, checked 15 Nov 2026

  3. 03Handled

    Zendesk custom fields can exceed Intercom's attribute limit

    The problem

    A workspace holds 5,000 conversation and ticket attributes in total, with 250 text attributes per ticket type. An account with years of ticket fields can reach that, and every attribute must exist before a value is sent.

    How we handle it

    We count the fields in use during scoping and agree with you which map one to one. The attributes are created from the approved mapping before the first conversation loads.

    Source: Intercom Help Center, checked 15 Nov 2026

  4. 04Handled

    Zendesk organizations without users have no contact to link to

    The problem

    Intercom cannot import companies by CSV, and a company shows only when a contact is linked to it, so a Zendesk organization with no end users would not appear.

    How we handle it

    Companies are created through the API and linked to their contacts. Organizations without users are listed in the report, and you decide whether they are kept.

    Source: Intercom Help Center, checked 15 Nov 2026

  5. 05Handled

    Intercom does not say whether past-dated conversations fire Workflows

    The problem

    No Intercom page says whether a conversation created with a past date triggers Workflows, emails or SLAs. Only tickets have a skip_notifications option.

    How we handle it

    Your Workflows are paused for the run. The sample goes through a test contact, so we see the behaviour on your workspace before any customer record is touched.

    Source: Intercom developer documentation, checked 15 Nov 2026

  6. 06Handled

    Large Zendesk attachments meet an undocumented base64 ceiling

    The problem

    A Zendesk email or web form attachment can be up to 50 MB. Intercom takes up to 10 attachment URLs on a message or base64 files, and its pages state no size ceiling for the base64 route.

    How we handle it

    We size every Zendesk attachment during export, send files through URLs where we can, and test the largest ones in the free sample. A file Intercom refuses is stored in your own storage and linked from the message.

    Source: Zendesk Help Center, checked 15 Nov 2026

Technical profile

What makes this route technical

Zendesk paces the export through plan limits and comments that must be read ticket by ticket, while Intercom accepts a conversation only from a contact and needs every attribute created before its values.

Exporting from Zendesk: request limits by plan
Zendesk allows 200 Support and Help Center API requests a minute on Team, 400 on Growth and Professional, 700 on Enterprise and 2,500 on Enterprise Plus. The High Volume API add-on lifts a qualifying plan to 2,500.

Source: Zendesk developer documentation, checked 15 Nov 2026

Exporting from Zendesk: incremental tickets without comments
The incremental ticket export returns up to 1,000 tickets a page at 10 calls a minute, or 30 with High Volume. Comment bodies arrive only when the ticket events export is asked for comment_events.

Source: Zendesk developer documentation, checked 15 Nov 2026

Exporting from Zendesk: comments 100 at a time
Zendesk lists a ticket's comments on their own endpoint, oldest first, at most 100 a page, so a long thread takes several calls.

Source: Zendesk developer documentation, checked 15 Nov 2026

Exporting from Zendesk: archived and deleted tickets
Zendesk archives a ticket 120 days after it is closed, and the list endpoints for tickets and for all audits skip archived tickets. The incremental export includes them, and also includes deleted tickets by default.

Source: Zendesk Help Center, checked 15 Nov 2026

Why the Zendesk export is not a source
Data exports are switched off by default and missing on Team plans. A CSV export omits comments, and an XML export is unavailable above 200,000 tickets.

Source: Zendesk Help Center, checked 13 Nov 2026

Exporting from Zendesk: side conversations
Side conversations need the Collaboration add-on, store their messages as events outside the comment list, and are listed ticket by ticket.

Source: Zendesk developer documentation, checked 15 Nov 2026

Importing into Intercom: a conversation starts from a contact
The create-conversation call accepts only a contact, user or lead, as the sender. It takes created_at in Unix seconds, which Intercom recommends for migrating past conversations, and it does not support HTML in the body.

Source: Intercom developer documentation, checked 15 Nov 2026

Importing into Intercom: agent replies come through reply calls
Later messages are added with the reply endpoint, as an admin, on behalf of a contact or as a note for admins. A reply on behalf of a contact takes created_at.

Source: Intercom developer documentation, checked 15 Nov 2026

Importing into Intercom: a ticket needs a ticket type
Creating a ticket through the API requires a ticket_type_id and takes one contact. It accepts created_at, and notifications can be switched off with skip_notifications.

Source: Intercom developer documentation, checked 15 Nov 2026

Facts checked 15 Nov 2026 against Zendesk and Intercom documentation. Each fact links its source.

Zendesk to Intercom questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

What migrates from Zendesk to Intercom?

Tickets move as Intercom conversations or tickets, end users as contacts, organizations as companies, agents as admins and groups as teams. Comments become conversation parts and notes, custom fields become data attributes, and Help Center articles move too.

Are Zendesk tickets mapped to conversations or to Intercom tickets?

Both, chosen per group of tickets. Tickets that began as a customer message become conversations, and tickets tracked by state become Intercom tickets, which need a ticket type. The split changes Intercom reporting, so it is agreed before the sample.

Do Zendesk attachments come across to Intercom?

Yes. Each Zendesk file is added to its message as an attachment URL (10 at most per message) or a base64 file. Intercom documents no base64 size ceiling, so the largest files are tested in the free sample.

Can I move tickets from Zendesk to Intercom and keep the original dates?

Yes. A new Intercom conversation, a contact reply and a ticket all accept created_at, so each message keeps its real time. Whether past-dated conversations fire Workflows is not documented, so Workflows are paused for the run.

What happens to Zendesk side conversations?

On request, each Zendesk side conversation is posted as a note on the parent Intercom conversation, with its participants and times in the text. Otherwise side conversations are not moved.

Can we use Zendesk's own export instead?

No. Zendesk's own export leaves comments out of CSV and has no XML above 200,000 tickets, and Intercom has no import for a Zendesk file, so tickets are read and written through both APIs.

Do Zendesk Help Center articles move to Intercom?

Yes. Zendesk categories and sections become Intercom collections and sections, and articles keep their published or draft state. Each author must be a teammate on your Intercom workspace, and redirects from old article addresses can be set.

How long does a Zendesk to Intercom migration take?

About 10 business days end to end. The export is paced by your Zendesk plan limit and per-ticket comment reads, and the load by the attributes and contacts that must exist first. The free sample shows the real pace.

What does a Zendesk to Intercom migration cost?

The price is set by what moves: tickets with their comments and attachments, custom fields, side conversations, organizations and Help Center size. A fixed quote arrives within 24 hours of the scoping call, after a free sample migration of 100 of your records.

How it compares

Four ways to run Zendesk to Intercom

The same data, moved four different ways. This is what changes between them.

Object coverage (cases, emails, comments, files, Knowledge)

  • MigrateX

    Every object in the mapping on this page, plus the ones you ask for during scoping.

  • Automated migration software

    Tickets and contacts are covered. Linked records, files and knowledge often are not.

  • Vendor CSV import

    One object per file, and only the fields the export template exposes.

  • In-house scripts

    Whatever you have time to build before the cutover date.

Public replies vs internal notes

  • MigrateX

    Each entry is posted separately, private stays private, public stays public.

  • Automated migration software

    Threads usually arrive, but per-entry author and visibility can be flattened.

  • Vendor CSV import

    Notes collapse into one field on the ticket, if they come across at all.

  • In-house scripts

    Possible, but it is the part teams most often run out of time for.

Attachments

  • MigrateX

    Uploaded against the right note, and re-hosted with a link when they exceed the Intercom cap.

  • Automated migration software

    Supported up to the destination cap. Oversize files are skipped.

  • Vendor CSV import

    Not carried by a CSV import.

  • In-house scripts

    Needs its own download, retry and upload pipeline.

Original IDs cross-referenced

  • MigrateX

    Every source id is stored on the destination record and handed back as a map.

  • Automated migration software

    Often kept as a tag or a single text field.

  • Vendor CSV import

    Lost once the file is imported.

  • In-house scripts

    Only if you design the mapping table up front.

Delta sync before cutover

  • MigrateX

    Included. Anything created or changed during the bulk pass is synced at cutover.

  • Automated migration software

    Usually a paid upgrade on the top tier.

  • Vendor CSV import

    You would re-export and re-import by hand.

  • In-house scripts

    Requires change tracking and idempotent writes on both sides.

Rate-limit handling

  • MigrateX

    Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.

  • Automated migration software

    Backs off, but a long run can still stall and leave partial records.

  • Vendor CSV import

    Not applicable, and the file size limits bite instead.

  • In-house scripts

    The most common reason a home-grown run dies overnight.

Validation report

  • MigrateX

    Counts per object and per status on both sides, with every default and placeholder listed.

  • Automated migration software

    A run log and an error list, rather than a reconciliation.

  • Vendor CSV import

    Row counts in a spreadsheet.

  • In-house scripts

    You write the reconciliation queries yourself.

Rollback plan

  • MigrateX

    Every write is tagged, so a batch can be reversed without touching your own records.

  • Automated migration software

    Some approaches can clear a migration, some cannot.

  • Vendor CSV import

    Manual cleanup of everything the import created.

  • In-house scripts

    Only if you built the tagging in from the start.

Who does the work

  • MigrateX

    A MigrateX engineer runs it and stays on the cutover call.

  • Automated migration software

    You run the software. Support answers tickets.

  • Vendor CSV import

    Your admins, one file at a time.

  • In-house scripts

    Your engineers, instead of your roadmap.

Guides

Guides for a Zendesk to Intercom migration

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    SOC 2 Type II

    Independently audited controls over how we handle your data.

  • GDPR compliant

    Data processing agreement available.

  • HIPAA compliant

    Business associate agreement available.

Start your Intercom move with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.