A traditional PBX is on-premise phone-system hardware — the box in the closet connected to copper lines or a PRI circuit. A cloud PBX moves that entire system to a provider. The honest comparison isn’t “old bad, new good”: it’s a question of what’s forcing your hand, and there are usually two pressures — the aging hardware itself, and the copper it’s plugged into.
SIPNEX is an FCC-licensed carrier that sits on both sides of this migration — trunks into aging PBXes and cloud PBX replacing them — so this guide has no stake in which path you pick, only that you pick it before a failure picks it for you.
What a traditional PBX still does well
Credit where due. A paid-off PBX with a competent maintainer delivers:
- Deterministic behavior. No internet dependency for internal calls; extension 204 rings extension 204 even when the fiber is cut.
- Zero subscription. The hardware is depreciated; the only recurring costs are lines and maintenance.
- Longevity. These systems run for decades — which is exactly how they became a problem.
The two pressures ending it
The hardware pressure: parts and people. End-of-life systems mean eBay part-hunting and a shrinking pool of technicians who still speak the platform. Every year, the maintenance contract renews higher — or doesn’t renew at all.
The carriage pressure: the copper and PRI circuits feeding traditional PBXes are being retired by the incumbent carriers, and the replacement rates on legacy circuits climb accordingly. Even a healthy PBX ends up connected to an increasingly expensive, officially deprecated network.
TCO math tends to surprise in one specific way: the traditional system’s visible cost (maintenance + lines) understates the risk cost — the business day lost when a 20-year-old power supply dies with no spare on the continent.
The two ways off
Path 1 — replace the system: move to a cloud PBX. Extensions, routing, and voicemail move to the provider; desk phones re-register over the internet; the closet empties. Right when nobody wants to own a phone system anymore. What to check before signing is covered in our cloud PBX pricing guide — feature tiers and contracts hide in the seat price.
Path 2 — keep a PBX, replace the carriage: IP PBX + SIP trunks. If the routing logic matters — call centers, complex sites, teams that want control — replace the hardware with a software PBX (FreePBX, 3CX, Yeastar) and feed it SIP trunks instead of PRI. You keep ownership; the copper dependence ends. Many migrations run this as a half-step: SIP trunks into the existing PBX via a gateway first, hardware replacement second.
Your numbers survive either path — porting moves them while the old service stays live.
How to decide in one meeting
Three questions, in order:
- Does anyone want to own the phone system? No → cloud PBX. Yes, and they’re competent → Path 2.
- Is call routing a differentiator or a utility? Utility → cloud PBX. Differentiator (queues, dialers, integrations) → own the PBX.
- What’s the failure budget? If a dead PBX for 48 hours is unthinkable and there’s no spare hardware, you’re already living on borrowed time — pick a path this quarter.
Frequently asked questions
What is a traditional PBX?
On-premise phone-system hardware — a dedicated cabinet or server in your building that handles extensions, routing, and voicemail, historically connected to the telephone network by analog copper lines or PRI/T1 circuits. It contrasts with a cloud PBX, where a provider runs the same functions from its own infrastructure.
Is a cloud PBX always cheaper than keeping a traditional PBX?
No. A depreciated PBX with cheap maintenance can beat per-seat subscriptions on visible cost — until hardware risk, climbing legacy-circuit rates, and technician scarcity are priced in. Cloud wins on predictability and zero ownership; owned IP PBX + SIP trunks wins on per-user cost at scale; the traditional system only wins while nothing breaks.
Can I keep my old PBX and just replace the phone lines?
Often yes, as a transition: a SIP gateway (or the PBX’s own IP trunk card) lets an existing system use SIP trunks in place of retired copper or PRI. It solves the carriage pressure without touching the hardware pressure — a good first step, not a destination.
Do my phone numbers change when I leave a traditional PBX?
No. Numbers are portable by FCC rule — they move to the new carrier through the LNP process while your existing service keeps working, whether you land on a cloud PBX or on SIP trunks feeding a new system.
SIPNEX is an FCC-licensed carrier for either exit: cloud PBX with every feature included, or SIP trunks for the PBX you keep — numbers ported, calls signed at A-level attestation. Talk to an operator or see rates.
Keep reading.
The carrier built by operators, for operators.
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.