Your On-Prem PBX Is End-of-Life: Repair, Replace, or Go Cloud?

When a manufacturer declares your PBX end-of-life, three honest options remain: repair it once more, replace the on-premise PBX with new hardware, or move to a hosted system. Which one is right depends on how much service life the chassis and cards have left, and on whether anyone still answers the phone when they fail.

What does end-of-life mean for a phone system?

End-of-life means the manufacturer has stopped producing the product. What matters operationally is the date after it: end-of-support, when security patches, firmware, and parts availability stop.

Between those dates a PBX is inconvenient. After the second one it is a risk with a schedule attached, because the failure mode is not gradual. A power supply or a line card fails, and the question becomes whether a used unit exists on the secondary market and whether anyone within driving distance knows how to seat it.

Three questions establish where you actually are:

• Is your maintenance contract still renewable, and at what price?
• Can you name the person who would fix this at 7am on a Monday — not a company, a person?
• Are the trunk cards you depend on still made, or are you already buying refurbished?

If the answer to the second is "the guy who installed it, and he retired," you are past the decision point regardless of how the hardware looks.

Is it worth repairing an old PBX?

Sometimes, and the honest case is narrower than vendors on either side will tell you.

One more repair cycle makes sense when four conditions hold together: the failure is a discrete component rather than the platform, parts are available new or reliably refurbished, you have a support relationship you trust, and you have a business reason to defer a project for 12 to 24 months — a lease ending, a building move, an acquisition in progress. Spending a few hundred dollars on a card to buy a year of stability is a rational trade, and running a migration during a merger is how migrations go badly.

Repair stops being reasonable when you are buying parts from listings rather than distributors, when the same subsystem has failed twice, or when the system has become the reason you cannot do things — no remote extensions, no way to change the after-hours greeting without a site visit, no call data beyond the paper log. At that point the repair is not preserving capability. It is preserving a constraint.

Should I replace my on-premise PBX with new hardware or go cloud?

Both are real answers. The comparison that matters is not features on a sheet — it is who is responsible when something breaks, and what the failure of a single building does to your phones.

On-premise still wins in specific situations. Analog infrastructure that must stay — overhead paging, elevator lines, alarm circuits — does not disappear because you moved the call control. Sites with genuinely poor internet and no second circuit are a real argument too, though that one is usually cheaper to fix at the circuit than at the phone system.

Where hosted wins is the boring part: nobody on your staff owns the platform. Signal runs each client on an isolated phone server, so upgrades, patching, and capacity are ours to manage, and the surface you touch is a portal rather than a chassis. For the vocabulary, see what hosted PBX, cloud PBX, and VoIP actually mean.

Can I keep my existing phones and wiring?

The wiring, usually. The phones, sometimes.

Cat5e or Cat6 runs to each desk carry SIP phones without modification, and switches that supply Power over Ethernet already cover the handsets. Digital station cabling for a proprietary PBX is different — those runs terminate at a card in the chassis, and the endpoints on them are not SIP devices.

For handsets, the dividing line is whether the phone speaks SIP and whether the provider provisions that model. Signal auto-provisions Polycom phones by MAC address, including much of the older VVX and SoundPoint range, so a shop full of serviceable handsets is often reusable. Proprietary digital sets are not. Can I keep my desk phones goes through the specifics, and the auto-provisioning explainer covers how a phone gets its configuration. Check the network requirements before you plan around reuse — bandwidth, QoS, and the firewall SIP ALG setting that causes more one-way-audio tickets than anything else.

What happens to my phone numbers when I replace a PBX?

That depends on how the numbers arrive today, and this is the piece that sets your timeline.

If your PBX is fed by analog lines or a PRI, your numbers live with that carrier and must be ported. Plan two to four weeks and expect at least one records mismatch against the losing carrier's billing record. If you already have SIP trunks, the numbers may move on a shorter path, but the trunk contract and its termination clause still apply.

Either way, build and test the new system on temporary numbers first, so the port changes one thing — where calls arrive — rather than being the moment you discover a gap in your call flow.

Emergency addresses do not carry over. E911 is registered per location and per number against a validated street address, so every location and number gets a record established on the new platform. Our E911 locations guide explains what a valid dispatchable address requires, including floor and suite detail.

Frequently asked questions

What does end-of-life mean for a phone system?

End-of-life means the manufacturer stopped building the product. End-of-support, which follows, means firmware updates, patches, and official parts supply have ended. A system between the two dates is workable; a system past end-of-support fails without a repair path, and the cost of that failure is measured in days of missed calls.

Is it worth repairing an old PBX?

It can be, when the failure is a single component, parts are available from a real distributor, you have a support relationship you trust, and a business reason argues for deferring a migration by a year or two. It stops being worth it once you are sourcing parts from listings or the same subsystem has failed twice.

Should I replace my on-premise PBX with new hardware or go cloud?

New on-premise hardware makes sense when you must keep analog infrastructure — paging, elevator lines, alarm circuits — or when site internet is genuinely unreliable. Otherwise hosted removes the platform from your staff's responsibility, keeps cost flat and monthly, and lets calls reroute when a building goes dark.

Can I keep my existing phones and wiring?

Ethernet cabling almost always carries over. SIP handsets often do — Signal auto-provisions Polycom phones by MAC address, including older VVX and SoundPoint models. Proprietary digital sets tied to a legacy PBX chassis do not, because they are not SIP devices and their station cabling terminates at a card.

What happens to my phone numbers when I replace a PBX?

They come with you, but they have to be ported. Numbers fed to an old PBX over analog lines or a PRI belong to that carrier, so plan two to four weeks and expect at least one mismatch against the losing carrier's billing record. Existing SIP trunks may move faster, though the trunk contract still applies. Build and test on temporary numbers first so the port changes only where calls arrive.

How long does the whole migration take?

Budget four to six weeks from decision to cutover if numbers must be ported, since porting alone runs two to four weeks. System build and handset provisioning happen in parallel on temporary numbers, so the port date is the only hard dependency.

If you want a straight assessment, tell us what PBX you have, how your lines arrive, and what analog equipment is attached. We will tell you what carries over and what does not — including when the sensible answer is to wait a year.