Lifecycle timeline
ShoreTel and Mitel support dates
| Product | What happened | Date / status |
|---|---|---|
| ShoreTel 14.2 / Mitel 14.2 | End of life | September 2020 |
| ShoreTel Connect Onsite | Renamed MiVoice Connect after Mitel acquired ShoreTel | Current name: MiVoice Connect |
| Mitel MiVoice Connect | End of Technical Support | December 31, 2029 |
| ShoreTel Connect Cloud / MiCloud Connect | End of sale; later acquired by RingCentral | June 2022 / June 2024 |
Primary source: Mitel, “What Happened to ShoreTel’s Products?”. Mitel’s Product Release Lifecycle Policy explains release-level support and the requirement for active software assurance. Always confirm your release and contract with your Mitel partner.
Avoid a naming mistake
Which ShoreTel system do you actually have?
ShoreTel 14.2
The pre-Connect release. It is not made current simply because Mitel acquired the company; Mitel lists it as EOL since September 2020.
MiVoice Connect onsite
The renamed ShoreTel Connect Onsite platform. Record the exact release, service pack, switches, appliances, and support entitlement.
MiCloud Connect
The former ShoreTel Connect Cloud service. RingCentral acquired the product assets and customer base in 2024, so its transition path differs from onsite.
MiVoice Business
A different Mitel call-control platform. Do not apply MiVoice Connect’s 2029 date to MiVoice Business releases without checking Mitel’s lifecycle matrix.
Why plan now
The deadline is not the only risk
- Security fixes depend on a supported release and active coverage. Mitel has published critical MiVoice Connect advisories; unsupported builds may not receive the remediation path you need.
- Expansion gets harder first. Licensing, replacement switches, compatible handsets, and certified technicians can tighten before the final support date.
- Adjacent products have their own clocks. Contact center, mobility, voicemail, conferencing, and phone models may not match the core system date.
- Operating-system dependencies age underneath the PBX. Windows, browsers, certificates, hypervisors, and integrations can force work before 2029.
Example security source: Mitel Product Security Advisory 23-0004, which identifies affected MiVoice Connect versions and recommends updating.
Migration choices
Stay with Mitel, move to cloud calling, or split the stack?
Move within Mitel
Preserves vendor familiarity and may allow selected endpoint or workflow reuse. Validate the commercial model and the long-term roadmap.
Move to UCaaS
Replace onsite call control with Teams Phone, RingCentral, Zoom Phone, Webex Calling, 8x8, or another cloud service.
Separate contact center
Move complex queues and agent workflows to a dedicated CCaaS while choosing employee calling independently.
Bridge with support
Use existing or third-party support to buy a defined window. Set the exit date before signing the bridge contract.
Start by exporting the dial plan, DIDs, route points, workgroups, auto attendants, schedules, prompts, and user/extension list. Then inventory ShoreTel voice switches, virtual appliances, edge devices, phones, analog ports, recording, and every contact-center dependency.
FAQ
Quick answers
Is Mitel itself going end of life?
No. This lifecycle applies to specific products and releases, not the entire company or portfolio.
Can we wait until 2029?
You can operate a supported MiVoice Connect system during the runway, but waiting until the deadline compresses budgeting, contract negotiation, number porting, and testing. A 2027–2028 decision window is safer for a complex estate.
Can ShoreTel phones be reused?
Sometimes, depending on model, firmware, and destination. Treat reuse as a tested cost option, not an assumption.
Related guides