Dialpad Migration: Move Numbers Without Losing Trust

Migrate into Dialpad 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 Dialpad 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 power dialer (Connect+) and CRM CTI (Connect+) 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

Dialpad migration takeaways

Numbers are the product — Dialpad is an AI-centred business communications platform. Dialpad Connect is the core cloud phone scored here (Standard list price Pro list price annual per user/month; Enterprise custom). Support (~list price) and Sell (~list price) are separate products and… 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, Slack, and Zoom on the Dialpad side — confirm the connectors your call and messaging loop depends on.
Watch packaging during cutover — Researched plans: Connect Standard, Connect Pro, Connect Enterprise, Dialpad Sell, Dialpad Support. Never invent list prices here — confirm seats, numbers/minutes, and quote terms on /pricing/dialpad/.

Dialpad migration map

Dialpad 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 weekDialpad 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

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

Inventory contacts, queues, calls, routing workflows, do-not-call numbers, and owners in the source tool.
Map each critical field to Dialpad (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 Dialpad import.

2. Pilot one queue — then scale

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

Choose one agent’s book or one priority queue (tens to low hundreds of records).
Import into Dialpad, 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 Dialpad, 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

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

Declare Dialpad 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 Dialpad.” Two violations restart the clock; week two is clean and they cut over.

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

Dialpad migration diagram 4. — Cut over to Dialpad 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 Dialpad.

5. Inventory what must move into Dialpad

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

Worked example: Teams that want AI transcription and call summaries included in the cloud phone licence 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 Dialpad passes non-admin proof. Name a rollback owner and maximum parallel window.

Worked example: Teams that want AI transcription and call summaries included in the cloud phone licence 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 Slack for Dialpad. Confirm which are native vs API before go-live.

8. Inventory what must move into Dialpad