Intercom Migration: Move Numbers Without Losing Trust

Migrate into Intercom with a number inventory, route map, pilot cutover, dual-run week, and CRM CTI validation — so calls keep routing and agents trust the logs.

By Lee M.Updated Aug 17, 20266 min readFact-checked

Quick answer

Migrate into Intercom with a list inventory, field map, pilot import, dual-run week, and CRM CTI / call logging validation — then cut over only when the sales + support team trusts the contacts. Confirm cloud phone (Essential+) and sms messaging (Essential+) are on the package you will actually buy. Prove one queue before you move the whole book of numbers and IVR / routing.

Inventory numbers and IVR / routing
Map fields and owners
Pilot one queue
Dual-run one week
Validate CRM CTI / call logging
Then cut over

Intercom migration takeaways

Numbers are the product — Intercom is an AI-first customer messaging and shared-inbox platform: Messenger, tickets, help center and Fin AI Agent on Essential/Advanced/Expert seats. First-party pricing on intercom.com/pricing (checked 2026-08-17) publishes Essential list price Advanced… A migration that moves rows but breaks do-not-call numbers or owners will burn seats/numbers and trust.
Pilot before bulk — One agent’s book or one priority queue first — fix mapping before volume.
CRM stays the system of record — Research names Salesforce, HubSpot, Zendesk, Shopify, and Slack on the Intercom side — confirm the connectors your call and messaging loop depends on.
Watch packaging during cutover — Researched plans: Essential, Advanced, Expert, Fin AI Agent. Never invent list prices here — confirm seats, numbers/minutes, and quote terms on /pricing/intercom/.

Intercom migration map

Intercom checklist

Bring these questions to every demo

Ask vendors to show the workflow live, not just describe it.

1Inventory source objectsNumbers, IVR / routing, routing books, do-not-call numbers, owners.
2Sign off the field mapTitles, emails, phones, owners, do-not-contact.
3Run a pilot importOne queue; fix mapping before bulk.
4Dual-run one weekIntercom is write-path; old tool is read-only.
5Validate with the sales + support teamSpot-check contacts and CRM CTI / call logging before cutover.

1. Inventory numbers and map fields before any import

Intercom migration diagram 1. — Map meanings and owners before volume into Intercom.

Inventory contacts, queues, calls, routing workflows, do-not-call numbers, and owners in the source tool.
Map each critical field to Intercom (and to CRM where sync will write).
Decide archive-only fields — do not invent destinations for junk.
Remap departed owners to living users before volume. Worked example: an 8-person sales + support team discovers 14% of open routing steps still owned by a departed agent; they remap those owners in the sheet before any Intercom import.

2. Pilot one queue — then scale

Intercom migration diagram 2. — Fix mapping on one Intercom queue before you scale.

Choose one agent’s book or one priority queue (tens to low hundreds of records).
Import into Intercom, then spot-check numbers, routes, owners, and do-not-call numbers.
Run one softphone and routing session from the pilot set.
Confirm CRM received the activities before approving bulk. Worked example: an 8-person sales + support team pilots Sam’s mid-market queue into Intercom, finds two title mappings wrong, fixes the map, and only then schedules the full import.

3. Dual-run one week with a hard write rule

Intercom migration diagram 3. — One dual-run week is enough if Intercom is truly the write path.

Declare Intercom the write path for new numbers and calling.
Old tool becomes read-only history — no new live traffic there.
If anyone starts new live traffic in the old tool, restart the dual-run week.
End the week with agent sign-off on 20 random contacts. Worked example: an 8-person sales + support team prints the rule on Slack: “New live calls only in Intercom.” Two violations restart the clock; week two is clean and they cut over.

4. Cut over after CRM CTI / call logging and team validation

Intercom migration diagram 4. — Cut over to Intercom only after the sales + support team trusts contacts and CRM CTI / call logging.

Validate CRM CTI for call creates and activity logging.
Freeze legacy write access.
Archive or export legacy numbers you still need for audit.
Schedule the first post-cutover usage review. Worked example: an 8-person sales + support team cutovers only after Priya and Sam each confirm five contacts and their last calling appear correctly in CRM from Intercom.

5. Inventory what must move into Intercom

List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.

Worked example: Support teams that want Messenger + shared inbox + Fin AI in one CS platform migrates active records only and archives the rest as read-only exports.

6. Run parallel cutover with a rollback path

Keep the old system read-only until Intercom passes non-admin proof. Name a rollback owner and maximum parallel window.

Worked example: Support teams that want Messenger + shared inbox + Fin AI in one CS platform caps parallel run at two weeks with daily checkpoint notes.

7. Verify counts and permissions after import

Reconcile user counts, role permissions, and a sample of migrated records. Research lists Salesforce, HubSpot, Zendesk, and Shopify for Intercom. Confirm which are native vs API before go-live.

8. Inventory what must move into Intercom