Cisco UCCX support ends December 31, 2028. After that date there are no more bug fixes, no security patches, and no TAC coverage. Production contact centers running past EOL inherit compliance and security exposure they cannot remediate.
The migration target is Webex Contact Center — and the right time to start your assessment is now, not the quarter before the deadline. Migrations at enterprise scale run 3–9 months.
20+ years Cisco UC · Certified CC Engineer
Four published Cisco milestones per UCCX release. Each one reduces what Cisco will do for you, and each one increases your migration risk.
No new UCCX licenses sold. Cisco stops accepting new orders for the platform. Existing customers remain on existing support contracts.
Routine updates and minor feature releases stop. Only critical patches (under extended support) flow downstream.
Cisco engineering stops accepting new defect reports and no longer ships remediation for known bugs. Workarounds become the only path forward.
No more CVE remediation, no more TAC cases, no more engineering assistance. Running UCCX past this date means running an unpatched, unsupported system with active compliance liability.
UCCX is not being deprecated quietly. Cisco has been unambiguous about the replacement path for years.
Webex Contact Center (WxCC) is Cisco's cloud-native replacement for UCCX. Where UCCX lived on a Windows server in your data center and ran Java-based script files (.aef) for call flows, WxCC runs on AWS, is administered through Webex Control Hub, and wires call flows together in a visual Flow Designer. It is subscription-based, continuously updated, and supports digital channels (email, chat, SMS) and AI features (virtual agents, Webex AI Assistant) that UCCX never had. UCCX 15 exists as a short-term on-premise bridge — useful only when a regulatory requirement prevents cloud deployment. The roadmap is unambiguously cloud-first, and forcing five more years into a platform with a published end-of-life date is a hard sell to anyone in your security or compliance org.
Concepts carry over: queues, skills, agent teams, supervisors, routing logic, real-time reporting. What does not carry over is the implementation — UCCX scripts do not import into WxCC, CUIC reports do not migrate to the WxCC Analyzer, and Finesse desktops are replaced by the browser-based Webex Desktop. Every migration is a rebuild, not a re-platform. The good news: the rebuild work has been done many times now, and the shape of a well-executed UCCX → WxCC migration is well-understood. The UCPivot CUCM Migration Advisor is built for this work — upload your BAT export and get a structured plan for how your environment maps across.
Three ways to move from where you are to WxCC. Pick the one that matches where you are in the process.
Analyze your CUCM BAT export in minutes. Get DN mapping, hunt group diff analysis, and forwarding rules translated for Webex Calling — before you commit to a full engagement.
Open the tool5-phase methodology, realistic timelines by deployment size, the seven gotchas that burn migrations — all written from hands-on engagements.
Read the guide10 questions, 5 minutes, scored readiness report (Ready / Plan / At Risk) with specific actions for your environment. Free, no signup required.
Start the assessment