Official Cisco milestones
CUCM lifecycle date table
| Release / entitlement | End of sale | End of software maintenance | Last support |
|---|---|---|---|
| CUCM 12.5 subscription (EOL14949) | August 31, 2023 | August 31, 2024 | August 31, 2025 |
| CUCM 14 perpetual app software (EOL15245) | April 7, 2025 | April 7, 2026 | April 30, 2027 |
| CUCM 15 | Cisco’s identified on-premises replacement for affected version 14 part numbers; check current lifecycle before purchase. | ||
Primary sources: Cisco EOL14949 for version 12.5 subscriptions and EOL15245 for version 14 perpetual application software.
It is bigger than call control
What the CUCM bulletins include
The notices cover a collaboration stack, not only the CUCM publisher and subscribers. Depending on the bulletin, affected applications include Session Management Edition, IM and Presence, Unity Connection, Emergency Responder, Paging Server, and Prime Collaboration Deployment.
Your phones, gateways, Expressway, contact center, recording, fax, paging, E911, virtualization platform, and third-party integrations each have separate compatibility or lifecycle constraints. A technically supported CUCM release does not automatically make the whole estate supported.
After maintenance ends
The practical risk of staying behind
- No engineering maintenance. After the software-maintenance date, Cisco says engineering will no longer develop, repair, maintain, or test that product software.
- Support is contract-bound. TAC access before the last support date still depends on active, paid service entitlement.
- Compatibility pressure grows. Phone firmware, certificates, browsers, identity platforms, VMware versions, and integrations keep changing.
- An emergency upgrade is a poor cloud strategy. A rushed in-place upgrade can consume the same discovery and testing effort that should have compared Webex Calling, Microsoft Teams Phone, or another UCaaS.
Decision point
Three paths from CUCM
Upgrade to CUCM 15
Best for organizations that deliberately need on-premises call control, existing Cisco integrations, and local operational control.
Move to Webex Calling
The closest strategic Cisco-cloud path. Validate gateways, survivability, contact center, devices, licensing, and migration tooling.
Run a competitive UCaaS process
Compare Teams Phone, RingCentral, Zoom Phone, 8x8, and other providers on total requirements, not just calling seats.
Split UC and contact center
Keep employee calling and customer-service routing as separate decisions when their feature, compliance, or deployment needs differ.
Inventory before you price
Export DNs, DIDs, route patterns, partitions and calling search spaces, hunt pilots, CTI route points, voicemail, gateways, SRST, Emergency Responder locations, recording, contact-center integrations, analog services, and phone models. Price migration services, carrier work, handsets, network readiness, and parallel operation, not only licenses.
The economics
Another on-prem cycle vs a cloud subscription
Upgrading to CUCM 15 is not a license purchase; it is another full on-premises cycle. The realistic budget covers software entitlement, a server or virtualization refresh where hosts age out, upgrade services, certificate and firmware work, and regression testing across gateways, voicemail, recording, and contact center. Recurring costs continue after go-live, maintenance contracts, data-center overhead, specialist admin skills, and in five to seven years the cycle repeats.
Cloud moves the same spending to a per-user subscription with no refresh at the end. For contact-center seats, list prices cluster between $50 and $110 per agent per month, full omnichannel typically $70–$95, and employee calling seats price well below agent seats. Our CCaaS pricing guide breaks down tiers and add-ons.
The honest comparison is total cost over the same five-to-seven-year window. A paid-off cluster looks cheap month to month, until you add the CUCM 15 project, the next refresh, and the digital channels and AI features customers now expect.
Work backward from the date
Planning backward from April 30, 2027
April 30, 2027 is the last date of support in the version 14 perpetual bulletin. Treat it as the end of your runway, not the start of the project, and plan in reverse:
- 3–6 months before: cutover complete. Final porting waves done, parallel run finished. Porting is the least compressible step, large DID inventories move in waves, and rejections reset the clock.
- 6–9 months before: build and pilot. Design signed off, network readiness confirmed, first user groups live.
- 9–12 months before: contracts signed. Quotes, security review, and contracting consume a quarter on their own.
- 12–18 months before: discovery. Inventory, requirements, shortlist, and demos.
Contact-center dependencies compress the runway. If UCCX or another platform relies on CUCM for call control and CTI, it must move before, or with, call control; you cannot retire the cluster underneath it. The same goes for recording, wallboards, attendant consoles, and paging. Counting back from April 2027, the comfortable start date has passed; compress discovery rather than skipping it.
Two shortlists
The Cisco-aligned path vs a vendor-neutral shortlist
The Cisco-aligned path. Webex Calling is the closest strategic Cisco-cloud move, and Webex Contact Center is where Cisco steers UCCX and UCCE estates on the customer-facing side; existing devices, integrations, and account relationships transfer most directly. Validate early rather than assuming: gateway reuse, survivability, contact-center attachment, device compatibility, licensing conversion. Price this path first if your estate is deeply Cisco, but still price it against the market. Incumbent quotes improve when the vendor knows you have credible alternatives.
The vendor-neutral shortlist. A forced migration is the cheapest moment to run a real evaluation, the switching cost is being paid either way. Microsoft-centric organizations should look at Teams Phone with a contact-center layer. For the customer-facing side, dedicated CCaaS platforms such as Five9 and Genesys Cloud typically out-feature UC-attached routing. New to the category? Start with what CCaaS is.
Budget lines
Migration cost factors beyond the subscription
Whichever direction you choose, seat price is only part of the budget. Quotes that look far apart often converge, or flip, once these lines are priced:
- Porting and carrier work. Moving DIDs, toll-free numbers, and fax lines, plus unwinding legacy PRI or SIP contracts; watch for early-termination clauses.
- Network readiness. QoS, PoE, wireless coverage, internet redundancy, and firewall changes; some sites need circuit upgrades before voice can move.
- Devices. Which handsets survive, who goes softphone-only, and what headsets cost at scale.
- Implementation services. IVR and routing rebuilds, integrations, and data migration typically run from a few thousand dollars to five figures on enterprise builds.
- Parallel operation. Weeks or months of running both platforms, double licensing, double administration, while users migrate in waves.
- Training and change management. Rarely itemized in quotes, always paid for in lost productivity if skipped.
List prices are a starting point: with competing quotes and term negotiation, mid-market and enterprise deals routinely close 15–30% below list, and migration line items become negotiable too. Start with a quick estimate of your seat mix.
FAQ
Quick answers
Is CallManager the same as CUCM?
CallManager is the older and still widely used name for Cisco Unified Communications Manager.
Does CUCM 14 stop working in April 2027?
No automatic shutdown is implied. April 30, 2027 is the last support date in the cited perpetual bulletin; operating after it means vendor support is unavailable for those covered products.
Should we upgrade or migrate to cloud?
Compare both before spending on the upgrade. Highly customized or survivability-heavy estates may justify CUCM 15; standard business calling often has stronger cloud options.
How long does a CUCM migration take?
Plan 12 to 18 months for a multi-site estate; a small single-site system can move in three to six months. Porting and contact-center dependencies are usually the pacing items.
What happens to UCCX when CUCM is retired?
Applications that depend on CUCM for call control, UCCX, recording, paging, attendant consoles, must move or be replaced before the cluster is decommissioned. Treat contact-center routing as its own evaluation; it need not land on the same platform as employee calling.
Can we keep our phone numbers if we leave CUCM?
Yes. Numbers belong to your organization, not the platform, and port to the new provider. Budget weeks to months for large inventories, port in waves, and keep old trunks live until every wave confirms.
Related guides