Your Phone System Is One Dead Part Away From a Very Bad Week

Here's what genuinely changes — and what doesn't — when an Australian business moves from an on-premise PBX to a cloud phone system. No hype, just the mechanics.

There's a phone system in a cupboard or a comms rack somewhere in your office right now. Nobody's opened it in years. Nobody really wants to.

That's fine — right up until it fails. Then it's a callout fee, a wait on a part that might not even be manufactured anymore, and someone at reception taking messages on paper like it's 1998.

That box is a PBX — a private branch exchange — and for a lot of Australian small businesses, it was installed well over a decade ago by an installer who's since moved on, retired, or stopped returning calls. Moving off it isn't really about chasing "the cloud" as a buzzword.

What "on-premise" actually means

An on-premise system means the hardware that runs your phones physically lives in your building. Every extension, every call-routing rule, every voicemail box is tied to that unit. Want to add a new starter? Someone needs to get into the system — sometimes onsite. Want calls to ring differently after 5pm? Same story. When the unit itself reaches end of life, you're not patching software, you're sourcing a replacement box, often from a vendor that's stopped making it.

A cloud phone system moves that logic off the physical unit and onto infrastructure that's maintained, patched and backed up as part of the service. Calls still arrive the same way — over your internet connection or SIP trunks — but the routing, voicemail and admin all live somewhere that isn't a single point of failure sitting in your office.

What actually changes when you switch

This is the part most providers skip past to get to the sales pitch. Here's the practical version — the stuff that shows up in your day, not a features page:

• Adding or removing staff becomes an admin task, not a callout. A new starter gets an extension the same day from a portal — nobody drives out to open a cabinet.
• Calls can follow the person, not the handset. With a softphone app paired to a desk phone, a call to someone's extension can ring their mobile too if they've stepped out, without anyone dialling a forwarding code.
• Voicemail, call recordings and chat sit in one inbox instead of three separate systems nobody checks consistently.
• Calls can log themselves against a CRM record. Comm Centre's cloud phone systems integrate with Salesforce and HubSpot, so a call shows up against the right contact without anyone typing up a note afterwards.
• The system doesn't live in one building. It's hosted with geo-redundancy across Australian data centres, so a single outage doesn't take every phone in the office down with it.
• Calls are encrypted by default (TLS/SRTP) — the practical answer to "can someone just listen in." On a lot of ageing on-premise setups, the honest answer was technically yes.

Cost is the other question everyone actually wants answered before "features." On-premise costs show up as one large chunk upfront (the hardware) and then unpredictably after that — repairs, callouts, eventual replacement. Cloud costs are typically a flat per-user monthly fee, easier to budget against, but ongoing rather than one-off. Run the comparison over three to five years, not year one against year one.

How a call actually moves

Here's "calls follow the person," mechanically. A call comes in, hits the cloud PBX, and rings the desk phone and the mobile app at the same time. Whoever picks up, picks up — there's no forwarding code to remember. If nobody does, it drops straight to voicemail, which lands in the same inbox as everything else.

Built for redundancy, not a single point of failure

This is what "geo-redundant" actually means in practice: the system runs across more than one Australian data centre. If one has an issue, calls fail over to the other automatically — nobody needs to notice, let alone do anything about it. Compare that to a single box in a comms rack with no backup, because that's genuinely the alternative.

On-premise vs cloud, side by side

The honest bit: what doesn't change

No phone system fixes a bad internet connection. A cloud phone system lives and dies by the connection it runs on, so it's worth finding out what your connection actually delivers under load — not what the plan says on paper — before switching, not after.

Desk phones aren't going anywhere for a lot of businesses either. Cloud doesn't mean everyone suddenly uses a headset and a laptop — reception desks, warehouses and shared spaces still function better with a proper handset sitting on the counter. And there's a genuine transition period — porting existing numbers, testing call flows before go-live, walking reception through the new system. Done properly, it's measured in days, not months. But "instant" isn't a realistic promise from anyone selling this.

The hardware, if you want it

Cloud doesn't lock you into any particular hardware. Here's what we actually deploy alongside it — real gear, real prices, pulled straight from our own catalogue, not a manufacturer's glossy brochure:

Yealink SIP-T87W

7" touchscreen desk phone, AI noise cancellation, dual-band Wi-Fi 6 — our go-to for reception and shared spaces.

$499.00

Yealink WH64

DECT/Bluetooth hybrid headset, 13-hour talk time, 3-mic noise cancellation — for anyone living on the softphone app.

$295.00

UniFi Dream Machine Pro

The network gateway that solves the "decent internet" point above — traffic prioritisation so call quality holds up under load.

$869.00

What the switch actually looks like

In practice, a migration runs in five steps:

Before you call anyone: a short checklist

1. Get a straight answer on what your internet connection delivers under real load — not the advertised speed.
2. List every number that needs porting, and who it's currently registered with.
3. Write down how calls should actually move through the business — after-hours, reception routing, call groups — before anyone configures anything.
4. Work out who "owns" the phone system today. On a lot of ageing setups, the honest answer is nobody.