What Happens to Your Call Tracking the Day You Switch Phone Systems

09 October 2026·6 min read

Quick answer: Switching phone systems is one of the most common ways businesses accidentally lose months of call tracking data, because tracking numbers, call recording and the GA4 or ad-platform events wired to the old system rarely move across automatically. Nothing throws an error — your phones still ring, calls still connect — but the data trail showing which ad, page or campaign drove each call can quietly go dark. Running a short pre-migration checklist, and testing a live call end-to-end before you fully cut over, is what catches it before go-live instead of three weeks later. 📈

Everyone plans the exciting parts of a phone system switch: new handsets, better call quality, maybe a cheaper monthly bill. Almost nobody plans the unglamorous plumbing underneath — the tracking numbers, the webhooks, the little integration that tells your analytics which campaign actually made the phone ring. We love a good upgrade 💖, but the upgrade itself was never the risky part. The risky part is the week either side of go-live, when the old system is being switched off and the new one is still half-configured, and call data has nowhere reliable to land.

What most businesses get wrong

The common assumption is that call tracking "just comes with" whatever phone system you're on, so migrating phone systems is treated purely as an IT and handset exercise — ported numbers, new extensions, a training session on the new dashboard. Call tracking numbers, GA4 conversion events and any ad-platform call conversion imports are rarely on that migration checklist at all, because they were set up once, years ago, by whoever ran the original campaign, and nobody currently on the team remembers they exist. The result is a gap nobody's looking for: calls keep coming in, the new phone system logs them happily, and everything looks fine operationally — while the marketing reporting slowly stops reflecting reality.

The Pre-Migration Call Tracking Checklist

Two to four weeks before go-live:

— List every tracking number currently in use (website, Google Business Profile, each ad platform, printed material) and confirm which ones need to port vs which can be retired.
— Confirm with the new provider, in writing, that number porting includes call forwarding rules and whisper messages, not just the raw number.
— Export call history and recordings from the old system — don't assume historical data carries over.
— Identify every place a tracking number's call events feed into: GA4, Google Ads conversion imports, Meta, any CRM webhook.

Week of go-live:

— Re-point each GA4 call event / conversion to fire from the new system's call data source, and republish before cutover, not after.
— Update Google Ads and Meta call conversion integrations to pull from the new system.
— Schedule the cutover for a low-traffic window (early morning, weekend) in case of hiccups.

Day of go-live — test before you trust it:

— Place a real test call to each ported number from an external phone and confirm it rings through correctly.
— Confirm the test call appears in the new system's call log within a few minutes.
— Confirm the test call appears in GA4 real-time reporting as the correct event.
— Check that call recording and whisper messages are working, not just call connection.

First week after:

— Compare daily call volume in the new system against the old system's recent average — a sudden drop usually means a porting or forwarding issue, not fewer customers.
— Check GA4 call conversions daily for the first week, not just at month-end reporting.

The number that ported but lost its forwarding rule: A business switches providers and the main tracking number ports successfully — calls still connect fine. But the specific forwarding rule that routed after-hours calls to a mobile doesn't carry across, so every call outside business hours quietly goes to a dead line for two weeks before a customer mentions it.

The GA4 event that pointed at the old system: The GA4 call conversion event was built around the old provider's webhook format. After migration, calls still happen, the new system logs them fine, but GA4 shows zero call conversions for three weeks — not because leads dried up, but because the event is still listening for data in a format that no longer arrives.

The recording feature nobody re-enabled: Call recording was switched on in the old system by default; in the new system it's an opt-in setting buried in an admin menu. A month goes by before someone goes looking for a recording to settle a customer dispute and discovers none exist.

How to actually do this

The single highest-leverage habit here is testing with a real external call before you consider the migration finished — not a test from an internal extension, an actual call from a mobile outside the building, to every tracking number you rely on. Walk it all the way through: does it ring the right place, does it get recorded, does it show up in GA4 within a reasonable window? If any one of those breaks, you want to know on day one with low traffic, not in week three when a client asks why the phone enquiry report looks wrong.

It also pays to nominate one person as the "data owner" for the migration, separate from whoever's handling handsets and desk phones. Their only job is confirming the marketing and analytics side survives the switch — porting the number is an IT task, but re-pointing GA4 and the ad platforms is a marketing task, and migrations go wrong most often in the gap between those two teams, where everyone assumes the other side has it covered.

💡 Keep the old system live in read-only mode for at least a month. Even with a clean migration, you'll want to compare historical call data against the new system while reporting season rolls around — don't let the provider delete your old account the moment you stop paying for it. A short overlap period costs little and saves you from a reporting gap you can't backfill.

Treating the migration as an IT project only, with no one responsible for analytics continuity.
Assuming number porting automatically includes forwarding rules, whisper messages and call recording settings.
Re-pointing GA4 events after go-live instead of testing them before you flip the switch.
Deleting the old system's historical call data the moment the contract ends.
Only checking that calls connect, without checking that they're still being tracked.

Frequently asked questions

How far in advance should we start this checklist?

Two to four weeks is realistic for most small businesses — enough time to confirm porting details with the new provider and re-point analytics events without rushing it the night before cutover. Larger or multi-location setups should allow longer.

Can our phone provider just handle all of this for us?

They can handle the number porting and call routing, but most providers won't touch your GA4 setup or ad platform integrations — that's marketing infrastructure, not telephony, and it's rarely in scope for a phone system vendor even when they seem helpful during the sales process.

What's the honest trade-off of testing this thoroughly before go-live?

Thorough testing takes real time — usually a few hours spread across the week before cutover — and it can feel like overkill when the new system "obviously works" in a demo. The trade-off is worth it almost every time, but we won't pretend it's free: someone has to actually place test calls and watch GA4 in real time, not just tick a box.

What if we only notice the gap after it's already happened?

You can often reconstruct roughly what happened by comparing call volume trends before and after the switch, even without exact event data, which at least tells you whether it was a tracking gap or a genuine drop in enquiries. It's not a full fix, but it stops you making decisions based on a number that was never real in the first place.

Keep reading 🤍

Written by

Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦