Intercom migration

Intercom migration

Intercom is a customer service helpdesk with the Fin AI Agent built in. It keeps support as conversations made of parts, and beside them as tickets that carry a ticket type and a state. We move that history from Zendesk or Freshdesk into Intercom, or from Intercom into either of them, and scope other routes on a call.

Scope my migration

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

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

Read how we handle your data

Intercom migration at a glance

Who it is for
Support teams moving customer conversations into Intercom or out of it, and the consultants who run those projects.
What moves
Conversations with their messages and internal notes, tickets and ticket types, contacts, companies, tags, custom data attributes, teammates, teams and Help Center articles.
What does not move as-is
Workflows, Series, bots, macros, assignment rules, Inbox settings and Fin AI Agent configuration are configuration, so we list each one for rebuilding.
What sets the scope
Conversation count and thread length, the split between conversations and tickets, contacts without an email, attachment volume and Help Center size.

What moves

What moves from Intercom?

MigrateX moves Intercom conversations with every message and internal note, tickets with their ticket types, contacts, companies, tags, data attributes, teammates and Help Center articles.

  • Conversations
  • Conversation parts
  • Tickets
  • Contacts
  • Companies
  • Articles
  • Data attributes

What does not move

What does not move from Intercom as-is

Configuration, not data. We list each item in scope so your team can rebuild it in the target.

Workflows and Series
What we do: Intercom states that workflows cannot be transferred. We list each one with what it does, then it is rebuilt as triggers and automations in the destination, or as workflows when Intercom is the destination.

Source: Intercom Help Center, checked 15 Nov 2026

Bots and Fin AI Agent configuration
What we do: Bot steps, Fin AI Agent settings and its training content are configuration. They are documented for your team to set up again, and bot-authored messages in old threads follow a rule agreed at mapping.
Macros
What we do: Documented with their text and actions, then rebuilt by hand in the destination.

Source: Intercom Help Center, checked 15 Nov 2026

Assignment rules, Inbox settings and outbound messages
What we do: Intercom lists assignment rules and one-off or ongoing messages as items that cannot be extracted, so they are recreated from a list we hand over.

Source: Intercom Help Center, checked 15 Nov 2026

SLAs, reports and dashboards
What we do: No Intercom page documents an export or import route for them. We list each one, and your team rebuilds them on the migrated fields.
Help Center themes, apps and integrations
What we do: Set up again in the destination. We hand over the list of apps and integrations in use, so none is missed at cutover.
Assignment events, state changes and bot steps inside a thread
What we do: They are not messages. On request each one is kept as a plain text line in an internal note, otherwise it is left out.

What does an Intercom migration have to handle?

An Intercom migration has to decide whether each request becomes a conversation or a ticket, set original dates when records are created, create attributes before values, and pause live messages before contacts load. Each of these is agreed with your admin before the free sample.

The company is Fin, the platform is Intercom
The company behind Intercom was renamed Fin on 12 May 2026. Intercom remains the name of the customer service software platform.

Source: Intercom blog, checked 15 Nov 2026

Salesforce completed its acquisition of Fin
Salesforce completed its acquisition of Fin, formerly Intercom, on 10 September 2026.

Source: Salesforce website, checked 15 Nov 2026

A request is a conversation or a ticket
Intercom has both, and a migration picks one for every source record. A conversation can only be started by a contact. A ticket needs a ticket type and takes one contact. We agree the rule per group of tickets before the free sample, because the choice changes how the history reports in Intercom.

Source: Intercom developer documentation, checked 15 Nov 2026

Original dates are accepted on create
The create-conversation call takes created_at, and Intercom marks the field as meant for migrating past conversations from another source. Replies on behalf of a contact and new tickets take created_at too, and both use the current time when it is left out.

Source: Intercom developer documentation, checked 15 Nov 2026

Attributes exist before their values
Every custom attribute sent on a company or contact must already exist in the workspace, or the call returns an error. We create attributes from the mapping first, then load values. Conversation and ticket attributes are separate definitions with their own limit.

Source: Intercom Help Center, checked 15 Nov 2026

Imported contacts can receive live messages
Contacts who match the audience of a live outbound message receive it straight away after an import. Live messages are paused before the contacts load and switched back on after sign-off.

Source: Intercom Help Center, checked 15 Nov 2026

Attachment links expire during the read
Links to Intercom attachment files expire after 30 minutes for message files, or about 6 months for email attachments. Files are therefore copied while each conversation is read, not collected from a list afterwards.

Source: Intercom Help Center, checked 15 Nov 2026

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

Scope my migration

Migration paths

Where can I move to or from Intercom?

Routes we run from and into Intercom. Open a route to see what migrates, or ask us about one that is not listed yet.

From Intercom

Into Intercom

191 connectors, all live

Every connector is live, so Intercom can be paired with any of them. Some of the help desk platforms:

  • Salesforce Service Cloud
  • HubSpot Service Hub
  • Zoho Desk
  • Dynamics 365 Customer Service
  • Help Scout
  • Gorgias
  • Kustomer
  • Front
  • HappyFox
See all 191 connectors

Platform not listed?

We build new connectors in 2 to 3 days. Tell us what you run and we scope the route with you.

Timeline

Your Intercom migration, step by step

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

      A 30 minute call with the engineer who will run the migration, to agree the objects, date ranges and volumes in scope.

    • Connect both platforms

      You0.5 day

      You create scoped API credentials on the source and the destination. Nothing is written until you sign off the mapping.

    • Field mapping review

      Both1 day

      We walk through every field, status and group mapping with your team and note the ones that need a decision.

  2. Migration

    Day 3-7

    • Free sample migration of 100 records

      MigrateX1 day

      A sample of your real records is migrated end to end so you can see the result before the full run.

    • You review the sample

      You1 day

      Your team opens the migrated records and tells us what to adjust. We rerun the sample until it is right.

    • Full migration

      MigrateX2-3 days

      The bulk pass runs in dependency order, paced to the destination rate limit. Your team keeps working normally.

    • Delta sync

      MigrateX0.5 day

      Everything created or changed during the bulk pass is synced at cutover so nothing falls between the two systems.

  3. Validation

    Day 8-10

    • Validation report

      MigrateX1 day

      Record counts per object and per status on both sides, plus every record that needed a default or a placeholder.

    • Spot checks and sign-off

      You1-2 days

      Your leads check a random sample and sign off. We stay available for two weeks after go-live.

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

See how it works in detail

Data model

Intercom data model and limits

How Intercom holds the records that move, and the vendor limits that set the pace of the migration.

How does Intercom store support data?

Intercom stores a support request as a conversation made of conversation parts, or as a ticket with a ticket type and a state. Contacts, companies and data attributes sit around them, and Help Center articles sit in collections. A migration in either direction reads or writes each of these in a fixed order.

  • Contact

    What it holds
    A customer or prospect: email, name, external_id, custom attributes, signed_up_at and last_seen_at. A user has signed up; a lead has not.
    How it links
    Linked to companies, conversations, tickets, tags and notes. Only email is required to create one.

    Source: Intercom developer documentation

  • Company

    What it holds
    The account that contacts belong to, keyed on company_id, which cannot be changed later.
    How it links
    Loaded through the REST API, because CSV import cannot carry company data. Custom attributes sent with it must already exist.

    Source: Intercom developer documentation

  • Conversation

    What it holds
    A thread with a customer: its first message (source), contacts, tags, state and assignee.
    How it links
    Contains conversation parts and can be linked to tickets. Created when a contact replies or an admin sends a message.

    Source: Intercom developer documentation

  • Conversation part

    What it holds
    One message, internal note, assignment or state change, with part_type, body, author, attachments, external_id and created_at.
    How it links
    Child of one conversation. The body can contain HTML, and the author is a contact, an admin or a team.

    Source: Intercom developer documentation

  • Ticket

    What it holds
    A tracked issue with a state, in one of three categories: Customer, Back-office or Tracker.
    How it links
    Child of exactly one contact, with an optional linked conversation and company. Tracker tickets are internal only.

    Source: Intercom Help Center

  • Ticket type and ticket type attribute

    What it holds
    The fields a ticket carries. The default attributes are title and description.
    How it links
    Parent of tickets. A ticket type must exist before a ticket can be created through the API.

    Source: Intercom developer documentation

  • Ticket state

    What it holds
    Submitted, in progress, waiting on customer, on hold and resolved, plus custom states.
    How it links
    Used by tickets. Statuses from the previous platform are mapped onto these values.

    Source: Intercom developer documentation

  • Data attribute

    What it holds
    A custom field definition for contacts or companies. Conversation and ticket attributes are defined separately.
    How it links
    Applies to contacts, companies, conversations or tickets, and must exist before values are sent.

    Source: Intercom developer documentation

  • Article and collection

    What it holds
    Help Center articles with a title, body, author_id and state, in a folder tree of collections and sections.
    How it links
    An article points to its collection through parent_id. Its author must be a teammate.

    Source: Intercom developer documentation

  • Admin and team

    What it holds
    Agents and the groups they belong to.
    How it links
    Authors and assignees of replies. A reply can be sent as an admin, on behalf of a contact or as a note for admins.

    Source: Intercom developer documentation

Intercom objects that hold support data, as of November 2026. Source: Intercom developer documentation and help centre.

Which Intercom limits set the pace?

Intercom limits are set per workspace and per request, and several of them stop the built-in exports well short of a full history. These are the allowances that decide how fast conversations, tickets and contacts move into or out of Intercom, and which exports can carry message text.

  • API rate limit

    Allowance
    Private apps: 10,000 calls a minute per workspace, shared by all private apps. Public apps: 10,000 a minute each. Across all apps: 25,000 a minute per workspace.

    Source: Intercom developer documentation

  • Rate limit windows

    Allowance
    Enforced in 10-second windows, a sixth of the per-minute limit each. Going over returns 429 rate_limit_exceeded.

    Source: Intercom developer documentation

  • Page size

    Allowance
    Cursor pagination with starting_after, at most 150 per page. The default is 20 for conversations and 10 for the contacts list.

    Source: Intercom developer documentation

  • Parts per conversation

    Allowance
    Retrieving one conversation returns its 500 most recent parts. Older parts need page and per_page (1 to 500), read oldest first.

    Source: Intercom developer documentation

  • Companies list

    Allowance
    The list stops at 10,000 companies. Beyond that the Scroll API is required: one scroll per app, expiring after 1 minute unused.

    Source: Intercom developer documentation

  • Data Export API

    Allowance
    Exports delivery and engagement data for outbound content only, never conversation content. At most a 90-day range, two active jobs, and download links that expire after a week.

    Source: Intercom developer documentation

  • Dataset export

    Allowance
    CSV of reporting metadata with no message content: 10,000 rows in the browser, larger files emailed, about two years of data.

    Source: Intercom Help Center

  • Saved Inbox View export

    Allowance
    CSV export released on 28 August 2026. A view matching more than 100,000 conversations is refused, two exports run at a time, and the Can export conversation data permission is required.

    Source: Intercom Help Center

  • Inbox bulk export

    Allowance
    PDF or text for 200 to 300 conversations per operation, without internal notes.

    Source: Intercom Help Center

  • Amazon S3 export

    Allowance
    JSON, historical up to two years or periodic hourly or daily. Intercom's article says it does not contain a transcript.

    Source: Intercom Help Center

  • Attachment sizes

    Allowance
    Messenger uploads up to 100 MB a file. Incoming email is capped at 20 MB including attachments.

    Source: Intercom Help Center

  • Contact CSV import

    Allowance
    20 MB a file. Rows match on Intercom ID, then user_id, then email, and a mix of email and user_id can create duplicates.

    Source: Intercom Help Center

  • Conversation and ticket attributes

    Allowance
    5,000 in total per workspace, with 250 text attributes per ticket type.

    Source: Intercom Help Center

  • Files on a new message

    Allowance
    Up to 10 image URLs as attachment_urls, or base64 attachment_files with content_type, data and name.

    Source: Intercom developer documentation

Intercom limits that shape a migration, as of 15 November 2026. Source: Intercom developer documentation and help centre, linked per row.

Facts checked 15 Nov 2026. Sources: Intercom blog, Salesforce website, Intercom developer documentation and Intercom Help Center.

Intercom migration questions

Still unsure? Ask us on the scoping call.

What does an Intercom migration cost?

The cost of an Intercom migration follows the conversations in scope, how many messages each thread holds, the tickets and ticket types, the contacts and companies, and the size of the Help Center. Before any commitment, 100 of your records are migrated free, then a fixed quote arrives within 24 hours.

How long does an Intercom migration take?

The default plan is about 10 business days end to end. Reading from Intercom takes one request per conversation, plus extra requests for threads past 500 parts, so the pace follows your conversation count and thread length. Into Intercom, the pace follows the rate limit of the platform you are leaving. The free sample measures it on your data.

How do I export Intercom conversations with their message text?

Through the Conversations API: list the conversation ids, then request each one. Intercom has no bulk export of conversation text in the interface or the Data Export API, and its CSV and S3 exports leave the message text out. MigrateX reads every conversation with its parts, and the workspace stays active until you sign off.

Can I export Help Center articles and macros from Intercom?

Articles, yes, through the Articles API, which lists 25 per page by default and 250 at most. Macros can be exported as an emailed CSV with a body_plain_text column, but Intercom has no feature to import them again. Articles move with their collections, and macros are rebuilt by hand in the destination.

Why does importing users into Intercom not create companies?

Intercom's CSV import cannot import company attributes or company data, so companies load through the REST API instead. Contacts load first and companies second, and each contact is linked to its company. Whether Intercom lists a company that has no linked user is confirmed during your free sample.

Can I move Intercom conversations to another Intercom workspace?

Not with Intercom's own features. Its help centre says exported conversation data cannot be loaded into a new workspace, and that open conversations cannot be moved between workspaces. Workspace-to-workspace moves are scoped on a call, because the answer depends on the data and the regions involved.

Which Intercom region and access do you need?

We need an access token for your workspace, and its region sets the API host: api.intercom.io for the United States, api.eu.intercom.io for the European Union and api.au.intercom.io for Australia. Intercom's pages do not say which plan includes API access, so we check your plan on the scoping call. MigrateX is SOC 2 Type II, GDPR and HIPAA compliant.

Do we have to stop using Intercom during the migration?

No. The export only reads from your workspace, and a delta sync after the full run copies every conversation and ticket that changed in the meantime, so the switch happens in one planned window. Keep the workspace active after cutover until the reconciliation report is signed off.

Guides

Guides for an Intercom migration

Start with 100 of your records.

Scope my migration

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