How to Migrate Your Business Phones Without Missing a Call

A phone migration has one measure of success: your customers never notice. The sequence below is how we make that happen — whether the move is planned, or forced by a provider that stopped supporting its customers.

Step 1: Audit what you actually have

Before touching anything, inventory:

• Numbers — main lines, direct dials, fax, alarm/elevator lines, toll-free. Missing one here is how numbers get lost.
• Call flows — auto-attendant menus, ring groups, business hours, holiday rules, voicemail boxes. Recreate these from documentation, not memory.
• Hardware — every desk phone’s model and firmware, to decide what can be re-provisioned and what gets replaced.
• Integrations — CRM screen-pops, fax services, call recording, paging.

Step 2: Prepare the network first

Voice is unforgiving of a mediocre network. Before cutover, verify bandwidth headroom, configure QoS so voice outranks downloads, and make sure switches deliver PoE where phones need it — the full checklist here. This step, done early, prevents ninety percent of “the new phones are bad” complaints. (It’s also where our networking practice earns its keep.)

Step 3: Build the new system in parallel

Stand up the new platform — Zoom Phone or another hosted VoIP — completely, before any numbers move: users, call flows, voicemail, test numbers. Old and new systems run side by side, so testing happens with zero customer impact.

Step 4: Port on a schedule you control

Submit port requests once the new system is proven. Two rules:

1. Old service stays alive until every port confirms. Cancel-first is the classic self-inflicted disaster.
2. Pick a low-traffic cutover window — porting completes on a scheduled date, so aim it at a quiet morning, never a Friday afternoon.

If the losing provider is unresponsive, ports may need carrier escalation — budget extra time and get help early rather than after a rejection.

Step 5: Cutover day

The port completes; calls arrive on the new platform. The team that set it up should be watching live — testing inbound and outbound, checking each auto-attendant path, confirming voicemail delivery. Users get a one-page cheat sheet and someone to wave down. Done right, cutover is boring.

Step 6: Decommission deliberately

After a week or two of clean running: cancel old service in writing, keep the final invoices, and recycle retired hardware securely. Update the number anywhere it appears — website, Google Business Profile, signage, invoices.

When you can’t do it in this order

Provider already failing? The sequence compresses: secure numbers first, use interim routing to keep calls flowing, and rebuild on the new platform while ports process — the emergency version of this playbook exists for that.

GTech runs migrations end to end — audit through cutover — as part of our business phone systems service, with managed IT available for everything after. Free consultation: 805-979-9897.