At a glance
Cisco UCCX 12.5 and 12.6 lifecycle dates
Cisco published two June 2025 notices for the same application releases. The dates overlap, but the notices govern different ways of buying the software. EOL15696 covers on-premises software and licenses; EOL15603 covers on-premises Flex subscriptions. Your first planning task is identifying which commercial model and part numbers you actually own.
| Commercial model | Milestone | Date |
|---|---|---|
| Software and licenses EOL15696 | End of sale | December 31, 2025 |
| Software and licenses EOL15696 | Last ship date | March 31, 2026 |
| Software and licenses EOL15696 | End of software maintenance releases | December 31, 2026 |
| Software and licenses EOL15696 | End of new service attachment | December 31, 2026 |
| Software and licenses EOL15696 | End of service-contract renewal | December 31, 2027 |
| Software and licenses EOL15696 | Last date of support | December 31, 2027 |
| Flex subscriptions EOL15603 | End of sale for new subscriptions | December 31, 2025 |
| Flex subscriptions EOL15603 | End of subscription change or renewal | December 31, 2026 |
| Flex subscriptions EOL15603 | Last date of support | December 31, 2027 |
Primary sources: Cisco EOL15696 for on-premises software and licenses and Cisco EOL15603 for on-premises Flex subscriptions. Both were announced June 30, 2025. The Cisco bulletins and your active contract control if a summary ever differs.
Read the notice correctly
The announcement is broader than UCCX
Both notices cover version 12.5 and 12.6 of Cisco's on-premises contact-center applications: Unified Contact Center Enterprise (UCCE), Packaged Contact Center Enterprise (PCCE), Unified Contact Center Express (UCCX), and Customer Voice Portal (CVP). Their product tables include associated application software, media kits, licenses, agent entitlements, servers, and other part numbers.
This page stays focused on UCCX. That matters because a UCCX estate is not interchangeable with UCCE or PCCE simply because one Cisco bulletin names all four. The architecture, scale, scripts, integrations, operational teams, and migration workload differ. If an integrator says “the Cisco contact center is EOL,” make them identify the exact application, release, purchasing model, and affected SKU.
Version is only one field
“12.5” or “12.6” tells you the software generation. It does not tell you whether EOL15696 or EOL15603 controls your licensing and renewal path.
CUCM has its own clock
UCCX depends on Cisco call control, but the UCCX notice does not replace the lifecycle notice for CUCM. Read the Cisco CallManager end-of-life guide and align both projects.
Support is entitlement-based
Cisco's bulletins condition continued TAC service on active, paid support contracts or subscriptions. The published last-support date is not a promise that every estate is covered until then.
Adjacent tools need separate proof
Recording, workforce management, CRM connectors, custom Finesse gadgets, and third-party reporting may have their own compatibility and support policies.
Milestone decoder
What each Cisco date changes
End of sale
December 31, 2025 was the last date to order the affected products through Cisco's point-of-sale mechanisms. It did not turn off deployed systems. It removed the normal route for buying new affected products and started the final lifecycle runway.
End of software maintenance
For EOL15696 application software, December 31, 2026 is the last date Cisco Engineering may issue final maintenance releases or bug fixes. Cisco states that engineering will no longer develop, repair, maintain, or test the affected product software after that date. TAC access and new engineering work are therefore different questions.
End of new service attachment
Also on December 31, 2026, affected perpetual software that is not covered can no longer be added to a new or existing service-and-support contract. An uncovered deployment cannot assume it can buy its way back into support later.
End of change or renewal for Flex
For EOL15603, December 31, 2026 is the last date to renew or add to an existing affected subscription. Cisco's footnotes say the requested start date for subscription changes or renewals must be on or before that date, and the projected term end date must be on or before December 31, 2027.
Last date of support
December 31, 2027 is the final day for applicable service and support under entitled contracts or subscriptions. Cisco says support services are unavailable and the product becomes obsolete after that date. Nothing in the notices says a server automatically shuts down; the operational risk is running it without Cisco behind it.
Do this first
Audit contracts and SKUs before choosing a path
A UCCX inventory that stops at hostname, version, and agent count is not enough. Tie technical discovery to commercial evidence so you know which rights expire when.
- Export the commercial record. Collect Cisco Commerce orders, Smart Account entitlements, subscription details, service-contract numbers, renewal quotes, and partner statements of work.
- Match affected part numbers. Compare every UCCX media, server, Standard or Premium agent, and related license SKU with the product tables in EOL15696 and EOL15603. Do not infer the notice from an invoice description alone.
- Confirm the actual coverage end. Ask the Cisco partner to document the contract or subscription end date, TAC entitlement, renewal/change deadline, and any items already outside support.
- Inventory the solution, not just UCCX. Record CUCM release, UCCX nodes and high availability, agents and ports, Finesse customizations, CUIC reports, scripts, prompts, calendars, outbound campaigns, recording, workforce tools, CRM integrations, certificates, identity, and disaster-recovery design.
- Separate standard from custom. Mark every script, gadget, report, API integration, database export, and operating procedure that cannot be reproduced from standard documentation. Those items drive testing and migration services.
- Put the answer in writing. “Supported through 2027” is too vague. The useful answer names the SKU, entitlement, milestone, date, and party responsible for escalation.
The cost of waiting
The practical risks between now and final support
A final support date can create false comfort. The safer question is whether the estate can absorb a failure, security issue, compatibility change, or staffing loss at every point in the runway.
Maintenance stops first
For perpetual application software, the final year of TAC availability begins after the software-maintenance deadline. Escalation remains valuable, but it is not the same as ongoing engineering fixes.
Renewal flexibility narrows
Flex customers cannot leave the commercial decision until 2027. The change and renewal gate closes a year before final support, with subscription terms constrained by the final date.
Compatibility becomes a project risk
Browsers, identity systems, certificates, hypervisors, CUCM, phones, recording, CRM, and security controls keep changing even when the contact-center release does not.
Knowledge walks out
Custom UCCX scripts and reports often depend on a few administrators or partners. Capture the design and test cases before the people who understand them become the critical path.
The UCCX support site continues to publish field notices and security advisories, which is another reason to preserve a supported path during migration. End-of-life planning is not evidence that the current system is failing; it is how you avoid discovering an unsupported dependency during an incident.
The real decision
UCCX 15, Webex Contact Center, or a wider shortlist?
Upgrade to UCCX 15 or higher
Cisco's two notices encourage affected customers to move to Version 15 or higher, and Cisco lists UCCX 15 as an available release. This is the natural path when on-premises control, existing Cisco operations, or local integrations outweigh the benefits of changing architecture. It is still a project: validate the supported upgrade sequence, CUCM compatibility, licensing, infrastructure, high availability, integrations, scripts, reporting, and operational procedures. The Cisco UCCX support page is the first-party starting point for current release documentation.
Move to Webex Contact Center
For teams that want Cisco cloud contact-center operations rather than another on-premises cycle, Webex Contact Center belongs in the comparison. Treat it as a migration, not a version upgrade. Rebuild and test routing, IVR behavior, agent and supervisor workflows, reporting, recording, workforce processes, CRM integration, identity, and voice connectivity. Ask the proposal to state exactly what is automated, what is rebuilt, and what historical data remains accessible.
Run a vendor-neutral CCaaS evaluation
The forced project is also the moment to test the broader market. A cloud platform may simplify lifecycle management, but the right answer depends on routing depth, digital channels, workforce tools, AI, compliance, global voice, integrations, and commercial terms. Use the CCaaS pricing guide to normalize seat and add-on costs instead of comparing headline prices.
Stage the contact-center and CUCM decisions
You do not necessarily need one all-at-once cutover. Some organizations upgrade UCCX to restore runway before a later cloud move. Others keep supported CUCM call control while moving customer-service queues to a cloud contact center. Either path needs a supported voice-integration design, explicit vendor ownership, and a dated end state so the bridge does not become permanent.
Reduce cutover risk
A staged UCCX migration plan
- Freeze the evidence. Export scripts, prompts, calendars, team and skill assignments, application settings, reports, integration maps, number inventories, and current performance baselines.
- Classify every call flow. Separate standard queues from complex routing, regulated recording, outbound, emergency, multilingual, after-hours, and high-value workflows.
- Build acceptance tests before the replacement. Define expected routing, prompts, screen pops, dispositions, recordings, reports, failover, and supervisor controls using real scenarios.
- Pilot a low-risk queue. Choose a contained team with representative integrations, then hold the old route open for rollback while the new environment proves stability.
- Move in waves. Group queues by shared scripts, business owners, integrations, and operating hours. Avoid mixing the most complex flows into the first wave.
- Run parallel reporting. Reconcile queue counts, service levels, abandons, handle time, recording, and disposition data before declaring a wave complete.
- Retire deliberately. Preserve required historical data, close licenses and contracts at the right date, remove routing and admin access, and document the final support boundary.
Plan backward
Work backward from December 31, 2026
The final date of support is December 31, 2027, but December 31, 2026 is the date that protects optionality. A complex contact-center migration begun after that milestone may spend most of its delivery period without new maintenance releases or without the ability to change an affected Flex subscription.
| Window | Planning objective |
|---|---|
| Now through 90 days | Complete the SKU, contract, architecture, integration, and call-flow inventory. Get written entitlement confirmation and compare UCCX 15, Webex Contact Center, and one alternative. |
| 3–6 months | Select the architecture, negotiate licensing and services, finish the target design, and create test cases and migration waves. |
| 6–12 months | Build, integrate, pilot, train, and move lower-risk queues. Preserve rollback and parallel reporting. |
| Before December 31, 2026 | Complete any required Flex renewal/change or new service attachment and have a funded, contracted migration underway. |
| Before December 31, 2027 | Finish production migration, stabilize the target, archive required data, and retire the affected UCCX estate before Cisco support ends. |
A small, documented UCCX deployment may fit in three to six months. A multi-site estate with custom scripts, CRM, recording, workforce tools, and strict change windows should reserve nine to fifteen months. Discovery and acceptance testing are the wrong places to recover a late start.
Budget lines
Migration costs beyond the agent license
Comparing a UCCX upgrade with CCaaS requires a common scope. Include the work and dependencies that a seat price does not show:
- Licensing and support. UCCX, CUCM, infrastructure, subscriptions, support contracts, cloud agent tiers, telephony usage, AI, workforce tools, and recording storage.
- Platform infrastructure. Compute, storage, backup, disaster recovery, certificates, monitoring, and administrator time for the on-premises path; connectivity, edge, and voice design for cloud.
- Call-flow rebuild. Script discovery, redesign, IVR prompts, calendars, overflow, callbacks, outbound campaigns, testing, and documentation.
- Integrations. CRM screen pops, APIs, bots, identity, recording, workforce management, quality management, data exports, and custom Finesse gadgets.
- Data and reporting. Historical retention, migration or archive, report recreation, dashboards, data feeds, and parallel reconciliation.
- Professional services. Architecture, implementation, project management, carrier work, security review, and specialized Cisco or application expertise.
- Change and parallel operation. Agent and supervisor training, sandbox time, double licensing, overlapping support, pilot staffing, and rollback capacity.
Ask every bidder to price the same inventory and acceptance tests. A lower subscription can lose once custom migration work is added; a larger first-year project can win if it removes infrastructure and recurring administration. Start with a contact-center estimate, then replace assumptions with scoped quotes.
FAQ
Quick answers
Is Cisco UCCX 12.5 or 12.6 already end of life?
The end-of-sale date has passed, but the support runway has not. Cisco stopped selling the affected UCCX 12.5 and 12.6 software, licenses, and Flex subscriptions on December 31, 2025. For perpetual application software, software maintenance and new service attachment end December 31, 2026. For Flex, changes and renewals end that day. The last date of support is December 31, 2027 under both notices, subject to an active contract or subscription.
Will UCCX stop working on December 31, 2027?
No automatic shutdown is described in Cisco's notices. December 31, 2027 is the last date Cisco will provide applicable service and support under an entitled contract or subscription. After that date, Cisco says support services are unavailable and the product becomes obsolete. The system may continue running, but recovery, security, compatibility, and escalation become your responsibility.
Which Cisco UCCX end-of-life notice applies to us?
EOL15696 applies to the affected on-premises software and licenses, while EOL15603 applies to the affected on-premises Flex subscriptions. Do not decide from the version number alone. Match the part numbers on your Cisco order history, Smart Account, subscription, and support contract to the affected-product tables in both notices.
Do the Cisco notices cover only UCCX?
No. Both notices cover version 12.5 and 12.6 on-premises contact-center applications across UCCE, PCCE, UCCX, and CVP, plus the associated software and licenses or Flex subscriptions. This guide focuses on UCCX because its migration design, agent scale, scripts, and CUCM dependencies differ from the enterprise products.
Is UCCX 15 the direct replacement for UCCX 12.5 and 12.6?
It is Cisco's current on-premises path: Cisco encourages affected customers to move to Version 15 or higher, and UCCX 15 is an available release. Treat it as an upgrade project rather than an automatic entitlement or a configuration copy. Confirm licensing, supported upgrade sequence, CUCM compatibility, infrastructure, integrations, and the exact feature behavior you depend on before choosing it.
Can we keep CUCM and move only the contact center?
Potentially. The call-control and contact-center decisions can be separated, but the target contact center still needs a supported voice-integration design. Compare a UCCX 15 upgrade with Webex Contact Center and other CCaaS options while separately mapping the CUCM lifecycle. This can reduce the size of one cutover, but it requires clear ownership of routing, numbers, reporting, and support boundaries.
How long should a UCCX migration take?
Allow roughly three to six months for a small, well-documented deployment and nine to fifteen months for a multi-site or integration-heavy contact center. Those are planning ranges, not Cisco commitments. Custom scripts, CRM integrations, recording, workforce tools, number routing, testing, and agent training usually determine the schedule.
Related guides