At a glance
Major PBX lifecycle dates
A vendor announcement can apply to a release, licensing model, or entire product family. Verify the exact release and support contract before making a budget decision.
| Platform | Milestone | Date / status |
|---|---|---|
| ShoreTel 14.2 | End of life | September 2020 |
| Mitel MiVoice Connect | End of Technical Support | December 31, 2029 |
| Cisco CUCM 12.5 subscription | Last date of support | August 31, 2025 |
| Cisco CUCM 14 perpetual | Software maintenance / last support | April 7, 2026 / April 30, 2027 |
| NEC UNIVERGE on-premises UC | New system sales ended outside Japan; Americas business transferred | Transition began in 2024–2025; confirm platform entitlement |
Sources: Mitel’s ShoreTel product history, Cisco CUCM 12.5 bulletin, and Cisco CUCM 14 bulletin. NEC dates and entitlements vary by region and successor support arrangement.
Read the fine print
“End of life” is not one event
End of sale
New licenses or systems stop selling. Existing support may continue for years, but expansion can become difficult.
End of software maintenance
Engineering stops regular bug fixes and maintenance releases. Security exposure becomes the bigger concern.
End of renewals
You can no longer extend the vendor contract beyond a specified date, even if the system still runs.
Last date of support
Vendor TAC and entitled services end. After this date, the product is operationally yours alone.
Your paths
Four realistic replacement strategies
- Upgrade on premises. Best when you have hard local-survivability, compliance, or customization requirements and a vendor still offers a supported release.
- Move business calling to UCaaS. Replaces PBX call control with a cloud service such as Teams Phone, Webex Calling, RingCentral, Zoom Phone, or 8x8.
- Separate UCaaS and CCaaS. Keep employee calling simple while moving queues, WFM, recording, and digital channels to a dedicated contact-center platform.
- Use third-party support as a bridge. Useful for a dated transition window; it does not restore vendor engineering, future integrations, or product strategy.
Before an RFP
The PBX exit checklist
- Export users, DIDs, hunt groups, IVRs, schedules, prompts, and call-flow diagrams.
- Inventory fax, elevators, alarms, paging, door phones, modems, and other analog lines.
- Document 911 location requirements and branch survivability.
- Separate employee calling seats from true contact-center agents.
- Test CRM, recording, compliance, and reporting requirements with real workflows.
- Plan number ports in waves and keep rollback routing available.
Platform guides
Check your exact system
FAQ
Quick answers
Can an EOL PBX keep working?
Yes. The risk is that recovery, patching, parts, expansion, and vendor escalation become less predictable precisely when you need them.
Should we replace the phones too?
Not automatically. Some SIP devices can be reused, but old firmware, proprietary features, and poor cloud provisioning may make reuse costlier than a staged refresh.
How long should we allow?
Allow 6–12 weeks for a simple site and 3–9 months for multi-site or contact-center-heavy environments.