# Migrating Unified CCE or Unified CCX to Webex Contact Center

Canonical: https://warmtransfer.net/knowledge/webex-cc-migration-from-ucce

Last verified: 2026-09-05

Cisco documents migration paths from on-premises Unified Contact Center Enterprise (CCE) and Unified Contact Center Express (CCX) platforms to cloud-based Webex Contact Center[^21][^53]. These migration frameworks address architecture differences, data transition limits, routing conversions, and coexistence models[^31][^27][^57].

## Migration Strategy and Coexistence

Cisco offers 2 migration strategies: a flash cut moving everything at once, and a phased migration by line of business[^40]. Cisco states that most organisations prefer the phased approach for better control in large or multi-region deployments[^40]. WarmTransfer's reading of the sources is that Cisco considers a flash cut often impractical for large contact centres and best suited to a smaller number of agents, while publishing no agent count threshold separating the 2[^15]. Cisco also recommends against a direct lift and shift of legacy Unified CCE configuration, advising teams to review and update business and technical requirements against cloud capabilities instead[^27].

The phased migration follows a 2-step transition consisting of a coexistence phase where some lines of business run on Webex Contact Center while others remain on Unified CCE, followed by a full transition phase producing a cloud-only environment[^7]. Cisco states that some organisations may maintain a hybrid Unified CCE and Webex Contact Center deployment indefinitely with no plan to fully transition, imposing no coexistence duration limit[^8]. Cisco describes typical coexistence duration only in qualitative terms, noting it spans months or years for some organisations and weeks or months for others[^9]. For configuration and data, the guide separately recommends a 3-phase transition: pre-migration to prepare both environments, migration preparation to define the strategy, and migration covering rollout and decommission[^39]. The Unified CCE transition guide publishes a sample migration timeline of 11 phases across weeks 1 to 14, from assessment and planning through cutover and ongoing management, labelling it a sample[^35]. Consequently, the Unified CCE transition guide uses the word phase for 3 unrelated numbering schemes: the 2-step coexistence and full transition, the 3-phase data transition, and the 11-phase sample timeline across 14 weeks[^30].

The Unified CCE transition guide organises the migration around Cisco's Prepare, Plan, Design, Implement and Optimize methodology, which neither Unified CCX transition document uses[^31]. Cisco recommends migrating the contact centre workload alone and treating telephony and public network migration as a separate effort either before or after, avoiding added complexity and risk[^12].

Cisco identifies 6 organisational profiles where remaining on Unified CCE may be the better fit[^37]:
* Highly customised interactive voice response (IVR) or voice extensible markup language applications on proprietary integrations[^37].
* Extensive custom Finesse gadgets or third-party computer telephony integrations with no supported cloud equivalent[^37].
* Heavy reliance on direct database access for custom reporting[^37].
* Specialised outbound dialling modes or regulatory requirements not supported by the cloud campaign system[^37].
* Environments lacking guaranteed high-quality internet access[^37].
* Extensive complex external database integrations[^37].

Cisco's Unified CCX transition deck also names the need to maintain historical data from on-premises systems as a reason to reconsider transitioning to Webex Contact Center at all[^38].

## Routing, Logic, and Component Mapping

The intelligent contact management router and logger map to Flow Designer, replacing scripted routing logic with a visual flow builder[^34]. Cisco states that there is no automated converter from Customer Voice Portal (CVP) and intelligent contact management routing logic to Flow Designer, requiring every function to be mapped by hand[^25]. Cisco Unified Intelligence Center (CUIC) maps to Webex Contact Center Analyzer[^10]. Enterprise Chat and Email maps to Webex Connect, adding short message service, WhatsApp, and Apple Messages for Business channels[^14].

Webex Contact Center Functions replace Call Studio Java logic but introduce architectural constraints[^17]:
* Functions do not permit direct database access, requiring database interactions to pass through middleware calls[^17].
* Functions have no filesystem access, requiring configuration to reside in environment variables and logs to pass through an external logging interface[^18].
* Simple object access protocol (SOAP) client libraries from Call Studio are not natively supported and must be wrapped behind a representational state transfer (REST) interface or gateway[^19].

For Unified CCX migrations, Cisco defines terminology mappings where a trigger becomes an entry point, an application becomes a routing strategy, the script editor becomes flow control, a contact service queue becomes a queue, and call and expanded call context variables become call associated data[^59]. However, the term team functions differently across platforms: in Webex Contact Center a team associates with a routing strategy and distributes calls, whereas in Unified CCX a team only groups agents and does not route calls[^58].

## Unified CCX Discovery Tool and Data Import

Cisco provides a first-party downloadable discovery tool—a Java application run against the Unified CCX server—that generates bulk upload spreadsheets for Webex Contact Center[^48]. Cisco warns that this tool is continuously evolving and may not support all latest features[^49]. The documentation contains discrepancies regarding the utility version: the migration article instructs users to download discovery tool version 3.5, while every command example in the same article invokes a version 3.4 archive[^50].

To avoid dependency errors, Cisco mandates a specific import sequence for generated files, starting with multimedia profiles, sites, and user profiles, and concluding with entry point mappings, outdial automatic number identification, and users[^47]. Webex Contact Center bulk operations enforce a limit of 5,000 rows per import file, requiring larger datasets to be split across multiple files[^44].

## Reporting and Data Retention

Cisco states that it is not currently possible to move on-premises Unified CCX reporting data to cloud Webex Contact Center, that Cloud Connect carries only abandoned call information, and that no one-to-one mapping exists between Unified CCX and Analyzer reports[^57]. This occurs because Unified CCX records call details across 5 tables—Agent Connection Detail, Agent State Detail, Contact Call Detail, Contact Queue Detail, and Contact Routing Detail—while Webex Contact Center records call data across 4 tables: Agent Activity Record, Agent Session Record, Customer Activity Record, and Customer Session Record[^45][^46]. During hybrid operations, Cisco states that Webex Contact Center uses only Analyzer for real-time and historical reporting, requiring supervisors to use CUIC for on-premises calls and Analyzer for cloud calls[^43].

Webex Contact Center Analyzer cannot directly ingest CUIC data[^3]. Unified CCE historical data reaches Analyzer only when Cloud Connect is enabled on the Unified CCE side and the cloud analytics engine is configured to pull from CUIC[^3]. This Cloud Connect path requires Unified CCE release 12.x or later with Cloud Connect onboarded[^6]. The integration carries specific constraints:
* Real-time Unified CCE data is not supported in Analyzer, limiting Cloud Connect delivery to historical and near real-time data only[^28].
* CUIC user synchronisation features, including supervisor roles and value lists, do not apply to Analyzer[^11].

In the cloud, Webex Contact Center stores 5 data types: call detail records, connected agent records, agent desktop data, call variables stored by the IVR, and call recordings[^51]. Call recordings are stored in the cloud for 30 days by default, a value its own revision history records as updated in June 2021[^56]. Retention periods are configurable, with examples including 13 months for call detail records generally and 6 months in the European Union, with data deletable on request or organisation deletion[^33]. Cisco separately manages Analyzer historical data retention for up to 13 months[^2]. On the agent desktop, data masking is visual only; backend logs and attachments may still contain raw data unless additional data loss prevention controls are applied[^24]. Cisco holds ISO/IEC 27001, payment card industry data security standard, and service organisation control certifications for Webex Contact Center, while stating the product can be configured to support compliance regimes such as the General Data Protection Regulation and the Health Insurance Portability and Accountability Act[^4].

## Telephony, Integrations, and Scale

For premises-based telephony connections, a registration-based local gateway supports up to 250 concurrent calls, while a certificate-based local gateway supports up to 6,500 concurrent calls depending on connectivity type and session border controller model[^22]. This is disputed: Cisco states that 1-way latency between the local gateway and the Webex Calling data centre should not exceed 100 milliseconds, with jitter under 10 milliseconds and packet loss under half a percent[^23]. Sources disagree on VoIP network thresholds: Cisco's Unified CCX transition guide cites general VoIP industry targets of end-to-end latency under 150 milliseconds, jitter under 30 milliseconds, and packet loss under 1 percent[^52].

Cisco states that once a public network (PSTN) option is configured for a tenant, it cannot be changed[^54]. Sources disagree on Cisco's role in PSTN supply: the Unified CCX transition guide states in 1 place that Cisco never supplies PSTN directly because third-party carriers provide it, yet describes a Cisco-provided flat-rate bundled PSTN service on a single Cisco invoice on the subsequent page[^55]. The Unified CCE transition guide notes that Cisco Calling Plan for Webex Contact Center is currently limited to trials and inbound toll-free numbers[^5]. Furthermore, agent desktop call-answering buttons are available only for Webex Calling and browser-based WebRTC endpoints; desktop call control buttons are unavailable when using endpoints registered to Unified CM[^13].

For third-party systems, Cisco documents native connectors for Salesforce, Microsoft Dynamics 365, Zendesk, and ServiceNow, distributing the ServiceNow connector as repository configuration files rather than a marketplace listing[^16]. Outbound progressive campaigns require Campaign Manager LCM version 4.2.1.2310 or above, while predictive campaigns require version 4.2.1.2401 or above[^29].

WarmTransfer's reading of the sources is that no maximum agent count, entry point count, or queue count ceiling is published for cloud Webex Contact Center in a migration context, with the only concurrent agent limit in the examined tranche applying to Webex Contact Center Enterprise[^26]. Cisco states that Webex Contact Center Enterprise supports up to 36,000 concurrent agents[^60]. Webex Contact Center Enterprise is licensed on a concurrent agent model under the Collaboration Flex Plan with standard and premium agent types[^61]. Unlike cloud Webex Contact Center, Webex Contact Center Enterprise retains Unified CVP for IVR and CUIC for reporting[^63].

## Discrepancies and Guide Currencies

The Unified CCE transition deployment guide is dated March 2026, and its own publication history records a single entry marking it as an initial release of a draft copy[^21]. The guide contains an unfilled authoring placeholder instead of a figure within its agent deployment section[^20]. Conversely, the Unified CCX transition deployment guide and its companion slide deck are dated September 2021, approximately 4 and a half years older than the Unified CCE guide[^53].

Documentation conflicts exist across several areas:
* **Finesse gadget portability:** This is disputed; the Unified CCE transition guide lists custom Finesse gadgets as having no supported cloud equivalent, whereas the Unified CCX transition deck asserts that gadgetised interfaces allow Unified CCX Finesse gadgets to be used on the Webex Contact Center desktop[^41][^42].
* **Regional availability:** This is disputed; the Unified CCE guide lists 7 operating regions (United States, Canada, United Kingdom, Germany, Singapore, Australia, and Japan)[^36]. However, Cisco's data locality documentation lists an active India data centre omitted from that guide[^32]. Separately, the Webex Contact Center Enterprise data sheet mentions Japan as an available region in 1 sentence, but limits its Asia country breakdown to Malaysia, the Philippines, and Singapore, showing Japan only as a data centre location[^62].

## See also

* See also [Webex Contact Center Flow Designer architecture](https://warmtransfer.net/knowledge/webex-cc-flow-designer).
* See also [Webex Contact Center Analyzer and reporting model](https://warmtransfer.net/knowledge/webex-cc-analyzer).
* See also [Webex Connect digital channel flow orchestration](https://warmtransfer.net/knowledge/webex-connect-digital-flows).
* See also [Webex Contact Center Enterprise as a distinct product](https://warmtransfer.net/knowledge/webex-contact-center-enterprise).
* See also [CUCM to Webex Calling migration](https://warmtransfer.net/knowledge/cucm-to-webex-calling).

## Applicability

Applies to: Cisco Webex Contact Center, Cisco Webex Contact Center Enterprise, and Cisco Webex Calling. Deployments: cloud and cisco-hosted-dedicated. Sources checked 2026-09-05. The Cloud Connect integration between Unified CCE and Analyzer requires Unified CCE release 12.x or later[^6]. Outbound campaign management requires Campaign Manager LCM version 4.2.1.2310 or above for progressive campaigns and version 4.2.1.2401 or above for predictive campaigns[^29].

## What remains uncertain

Whether Webex Contact Center supports automated conversion tools for Call Studio scripts, or whether third-party tooling exists outside Cisco documentation, is not covered by the sources below. The maximum scale ceilings for concurrent agents, queues, and entry points on multi-tenant cloud Webex Contact Center are not covered by the sources below. Specific network latency requirements between cloud Webex Contact Center and external CRM platforms are not covered by the sources below.

## Sources

[^1]: Using AI Agent Studio with Contact Center Enterprise requires Unified Customer Voice Portal, Cisco Virtualized Voice Browser and Cloud Connect on release 15.0(1) ES202511 or later. Source: [Webex AI Agent Studio Administration guide](https://help.webex.com/en-us/article/ncs9r37/Webex-AI-Agent-Studio-Administration-guide), Prerequisites, Webex Contact Center Enterprise and Contact Center Enterprise. Checked 2026-09-05.
[^2]: The transition guide separately states that Cisco manages Webex Analyzer historical data retention for up to 13 months. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 45, Webex Analyzer, and table 15. Checked 2026-09-05.
[^3]: Webex Contact Center Analyzer cannot directly ingest Unified Intelligence Center data; Unified CCE historical data reaches Analyzer only by enabling Cloud Connect on the Unified CCE side and configuring the cloud analytics engine to pull from Unified Intelligence Center. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 92, Phase 8 Analytics and Reporting. Checked 2026-09-05.
[^4]: The transition guide distinguishes certifications Cisco holds for Webex Contact Center, naming ISO/IEC 27001, payment card industry data security standard and service organisation control reports, from regimes it says the product can be configured to support including the General Data Protection Regulation and the Health Insurance Portability and Accountability Act. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 22 to 23, Compliance and Security Policies. Checked 2026-09-05.
[^5]: The Unified CCE transition guide states that Cisco Calling Plan for Webex Contact Center is currently limited to trials and inbound toll-free numbers. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 32, Cisco Calling Plan. Checked 2026-09-05.
[^6]: The Cloud Connect path to Analyzer requires Unified CCE release 12.x or later with Cloud Connect enabled and onboarded. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 93, Prerequisites. Checked 2026-09-05.
[^7]: The phased migration is a 2-step transition: a coexistence phase where some lines of business run on Webex Contact Center while others remain on Unified CCE, and a full transition phase producing a cloud-only environment. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 16 and figures 8 to 10, Migration Approach. Checked 2026-09-05.
[^8]: Cisco states that some organisations may maintain a hybrid Unified CCE and Webex Contact Center deployment indefinitely with no plan to fully transition, and imposes no coexistence duration limit. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 18, note under figure 10. Checked 2026-09-05.
[^9]: Elsewhere the transition guide describes typical coexistence duration only in qualitative terms — months or years for some organisations, weeks or months for others. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 18, note under figure 10. Checked 2026-09-05.
[^10]: Cisco Unified Intelligence Center maps to Webex Contact Center Analyzer. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 30, table 8, Component Mapping. Checked 2026-09-05.
[^11]: Unified Intelligence Center user synchronisation features including supervisor roles and value lists do not apply to Analyzer. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 96, Important Notes and Limitations. Checked 2026-09-05.
[^12]: Cisco recommends migrating the contact centre workload alone and treating telephony and public network migration as a separate effort either before or after, to avoid additional complexity and risk. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 64, PSTN section under Design. Checked 2026-09-05.
[^13]: Answering a call from the Webex Contact Center agent desktop is available only on Webex Calling and browser-based real-time communication connections; the call control buttons are unavailable when the agent uses a device registered to Unified CM. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 58, Agent Deployment note. Checked 2026-09-05.
[^14]: Enterprise Chat and Email maps to Webex Connect, which adds short message service, WhatsApp and Apple Messages for Business channels that Enterprise Chat and Email does not carry. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 31, table 8, Component Mapping. Checked 2026-09-05.
[^15]: Cisco says a flash cut is often impractical for large contact centres and best suited to a smaller number of agents, and publishes no agent count that separates the 2 (inferred). Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 15, Migration Approach. Checked 2026-09-05.
[^16]: Cisco documents native Webex Contact Center connectors for Salesforce, Microsoft Dynamics 365, Zendesk and ServiceNow, with ServiceNow distributed as configuration files published on a repository rather than as a marketplace listing. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 89 to 92, Phase 7 CRM and Third-Party Integrations. Checked 2026-09-05.
[^17]: Webex Contact Center Functions, the replacement for Call Studio Java logic, do not permit direct database access; database work must go through a call to middleware. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 86, table 29, Database Access. Checked 2026-09-05.
[^18]: Webex Contact Center Functions have no filesystem access, so configuration must move to environment variables and logs must be pushed through an external logging interface. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 86, table 30, File Handling. Checked 2026-09-05.
[^19]: Simple object access protocol client libraries used in Call Studio are not supported directly in Webex Contact Center Functions and must be wrapped behind a representational state transfer interface or gateway. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 85 to 86, table 28, REST and Web Service Calls. Checked 2026-09-05.
[^20]: The Unified CCE transition guide ships with an unfilled authoring placeholder in place of a figure in its agent deployment section. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 58, immediately after the agent desktop call control note. Checked 2026-09-05.
[^21]: Cisco's Transitioning from Unified Contact Center Enterprise to Webex Contact Center deployment guide is dated March 2026 and its own publication history records a single entry describing it as an initial release of a draft copy. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 4, What's New in This Guide, publication history table. Checked 2026-09-05.
[^22]: A registration-based local gateway supports up to 250 concurrent calls and a certificate-based local gateway supports more, up to 6,500 depending on connectivity type and session border controller model. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 33, premises-based PSTN connection. Checked 2026-09-05.
[^23]: Cisco states that 1-way latency between the local gateway and the Webex Calling data centre should not exceed 100 milliseconds, with jitter under 10 milliseconds and packet loss under half a percent (disputed). Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 33 to 34. Checked 2026-09-05.
[^24]: The transition guide states that agent desktop masking is visual only and that backend logs and attachments may still contain raw data unless further data loss prevention controls are enforced. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 23, Data Masking and PII Protection. Checked 2026-09-05.
[^25]: Cisco states plainly that there is no automated converter from Customer Voice Portal and intelligent contact management routing logic to Webex Contact Center Flow Designer, and that every function must be mapped by hand. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 79, Phase 6 Routing and IVR Migration, High-Level Reality Check. Checked 2026-09-05.
[^26]: No source read in this tranche publishes a maximum agent count, entry point count or queue count for cloud Webex Contact Center in a migration context; the only concurrent agent ceiling found belongs to Webex Contact Center Enterprise (inferred). Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), whole-guide scan of the March 2026 transition guide for scale figures. Checked 2026-09-05.
[^27]: Cisco recommends against a direct lift and shift of legacy Unified CCE configuration and tells the reader to review and update business and technical requirements against cloud capabilities instead. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 19, Migration Preparation. Checked 2026-09-05.
[^28]: Real-time Unified CCE data is not supported in Analyzer; the Cloud Connect path delivers historical and near real-time data only. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 96, Important Notes and Limitations. Checked 2026-09-05.
[^29]: Cisco states that Webex Contact Center outbound progressive campaigns are managed by Campaign Manager LCM version 4.2.1.2310 or above and predictive campaigns by version 4.2.1.2401 or above. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 54, Webex Contact Center Outbound Option. Checked 2026-09-05.
[^30]: The Unified CCE transition guide uses the word phase for 3 unrelated numbering schemes: a 2-step coexistence and full transition, a 3-phase data transition, and an 11-phase sample timeline across 14 weeks. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 16 to 20 and pages 58 to 60. Checked 2026-09-05.
[^31]: The Unified CCE transition guide organises the whole migration around Cisco's Prepare, Plan, Design, Implement and Optimize methodology, which neither Unified CCX transition document uses at all. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 12 to 15, PPDIO Process Overview; compared against both Unified CCX documents' tables of contents. Checked 2026-09-05.
[^32]: Cisco's current data locality article names an India data centre for Webex Contact Center that the March 2026 transition guide's region list omits (disputed). Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), the eight per-data-centre tables, India data center table. Checked 2026-09-05.
[^33]: The transition guide gives configurable retention periods as an example, 13 months for call detail records generally and 6 months in the European Union, and states data can be deleted on request or on organisation deletion. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 23, Data Retention and Deletion. Checked 2026-09-05.
[^34]: The intelligent contact management router and logger map to Flow Designer, replacing scripted routing logic with a visual flow builder. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 29 to 30, table 8, Component Mapping. Checked 2026-09-05.
[^35]: The guide publishes a sample migration timeline of 11 phases across weeks 1 to 14, from assessment and planning through cutover and ongoing management, and labels it a sample. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 58 to 60, Sample Migration Timeline. Checked 2026-09-05.
[^36]: The transition guide names 7 Webex Contact Center regions - United States, Canada, United Kingdom, Germany, Singapore, Australia and Japan - and states the country of operation chosen at provisioning fixes the data centre (disputed). Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 61 to 63, Region selection and table 20. Checked 2026-09-05.
[^37]: Cisco names 6 organisational profiles for which remaining on Unified CCE may be the better fit: highly customised interactive voice response or voice extensible markup language applications on proprietary integrations, extensive custom Finesse gadgets or third-party computer telephony integrations with no supported cloud equivalent, heavy reliance on direct database access for custom reporting, specialised outbound dialling modes or regulatory requirements the cloud campaign system does not support, environments without guaranteed high-quality internet access, and extensive complex external database integrations. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 8, bulleted list following the figure 2 introduction. Checked 2026-09-05.
[^38]: Cisco's Unified CCX transition deck names the need to maintain historical data from on-premises systems as a reason to reconsider transitioning to Webex Contact Center at all. Source: [Collaboration Transitions: Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/TDM_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 4, Scenario Introduction: Decision. Checked 2026-09-05.
[^39]: The guide separately recommends a 3-phase transition for configuration and data: pre-migration to prepare both environments, migration preparation to define the strategy, and migration covering rollout and decommission. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 19 to 20, Recommended 3-Phase Transition. Checked 2026-09-05.
[^40]: Cisco offers 2 migration strategies, a flash cut moving everything at once and a phased migration by line of business, and states that most organisations prefer the phased approach for better control in large or multi-region deployments. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 15 to 16, Migration Approach. Checked 2026-09-05.
[^41]: Cisco's Unified CCE transition guide names extensive custom Finesse gadgets as having no supported equivalent in Webex Contact Center, while the Unified CCX transition deck states that gadgets built for the Unified CCX environment can also be used in the Webex Contact Center agent desktop (disputed). Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 8 reasons to stay on premises, against the Unified CCX deck page 27 agent desktop considerations. Checked 2026-09-05.
[^42]: Cisco's Unified CCX transition deck states that both the Unified CCX and Webex Contact Center agent desktops are gadgetised and that gadgets built for Unified CCX can also be used in the Webex Contact Center desktop (disputed). Source: [Collaboration Transitions: Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/TDM_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 27, agent and supervisor desktop considerations. Checked 2026-09-05.
[^43]: Cisco states that Webex Contact Center uses only Analyzer for real-time and historical reporting and that during the hybrid phase supervisors must continue using Unified Intelligence Center for on-premises calls and Analyzer for cloud calls. Source: [Collaboration Transitions: Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/TDM_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 26, Reporting Considerations. Checked 2026-09-05.
[^44]: Webex Contact Center bulk operations limit any import file to 5,000 rows and larger datasets must be split across multiple files. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Run the discovery tool for migration, step 6. Checked 2026-09-05.
[^45]: Unified CCX records call detail across 5 tables and Webex Contact Center across 4 with a different event to table mapping, which is why no direct report mapping exists. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), pages 30 to 31, tables 7 and 8. Checked 2026-09-05.
[^46]: Unified CCX records call detail across the Agent Connection Detail, Agent State Detail, Contact Call Detail, Contact Queue Detail, and Contact Routing Detail tables, while Webex Contact Center records the equivalent data across the Agent Activity Record, Agent Session Record, Customer Activity Record, and Customer Session Record tables. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), pages 30 to 31, tables 7 and 8. Checked 2026-09-05.
[^47]: Cisco publishes a required import order for the discovery tool's generated files to avoid dependency errors, beginning with multimedia profiles, sites and user profiles and ending with entry point mappings, outdial automatic number identification and users. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Run the discovery tool for migration, step 6. Checked 2026-09-05.
[^48]: Cisco publishes a first-party downloadable discovery tool, a Java application run against the Unified CCX server, that generates bulk upload spreadsheets for Webex Contact Center. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Prepare for migration. Checked 2026-09-05.
[^49]: Cisco warns that the migration tool is continuously evolving and may not currently support all the latest features. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Prepare for migration. Checked 2026-09-05.
[^50]: The migration article instructs downloading discovery tool version 3.5 while every command example in the same article invokes a version 3.4 archive. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Prepare for migration against Run the discovery tool for migration steps 3 and 6. Checked 2026-09-05.
[^51]: The Unified CCX transition guide names 5 data types Webex Contact Center stores in the cloud: call detail records, connected agent records, agent desktop data, call variables stored by the interactive voice response, and call recordings. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 12, understand security requirements. Checked 2026-09-05.
[^52]: Cisco's Unified CCX transition guide gives general voice over internet protocol targets of end-to-end latency under 150 milliseconds, jitter under 30 milliseconds and packet loss under 1 percent, attributed to industry standards rather than to a Cisco specification (disputed). Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 15, perform network readiness assessment. Checked 2026-09-05.
[^53]: Cisco's Unified CCX to Webex Contact Center deployment guide is dated September 2021 and its companion deck September 2021, roughly 4 and a half years older than the Unified CCE guide. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), title page and publication history table. Checked 2026-09-05.
[^54]: Cisco states that the public network option cannot be changed once it is configured for a tenant. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 17, understand PSTN options. Checked 2026-09-05.
[^55]: The Unified CCX transition guide states that Cisco itself never supplies the public network because that is provided by third-party carriers, and describes a Cisco-provided flat rate bundled public network service on a single Cisco invoice 1 page later (disputed). Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 17 general statement against page 18 Cisco Provided Bundled PSTN. Checked 2026-09-05.
[^56]: Cisco states that Webex Contact Center call recordings are stored in the cloud for 30 days by default, a value its own revision history records as updated in June 2021. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 16, determine call recording requirements, and the publication history table. Checked 2026-09-05.
[^57]: Cisco states that it is not currently possible to move on-premises Unified CCX reporting data to cloud Webex Contact Center, that Cloud Connect carries only abandoned call information, and that there is no one-to-one mapping between Unified CCX and Analyzer reports. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), pages 29 to 30, Reporting Considerations. Checked 2026-09-05.
[^58]: The word team means different things on the 2 platforms: in Webex Contact Center a team is associated with a routing strategy and used for call distribution, while in Unified CCX a team only groups agents and is not used for distribution. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 25, table 6. Checked 2026-09-05.
[^59]: Cisco publishes a Unified CCX to Webex Contact Center terminology crosswalk: a trigger becomes an entry point, an application becomes a routing strategy, the script editor becomes flow control, a contact service queue becomes a queue, and call and expanded call context variables become call associated data. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), pages 24 to 25, table 6. Checked 2026-09-05.
[^60]: Cisco states that Webex Contact Center Enterprise supports up to 36,000 concurrent agents. Source: [Webex Contact Center Enterprise Data Sheet](https://www.cisco.com/c/en/us/products/collateral/contact-center/webex-contact-center-enterprise/datasheet-c78-743365.html), Product overview, Enterprise scale. Checked 2026-09-05.
[^61]: Webex Contact Center Enterprise is sold on a concurrent agent buying model under the Collaboration Flex Plan with 2 combinable agent types, standard and premium. Source: [Webex Contact Center Enterprise Data Sheet](https://www.cisco.com/c/en/us/products/collateral/contact-center/webex-contact-center-enterprise/datasheet-c78-743365.html), Licensing, agent types, tables 2 and 3. Checked 2026-09-05.
[^62]: The Webex Contact Center Enterprise data sheet names Japan among its available regions in 1 sentence and lists only Malaysia the Philippines and Singapore under Asia in the country breakdown immediately below, showing Japan only as a data centre location (disputed). Source: [Webex Contact Center Enterprise Data Sheet](https://www.cisco.com/c/en/us/products/collateral/contact-center/webex-contact-center-enterprise/datasheet-c78-743365.html), Global availability, summary sentence against the Asia line. Checked 2026-09-05.
[^63]: Webex Contact Center Enterprise retains Unified Customer Voice Portal for self-service interactive voice response and Unified Intelligence Center for agent and queue reporting, which are the components the cloud transition guide describes as replaced. Source: [Webex Contact Center Enterprise Data Sheet](https://www.cisco.com/c/en/us/products/collateral/contact-center/webex-contact-center-enterprise/datasheet-c78-743365.html), Table 1, self-service interactive voice response and reporting feature rows. Checked 2026-09-05.
[^64]: The 30-day cloud recording storage default stated in Cisco's 2021 Unified CCX transition guide is not supported by any current source; the current documented default is 1095 days for a new organisation, configurable from 7 to 3600 days (inferred). Source: [Manage Retention and Purge Recordings and Transcripts in Webex Contact Center](https://help.webex.com/en-us/article/uimme/Manage-Retention-and-Purge-Recordings-and-Transcripts-in-Webex-Contact-Center), Key Features and Setting the retention period, against the September 2021 transition guide. Checked 2026-09-05.
[^65]: No current source confirms the 13-month call detail record retention or the 6-month European figure that Cisco's draft migration guide offers as configurable examples; the current offer disclosure gives 1 year for call detail records and defers recordings to the customer's setting (inferred). Source: [Cisco Webex Contact Center Service Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/webex-contact-center-offer-disclosure.pdf), Table 1 and Table 2 of the offer disclosure, against the March 2026 draft transition guide. Checked 2026-09-05.
[^66]: The documentation index treats Webex Contact Center 1.0, a classic platform and a next generation platform as distinguishable states of the cloud product's own history, and separately documents migration from Customer Journey Platform and CC-One releases. Source: [Webex Contact Center Documentation](https://help.webex.com/en-us/article/n2re5jy/Webex-Contact-Center-Documentation), upgrade and migrate article references. Checked 2026-09-05.
[^67]: Webex Contact Center Enterprise and cloud Webex Contact Center differ on every major component: routing runs in a Unified Contact Center Enterprise router against Flow Designer, voice response runs on Customer Voice Portal against Flow Designer activities, reporting runs on Unified Intelligence Center against Analyzer, the desktop is Cisco Finesse against an unbranded agent desktop, digital channels arrive through Enterprise Chat and Email against Webex Connect, and licensing is concurrent agent against the cloud product's own model (inferred). Source: [Webex Contact Center Enterprise for Government Data Sheet](https://www.cisco.com/c/en/us/products/collateral/contact-center/webex-contact-center-enterprise/webex-cc-enterprise-govt-ds.html), Table 1 of the government data sheet against the cloud documentation index and the cloud transition guide. Checked 2026-09-05.
[^68]: Cisco names Cisco Finesse as the agent and supervisor desktop for the government edition, a web-based customisable interface supporting multiple gadgets accessed through tabs. Source: [Webex Contact Center Enterprise for Government Data Sheet](https://www.cisco.com/c/en/us/products/collateral/contact-center/webex-contact-center-enterprise/webex-cc-enterprise-govt-ds.html), Table 1, agent and supervisor desktops row. Checked 2026-09-05.