Building the business case for retiring your legacy PBX

Most legacy PBX systems do not fail dramatically. They fade: support contracts get more expensive, spare parts get scarcer, the engineers who know the system retire, and every office move or team change turns into a billable engineering visit. The business case for replacement is rarely about a single number — it is about comparing the full cost of standing still with the cost of moving.

The costs of keeping the PBX

• Maintenance and support contracts that typically rise as the platform ages and the vendor pushes customers towards its own cloud offering.
• ISDN line rental and call charges — costs that disappear entirely under a Teams calling plan or SIP-based model, and that are living on borrowed time given the PSTN switch-off.
• Moves, adds and changes. Every reconfiguration of an on-premises PBX tends to need specialist time. In Teams, the same change is an administrator action in a web portal.
• Parallel infrastructure. Separate handsets, voicemail systems, call recording platforms and conferencing services, each with its own contract and refresh cycle.

The costs of moving — counted honestly

A credible business case includes the licensing uplift for Teams Phone, PSTN connectivity via Operator Connect or Direct Routing, any network remediation identified in a readiness assessment, headsets or handsets for users who need them, and the migration project itself. Overstating the savings undermines the case faster than any objection.

The benefits that are hardest to spreadsheet

• One platform for all communication — calls, meetings and chat in the application users already work in, wherever they are working.
• Resilience by design. Telephony no longer depends on a box in a comms room; users can take calls from any location on any device.
• An exit from the upgrade treadmill. The platform is evergreen; there is no future PBX refresh project on the horizon.

Framing it for the board

The strongest framing is usually risk, not savings: the PSTN switch-off puts a fixed end date on the status quo, so the real choice is between a planned migration on your timetable and a forced one on someone else's. Cost reduction is the supporting argument, not the headline.