It's not just a version upgrade. The capability gap between Cisco's on-premises UCCX and the cloud-native Webex Contact Center spans scripting models, reporting architecture, licensing structure, and the fundamental nature of what's possible with your contact center.
This is the feature-by-feature breakdown engineers use when they're evaluating the switch — not the marketing version.
Direct side-by-side. No marketing language. The goal is to show you exactly where the operational model changes — so you know what you're actually migrating into.
| Capability | Cisco UCCX (on-prem) | Webex Contact Center (cloud) |
|---|---|---|
| Architecture | On-premises VMware/ESXi host, UCCX engine + DB | Cloud-native (AWS) Multi-tenant, Cisco-operated,always-on |
| Scripting Model | Java-based, CCX Script Editor Custom .aef files, Java steps, DB lookups | Visual Flow Designer No-code nodes, HTTP Request, conditions, queues |
| Script Import / Migration | Native files available .aef files, enterprise queue config | No import path Scripts must be analyzed and rebuilt in Flow Designer |
| Call Routing — IVR | Full support Multi-level menus, DB lookups, prompt mgmt | Full support Menu nodes, conditions, digit collection, multilingual |
| Call Routing — Hunt Groups | Built-in Skill-based, overflow, time-of-day | Built-in Queue-based routing, priority, overflow rules |
| Contact Center Features — ACD | Full UCCX ACD CSQs, resource groups, skills, agent teams | Full WxCC ACD Multichannel queues, skills, routing profiles |
| Real-Time Reporting | Supervisor desktop Real-time queue stats, agent states | Analyzer real-time Live dashboards, queue activity, agent scorecards |
| Historical Reporting | CUIC Deep historical data, custom reports, ODBC access | Analyzer Different schema; CUIC data doesn't migrate |
| Call Recording | SIPREC / SPAN / native Calabrio, Verint, NICE, or UCCX native | Native or third-party WxCC native recording + Calabrio/Verint cloud |
| PSTN Options | SIP trunks, PRI, PSTN gateway CUBE, gateway, ITSP integration | Webex Calling PSTN, CUBE hairpin, Edge Connect Multiple on-ramp paths; CUBE hairpin most common |
| Licensing Model | Perpetual + active subscription One-time license + annual support | Per-agent subscription (monthly/annual) Standard or Premium tiers; grows with headcount |
| Agent Desktop | Finesse (desktop or browser) On-premises; Jabber softphone supported | Webex Contact Center Desktop Browser-based, WebRTC audio; replaces Finesse |
| End-of-Life Status | EOL: December 31, 2027 12.5/12.6 end-of-sale Dec 31, 2025 | Active, actively developed Cisco's primary CCaaS investment direction |
| Migration Complexity | N/A — origin platform | Moderate-to-High Script rebuild, CUIC archival, AD provisioning, parallel-run |
| CRM Integration | Native connectors Salesforce, ServiceNow, custom via CTI OS | Built-in + webhook Salesforce, ServiceNow, Webex Connect channel integrations |
| Workforce Management | Via third-party Calabrio WFM, Verint, NICE WFM integration | Cisco WFM integrated Webex Workforce Management, or third-party via API |
| Active Directory / SSO | UCCX native or LDAP sync Local accounts or AD integration | Webex Control Hub Azure AD, Okta, SAML 2.0 IdP; bulk CSV import |
Note on historical reporting: CUIC and WxCC Analyzer are not compatible schemas. Your CUIC historical data does not migrate. Export via ODBC before cutover and load to an external SQL database if retention or compliance requires access after decommission.
The table shows what's different. This section explains why those differences translate to real operational risk — the things that break your cutover timeline if you don't plan for them.
UCCX scripts are Java-based .aef files. There is no export that Webex Contact Center can consume. Every trigger, every branch, every DB lookup must be analyzed, documented, and manually rebuilt in Flow Designer. The scripts themselves aren't the hard part — it's the undocumented business logic buried in them. Organizations that assumed a "migration tool" would handle this routinely add 6–10 weeks to their timeline when they discover what's actually in their scripts.
Your CUIC database (db_cra) and WxCC Analyzer have completely different schemas. The moment UCCX is decommissioned, access to your historical reporting data is gone — unless you've already exported it via ODBC to an external SQL database. This catches operations teams off guard: after cutover, they expect to be able to pull 12-month reports and find only empty Analyzer schemas. Build the archival step into your migration plan, not as an afterthought.
Finesse and Webex Contact Center Desktop are different enough that agents who've run Finesse for years will stumble on the new interface under live call pressure. The desktop replacement is not a configuration change — it's a workflow change. Successful migrations run 2–3 weeks of parallel training with the new desktop before any production traffic hits WxCC. Skip this and you get a post-cutover spike in handle time, misrouted calls, and supervisor escalations that could have been avoided.
The routing engine is one dimension. The integration surface — what your contact center connects to — is where many migrations reveal unexpected scope.
Salesforce, ServiceNow, and custom CTI integrations that surface caller context during routing and agent handling.
WFM integration for scheduling, adherence, and forecasting. Affects how you manage agent capacity post-migration.
Identity management and single sign-on. Affects provisioning speed and security posture for all users.
Desk phone provisioning, softphone configuration, and mass deployment capabilities post-migration.
No. UCCX scripts (.aef files) are Java-based and cannot be imported into WxCC Flow Designer. Every call flow must be analyzed and rebuilt. Basic IVR trees can sometimes be auto-converted with tools like Univonix CC Accelerator, but custom Java steps require manual rebuild. Plan for a dedicated script audit phase in your migration timeline — it's typically the longest single task.
CUIC decommissions with UCCX — there is no migration path. You must export historical data via ODBC to an external SQL database before cutover. After decommission, that data is gone unless you've already exported it. Rebuild key reports in WxCC Analyzer before UAT. Third-party tools like Expo XT can unify legacy UCCX data and live WxCC data during the transition period.
Three options: (1) Webex Calling PSTN — port DIDs to Cisco's cloud, simplest architecture. (2) CUBE hairpin — existing SIP trunks route via your CUBE to WxCC. (3) Webex Edge Connect — dedicated connection for high-volume, latency-sensitive sites. Most mid-market deployments use the CUBE hairpin to avoid SIP migration complexity.
Not for contact center calls. Standard WxCC agent licenses cover agent audio via WebRTC. Webex Calling licenses are only required if agents need internal enterprise telephony features (agent-to-agent calls via the Webex app). Clarify your actual use case before sizing subscriptions — most organizations find standard WxCC agent licenses cover their contact center use case.
Small (under 25 agents, 5 or fewer scripts): 6–10 weeks. Medium (25–100 agents): 10–18 weeks. Large (100–300 agents): 18–28 weeks. Enterprise (300+ agents): 28–40+ weeks. The primary timeline driver is script complexity — specifically custom Java steps, REST API integrations, and database lookups that must be manually rebuilt. Add 20–30% buffer for organizations with complex AD structures or multiple third-party integrations.
Fractional UC engineering — an experienced UCCX-to-WxCC engineer on your engagement, without the overhead of a full Cisco Professional Services contract. Weekly or monthly retainer. Covers assessment, flow rebuild, cutover planning, and post-migration support. Not a generalist consulting firm — we've executed these migrations and work on the technical details directly. Start with a Flow Audit to understand your migration complexity before committing.
Yes. The standard approach is parallel-run: WxCC is built alongside UCCX with zero production traffic until validation is complete. Primary DNs are cut over only after a pilot group (10–15% of agents) validates routing, quality, and desktop behavior in production. UCCX stays live as rollback option for 30–60 days after cutover. This is how you cut over without a Sunday night incident.
No. UCCX 15 is Cisco's final on-premises release — a short-term bridge, not a long-term platform. Cisco's roadmap is unambiguously cloud-first. WxCC is where investment goes. Choose UCCX 15 only for specific regulatory requirements that prevent cloud deployment. The EOL clock keeps running either way — and engineers who understand this work are already booking out.
8-point inventory checklist + risk scoring rubric. Know exactly what you're moving before your first scoping call.
The checklist is on its way. Or read it here right now.
You don't need a full engagement to know what you're dealing with. The Flow Audit analyzes your existing UCCX scripts, identifies migration complexity, and gives you a realistic timeline estimate. No vendor pitch, no upsell. Just an engineer who's done this before telling you what you're actually facing.
Or read the checklist before talking to anyone.