The nudge usually comes from outside. The carrier writes to say your copper lines are being retired, or the bill for three analog lines has crept past what a whole cloud phone system would cost, or the office is moving and the old system is not worth packing. However it starts, the question is the same — can you move the business to VoIP without losing your number, your call quality, or a week of answered calls?
Mostly, yes. Millions of businesses have made this exact move and the mechanics are routine. What separates a smooth cutover from a miserable one is doing things in the right order, and one rule above all others: never cancel your old phone service until the port has completed. Everything else is detail. That rule is the whole game.
What actually changes
VoIP carries your calls over your internet connection instead of a dedicated phone line. Your number stays, callers notice nothing, and the handset on the desk can look identical to the one it replaced — it just plugs into the network instead of a phone jack. What changes is everything around the call. The system lives in software, so features that used to mean a PBX upgrade — an auto-attendant, call recording, a mobile app — become settings you switch on. You stop paying per copper line; you pay per user, or once for a system you own.
Porting: the step everyone fears
Porting moves your number to the new provider. It is better protected than owners fear — the number belongs to you, and the old carrier must release it. The process:
- Sign a letter of authorization with the new provider. They run the port; you never call your old carrier to arrange it.
- Match the records exactly. The port request must match the old carrier's file — business name, service address, account number — character for character. Ask them for a CSR (customer service record) or work from a recent bill. Mismatches are the number-one cause of rejected ports.
- Schedule the cutover. Under FCC rules a simple port — a single line with nothing unusual on the account — must complete in one business day, and non-simple ports, which most multi-line business accounts are, in four. In practice your provider agrees a port date with you; pick a quiet day, not the Monday of your busiest week.
- Keep the old service running until the number answers on the new system. The old line dies by itself the moment the port completes. Cancel early and the number can be released before it moves, and a released number is genuinely hard to get back.
Check the internet first
A VoIP call needs about 100 kbps each way — the planning figure providers publish, and a rounding error next to one video stream. Raw speed is almost never the problem; stability is. Voice cannot buffer the way Netflix can, so jitter and packet loss you would never notice in a browser turn into robotic audio and dropped calls.
- Count concurrent calls, not employees. Ten people making occasional calls may peak at three at once.
- Turn on QoS (quality of service) on your router so voice traffic jumps the queue ahead of downloads and cloud backups.
- Wire the busiest phones with ethernet. Wi-Fi handles calls fine right up until it doesn't.
If calls later echo, drop or go metallic, the cause is almost always on that list — the call-quality guide walks the full diagnosis.
Cloud-hosted or on-premise
A cloud-hosted system means the provider runs the phone system in their data center and you pay per user per month. RingCentral, Nextiva, 8x8 and Zoom Phone are the big hosted names; as of September 2026 their published entry plans run roughly $10 to $25 per user per month and climb with features — the comparison guide covers how they differ.
An on-premise system puts the phone system on a small server or appliance in your office, connected to the world through SIP trunks. It costs more up front and carries no per-user subscription afterwards, which is why the math starts favoring it as headcount grows. It also suits offices with analog equipment worth keeping — overhead paging, door intercoms — and anyone who dislikes subscriptions on principle. The catch: someone has to maintain it.
The features worth turning on
- Auto-attendant — the "press 1 for sales" menu. It answers every call instantly and routes it without a human.
- Ring groups — one number rings several phones at once or in sequence, so a call stops dying at an empty desk.
- Mobile apps — the business line on a personal phone, showing the business caller ID. Nobody has to hand out a personal cell number again.
- Voicemail-to-email — messages arrive in the inbox as audio with a transcript, instead of living in a blinking light nobody checks.
If the honest problem is that nobody is free to answer at all, that is a different fix — see what an AI receptionist can and can't do.
Desk phones or softphones
You do not have to buy hardware. A softphone — the provider's app on a computer or mobile, plus a headset — comes with every hosted plan and suits most desks. Physical IP handsets still earn their place where a phone is shared or answered constantly: reception, a shop counter, a warehouse wall. Most offices mix the two, buying handsets only where hands actually pick one up.
911: the part that is law, not preference
Two federal laws apply to any multi-line phone system, VoIP included. Kari's Law, in force since 2020, requires that 911 connects directly — no dialing 9 for an outside line first — and that the system notifies someone on site when 911 is dialed. RAY BAUM's Act, since 2021, requires every 911 call to carry a dispatchable location: the street address plus the floor or suite, so responders reach the right door, not just the right building.
That means registering an accurate address for every phone with your provider, and updating it when one moves — including the softphone an employee takes home. There are federal fines for getting this wrong, but the better reason is the ambulance.
What goes wrong
- Porting delays. Almost always a records mismatch. Get the CSR before you submit, and the port that would have bounced twice goes through once.
- One-way audio. You hear the caller; they don't hear you. The usual culprit is a router feature called SIP ALG mangling the traffic — turning it off fixes most cases, and a technician on Koadi can trace the rest over a screen-share.
- Fax. Fax tones do not survive VoIP compression. Move to an e-fax service, or ask your provider about a T.38 adapter — and test it before the old line goes.
- Alarm, fire and elevator lines. These must not ride your office VoIP — code requires monitored analog-style circuits, and the POTS replacement guide covers what to do with them instead.
- Outages. Copper phones stayed up when the power failed; VoIP dies with the internet. Set failover forwarding to cell phones now, while nothing is broken.
When you'd rather hand off the whole cutover
Koadi designs and installs VoIP phone systems end to end — cloud or on-premise — handsets, call flows, the number port and the E911 records, then supports the system afterwards. For a smaller job, like a port that keeps bouncing or one phone that won't register, post the problem free and vetted technicians pick it up: you set a fixed price or take bids, payment sits in escrow until you approve the fix, and help is remote in every US state with on-site visits available through local techs. You pay only when it works.