By the end of 2025, around 70-75% of mid-to-large enterprises had moved from legacy on-premise PBX to cloud-based UCaaS - up from 45% just three years earlier. That migration wave is still rolling, and the vendors selling cloud communications are not shy about telling you which direction to go. What they are less forthcoming about is when the migration goes wrong, what it actually costs beyond the per-user licence, and when staying on-premise is the smarter call.

This guide gives you the comparison without the sales spin.

Key Takeaways

  • UCaaS (Unified Communications as a Service) replaces your physical phone system with a cloud-hosted subscription covering voice, video, and messaging
  • On-premise PBX keeps hardware and call processing on-site, giving you full control but requiring your team to manage and maintain it
  • Cost range for UCaaS: $20-$50/user/month in licences alone - a 20-person business pays roughly $10,200/year all-in
  • Hidden costs are real: hardware, porting fees, network upgrades, training, and add-ons are frequently missing from initial quotes
  • Migration failures cluster around the same causes: overlooked analogue endpoints, no rollback plan, and adoption problems post-cutover
  • Hybrid UCaaS is the often-ignored third option, keeping critical on-site infrastructure while moving flexible workloads to the cloud

What Each Option Actually Is

UCaaS is a cloud-hosted platform that delivers voice calls, video conferencing, messaging, and often contact centre features as a monthly subscription. Providers host the hardware and software; you connect via internet. RingCentral, Nextiva, Zoom Phone, 8x8, and Sangoma are common examples.

On-premise PBX keeps the call processing hardware at your site. Your IT team manages it. You own the hardware, control the configuration, and are responsible for maintenance, updates, and continuity.

The choice is not as simple as cloud-good / on-prem-bad. Context determines which is correct.

The Real Cost Comparison

Advertised UCaaS pricing focuses on the per-user monthly licence. The full picture is more expensive.

UCaaS Pricing Breakdown

Cost Component Typical Range
Licence (per user/month) $20-$50
Desk phones (per device) $45-$300+
Hardware rental alternative $4-$15/user/month
Number porting $0-$15 per number
Onboarding and installation Varies; often separate
Network upgrades Emergency spend if underestimated
Premium features (analytics, contact centre) Extra above base licence

Provider licence benchmarks: RingCentral $20-$45/user/month, Nextiva $20-$35, Zoom Phone $22.49+, Sangoma $20-$30.

For a 20-person business at $25/user/month in licences, add hardware, setup amortisation, and connectivity costs and you reach approximately $750/month or $10,200/year. A 100-user mid-size organisation lands around $46,000/year; 250-user enterprise around $112,000/year.

On-Premise PBX Costs

On-premise costs are front-loaded. Hardware purchase, installation, PRI or SIP trunk connectivity, and IT staff time to manage the system. The ongoing cost is lower if you already have the infrastructure and the staff, but maintenance contracts, software upgrades, and hardware replacement accumulate over time.

The calculation tilts toward on-premise when you have a stable headcount, existing hardware that is not yet end-of-life, and an IT team already on payroll for other reasons.

Who Should Move to UCaaS

UCaaS is the right call if:

  • Your workforce is distributed across multiple sites or works remotely - UCaaS is built for this
  • Your headcount is growing and you need to add lines without IT intervention
  • Your IT team is small and you cannot justify a dedicated telecoms resource
  • You are already replacing an end-of-life PBX and there is no reason to buy more hardware
  • Your legacy system does not support Microsoft Teams or other collaboration tools your business needs

Who Should Stay On-Premise

On-premise PBX still makes sense if:

  • You operate in a regulated industry with strict data residency requirements (HIPAA, FINRA, GDPR-mandated local processing)
  • You have continuous-operation requirements - manufacturing, utilities, emergency services - where internet dependency is a real risk
  • You made a significant PBX investment in the last 2-3 years and the hardware still has a long service life
  • You have a dedicated IT team and deep PBX customisation that UCaaS providers cannot match

The honest position, as Sangoma's own migration guide acknowledges, is that "the right model for a 50-person distributed company looks very different from the right model" for a manufacturer with always-on requirements.

The Hybrid Option

Hybrid UCaaS is a staged model: critical on-site infrastructure stays local while flexible workloads move to the cloud. It is commonly used for phased migrations but also as a permanent architecture.

A typical hybrid setup keeps core call routing on-premise for a primary site with high reliability requirements, while branch offices and remote workers use cloud endpoints. This reduces internet dependency for the most critical operations while still enabling the flexibility UCaaS provides for everyone else.

Hybrid is more complex to manage, but it removes the all-or-nothing risk of a full cutover.

Why UCaaS Migrations Fail

The industry tracks these failure modes repeatedly. They are worth knowing before you start.

Overlooked Analogue Endpoints

Fax machines, door intercoms, lift emergency phones, paging systems, and alarm dialers all connect through your current PBX. They are easy to miss when an inventory focuses only on staff handsets. When they fail after cutover, the fix is expensive and urgent.

Mitigation: Conduct a full site walkthrough with facilities and operations staff, not just IT. Document every device connected to the phone system.

Network Readiness Underestimated

UCaaS requires reliable, low-latency internet. Businesses that do not test network performance before migration discover the problem through jitter, dropped calls, and call quality complaints after go-live. Emergency fibre installs and QoS upgrades cost significantly more than planned upgrades.

Mitigation: Test packet loss and jitter with a tool like PingPlotter or your UCaaS provider's network assessment tool before committing to a cutover date.

Adoption Is Not Automatic

One documented case found only 28% of users had activated the new mobile softphone app after migration. Without a deliberate change management programme, employees default to workarounds - personal mobile calls, external chat apps, email - which fragments communication and defeats the purpose of the UCaaS investment.

Mitigation: Plan training close to go-live, not weeks before. Role-based training (receptionist vs. sales vs. remote worker) works better than organisation-wide sessions.

No Rollback Plan

When issues arise during cutover, decisions made under pressure without predetermined rollback criteria tend to go badly. Running parallel systems costs money but provides a safety net.

Mitigation: Define the specific conditions that trigger rollback before migration starts. Keep the legacy system operational in parallel for 2-4 weeks post-cutover.

Hidden Fees

Telecom taxes, regulatory surcharges, and add-on features (call recording, advanced analytics, contact centre queuing) are frequently excluded from initial quotes. These can add 20-30% to the advertised per-user price.

Mitigation: Request a fully loaded quote that includes all taxes, porting, hardware, and any feature you currently rely on. Compare this number against your current total spend.

The Migration Process: Step by Step

If you decide UCaaS is the right direction, the migration follows a consistent structure regardless of provider.

Phase 1: Assessment and Planning

  • Audit every device connected to your phone system (phones, fax, intercoms, alarms)
  • Document call flows, hunt groups, IVR menus, and any custom integrations
  • Evaluate network performance under simulated voice load
  • Budget for licences, hardware, porting, network upgrades, and training - not just licences

Phase 2: Preparation

  • Configure QoS on your router to prioritise voice traffic
  • Set up the UCaaS environment and test call flows before porting any numbers
  • Define rollback criteria and keep the legacy system operational

Phase 3: Migration

  • Port numbers in batches, starting with non-critical lines
  • Run parallel systems during the transition period
  • Set temporary call forwarding from old numbers as a safety net

Phase 4: Post-Migration

  • Conduct role-based training close to go-live
  • Monitor call quality with your provider's analytics tools for the first 30 days
  • Decommission legacy hardware only after you are satisfied the new system is stable

Frequently Asked Questions

Q: Can UCaaS replicate everything my current PBX does? Most standard PBX features (auto-attendant, hunt groups, call queuing, voicemail, call recording) are covered by mainstream UCaaS platforms. Highly customised configurations, complex IVR trees, and integrations with older on-site systems may require custom middleware or may not be replicable without compromises.

Q: What happens if my internet connection goes down? Your UCaaS service goes down with it unless you have a failover arrangement. Options include a secondary internet circuit (4G/5G backup), call forwarding to mobile numbers, or a hybrid architecture that keeps core call processing on-site. Configure failover before you need it.

Q: How long does a typical UCaaS migration take? For a straightforward setup, provisioning takes 24-48 hours. Number porting from UK/US carriers takes 2-4 weeks. A full migration including testing, training, and parallel running typically takes 4-8 weeks for a business of 20-50 users, longer for complex environments.

Q: Is cloud UCaaS more secure than on-premise? Neither is inherently more secure. UCaaS shifts security responsibility to the provider but introduces new risks: remote endpoint vulnerabilities, AI feature data exposure (transcription and meeting summaries stored in the cloud), and dependency on the provider's compliance certifications. Verify that your provider holds the certifications relevant to your industry (HIPAA, SOC 2, ISO 27001) before signing.

Q: Can I keep my existing phone numbers? Yes. Number porting transfers your geographic and non-geographic numbers to your UCaaS provider. Most reputable providers handle porting at no charge or for a small per-number fee. Allow 2-4 weeks for the process.

Q: What is the minimum internet speed needed for UCaaS? Each concurrent voice call requires approximately 85-100 kbps. A 10 Mbps symmetric connection comfortably supports 80-100 simultaneous calls in terms of raw bandwidth. The more important metric is packet loss (target: under 1%) and jitter (target: under 30ms). Speed alone does not determine call quality.

The Bottom Line

UCaaS migration is not the automatic upgrade that vendors present it as. For distributed teams replacing ageing hardware, it is a genuine improvement in cost, flexibility, and collaboration capability. For businesses with strict data requirements, continuous-operation environments, or significant existing PBX investments, the calculus is less obvious.

The migration failures that occur most often are predictable and preventable: incomplete device inventories, network problems discovered after cutover, and adoption programmes that do not stick. Address these before you start and the transition is manageable. Ignore them and a cost-saving project becomes an expensive firefight.

Run the real numbers, not the headline per-user price, and make the decision based on your operational context rather than market momentum.