VoIP Migration Best Practices: How to Move Off POTS Without Disrupting Your Business
Back to Blog
VoIPPOTS replacementbusiness phone systemsunified communicationstelecom migration

VoIP Migration Best Practices: How to Move Off POTS Without Disrupting Your Business

The copper phone network is going away. Carriers are retiring POTS lines market by market, and businesses that haven't planned their migration are increasingly finding themselves scrambling when a discontinuation notice arrives. If you've decided VoIP is the right path forward — and for most businesses, it is — the question isn't whether to migrate. It's how to do it without dropping calls, losing numbers, or taking your operations offline during the cutover.

This guide covers the practical steps, common pitfalls, and decision points that determine whether a VoIP migration goes smoothly or sideways.

Step 1: Audit Everything Before You Touch Anything

The single biggest mistake businesses make in a VoIP migration is starting with the technology before they understand the environment. Before you evaluate a single provider or configure a single handset, you need a complete picture of what you're replacing.

Your audit should capture:

  • Every phone number in use — main lines, direct-dial extensions, fax numbers, toll-free numbers
  • Every analog device on the network — desk phones, conference room systems, fax machines, modems
  • Every non-voice device using a POTS line — alarm panels, elevator phones, door entry systems, POS terminals, fire suppression monitoring
  • Your current call volume and call patterns — peak hours, average hold times, call queue behavior
  • Any call center or IVR functionality that needs to be replicated
  • Integration requirements — CRM systems, ticketing platforms, call recording, compliance logging
  • This audit typically surfaces surprises. Most businesses discover analog lines they forgot about — a fax machine in the back office, an elevator phone that hasn't rung in years, a security panel that's been quietly dialing out every night. Each one needs a plan before you cut over.

    Step 2: Assess Your Network Readiness

    VoIP runs over your internet connection. That sounds simple, but it introduces dependencies that POTS never had. Before you migrate, your network needs to be ready to carry voice traffic reliably.

    Bandwidth: VoIP calls use roughly 85–100 Kbps per concurrent call with standard codecs. A business with 20 simultaneous calls needs at least 2 Mbps dedicated to voice — but that's a floor, not a target. Factor in your other internet usage and build in headroom.

    Latency: Voice is sensitive to delay in a way that file transfers and web browsing are not. One-way latency above 150ms starts to degrade call quality. Above 200ms, conversations become noticeably awkward. Test your current latency before committing to a provider.

    Jitter: Jitter is variation in packet delivery timing. High jitter causes choppy audio. Most enterprise VoIP platforms handle moderate jitter through buffering, but your network should target under 30ms.

    Packet loss: Even 1–2% packet loss is audible on a voice call. Anything above that is unacceptable. If your current internet connection has reliability issues, fix them before you migrate — VoIP will make every problem more visible.

    QoS (Quality of Service): Your router and switches need to be configured to prioritize voice traffic over other data. Without QoS, a large file download or a video conference can degrade call quality for everyone on the network simultaneously.

    If your network isn't ready, a VoIP migration will fail regardless of which provider you choose. Network readiness is a prerequisite, not an afterthought.

    Step 3: Choose the Right VoIP Architecture

    Not all VoIP deployments are the same. There are three primary architectures, and the right one depends on your size, IT resources, and requirements.

    Hosted VoIP / UCaaS

    The most common choice for small and mid-market businesses. The phone system lives in the cloud — the provider manages all the infrastructure, and you access it through IP phones, desktop apps, or mobile apps. No on-premises hardware to maintain, predictable per-seat pricing, and built-in redundancy.

    Best for: Businesses without dedicated IT staff, multi-location organizations, remote and hybrid teams.

    SIP Trunking

    SIP trunking replaces your POTS lines while keeping your existing on-premises phone system (PBX). Instead of copper lines connecting your PBX to the carrier network, SIP trunks carry calls over IP. This is a good option if you've recently invested in a PBX and aren't ready to replace it.

    Best for: Businesses with an existing IP-capable PBX, larger organizations with complex call routing requirements.

    On-Premises IP PBX

    A full IP phone system hosted on your own hardware. Maximum control and customization, but requires IT resources to manage and maintain. Less common for new deployments given the maturity of hosted options.

    Best for: Large enterprises with dedicated telecom staff and specific compliance or customization requirements.

    Step 4: Plan Your Number Porting Strategy

    Your phone numbers are business assets. Customers know them. They're on your website, your business cards, your Google Business Profile. Losing them — or having them go dark during a migration — is a serious operational risk.

    Number porting is the process of transferring your existing numbers from your current carrier to your new VoIP provider. It's a standard process, but it has rules and timelines that need to be built into your migration plan.

    Key porting considerations:

  • Porting takes time. Simple ports typically take 5–10 business days. Complex ports — toll-free numbers, large blocks of DIDs, numbers from carriers with manual processes — can take 3–6 weeks. Plan accordingly.
  • You cannot cancel your old service before porting is complete. If you cancel your POTS lines before the port completes, you may lose your numbers permanently. Keep the old service active until every number has successfully ported and been tested.
  • Fax numbers can be ported too. If you're moving fax to a cloud fax service or a VoIP fax adapter, port the number rather than abandoning it.
  • Get a Letter of Authorization (LOA) ready. Your new provider will need a signed LOA and a copy of your current phone bill to initiate the port. Have these ready before you start.
  • Step 5: Plan the Cutover — Don't Just Flip a Switch

    The cutover is the moment your calls move from POTS to VoIP. How you manage it determines whether your business experiences a seamless transition or a chaotic outage.

    Parallel running: Where possible, run both systems simultaneously for a period before cutting over. This lets you test VoIP call quality, train staff on new features, and identify issues without risking live calls.

    Cutover timing: Schedule the cutover during your lowest-traffic period — typically early morning on a Tuesday, Wednesday, or Thursday. Avoid Mondays (high call volume), Fridays (staff may be unavailable to troubleshoot), and any period around a major business event.

    Rollback plan: Know exactly what you'll do if something goes wrong. Can you revert to POTS temporarily? Who makes the call to roll back? What's the threshold — one dropped call, or a pattern of failures? Having a documented rollback plan means you can make decisions quickly under pressure instead of improvising.

    Test before you go live: Before the cutover, test every number, every extension, every call queue, every IVR prompt, and every integration. Call in from external numbers. Test hold music. Test voicemail. Test call recording if it's required for compliance. Don't assume it works — verify it.

    Step 6: Train Your Team

    VoIP systems have features that POTS never had — visual voicemail, call recording, presence indicators, softphone apps, video calling, chat integration. That's a good thing, but only if your team knows how to use them.

    Plan for training before the cutover, not after. Cover the basics: how to make and receive calls, how to transfer, how to access voicemail, how to use the mobile app. Then cover the features that will actually change how people work. A 30-minute training session before go-live prevents a week of help desk tickets after.

    Step 7: Don't Forget the Analog Exceptions

    As covered in our POTS replacement guide, not everything can move to VoIP. Alarm panels, elevator phones, fax machines, and life safety systems often need a different solution — typically a cellular POTS replacement device that plugs into the existing analog equipment and routes calls over 4G/5G.

    These devices need to be ordered, configured, and tested before your POTS lines are cut. They're often the last thing businesses think about and the first thing that causes a compliance problem.

    Common VoIP Migration Mistakes to Avoid

    Choosing a provider based on price alone. The cheapest VoIP provider is rarely the right one. Evaluate call quality, uptime SLAs, support responsiveness, and contract terms alongside pricing.

    Skipping the network assessment. A VoIP system on a network that isn't ready will have call quality problems from day one. Fix the network first.

    Underestimating porting timelines. Build porting time into your project plan. Don't promise a go-live date before you know how long your specific ports will take.

    Forgetting analog devices. Every unplanned analog line is a potential outage or compliance issue. The audit is not optional.

    Not testing call recording and compliance features. If your industry requires call recording — financial services, healthcare, legal — verify that recording is working and that recordings are being stored correctly before you go live.

    How BTSI Manages VoIP Migrations

    A VoIP migration touches your network, your carrier relationships, your phone numbers, your devices, and your staff. Getting it right requires coordinating all of those pieces simultaneously — and knowing what to watch for at each step.

    At BTSI, we've managed VoIP migrations for businesses ranging from 10-seat professional services firms to multi-site enterprises with hundreds of endpoints. Because we're vendor-neutral, we don't have a preferred platform to push — we evaluate options from our 220+ provider network and recommend the one that fits your environment, your budget, and your requirements.

    We handle the audit, the network assessment, the provider evaluation, the porting coordination, the cutover planning, and the post-migration support. You get a migration that goes smoothly — and a phone system that actually works better than what you had before.

    Schedule a free VoIP migration consultation with BTSI — we'll assess your current environment and build a migration plan that keeps your business connected through every step of the transition.

    Share this article

    Ready to see what vendor-neutral IT advice can do for your business?

    Book a free consultation with BTSI — no cost, no obligation.

    Book My Free Consultation