For a business operating from one office, moving to VoIP is largely a cost and features decision. Across several locations it becomes something more useful: a single phone system spanning every site, with one set of extensions, one directory, and calls routed by rules rather than by geography.
It is also where migrations most often go wrong, because the failure points are in the network and the planning rather than in the phones themselves. Here is what to work through before committing.
What actually changes with multiple sites
Traditional systems treat each location as a separate island — its own hardware, its own lines, its own maintenance contract, and inter-site calls that go out to the carrier and back. A cloud-based VoIP platform treats all sites as one system.
The practical differences:
- One dial plan. Four-digit dialling between offices regardless of distance, with no per-call cost between sites.
- One directory. Staff see everyone in the company, not just their own building.
- Presence across locations. You can see whether a colleague in another office is available before transferring a customer to them.
- Centralised administration. Adding an extension, changing a greeting or adjusting call routing is done once, from one place.
- Location-independent numbers. A local number for each market can ring wherever the right person actually is.
- Shared coverage. Calls to one office can overflow to another when the first is busy or closed — useful across time zones, and useful when one site is disrupted.
That last point is worth dwelling on. When one location loses power or is inaccessible, calls can be redirected to another site or to mobiles in minutes. With on-premise hardware at each location, they cannot.
Your network is the actual dependency
The most common cause of a disappointing VoIP rollout is not the platform. It is the connection at one or more sites.
Voice traffic is unforgiving in a specific way: it needs consistency more than raw speed. A connection that streams video perfectly can still produce choppy calls if latency varies. The measures that matter are latency, jitter and packet loss, not megabits.
Before committing, assess each site individually:
- Test the connection at every location. Sites differ, and the weakest one determines the experience for everyone who calls it. Branch offices on older infrastructure are the usual culprits.
- Confirm you can prioritise voice traffic. Quality of Service configuration on the router keeps a large file upload from degrading a customer call. On shared or consumer-grade connections this may not be possible at all.
- Check bandwidth against concurrent calls, not headcount. Estimate peak simultaneous calls per site and size for that, with headroom.
- Decide what happens when a site loses internet. Options include automatic failover to mobile, rerouting to another location, or a cellular backup connection. Decide deliberately rather than discovering the default during an outage.
- Verify the switches will power the phones. Power over Ethernet is far tidier than a power adapter at every desk, but older switches may not supply it, or may not supply enough across every port.
Number porting deserves early attention
Moving existing numbers to a new provider is routine but not instant, and it is the part of a migration most likely to slip. Timelines vary by carrier and number type, and porting requests are rejected for small clerical reasons — a service address that does not match the carrier’s records, a billing name that differs slightly, an account number transposed.
Three things reduce the risk:
- Request a copy of your current bill early and match the port request to it exactly.
- Do not cancel the old service until the port has completed. Cancelling first can release the number entirely, and recovering it may be impossible.
- Port in stages where you can — a pilot group first, main numbers once the platform is proven.
Pay particular attention to numbers that are not obvious: fax lines, alarm and lift lines, and anything printed on vehicles, signage or stationery.
Questions to put to a provider
- How is the system administered across sites — one interface, or one per location?
- What happens to calls when a site loses connectivity, and is failover automatic?
- Are there per-site charges, or is pricing per user across the organisation?
- How are emergency calls handled, and how is location information maintained when staff move between sites or work remotely? This is a regulatory matter, not a preference.
- What does the migration plan look like, and who manages the number porting?
- Is training included, and is it delivered per site?
Plan the cutover realistically
Run both systems in parallel for a short period if you can. Start with a pilot group who are comfortable reporting problems, and move the main numbers once the platform has proven itself on your network.
Train staff before the switch rather than after. Most post-migration complaints are not faults — they are people who cannot work out how to transfer a call or retrieve voicemail, and the resulting frustration attaches itself to the new system regardless.
Avoid cutting over during your busiest period, and make sure someone is clearly responsible for collecting issues in the first fortnight.
Getting it planned properly
Techvo operates from offices in Northern Virginia and North Myrtle Beach, so multi-site phone systems are something we run ourselves as well as implement for clients. We assess each location’s connectivity before recommending a platform, because the honest answer is sometimes that a site needs its connection improved first.
Read more about our VoIP telephone systems, or get in touch to talk through what a migration would involve for your locations.