PBX lifecycle and end of life: extending its life safely
A PBX that works can serve your organisation for many more years, if it is kept secure. This is how the manufacturers’ lifecycle works up to end of support (EOS) and end of life (EOL), and how to extend the life of your PBX safely.
In short
- As long as the PBX gets security fixes, spare parts are available and it does what your organisation needs, it is a good investment.
- Mitel requires active Software Assurance (SWA) for support and fixes. At Alcatel-Lucent Enterprise (ALE), the Software Premium Service (SPS) agreement provides new versions and security fixes.
- The manufacturers announce product retirements in advance. Mitel’s intention is to provide at least five years of support after end of sale.
- Virtualisation, upgrading within the platform and running Teams alongside all extend the life of your PBX. So does a SIP trunk via an SBC, which replaces older connections to the operator.
- Write a lifecycle plan, so the next step is taken in good time.
How Mitel’s lifecycle works
Mitel’s lifecycle policy is public and applies to products with Software Assurance or a subscription, which includes Mitel MX-ONE, Mitel OpenScape 4000 and Mitel OpenScape Voice:
- Active Software Assurance is required for any support at all, and provides new versions, fixes and hotfixes.
- Bugs are fixed in the latest version. Critical bugs are fixed in the previous major version for up to 18 months after the new one is released.
- A product retirement is announced at least 90 days before the last order date, and the intention is to provide at least five years of support after that.
- The phases are end of sale, end of expansion, end of technical support and end of life (EOL), when the product is retired completely.
- After end of technical support, Mitel decides at its own discretion which security fixes are made.
- For some OpenScape products, extended support is available for up to 18 months, as a bridge while an upgrade is planned.
We find out from Mitel which dates apply to your specific version.
Alcatel-Lucent Enterprise
ALE notifies its partners of product retirements. According to ALE, a valid SPS agreement gives access to new versions and security fixes for Alcatel-Lucent OmniPCX Enterprise.
What happens without software support
- Security: vulnerabilities may no longer be fixed, and the risk increases if the PBX can be reached from the internet or via remote access.
- Spare parts: they remain available after end of sale, but supply may become limited, and standard servers follow the server manufacturer’s lifecycle.
- Integrations: new versions of SBCs, contact centres and other systems often require a minimum PBX version.
- Certificates: certificates in older equipment can expire and stop features from working.
- Skills: knowledge of older versions and of your configuration becomes more fragile over time.
- The operator’s network: older connections are phased out over time, so the PBX needs a plan for SIP.
How to extend the life of your PBX safely
| Action | What it gives you |
|---|---|
| Up-to-date software | Fixes, security features, new integrations and the manufacturer’s support, via Software Assurance or SPS |
| Virtualisation | Old servers are replaced with virtual machines. MX-ONE, OpenScape 4000 and OmniPCX Enterprise can all run virtually |
| Upgrade within the platform | Numbering plan, phones, extensions and integrations are kept |
| SIP trunk via SBC | Replaces older connections and protects SIP traffic |
| Teams alongside the PBX | Direct Routing via a certified SBC, with users moving at their own pace |
| Spare parts | Shorter resolution times for faults on cards, gateways and DECT base stations |
| Separate network segment | The PBX and the remote support connection are protected and cannot be reached directly from the internet |
Make a plan
A written lifecycle plan shows when the next step is needed, so it can be budgeted for and taken without rushing. It usually covers version and support status, the end date of your software assurance, hardware age, integrations, when an upgrade or virtualisation is needed and what is planned for Teams.
The guide Upgrade or replace your PBX? covers the questions to ask when it is time to choose between upgrading and replacing.
Last updated 14 October 2026.
Common questions
More questions
How long does a PBX last?
There is no fixed answer. With current software, spare parts and a plan, a PBX can serve your organisation for many years. What decides it is security fixes, spare parts and whether it does what you need.
Is it risky to use a PBX that no longer gets updates?
The risk grows over time, especially if the PBX can be reached via the internet or remote access. Put it in a separate network segment and plan an upgrade or replacement in good time.
Can we buy extended support?
For some OpenScape products, Mitel offers extended support for up to 18 months, as a bridge while the upgrade is planned. After that, a partner can still provide support, but without new fixes from the manufacturer.
Do we have to move to the cloud?
No. Many keep their PBX, connect Teams alongside it and move more users when it suits them. What matters is that the PBX is kept secure in the meantime.
Further reading
Guide
Upgrade or replace your PBX?
Decision support for organisations that run MX-ONE or OpenScape today.
Solution
Third-party PBX maintenance
Keep the PBX that works. We take over support for MX-ONE, OpenScape and OmniPCX Enterprise and keep your PBX up to date with the manufacturer’s security fixes.
Product
Alcatel-Lucent OmniPCX Enterprise
Support, upgrades, virtual deployment and Teams integration for OmniPCX Enterprise.
Third-party PBX maintenance
Start with an inventory
Do you have an MX-ONE, OpenScape or OmniPCX Enterprise? We usually start with a simple inventory of your PBX, licences and integrations, free of charge. You then know where you stand, and we can give you a quote for support, operations or replacement.