Cloud VoIP suits businesses with staff working away from the office or across multiple sites, and removes the hardware entirely. An on-premises PBX still wins where the internet connection is unreliable, where the existing system is paid for and working, or where door intercoms, lift phones or alarm diallers are wired into it. A hybrid — the PBX for the office and cloud extensions for everyone else — is often the right answer for both. Call 07 3041 8993.
The decision is not really about phones
Almost every comparison of these two is written by somebody selling one of them, which is why they all reach the same conclusion. The honest position is that this decision turns on two questions that have nothing to do with phone features.
Where do your people work? If everyone is in one building, an on-premises system does that job perfectly well and has for decades. The moment staff are at home, in vehicles or across two sites, an on-premises system starts costing money and effort to do something cloud does by default.
Can your connection carry voice? Not whether it is fast — whether it is consistent. A cloud phone system is only as good as the link underneath it, and a business that moves onto one across a connection with afternoon packet loss has bought a worse phone system than the one it replaced.
bcom ICT runs its own cloud PBX platform and also maintains legacy Panasonic, NEC, LG Ericsson and Alcatel-Lucent systems. We have advised clients to keep a PBX we could have replaced, because the alternative would have been worse for them.
Cloud is the right answer here
- People work somewhere other than the office. The extension follows the person to a laptop, a mobile or a home desk. This is the reason most businesses move, and an on-premises system handles it poorly or expensively.
- You have more than one site. One numbering plan across offices, without a link between buildings to maintain.
- You do not want to own hardware. No box in a cupboard to fail, no card to source in eight years, no installer to find.
- You want the features without the project. Call queues, IVR menus, recording, transcription and after-hours routing are configuration rather than capital.
And keeping the PBX is the right answer here
- Your internet cannot be trusted. This is the honest one. If the connection drops and there is no failover, a cloud system drops with it. An on-premises PBX on copper keeps working.
- It is paid for and it works. A functioning system with parts still available owes you nothing. Replacing it because it is old is not a reason.
- Something is wired into it. Door intercoms, lift phones, paging, alarm diallers and some hospitality integrations sit on the PBX and do not move casually.
- You are mid-lease. A finance agreement with years to run constrains the options, and there are usually better things to do with the money than break it.
The answer is frequently both
The framing of this decision as a replacement is usually wrong. A business with sixteen people in an office and six working elsewhere does not need to discard a working system to solve a problem affecting six people.
Keep the PBX for the building. Add cloud extensions for the people who are not in it. Join the two so one published number rings whoever is available, wherever they are. It costs a fraction of a full replacement, it removes the pressure to decide, and when the PBX genuinely reaches its end the move is already half done.
What people get wrong deciding this
“Cloud is just cheaper”
Usually a comparison of a monthly fee against a system that was paid for years ago. Against a written-down PBX, cloud often costs more per month and still wins on capability — but it should win on the right grounds.
What we do Compare against what the next five years actually look like, including the maintenance, the parts risk and the day nobody will touch it. Not against a sunk cost.
“On-premises is obsolete”
Usually a sales position more than a technical one. Plenty of PBX systems are doing exactly what their business needs and will keep doing it for years.
What we do Judge it on whether it does what you need, whether parts are obtainable and whether anyone will support it. We still program Panasonic, NEC, LG Ericsson and Alcatel-Lucent systems.
“We will move everything at once”
Usually an all-or-nothing framing that is rarely necessary. A hybrid — the existing system for the office, cloud extensions for people outside it, joined on one published number — is frequently a fraction of the cost.
What we do Consider the middle path before the full replacement. It is often the right answer for two years, and it makes the eventual move smaller.
“Our internet is fine, we did a speed test”
Usually the most expensive assumption in this decision. Voice needs consistency, not speed, and a connection can pass every speed test and still be unusable for a call.
What we do Measure latency variation and packet loss across a working week before committing. This is the one check that decides whether a cloud move succeeds.
“We will keep the handsets”
Usually sometimes possible and often not. Whether existing desk phones carry across depends on the specific models and how they are locked.
What we do Establish it for your exact handsets before planning around it. It changes the shape of the project and it is a ten-minute check.
Questions Gold Coast businesses ask us
Should we move from a PBX to a cloud phone system?
It depends on two things: whether people need to work away from the office, and whether your internet connection is genuinely stable enough to carry voice. If staff are remote or across sites, cloud is usually the right move. If your existing system works, is paid for, and everyone sits in one building on an unreliable connection, staying put is a defensible decision. bcom ICT supplies cloud and still programs legacy PBX systems, so we have no stake in the answer.
What happens to a cloud phone system if the internet drops?
Calls stop, unless there is a second path. That is the honest limitation. It is why we add mobile failover on a site that depends on its phones, and why we measure the connection before recommending a move rather than after. An on-premises system on copper does not have this exposure, and that genuinely counts in its favour.
Is cloud cheaper than an on-premises PBX?
Against a new PBX, usually yes — there is no hardware, no installer and no maintenance contract. Against a system you already own and have written down, often no on a monthly basis. The case for moving is usually capability and flexibility rather than price, and anyone telling you it is purely a saving has not compared it properly.
Can we keep our existing phone numbers?
Yes. Local, mobile, 1300 and 1800 numbers are all portable. Most porting delays are administrative — account details not matching the losing provider's records — which is why we reconcile those before submitting rather than after a rejection.
Can we run both at once?
Yes, and it is frequently the sensible answer. The existing system covers the office while cloud extensions cover people working elsewhere, joined so one published number reaches whoever is free. It costs a fraction of a full replacement and it makes the eventual move smaller.
What about our lift phone and alarm dialler?
They stay where they are. Lift emergency phones, monitored alarm diallers and fire panels sit on their own services and are the most commonly forgotten casualty of a phone changeover. We identify every service in the building and what depends on it before anything is switched.
Want the honest answer for your business?
Tell us where your people work and we will measure whether your connection can carry it. Those two answers decide this, and we will tell you if the answer is to stay put.