UCCX to Webex Contact Center Migration

Two Cisco documents describe a UCCX to Webex Contact Center migration, and read side by side they appear to contradict each other. One ships a migration utility and lists what it extracts. The other states plainly that no mechanism exists for transferring your configuration.

Both are correct. The tool moves administrative objects. It does not move logic. Understanding which side of that line each part of your contact center falls on is the difference between a project plan and a surprise.

A UCCX to Webex Contact Center Migration: What the Tool Actually Does

Cisco publishes a discovery and migration utility for this, distributed as a Java archive and run against the UCCX installation. It requires Java 8 or above, reads your UCCX configuration, and writes a spreadsheet called WebexCC_Bulk_Upload.xlsx that is then bulk imported into the Webex Contact Center tenant. Cisco revises the utility, so check the version on the help article rather than against a number quoted anywhere else, including here.

What it extracts is a defined list. Cisco documents seventeen entities, generated as separate files and imported in a fixed order:

• Multimedia profiles
• Sites
• User profiles
• Work types
• Auxiliary codes
• Agent profiles
• Address book
• Skill definitions
• Skill profiles
• Teams
• Entry points
• Outdial entry points
• Queues
• Outdial queues
• Entry point mappings
• Outdial ANI
• Users

Cisco attaches a caveat worth reading before you plan around the output. The tool is described as continuously evolving, with new functionality developed over time, and as a result it may not currently support all the latest features. Treat the spreadsheet as a strong first draft of your configuration rather than a finished migration.

Every item on that list is a record: a name, an attribute, a membership. These are the objects that are tedious to retype and easy to get wrong at volume, which is exactly the right thing to automate. At several hundred agents, the skills and team assignments are the part of the build the tool takes off the schedule.

What Does Not Move, and Has to Be Rebuilt

Four things do not transfer, and together they are typically where the bulk of the effort sits.

Routing scripts

Cisco is unambiguous. The transition guide states that there is currently no mechanism available for transferring existing UCCX configuration to Webex Contact Center, and separately that Cisco does not have a tool to migrate existing UCCX scripts. Scripts must be rebuilt before agents are transitioned.

This is not a format conversion that somebody has not gotten around to writing. UCCX scripts are built in Cisco Unified CCX Editor against a step-based execution model. Webex Contact Center flows are built in a different designer against a different model. The business rules carry across because they live in your head and your documentation. The implementation does not.

The practical consequence: somebody has to read every production script and write down what it actually does, including the branches nobody has triggered in years. That documentation exercise is the real first task of the migration, and it is frequently the point at which an organization discovers that the only person who understood the overflow logic has since left.

Historical reporting

Cisco states that it is currently not possible to move on-premises UCCX reporting data to cloud Webex Contact Center.

Your CUIC reports do not migrate, and neither does the history behind them. If you report year over year, or if a regulator or a customer contract obliges you to retain interaction history, decide before cutover how that obligation will be met. The workable options are to export and archive the historical data outside the platform, or to run a read-only reporting path against the retained UCCX database for as long as the retention period demands. Both are work items with a cost.

IVR prompts

Recorded prompts are uploaded manually into Resource Files. Cisco specifies the format in the transition guide as CCIT U-law, 8-bit sample and 8 kHz sample rate.

This is a small task that becomes a large one at volume. A short prompt set is an afternoon. An estate with prompts across multiple languages and seasonal variants, some of which exist only as files on a share nobody has audited, is a project of its own. Count them early.

Finesse desktop customizations

Cisco's transition guide does not describe a migration path for Finesse gadgets, and the Webex Contact Center Agent Desktop is a different architecture. Any gadget your agents rely on, whether a CRM screen pop, a lookup panel or a homegrown wrap-up form, is a rebuild against the new desktop's extensibility model.

Ask your supervisors which gadgets agents actually use, rather than which ones are installed. The answer is usually shorter than the list, and that difference is scope you do not have to carry.

Why the Two Documents Read Differently

The reconciliation is straightforward once you see it. The help article documents a tool and is written from the tool's perspective, so it describes what the tool covers. The deployment guide is written from the project's perspective, so it describes the whole job, of which the tool is a small and early part.

The deployment guide's summary is the sentence to plan against: all of the necessary configuration needs to be carried out on Webex Contact Center for proper functioning of the solution.

If a proposal you receive leans on the existence of the migration tool as evidence that the project is small, that proposal has read one document.

The Deadline That Sits Underneath This

Most organizations reading this are not choosing freely. Cisco announced end of life for Version 12.5 and 12.6 of the on-premises contact center applications on 30 June 2025, and the milestone dates are close enough to shape a budget cycle. Cisco published two bulletins on the same day, one for the on-premises software and licenses and one for the associated on-premises Flex subscriptions, and both carry a December 2026 date that means something different. On the software and licenses bulletin, 31 December 2026 is the end of software maintenance releases and the end of new service attachment. On the Flex subscription bulletin, 31 December 2026 is the end of change and renewal. We have set out which UCCX end of life date applies to which licensing model in detail.

There is also a capability gap worth knowing about if artificial intelligence is on your roadmap. Cisco's Flex 3.0 licensing lists Cisco AI Assistant and Webex AI Agent as available on Webex Contact Center, Webex CCE and UCCE/PCCE. Both are listed as not available on UCCX. Staying on UCCX is therefore a decision to stay outside that capability set, which may or may not matter to you, but should be a decision rather than a discovery.

Where This Goes Wrong

Planning the timeline from the tool's scope. The tool populates a spreadsheet of records. It does not build a single routing flow. A plan that treats the bulk upload as the migration will be wrong by the whole script rebuild.

Discovering the script documentation gap late. Nobody schedules "read every script and write down what it does" because it is not a deliverable anyone asks for. It is nonetheless the task the rest of the project waits on, and it should be the first line of the plan rather than an implicit assumption.

Finding the reporting obligation after cutover. Historical data does not move. If somebody in finance, quality or compliance depends on multi-year trend reporting, they need to be in the room before the cutover date is set, not after their report stops working. This is one of several items worth settling while you scope routing, recording and reporting before a platform is chosen.

Counting agents and calling it sizing. Agent count is the easiest number to produce and the least informative. The prompts, the integrations, the gadgets and the scripts are what determine the duration.

A Sequence That Holds Up

1. Inventory the scripts. Every production flow, what it does, which branches are live, who owns the business rule behind it.
2. Inventory the prompts. Count them, find them, identify which are still in use and which language variants exist.
3. Inventory the desktop. Which Finesse gadgets do agents genuinely use, and what does each one reach. Agents also answer on something, and where a desk phone stays the voice path rather than the browser, the Cisco Desk Phone 9800 Series model mix is part of the same inventory.
4. Settle the reporting obligation. Decide how historical data will be retained and who signs off that the decision meets the requirement.
5. Run the discovery tool. Now the spreadsheet it produces lands into a project where its place is understood.
6. Rebuild flows in the new designer, validate against the documented behavior, then transition agents.

Steps one through four contain no Cisco tooling at all, and they are where the schedule is won or lost.

Trybus Solutions runs these migrations end to end, and also supports organizations that intend to remain on-premises on Version 15. We design and deploy contact center environments and provide managed services and support afterward.

Common questions

Does the migration tool move our routing scripts? No. Cisco states that no tool exists to migrate UCCX scripts and that scripts must be rebuilt before agents transition. The tool extracts administrative records such as agents, teams, skills, queues and entry points.

Can we keep our historical reports? Not inside the new platform. Cisco states that on-premises UCCX reporting data cannot currently be moved to cloud Webex Contact Center. Historical data is archived or retained separately.

What format do the IVR prompts have to be in? CCIT U-law, 8-bit sample and 8 kHz sample rate, uploaded manually into Resource Files. That is Cisco's own spelling of the codec in the transition guide.

Is a UCCE or PCCE migration the same? No, and the documentation differs. Cisco publishes a separate deployment guide for transitioning Unified CCE to Webex Contact Center, issued in March 2026, which covers Unified CCE only. We were not able to locate an equivalent published document for PCCE, so treat any claim about PCCE tooling as needing confirmation from Cisco directly.

Sources

• Webex Help Center - Migrate Cisco Unified Contact Center Express to Webex Contact Center
• Cisco - Unified CCX to Webex Contact Center deployment and transition guide
• Cisco - Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center deployment guide, March 2026
• Cisco - End-of-sale and end-of-life announcement for Version 12.5/12.6 on-premises contact center applications and associated on-premises software and licenses
• Cisco - End-of-sale and end-of-life announcement for Version 12.5/12.6 on-premises contact center applications and associated on-premises Flex subscriptions
• Cisco - Collaboration Flex 3.0 Contact Center data sheet