IntercomZendesk

Intercom to Zendesk migration

Migration specialists move your conversations, messages and internal notes into Zendesk, 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 · 14 object types mapped

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

Intercom to Zendesk at a glance

An Intercom to Zendesk migration turns conversations into tickets, contacts into end users and companies into organizations. The hard part is the read, because Intercom has no bulk export of message text. Intercom stays live until the final delta sync.

Objects mapped
14
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 leaving Intercom's conversational inbox for Zendesk's ticket queues, forms and reporting.
What does not move
Intercom Workflows, Series, bots, Fin AI Agent configuration, macros, Inbox views and reports stay behind, listed for your admin to rebuild in Zendesk.
What sets the scope
Conversation count, parts per thread, bot-authored parts, attachment volume, contacts without an email, and the number of Help Center collections and articles.

What moves

What moves from Intercom to Zendesk

Conversations become tickets, contacts end users, companies organizations and teammates agents, with customer and teammate messages as public comments, internal notes as private comments and Help Center articles as Zendesk articles.

  • 14 included
IntercomZendesk
  • Contacts (role user)End users

    Matched on email, with the Intercom contact id kept in a user field.

  • Contacts (role lead)End users

    Zendesk has no lead role, so the lead flag is kept in a user field. Leads without an email follow the rule agreed at mapping.

  • CompaniesOrganizations

    The Intercom company_id is stored in an organization field.

  • ConversationsTickets

    One ticket per conversation, with the subject taken from the conversation title or its first message. The conversation id goes to external_id.

  • MessagesPublic comments

    Author, original time and body are kept.

  • Internal notesPrivate comments

    Notes between teammates stay internal.

  • Assignments, state changes and bot stepsText line in a private comment

    On request. Otherwise they are left out of the ticket.

  • Tickets (Customer category)Tickets

    The ticket type becomes a ticket form or a tag, and ticket attributes become ticket fields.

  • Ticket statesTicket statuses

    Submitted and in progress become open, waiting on customer becomes pending, on hold becomes hold, and resolved becomes solved.

  • TagsTags

    Applied to the ticket, and to the end user where the Intercom tag sat on the contact.

  • Data attributesUser, organization and ticket fields

    Contact and company attributes become user and organization fields. Conversation and ticket attributes become ticket fields. All fields are created first.

  • Admins and teamsAgents and groups

    Admins are matched to agents by email.

  • ArticlesHelp Center articles

    You choose the author, permission group and user segment before they load.

  • Collections and sectionsHelp Center categories and sections

    The folder tree is rebuilt before any article is loaded.

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

What does not move

What does not move from Intercom to Zendesk as-is

Workflows, Series, bots, macros and Inbox views are configuration with no import path into Zendesk, so each is documented and rebuilt as triggers, automations and macros.

Back-office and Tracker ticketsOn request
In Zendesk: TicketsInternal-only tickets in Intercom. Whether they move, and as which form or tag, is agreed per account.
MacrosNot migrated
Intercom lets you export macro text, not import it. We document each macro so your team can rebuild it.
Workflows, Series and botsNot migrated
In Zendesk: Triggers and automationsIntercom states workflows cannot be transferred. They are listed and rebuilt as Zendesk triggers and automations.
Inbox views, reports and dashboardsNot migrated
In Zendesk: Views and ExploreRebuilt on the migrated fields. The Intercom conversation id is kept so old reports can be matched.
Fin AI Agent configuration and training contentNot migrated
Set up again by your team.
Apps, integrations and Messenger settingsNot migrated
Installed again in Zendesk. We hand over the list in use.

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

Scope my migration

Timeline

Intercom to Zendesk 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 how bot-authored parts are kept, what happens to contacts without an email, which collections and ticket types move, and the date range of history.

    • Connect both workspaces

      You0.5 day

      You give us an Intercom access token with read access and a Zendesk admin connection, because the Ticket Import API is open to admins only.

    • Field and status review

      Both1 day

      Data attributes to user, organization and ticket fields, Intercom ticket states to Zendesk statuses, and teams to groups. You approve the mapping we send.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      100 of your records, picked for the longest threads, the most bot-authored parts and the largest files, loaded into Zendesk end to end.

    • You review the sample

      You1 day

      Your team opens the tickets as an agent and checks comment order, private notes, authors, dates and attachments.

    • Full load

      MigrateX2-3 days

      Organizations and end users first, then tickets with their comments in bulk calls, then Help Center articles, paced to your Zendesk plan.

    • Delta sync

      MigrateX0.5 day

      Conversations that changed in Intercom since the full load are brought across, matched on the conversation id in external_id, so nothing is created twice.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Conversations against tickets by state and year, parts against comments, files against attachments, and every part handled by the bot rule.

    • Spot checks and sign-off

      You1-2 days

      Your leads check a random sample, and Intercom stays active and 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
  • 6 handled
  1. 01HandledMost critical

    The Intercom read sets the pace of the whole run

    The problem

    Intercom releases message text one conversation at a time, with extra paged requests for threads over 500 parts. The Zendesk load runs under its own, separate plan limit.

    How we handle it

    We list every conversation id first, read threads in parallel within your workspace's rate limit, and bulk-load each completed batch. The free sample times both sides on your data.

    Source: Intercom Help Center, checked 15 Nov 2026

  2. 02Handled

    Fin AI Agent and bot messages have no Zendesk comment type

    The problem

    An Intercom thread mixes customer messages, teammate replies, notes, assignments, state changes and messages written by the Fin AI Agent or a bot. Zendesk comments are only public or private.

    How we handle it

    At mapping we agree one rule for bot-authored parts: a public comment from an Intercom Bot user, a private comment, or left out. Assignments and state changes can be kept as a text line in a private comment.

    Source: Intercom developer documentation, checked 15 Nov 2026

  3. 03Solved

    Conversations have no ticket number, and Zendesk issues its own

    The problem

    Zendesk assigns every ticket its own id, which cannot be chosen. Without a link back, nobody can find the old Intercom thread from the new ticket.

    How we handle it

    The Intercom conversation id is written to the Zendesk ticket's external_id, so a search on the old id finds the new ticket.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  4. 04Handled

    Leads and visitors without an email do not fit a Zendesk end user

    The problem

    Intercom keeps leads and anonymous visitors beside signed-up users. Zendesk has no lead role, and an Intercom contact without an email cannot be matched to a Zendesk end user.

    How we handle it

    Contacts with an email become end users, with the lead flag in a user field. For contacts without one, you choose at mapping between a placeholder identity and leaving the conversation out.

    Source: Intercom developer documentation, checked 15 Nov 2026

  5. 05Handled

    Open conversations arrive without routing

    The problem

    Zendesk runs no triggers on an imported ticket that is not closed, until that ticket is next updated, so an open Intercom conversation would land unassigned and outside your SLA policies.

    How we handle it

    For each open Intercom conversation, the group, assignee and priority are agreed at mapping and set on the Zendesk ticket itself.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  6. 06Handled

    Bulk user import is off until Zendesk switches it on

    The problem

    Zendesk creates up to 100 users in one call, but bulk user imports are not enabled by default and return a 403 error until Zendesk Customer Support turns them on for the account.

    How we handle it

    We check it on the scoping call. If it is off, your admin asks Zendesk Customer Support to enable it before the sample, and users are created without a verification email.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  7. 07Handled

    Help Center articles lose their Intercom dates

    The problem

    Zendesk sets created_at and updated_at on Help Center articles itself. An article's author can be set, but the permission group and user segment must exist before the article loads.

    How we handle it

    We create the permission groups and segments you choose first, map each Intercom collection to a category or section, and list the original article dates in the reconciliation report. Subscribers are not emailed about the new articles.

    Source: Zendesk developer documentation, checked 15 Nov 2026

Technical profile

What makes this route technical

Intercom hands over message text only one conversation at a time, and Zendesk's Ticket Import API sets original dates but runs no triggers and keeps no metrics or SLAs on what it loads.

Exporting from Intercom: one request per conversation
Intercom has no bulk export of conversation text, in the interface or the Data Export API, so each conversation is requested on its own after its id is listed.

Source: Intercom Help Center, checked 15 Nov 2026

Exporting from Intercom: 500 parts a request
One conversation request returns the 500 most recent parts. A longer thread needs further paged requests to reach its oldest messages.

Source: Intercom developer documentation, checked 15 Nov 2026

Exporting from Intercom: file links expire in 30 minutes
Intercom links to Messenger files expire after 30 minutes and links to email attachments after about 6 months, so each file is copied during the read.

Source: Intercom Help Center, checked 15 Nov 2026

Importing into Zendesk: the Ticket Import API
The Ticket Import API runs as a background job for admins and accepts up to 100 tickets in one create_many call. It sets created_at, updated_at and solved_at on each ticket, and each comment carries its own created_at.

Source: Zendesk developer documentation, checked 15 Nov 2026

Importing into Zendesk: 5,000 comments a ticket
A Zendesk ticket holds up to 5,000 comments, public and private together, and an attempt to add more returns a 422 error.

Source: Zendesk developer documentation, checked 15 Nov 2026

Importing into Zendesk: no CC notifications
Zendesk sends no notification to users in CC on an imported ticket. Notifications start again on later updates to that ticket.

Source: Zendesk developer documentation, checked 15 Nov 2026

Importing into Zendesk: no metrics or SLAs on imported tickets
Zendesk metrics and SLAs are not supported for imported tickets, and Zendesk recommends tagging them and leaving them out of reports.

Source: Zendesk developer documentation, checked 13 Nov 2026

Importing into Zendesk: upload first, attach by token
Each file is uploaded to Zendesk first, and the returned token, valid for 60 minutes, is passed in the comment that carries it.

Source: Zendesk developer documentation, checked 15 Nov 2026

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

Intercom to Zendesk questions

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

Can I move Intercom conversations to Zendesk with their original dates?

Yes. Zendesk's Ticket Import API sets created_at, updated_at and solved_at on each ticket and created_at on each comment. Zendesk keeps no metrics or SLAs on imported tickets, so Intercom reply-time figures do not carry over.

What happens to Fin AI Agent and bot messages in Zendesk?

They follow one rule you choose at mapping: a public comment from an Intercom Bot user, a private comment, or left out, because Zendesk comments are only public or private.

How do Intercom leads and users become Zendesk users?

Users and leads with an email become Zendesk end users matched on that email, with the lead flag in a user field you can filter on. Contacts without an email get a placeholder identity or are left out, as you choose at mapping.

Do notes between teammates arrive as private comments?

Yes. Each Intercom internal note becomes a private comment on the Zendesk ticket, with its author and original time, so the requester never sees it.

Do Intercom Help Center articles and collections move to Zendesk?

Yes. Intercom collections and sections become Zendesk Help Center categories and sections. Zendesk sets article dates itself, so the originals are listed in the reconciliation report, and each article needs an author, permission group and user segment chosen first.

Will customers get emails when old conversations are loaded into Zendesk?

No. Zendesk sends no CC notifications on imported tickets and runs no triggers on imported tickets that are not closed. Notifications resume only when a ticket is next updated.

How long does an Intercom to Zendesk migration take?

About 10 business days end to end. The read is paced by one Intercom request per conversation, plus extra requests past 500 parts, and the load by your Zendesk plan limits and 100 tickets per bulk import call. The free sample shows the real pace.

What does an Intercom to Zendesk migration cost?

The price is set by what moves: conversations and their parts, tickets, contacts, companies, attachments and Help Center size. You get a fixed quote within 24 hours of the scoping call, after a free sample migration of 100 of your records.

How it compares

Four ways to run Intercom to Zendesk

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 Zendesk 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 an Intercom to Zendesk 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 Zendesk move with 100 of your records.

Scope my migration

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