VoIP Migration Testing Checklist for U.S. Businesses

So your carrier sent a notice that your copper phone service is changing, and your calls are moving to a new service. The new lines work, your team can call out, and the provider says you're done. Are you? Not until you've checked what customers experience. Call every published business number from an outside phone, follow the call to wherever it lands, and test any menus, transfers, voicemail, and after-hours rules. Do it again after the numbers move, and give every failure an owner before anyone signs off.

This is happening now, not someday. AT&T said on October 19, 2026 that it has already discontinued copper services in more than 500 communities, and it aims to exit copper across most of its footprint by the end of 2029. That's AT&T's own goal, not a nationwide deadline. Your real date depends on your carrier and your service address, so go by the notice you received.

Which customer numbers and call routes must keep working?

Before you test anything, write down four things: the affected service address, the change date from your notice, the replacement service, and who's handling the transition on each side.

Then list every number a customer might dial:

• The main number on your website and contact page
• Support, billing, and sales lines
• Numbers on invoices, receipts, and packaging
• Numbers in ads, directory listings, and email signatures
• Older numbers you still forward, even if nobody remembers why

For each one, ask the team that answers it where the call should land. Don't assume. Whoever set up the old system may have had a different idea than the people picking up today.

Put it all in a simple test sheet:

One row per scenario. It looks tedious. It's also what saves you from a customer email that starts with "I've been trying to call you for two days."

What can you test before the service change?

First, know what's actually changing. Losing copper access, porting your numbers, and switching to a new calling platform are related but separate moves, and you may not need all three. Verizon, for example, says replacement options can include fiber, wireless, or VoIP service, and that you can port your numbers to another Verizon service or a different provider. Check what's offered at your address before you shop for a whole new phone system.

If you are moving to a new provider, two things help before cutover:

1. Test on a pilot number. If your provider supports a pilot or temporary number, build your routes on it and run your test sheet there first. Microsoft's migration guide uses this approach, then has you call every migrated number to confirm it reaches the right person or queue.
2. Line up the port details. Porting usually needs account details that match your current carrier's records. Vonage, for example, asks for an active account and info from a recent bill or customer service record. Confirm the port is eligible and agree on a transfer date with the new provider.

While you're at it, check what else at that address runs on the same copper lines. Alarm panels, fax machines, and card terminals are easy to forget until they stop working.

Do phone menus, extensions, and transfers reach the right people?

If you only have a basic line, keep it simple: call in from outside, check where it rings, check voicemail if you use it, and call out to confirm your caller ID shows your business number. Only add the tests below for features you actually have.

If you have an IVR, the automated phone menu that greets callers and routes them by keypress, test more than "press 1." Zoom's IVR settings, for example, set a separate route for each key, plus separate handling for callers who press nothing or press a key that isn't on the menu. For each menu, try:

1. Every listed option. The greeting should match where you land. A "Thanks for calling billing" message that rings the warehouse is a fail.
2. No input. Stay silent and see what happens after the timeout.
3. An invalid key. Press 9 on a menu that only goes to 4.
4. Extensions and transfers. Dial an extension directly, then have whoever answers transfer you to another team.

Takes a while, sure. Still faster than explaining to your best customer why billing kept ringing the stockroom.

Do after-hours, voicemail, and overflow routes work correctly?

Schedules decide where calls go, and nobody notices a broken one until Saturday. Zoom Phone auto receptionists, for instance, keep separate settings for time zone, business hours, closed hours, and holidays. Test each one:

• Open hours: calls reach live people or the right queue.
• Closed hours: the after-hours greeting plays and messages go somewhere someone checks.
• Holidays: the holiday schedule exists and actually kicks in.
• Voicemail: leave a message, then confirm someone can find and play it back.

Two warnings from people who've done this. Check the time zone for each location: if the system thinks you're on Pacific time and you're in New York, customers hit "we're closed" at 2 p.m. And check where voicemail goes. A box that sends messages to a former employee's inbox looks fine to callers and fails silently for months.

Still with us? Good. The next part is where most "it worked in testing" surprises come from.

Queue problems sound like one scenario, but they're usually several. Microsoft Teams call queues handle a full queue, a caller who's waited past the limit, and no agents signed in as separate rules. Busy agents don't necessarily count as "no agents." Test each one using the limits you configured.

Outage fallback is something else again: what happens when the internet connection or the phone service itself goes down. Check what it actually covers. Vonage's Call Continuity, for example, covers lost connectivity at an extension but excludes virtual receptionists, call groups, and call queues. If your main number points to one of those, ask your provider what happens during an outage.

For disruptive tests like these, use a test route or an agreed maintenance window. Please don't unplug the office router mid-afternoon.

What must you retest once the new service is live?

A pilot proves your setup works. It doesn't prove your real numbers landed in the right place. Once the new service is active or the port completes:

1. Get port completion in writing. Have the new provider confirm the port is done before you cancel anything with the old carrier.
2. Check the rest of the old account. Ask what happens to any other services billed on it, like extra lines or internet.
3. Rerun the whole test sheet on the real public numbers, from an outside phone, during open, closed, and holiday hours.
4. Make an outbound call and confirm your business number shows as the caller ID.

What evidence should you require before signing off?

A migration isn't finished because the provider says so. It's finished when your test sheet comes back clean, or every failure has a name next to it.

1. Pick one person to approve the migration, usually the office manager or IT lead.
2. Give every failed test an owner, whether that's your team or the provider.
3. Schedule a retest for each fix and log the result on the same sheet.
4. Don't sign off until the main number, every menu option, and the after-hours route all pass on the real numbers.
5. Keep the sheet. It's your starting point the next time anything changes.

One scope note: this checklist covers ordinary customer calls. Fire alarms, elevator phones, fax machines, card terminals, and emergency lines often run on copper too, and they need their own provider or specialist testing. For more on that side, read our guide on elevator phones and copper retirement.

Frequently asked questions

How do I find the change date for my U.S. business location?
Check the notice your carrier sent for that service address. Dates vary by carrier and location, so a national news headline won't tell you yours. If you can't find the notice, call your carrier's business support and ask for the date at that address.

Can I keep my business phone number when changing providers?
In many cases, yes. Verizon, for example, says customers can port their numbers to another provider. Confirm eligibility and the transfer date with the new provider before you cancel the old service.

Does one successful test call prove every route works?
No. One call tests one path. Menus, transfers, after-hours rules, queues, and voicemail each follow their own route, so each needs its own test on every published number.

Is queue overflow the same as internet-outage fallback?
No. Overflow handles busy conditions while the system is working, like a full queue or a long wait. Outage fallback covers what happens when the connection or service fails. Some fallback features don't cover queues or auto attendants at all, so check with your provider.

Does leaving copper require a new hosted phone system?
Not necessarily. Your carrier may offer fiber, wireless, or VoIP replacements for the same line. Check what's available at your address and what features it includes before you buy a new platform.

Official resources

• AT&T: Network modernization update (Oct 19, 2026)
• Verizon: Copper service update
• Vonage: Transfer phone numbers
• Microsoft: Migration guide
• Microsoft Teams: Set up a call queue
• Zoom Phone: Auto receptionist settings
• Zoom Phone: IVR configuration
• Vonage: Call Continuity

Comments? Questions? We got you covered!