Migrating Unified CCE or Unified CCX to Webex Contact Center

Verified 2026-09-05 · 68 claims · sources tier 2 · 8 disputed · 1 superseded

Also known as discovery tool.

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.
• See also Webex Contact Center Analyzer and reporting model.
• See also Webex Connect digital channel flow orchestration.
• See also Webex Contact Center Enterprise as a distinct product.
• See also CUCM to Webex Calling migration.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Contact Center, Cisco Webex Contact Center Enterprise, and Cisco Webex Calling across cloud and cisco-hosted-dedicated deployments, verified as of 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 any claim in this article. The maximum scale ceilings for concurrent agents, queues, and entry points on multi-tenant cloud Webex Contact Center are not covered by any claim in this article. Specific network latency requirements between cloud Webex Contact Center and external CRM platforms are not covered by any claim in this article.

WarmTransfer. (2026, September 5). Migrating Unified CCE or Unified CCX to Webex Contact Center. WarmTransfer. https://warmtransfer.net/knowledge/webex-cc-migration-from-ucce

@misc{warmtransfer-webex-cc-migration-from-ucce,
  title  = {Migrating Unified CCE or Unified CCX to Webex Contact Center},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-cc-migration-from-ucce},
  note   = {Verified 2026-09-05}
}