Switching Call Tracking Providers: A Migration Guide That Does Not Drop Calls

Nobody migrates call tracking platforms for entertainment. It happens because a bill got unpredictable, a feature was needed and priced as an add-on, or support went quiet during an outage. And then the migration stalls, sometimes for years, because of one specific fear: what if we drop a call?

That fear is legitimate. A dropped lead is real money and, for emergency services, a real customer in a bad situation. But it is also entirely avoidable. Done in the right order, a call tracking migration never has a moment where a published number is unreachable.

Here is the sequence.

Before anything: export your history

Do this first, before you evaluate anything, because it is the only step that is irreversible if skipped.

When you cancel a call tracking account, your data goes with it — usually within a short window, and support cannot bring it back. Export:

• The full call log as CSV. Every call, with timestamp, tracking number, source attribution, campaign, caller number, duration, outcome, and any custom fields or tags.
• Recordings you are required to retain, or want for training and dispute evidence.
• Transcripts, if the platform stores them separately from recordings.
• Configuration, as documentation: number-to-source mappings, routing rules, business hours, IVR trees, notification rules, and integration settings. You will need every one of these to rebuild, and reading them off an expiring dashboard on cutover day is a bad plan.

Understand upfront that historical data does not migrate as native history. No platform ingests a competitor's call log into its own reporting. Your archive lives as CSVs and files alongside the new system. Plan your year-over-year comparisons accordingly.

A note on recordings: if you operate under all-party consent rules in any state you take calls from, your retention obligations do not disappear because you changed vendors. Check what you are required to keep and for how long before you delete anything — see the call recording consent laws guide.

Understand which numbers actually need porting

This is where migrations get overcomplicated. Not every tracking number needs to move.

Sort your numbers into three buckets:

Bucket	Examples	Action
Published and hard to change	Google Business Profile, printed materials, vehicle wraps, directory citations, signage	Port. These are known to customers and third parties.
Published and easy to change	Website static numbers, ad extensions, email signatures	Provision new, update the reference, retire the old.
Pool numbers	DNI rotation pool, session-level numbers	Do not port. Nobody has these memorized. Provision a fresh pool.

For most businesses this cuts the porting job dramatically. A company running a 15-number DNI pool plus three location profile numbers and one van-wrap number needs to port four numbers, not nineteen. Everything else is provisioned new in an afternoon.

The pool sizing for the new platform is worth revisiting rather than copying — most incumbent pools were sized under per-minute cost pressure and are too small. The arithmetic is in how many tracking numbers do I need.

The three-week sequence

Week 1 — Build in parallel, change nothing

Nothing customer-facing changes this week.

1. Provision the new pool and any new static numbers on the new platform. Forward them to the same destinations your current numbers use.
2. Install the new tracking script alongside the existing one. Two DNI scripts on one page will fight over which number displays, so configure the new one in a passive or reporting-only mode if the platform supports it, or scope it to a staging or low-traffic subset of pages first.
3. Rebuild configuration from the documentation you exported: routing, business hours, notification rules, spam filters, scoring thresholds, integrations.
4. Wire integrations but leave uploads OFF. Connect Google Ads, Meta, GA4, and your CRM, but do not enable conversion uploads yet. The old platform is still uploading; two systems uploading against the same conversion action is a guaranteed double-count.

Week 2 — Parallel run and reconcile

Both platforms now see traffic. Compare them daily.

The reconciliation questions:

• Do total call counts match? A small gap is normal — platforms differ on whether they count sub-ring abandons. A gap over about 5% means something is misconfigured.
• Does source attribution agree? If the old platform says 62% of calls are paid search and the new one says 41%, one of them has a tagging problem. Usually it is a parameter mapping in the new setup, and this is precisely why you run in parallel.
• Are recordings capturing cleanly? Spot-check for audio quality, correct announcement playback, and that both legs are captured.
• Are notifications firing to the right people? Missed-call alerts silently not firing is a nasty discovery to make after cutover.

Do not skip or shorten this week. It is the entire safety mechanism. If the parallel run reveals a discrepancy you cannot explain, extend it — the incumbent is still catching every call, so there is no urgency and no risk in waiting.

Week 3 — Port, cut over, and verify

Now, and only now, make customer-facing changes.

1. Submit the port request for your published numbers. You will need: the exact account name and service address on file with the losing carrier, the account number, and often a PIN or a recent bill copy. Any mismatch — a suite number, a dba versus legal name — gets the port rejected and restarts the clock. Ports take business days; schedule them mid-week, mid-morning, never on a Friday afternoon.
2. Keep old numbers live until the port completes. Do not cancel the old account before the port lands. Cancelling releases the number and the port fails permanently — that is the one genuinely unrecoverable mistake in this process.
3. Switch the tracking script to the new platform as the active DNI source, and remove the old one.
4. Flip conversion uploads in a single change: disable the old platform's upload, enable the new one. Then check Google Ads the next day. Conversion volume should be roughly stable. Doubled means both are running; zeroed means neither is. The integration mechanics are in call tracking + Google Ads integration.
5. Update citations and profiles for any number that changed rather than ported: Google Business Profile, directories, ad extensions, email signatures. For the profile-specific rules, see Google Business Profile call tracking.
6. Wait one full week before cancelling the old account. Confirm the ported numbers are ringing on the new platform, confirm recordings and integrations are healthy, then cancel. Confirm your export is complete one more time before you do.

The five mistakes that cause real damage

1. Cancelling before the port completes. The number is released and gone. Unrecoverable.
2. Skipping the export. Two years of call history and recordings deleted, with no restore path.
3. Running both conversion uploads simultaneously. Google Ads conversions roughly double, Smart Bidding recalibrates on fiction, and it takes weeks to unwind.
4. Porting the DNI pool. Weeks of avoidable paperwork for numbers nobody has ever memorized.
5. Migrating during peak season. Move during your slowest month. An HVAC company should not migrate in July.

What to actually evaluate before you commit

Since you are already doing the work, evaluate on the things that made you leave rather than on feature-checklist parity:

• Pricing model. Per-minute billing makes your bill scale with success and quietly encourages recording less and analyzing less — degrading the data you bought the platform for. Flat rate makes the cost predictable. The trade-offs are compared in per-minute vs flat-rate call tracking pricing and totalled up in call tracking software cost per month.
• What is included versus an add-on. AI lead scoring, intent detection, transcription, and automation are core capabilities, not premium extras. On CallFlux, recording, transcription, and AI call summaries are on Starter ($99/mo); AI lead scoring, intent detection, keyword tracking, the automation rules engine, and Google and Meta integrations are on Growth ($249/mo); Pro is $499/mo. Tracking numbers are $1.15/mo local and $2.15/mo toll-free, with unlimited calls at every tier.
• Integration depth. Confirm it does GCLID capture and offline conversion upload, not just a Zapier hook.
• Agency features, if relevant — sub-accounts, white-labelling, and client reporting. See white-label call tracking for agencies.

Direct comparisons are in best call tracking software, CallFlux vs CallRail, vs WhatConverts, and vs CallTrackingMetrics.

Frequently Asked Questions

Can I keep my phone numbers when switching call tracking providers?

In the United States, yes — number portability is a regulatory right, and tracking numbers port between providers the same way any business line does. The practical constraints are that the losing provider must not have the number locked or the account in arrears, the account details on the port request must match the existing carrier record exactly, and porting takes business days rather than hours. Numbers you no longer need do not have to be ported; only port the ones published somewhere you cannot easily change.

How long does a call tracking migration take?

Plan three weeks end to end for a typical single-brand setup. Roughly: week one to provision new numbers, install the new script, and run both platforms in parallel; week two to validate that both are recording the same calls and reconcile any discrepancy; week three to port published numbers, cut over conversion integrations, and decommission the old platform. Complex multi-location or agency accounts should plan four to six weeks.

Will I lose my historical call data when I switch?

You lose it only if you fail to export it before the account closes. Before cancelling, export the full call log as CSV — timestamps, source attribution, duration, outcome, and any custom fields — and download recordings and transcripts you are required to retain or want to keep. Most providers delete data shortly after cancellation, and support will not restore it. Historical data does not import into a new platform as native history, so keep it as an archive alongside the new system.

What is a parallel run and why does it matter?

A parallel run means both the old and new platforms track calls at the same time for one to two weeks before you commit. It is the only way to prove the new setup is capturing everything before the old safety net is removed. It also gives you an overlap period for reconciling call counts, verifying attribution matches, and catching configuration mistakes while calls are still being caught by the incumbent.

Do I have to redo my Google Ads conversion setup?

Partly. The conversion action in Google Ads can usually stay, but the integration that uploads to it must be repointed at the new platform, and the two must never upload simultaneously or you will double-count. The safe sequence is to keep the old upload running during the parallel run with the new one disabled, then switch them in a single change and verify the next day that conversion volume is stable rather than doubled or zeroed.

What is the main reason businesses switch call tracking providers?

Cost predictability is the most common trigger. Per-minute pricing means the bill scales with success, so a good month produces an unwelcome invoice and teams start rationing recording and AI analysis to control spend. The second most common is feature gaps — needing AI lead scoring, intent detection, or automation that the incumbent charges as an expensive add-on. Poor support responsiveness during outages is a distant but decisive third.

Three weeks, zero dropped calls

Export first. Port only what is published. Run in parallel until the numbers agree. Cut over integrations in a single change. Cancel last.

Follow that order and the migration is uneventful, which is exactly what you want from it.

Compare pricing, read the FAQ, or book a demo — we will map your current number inventory and tell you which ones actually need porting.