The case for moving off traditional business lines is strong and getting stronger. But the honest version of that case includes a dependency you didn't have before: your phones now ride on your internet connection. Understanding that trade is the whole decision.
What a cloud system replaces
A traditional setup is a set of physical lines terminating in on-site hardware — a PBX or key system — that routes calls to desk phones. A cloud system moves the routing to the provider's network. Your "phone" becomes any device that can register: a desk handset, a laptop, a mobile app.
The practical consequences: no on-site box to fail or be maintained, changes are made in a web console rather than by a technician visit, and adding a person is a licence rather than a line.
Where the money actually goes
You pay for people, not copper. For most businesses this is where the saving is, and it scales down as well as up.
Handsets are a choice rather than a requirement. Many teams run entirely on softphones and mobiles.
The recurring line item that quietly accumulates on traditional systems — every reconfiguration — largely disappears.
The offsetting cost is that your internet now needs to be good enough, and ideally redundant. Budget for the connection, not just the phone plan.
Porting your number
This is the part that worries people most and causes the fewest actual problems — provided you don't do the one thing that breaks it. Number portability is well established in Canada and your number is yours to move.
Never cancel your existing service to "make room" for the port. Cancelling releases the number and can lose it permanently. The port pulls the number across and closes the old service as part of the process.
Expect the port itself to take days rather than hours, and expect to run the new system alongside the old one until it completes. Details on the account — the exact registered name and address — must match what the losing carrier holds, which is the usual cause of delays.
What decides call quality
Not bandwidth, mostly. Voice uses very little of it. Quality is decided by three things: jitter (variation in packet timing), latency, and packet loss. A connection can test at high speed and still deliver poor calls if it's unstable under load.
Two practical measures matter more than buying a bigger plan: give voice traffic priority on your network, and make sure your upload isn't saturated by backups, cameras or cloud syncing during business hours. That's a network configuration question, and it's where a badly deployed cloud system gets its reputation.
Features that matter after the demo
Every provider demos auto-attendants and call recording. The features that change daily life are duller: sensible call routing when someone is unavailable, voicemail that reaches you by email or transcript, a shared number that rings the right people in the right order, and call reporting that tells you how many calls you missed and when.
That last one is worth more than it sounds. Most businesses have no idea how many calls they don't answer.
When the internet drops
This is the honest weakness, and it's solvable. A cloud system can fail over calls automatically to mobiles or to a backup connection — but only if you've configured it to. Decide the failover behaviour before you go live rather than discovering it during an outage.
If phones are how you take business, pairing the system with a backup connection is the difference between a technology that's more reliable than copper and one that's less.
Remote and multi-site teams
This is where the model stops being a cost saving and becomes a capability. One number plan can span several locations and people working from anywhere, with internal calls between sites, a single directory, and consistent handling regardless of where anyone physically is. For businesses running multiple locations, that consolidation is often the real reason to move.
Questions to ask
- What happens to calls if this site's internet fails — specifically, and configured by whom?
- Is the number port included, and what's the realistic timeline?
- What's the per-user cost at my headcount, including the features I actually named?
- Do I need handsets, or will softphones and mobiles do?
- Is my current connection good enough for voice — and can you tell me before we sign?
- Who configures the call flow, and what does it cost to change it later?
FAQ
Yes, in almost all cases — number portability is well established. The critical rule is not to cancel your existing service first, because that releases the number. Port first, cancel second.
Not necessarily. Many teams run entirely on computer and mobile apps. Some existing IP handsets can be reused depending on model. Traditional analogue phones generally can't be, though adapters exist for specific cases like fax lines or alarm panels.
On a properly provisioned connection with voice prioritised, yes — and often better, since the audio isn't limited to the narrow band a traditional line carries. On a saturated or unstable connection, no. The connection is the variable, not the technology.
These need explicit attention. Some devices depend on characteristics of an analogue line and either need a dedicated line retained or a specific replacement path. Flag every one of them before the cutover — they're the most common thing missed.
We'll look at what you have, what your calls actually need, and tell you honestly whether the connection needs work first. That answer comes before any phone quote.
Book a voice review