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.
The 2029 runway
How to use the runway to December 31, 2029
Three and a half years sounds like plenty. Worked backward, it is not: vendor selection takes one to two quarters, contracting another, and a multi-site cutover, porting numbers, staging phones, rebuilding call flows, training, six to twelve months. Start the math at December 31, 2029 and the real decision lands in 2027–2028.
2026–2027: inventory and strategy
Document releases, switches, workgroups, integrations, and contracts. Decide whether calling and contact center move together or separately.
2027–2028: selection and contracting
Run three or four vendors against one comparable scope, negotiate term and rate, and lock implementation dates while you have leverage.
2028–2029: migration by site
Pilot a small site first, refine the runbook, then migrate in waves. Keep the last complex site well clear of the deadline.
Throughout: co-terminate contracts
Pull circuits, SIP trunks, maintenance, and software assurance onto one common end date so nothing auto-renews past your exit.
MiCloud Connect customers
What the RingCentral deal means in practice
If you are on MiCloud Connect, the former ShoreTel Connect Cloud, your situation differs from an onsite estate. The service reached end of sale in June 2022, and RingCentral acquired the product assets and customer base in 2024. Your renewal and transition conversation now runs through RingCentral, and the default path is its own platforms: RingCentral cloud calling for users and RingCX for the queues.
The default may be the right answer, RingCX prices aggressively and bundles AI, but being acquired is not an obligation. Treat the RingCentral proposal as the incumbent quote: re-scope queues and integrations, price two or three alternatives against it, and confirm how numbers and contract terms carry over before agreeing to a like-for-like seat swap.
Replacement paths
UCaaS for calling, CCaaS for the queues
Most ShoreTel estates did two jobs: everyday employee calling, and workgroup routing for support, sales, or dispatch desks. Modern replacements split those jobs.
Cloud calling for users
Teams Phone, RingCentral, Zoom Phone, Webex Calling, or 8x8 replaces dial tone, voicemail, and auto attendants for the workforce.
CCaaS for the queues
Workgroups map to a dedicated cloud contact center with skills routing, callbacks, and AI. New to the category? Start with what CCaaS is.
One vendor for both
8x8 and RingCentral sell UCaaS and CCaaS as one platform with one directory, simplest to run if the fit works on both sides.
Best-of-breed split
Pair any calling platform with a voice-and-outbound specialist like Five9, or run the contact center inside Microsoft Teams if you are standardizing there.
Before shortlisting, translate the workgroup export into real requirements. Many are simple hunt groups any UCaaS handles at no extra cost; a few are genuine queues that deserve CCaaS licensing. Buying agent seats for hunt groups, or forcing real queues into a calling platform, are the two costliest mistakes here.
Budget
Migration cost factors
Planning-grade numbers, consistent with our CCaaS pricing guide:
- Contact-center seats: most CCaaS contracts land between $50 and $110 per agent per month, full omnichannel $70–$95, AI and workforce suites $95–$110. Cloud calling seats cost far less.
- Implementation: one-time professional services for routing, IVR rebuilds, and migration typically run from a few thousand dollars to five figures on complex builds.
- Telephony usage: metered outbound or international traffic can add 20–40% on top of seat prices; inbound-heavy teams see less.
- Handsets: budget replacement phones unless reuse is tested and confirmed on the target platform.
- Double-running: expect one to three months paying old and new in parallel during a site-by-site cutover.
- Negotiation: mid-market and enterprise deals routinely close 15–30% below list with competing quotes, a deadline only works against you if vendors know you have no alternatives.
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.
Do MiCloud Connect customers have to move to RingCentral?
No. RingCentral acquired the MiCloud Connect assets and customer base, so the transition conversation runs through RingCentral, but you can price its proposal against any other UCaaS or CCaaS provider. Treat it as the incumbent quote, not the only option.
What does replacing MiVoice Connect cost?
For the contact-center side, most CCaaS contracts land between $50 and $110 per agent per month, plus one-time implementation running from a few thousand dollars to five figures. Cloud calling seats cost much less.
Should calling and the contact center move at the same time?
Not necessarily. Many organizations move the contact center first, it carries the most risk and gains the most from cloud features, then migrate calling site by site. The reverse also works, as long as one decision does not silently constrain the other.
Related guides