For years, keeping the phone system in the equipment closet was the safe choice. It was paid for, it worked, and nobody had to think about it. In 2026 that math has changed. The cost of staying on an on-premises PBX is now rising faster than the cost of moving, and much of it never shows up on a single budget line.
First, a working definition.
An on-premises PBX is a business phone system whose call-control hardware and software sit in your own building and are maintained by your own team or a contractor. A cloud PBX moves that call control to a provider's redundant data centers, so there is no phone-system hardware for you to patch, power, or replace.
Here is what is changing in the market, where an aging PBX quietly costs you, and how to plan a move without disrupting the business.
The trend: waiting is no longer cost-neutral
In a February 2026 analysis, UC Today argued that "do nothing" PBX strategies are breaking. It points to stepped price increases on legacy copper lines in the UK, vendor support windows closing (it cites Avaya Aura reaching end of manufacturer support by the end of 2026), and a shrinking pool of engineers who can maintain older systems. The question for finance teams, the article says, has shifted from what migration costs to what waiting costs.
The pressure is just as real in the US. Industry reporting from March 2026 noted that AT&T stopped accepting new POTS orders in 18 states as of October 15, 2025, and that once a carrier files a discontinuance notice, businesses may have only 180 days to transition. Other industry analysis puts US copper lines at about 36 million, down from 122 million in 2010, and notes that the FCC has streamlined its copper retirement process.
Four places an aging PBX quietly costs you
Most organizations only notice these costs when something breaks or a notice arrives. Look for them now:
- Copper and trunk pricing. Analog lines and legacy trunks ride on networks carriers want to retire, and prices and notice periods are moving against you.
- Support and parts. When a vendor ends support, you pay for third-party maintenance, hard-to-find parts, and scarce engineers.
- Duplicate systems. Running a cloud platform next to a legacy PBX means paying twice for numbers, calling plans, and carrier invoices, a pattern UC Today calls out.
- Life-safety and continuity risk. Fire alarm panels, elevator phones, and fax lines often sit on analog circuits. Industry guidance notes they cannot be swapped overnight because of inspection and code requirements.
None of these is a crisis today. Together they make a steady, compounding cost, and the longer you wait, the more a move happens on the carrier's schedule instead of yours.
What moving to cloud PBX actually involves
The fear behind most delayed migrations is a rip-and-replace project with downtime. A well-run move is closer to a staged handover. A practical plan looks like this:
- Inventory every line and device. Include analog phones, fax, door phones, alarms, and elevator lines at every site.
- Flag what is life-safety or revenue-critical. Those circuits get the most careful testing and the most lead time.
- Decide what stays. Many analog and IP phones can be reused, so you can avoid a full handset refresh.
- Port numbers and cut over site by site. Start with a pilot location, then repeat what worked.
- Train your admins. A cloud portal replaces the closet, so the people who manage it need to be comfortable in it.
The goal is to be running on the new platform before a carrier notice or a vendor end-of-support date forces the timeline.
Five questions to ask before you retire your PBX
Use this checklist with any cloud PBX provider.
- Can we keep the phones we already own? Ask which analog and IP devices are supported.
- How is service kept up if a data center or a connection fails? Look for geo-redundancy and diverse carrier connections.
- Who is responsible for the carrier network? Ask who handles call quality and number porting when something goes wrong.
- What compliance attestations can you show us? Ask for them in writing, especially in healthcare.
- What happens to our analog and life-safety lines? Get a site-by-site plan before cutover day.
Frequently asked questions
Do I have to replace all of my phones to move to cloud PBX?
Not necessarily. Many analog and IP phones can be configured to work with a cloud PBX, depending on the provider and the models in use. Ask for a list of supported devices before you plan a handset refresh.
How long does a move to cloud PBX take?
It depends on the number of sites, number porting, and site readiness. A single-site move can be quick, while multi-site rollouts take longer. Starting with a pilot location is the usual way to find problems early.
Is cloud PBX suitable for healthcare?
It can be, but ask for written documentation of the compliance attestations that matter to you, such as SOC 2 Type II reports, and for HIPAA-related agreements where they apply. Confirm the specific requirements for your organization with your compliance team.
What internet connection do I need?
Voice quality depends on a stable connection with enough bandwidth for your peak number of concurrent calls, plus QoS-enabled switches and VoIP-capable routers. Ask your provider for its connectivity requirements and plan any upgrades before cutover.
Start with the inventory
Keeping an aging PBX is no longer the neutral choice it used to be. If copper notices, end-of-support dates, or duplicate phone bills are on your radar, a site-by-site inventory of lines and devices is a low-risk first step and the foundation for any migration plan.
Sources: UC Today, February 26, 2026; MetTel, March 11, 2026; FluentStream.
