VoIP vs. PBX for Schools: Which Telephone System is Best?

Quick Summary: Legacy PBX systems require on-site hardware, engineer-led changes, and a large capital refresh every 5–10 years. Hosted VoIP (cloud PBX) moves the exchange off-site, scales in minutes via a web portal, and is switch-off ready. Most schools reduce total cost of ownership over five years by migrating — the right choice depends on your internet resilience, growth plans, and existing hardware investment.

If your school’s phone system is starting to feel like a liability rather than a utility, you’re not alone. Ageing hardware, rising engineer call-out fees, and an inability to support flexible working are pushing school leaders and IT directors to ask the same question: should we stick with what we know, or move to the cloud? This decision sits right at the heart of our The Ultimate Guide to School Telephone Systems: Upgrading Education Communications, and it’s one of the most consequential a school will make about its infrastructure this decade.

This guide breaks the VoIP vs PBX for schools decision down into its component parts — what hosted PBX, cloud PBX, and SIP telephony actually mean in practice, what each costs, how much work it creates for your IT team, and how to match the right business VoIP phone system to your specific campus. For the equivalent comparison outside education, see T2K’s general cloud PBX vs on-premise vs hybrid phone systems guide.

Understanding Traditional On-Premise PBX in Education

A Private Branch Exchange, or PBX, is the traditional backbone of school telephony. It’s a physical piece of hardware — usually a cabinet or rack-mounted unit — installed somewhere on-site, most often in a server room, cupboard, or reception back-office. This unit connects your internal extensions to the outside telephone network via analogue or ISDN lines.

How On-Premise PBX Works Day to Day

Every call, whether internal or external, is routed through this central box. When a parent calls the school office, the PBX receives the call over the external line and routes it to the correct extension. Internal calls also pass through the same unit, even though both parties are in the same building. Larger deployments often add hunt groups (so a call rings several extensions in sequence until answered) and a receptionist console for staff fielding high call volumes.

The Limitations Schools Run Into

• Physical capacity limits — a fixed number of ports, meaning growth often requires a costly expansion card or new unit
• Site-bound by design — every extension is physically wired to the PBX; a satellite building needs its own cabling run
• Single point of failure — hardware failure can take out the entire school’s calling ability at once
• Engineer dependency — even minor configuration changes typically require a paid engineer visit
• Approaching obsolescence — most on-premise PBX systems rely on ISDN or analogue lines being retired nationally

Common mistake: Assuming a PBX that’s “still working” carries no urgency. In practice, the risk isn’t day-to-day reliability — it’s that spare parts and ISDN circuits for these systems are being withdrawn nationally, regardless of how well the hardware currently performs.

How Hosted VoIP Telephony Works for Schools

Hosted VoIP — also called cloud PBX or hosted PBX — takes the same core function and delivers it through an entirely different architecture. Instead of routing calls through an on-site exchange, your phone system lives in the cloud, hosted and managed by your provider. Calls travel as data over your existing internet connection, using IP telephony and the SIP standard that underpins most modern business VoIP, whether delivered through dedicated IP phones, SIP phones, or softphone apps.

The Practical Difference

For staff, day-to-day use looks almost identical — a handset on the desk, extensions to dial, the same published school number. The difference is entirely in the infrastructure behind the scenes.

Key characteristics of a modern internet phone system include:

• No on-site exchange hardware to maintain — your provider hosts the core system
• Extensions added or removed in minutes, via a web-based admin portal
• Calls follow staff anywhere, via a softphone app on a laptop or mobile
• Automatic failover, rerouting calls to mobile numbers if internet drops
• Built-in features as standard — auto-attendants, call queues, call groups, voicemail-to-email, call recording

Bandwidth and Network Considerations

Because voice calls now share the same connection as your school’s internet traffic, IT directors need to configure Quality of Service (QoS) to prioritise voice packets over VLANs, particularly in larger schools where classroom streaming and cloud PBX traffic run simultaneously. Power-over-Ethernet (PoE) switches are also worth planning for, since they let IP phones draw power directly from the network cabling rather than needing a separate socket at every desk.

Expert tip: A site survey should map exactly where existing network cabling and PoE capacity fall short of new handset locations — this is one of the most common causes of a delayed go-live date, and it’s far cheaper to identify in the planning phase than during installation week.

Cost Comparison: Upfront Hardware vs. Ongoing Cloud Licenses

On-Premise PBX Cost Structure

Dominated by upfront capital expenditure: hardware purchase, installation and cabling, handset hardware, ongoing line rental, and annual maintenance contracts — typically requiring a significant capital refresh every 5–10 years.

Hosted VoIP Cost Structure

Upfront costs are usually limited to handsets and any network upgrades. The ongoing cost is a predictable per-user, per-month licence fee, which bundles in features that would be costly add-ons on a legacy PBX.

Comparison Matrix

In many schools, the total cost of ownership over five years works out lower with hosted VoIP, largely because it removes engineer call-outs, ISDN line rental, and the need for a major hardware refresh partway through the contract term. For full pricing detail and worked examples by school size, see A Guide to Budgeting for a New School Telephone System.

Maintenance, IT Burden, and Scalability Differences

With an on-site PBX, your IT team is responsible for the physical health of the hardware. With hosted VoIP, this burden shifts almost entirely to the provider, typically backed by a service-level agreement covering uptime and fault response.

Scalability is where the gap is starkest. Expanding a PBX typically means new cabling, new hardware, and an engineer visit. Expanding hosted VoIP means logging into a portal and adding a user — live, within minutes. This matters enormously for growing schools and especially for MATs bringing new schools into the fold, covered in Unified Communications for Multi-Academy Trusts (MATs) and School Districts.

Common Objections to Making the Switch — Addressed

“Our internet isn’t reliable enough.” A proper site survey and QoS configuration resolve most concerns; failover to mobile numbers covers genuine outages.

“We’ve already invested in handsets.” Many hosted VoIP platforms support existing SIP-compatible handsets, and a hybrid approach can bridge the gap during a phased migration.

“It sounds complicated to switch.” With a phased, education-experienced provider, migration is typically completed in stages around the school calendar, with parallel running to eliminate disruption.

“Our current system still works fine.” The question isn’t whether it works today, but what it costs to keep working — and whether it will survive the PSTN/ISDN switch-off. See Navigating the PSTN/ISDN Switch-Off: What Schools Need to Know.

Pros and Cons at a Glance

Legacy PBX - ✅ Familiar to long-serving staff; no retraining required - ✅ No dependency on internet quality for call reliability - ❌ Being phased out nationally as ISDN retires - ❌ Expansion and repairs require an engineer visit

Hosted VoIP / Cloud PBX - ✅ Scales instantly; supports remote and mobile working - ✅ Switch-off ready, with features bundled as standard - ❌ Call quality depends on internet resilience and QoS setup - ❌ Requires a migration and training period to embed

Migration Checklist: Moving from PBX to Hosted VoIP

1. Audit existing extensions, lines, and connected systems (alarms, lifts)
2. Assess internet bandwidth and resilience; plan QoS configuration
3. Choose a provider with genuine education-sector experience
4. Agree a number porting plan with zero service gap
5. Schedule migration around a half-term or holiday period
6. Run a parallel testing period before full cutover
7. Train reception and office staff before go-live

Making the Right Choice for Your Campus Size and Internet Capabilities

There’s no universally correct answer — the right choice depends on your circumstances. A small, single-building school with an already-modernised digital PBX may see limited urgency to migrate immediately, though the switch-off will eventually force the issue regardless. For the vast majority of schools — especially those managing multiple buildings, needing remote working for admin staff, or escaping a costly maintenance contract — hosted VoIP is the stronger long-term choice.

FAQs

Is VoIP cheaper than PBX for schools? In most cases over a five-year period, yes — largely due to lower maintenance costs and no large hardware refresh cycle. The exact figure depends on your current contract and school size; see our budgeting guide for a worked example.

Can a school keep its existing phone number when switching to VoIP? Yes, via number porting, handled by your provider as part of migration with no loss of service.

Does VoIP work if the school’s internet goes down? Most hosted VoIP platforms support automatic failover to mobile numbers during an outage, minimising disruption.