00 · Header

T6 · Migrations

UCCE and PCCE to Webex Contact Center

Cisco publishes three different moves that people collapse into one sentence: Unified CCX into multi-tenant Webex Contact Center, Webex Contact Center 1.0 into the current platform, and Webex Contact Center Enterprise portal data from one tenant to another. An ICM script, a CVP application, a peripheral gateway, CUIC, and Finesse do not have a published node-for-node import into Flow Designer or Agent Desktop. This room prints that crosswalk and marks every pair Cisco has not documented.

Expand all sections

01 · Executive summary

Five lines, then why it matters

• Unified CCX has a discovery tool. The article says to download discovery tool v3.5, and the printed command runs uccx-to-webexcc-v3.4.jar. It writes WebexCC_Bulk_Upload.xlsx and a prompts zip. Bulk Operations in Control Hub imports the CSVs. The tool needs access to a Unified CCX server. [cite:1]
• Webex Contact Center 1.0 upgrades in three stages: Pre-Upgrade Setup, New Platform Setup, and Post-Upgrade Cleanup, all from Contact Center > Settings. Routing strategies are created again with flow scripts. Test with a few users before you move every dialed number. Agents cannot be signed in to both desktops at once, and calls cannot be transferred between the two platforms. [cite:2]
• The Webex CCE Tenant Data Migration Tool copies portal data: routing controls, access groups and collections, collection objects, role-group assignments, audio-group metadata, and schedule skills. A flag of 1 replaces that class on the target. It does not copy the audio files. The article’s sample command contains credentials; replace every parameter and do not reuse that sample. [cite:3]
• On Webex CCE, Bulk Request can move agents from one peripheral to another, individually or by team, and it identifies their skill groups so you do not delete and recreate them. Common Identity phase 1 lets those agents sign in to Finesse with Webex identity. That is still Finesse on Enterprise, not multi-tenant Agent Desktop. [cite:4]
• The multi-tenant picture in the architecture article is entry point, flow, queue, team, and agent. The rows that would rename an ICM script, CVP/VXML, a skill group, a peripheral, CUIC, or Finesse are not claimed in this room. The cutover below those rows is a Canon method, labeled as ours. [cite:5]

02 · Architecture map

Three published moves, then the unmarked gap

flowchart LR
  UCCX[Unified CCX] --> Bulk[Bulk Operations]
  V1[WxCC 1.0] --> V2[Current WxCC]
  CCE[Webex CCE portal] --> CCE2[Another CCE tenant]
  ICM[ICM script] --> Gap[Marked gap]

03 · Core concepts

Crosswalk

Node and concept crosswalk

Coexistence that is published

Canon method for UCCE or PCCE into multi-tenant WxCC

1. Stand up the Webex Contact Center tenant and the Control Hub users before any number moves. The CCX article’s prepare list is the closest published checklist, and it is for CCX. [cite:1]
2. Build entry points, flows, queues, and teams beside the old estate. Reuse names only as labels. Do not claim the new queue is the old skill group. [cite:5]
3. Sign in a few agents on Agent Desktop and place test calls to a number that is not yet the production dialed number.
4. Cut one number only after that flow answers. Keep a written map of which old dialed number you intended. Open the UCCE dialed number in its own admin tool and the entry point in Control Hub. The 1.0 article moves a Dialed Number–Entry Point pair inside Webex Contact Center 1.0, which is not a UCCE field map, and the pair you keep is the one you wrote down.
5. Leave CUIC in place until someone compares the Analyzer report to the CUIC report by hand. The 1.0 cleanup makes legacy Analyzer data visible; it does not convert CUIC. [cite:2]
6. Schedule the agent on one desktop. Check the desktop profile before the shift, because the 1.0 article says an agent cannot sign in to both desktops at once.

04 · Ecosystem & sister technologies

Glossary, map, sisters, edges

Glossary

Unified CCX

Cisco Unified Contact Center Express. Article 0hd75db migrates it to Webex Contact Center with a discovery jar and a bulk workbook. [cite:1]

Discovery tool

The CCX extract. The page says download v3.5 and the command names uccx-to-webexcc-v3.4.jar. It needs Java 8 or above, CCX server access, and the CCX administrator account. Default port 443 if you omit the port. [cite:1]

WebexCC_Bulk_Upload

The workbook and prompts zip the discovery tool writes. Edit the sheets, then import through Control Hub Bulk Operations. A CSV over 5000 rows must be split. [cite:1]

WxCC 1.0

The legacy Webex Contact Center platform in article nb2ve0e. The upgrade enrolls the tenant, copies Management Portal configuration, and then you create flow scripts. [cite:2]

Pre-Upgrade Setup

Contact Center > Settings. Carries tenant settings, provisions the new Management Portal, copies configuration, provisions voice and digital channels, and creates agent accounts. Do not change the legacy Management Portal while it runs. [cite:2]

Post-Upgrade Cleanup

Same Settings area, after you are finished with the legacy platform. It decommissions the legacy Management Portal, and it makes legacy recordings and Analyzer data available on the new platform. [cite:2]

Tenant Data Migration Tool

Webex CCE portal-to-portal copy. Use cases include a POD move, an upgrade of UCCE for a tenant, and sandbox to production. It copies portal classes, not ICM scripts into Flow Designer. [cite:3]

Routing controls

A CCE portal class. Flag 1 on the tenant tool replaces every routing control on the target. [cite:3]

Peripheral gateway

On Webex CCE, Bulk Request can migrate agents from one peripheral to another and identify their skill groups. Multi-tenant architecture does not name a PG. [cite:4] [cite:5]

Common Identity phase 1

Webex CCE Portal provisioning so agents and supervisors sign in to Finesse with Webex Common Identity. [cite:4]

Entry point

Multi-tenant ingress. Telephony maps it to a number. A flow is attached through a routing strategy. [cite:5]

Flow Designer

Where you build the multi-tenant voice flow. The 1.0 article calls the new scripting surface Flow Control and says legacy routing strategies are incompatible, so you create them again. [cite:2] [cite:5]

Team

Multi-tenant group of agents at a site. The CCX workbook has a Team sheet with type AGENT or CAPACITY. That sheet is a CCX extract, not a UCCE skill group. [cite:1]

Analyzer

Multi-tenant reporting fed by contact events. After 1.0 cleanup, legacy Analyzer data is reachable from the new Analyzer. CUIC is unmarked. [cite:2] [cite:5]

Agent Desktop

The multi-tenant desktop. nb2ve0e says agents cannot simultaneously access the desktop on both the legacy and new platforms, and that agents can’t log in simultaneously to both. A separate sentence uses “at the same time” for Recording Management, which shows each platform’s own recordings during the upgrade. [cite:2]

Canon method

This room’s study sequence for UCCE or PCCE into multi-tenant WxCC: build beside the old estate, test a few agents, cut one number after the flow answers, keep CUIC until Analyzer is compared by hand. It is Canon planning.

Mind map

mindmap
  root((T6-R04))
    CCX
    WxCC1
    CCE portal
    Marked gap

Sister-technology matrix

Integration edges

Cross-platform bridges

Future-integration hooks

• Canon planning: when a later Cisco article maps one ICM node to one Flow Designer activity, replace that crosswalk row.
• The CCX article says the tool is still evolving and may not support every current feature. re-check the download page when you run it. [cite:1]
• Open the gadget in Finesse and the layout in Agent Desktop. The articles do not print a gadget-to-layout map, and each desktop changes on its own release.

Ecosystem troubleshooting

05 · Flow

What actually moves

06 · Config

Paths the articles print

1. CCX prepare: Webex Contact Center tenant, Control Hub users, users synchronized for Contact Center, discovery package on a host that can reach CCX. [cite:1]
2. Extract: java -jar uccx-to-webexcc-v3.4.jar -extract. The download line says v3.5. If the sheet name differs, edit application-pro.yml before -zip. Macintosh file names are case-sensitive. [cite:1]
3. CSV order: MultimediaProfiles, Site, UserProfiles, WorkTypes, AuxiliaryCodes, AgentProfiles, AddressBook, SkillDefinition, SkillProfile, Team, EntryPoint, OutdialEntryPoint, Queues, OutdialQueue, EntryPointMappings, OutdialANI, Users. [cite:1]
4. Sign in at https://admin.webex.com, Services, Contact Center, and confirm the entities. [cite:1]
5. 1.0: Contact Center > Settings, Pre-Upgrade Setup. Contact Cisco Solution Assurance to enable that workflow. Choose the PSTN provider when the workflow asks. [cite:2]
6. Create flow scripts, queues, teams, and routing strategies. Onboard agents. Move telephony, then chat, then email. [cite:2]
7. Cleanup only after every agent and every customer route has moved: Contact Center > Settings, Post-Upgrade Cleanup. [cite:2]
8. CCE tool: download TenantMigrationScripts.zip from the HuPortal Releases folder on sftp.ttec.com. Run copy_tenant_data.cmd from that folder. Do not paste the article’s sample passwords into a script you keep. [cite:3]
9. After a routing-control copy on Portal 12.6.0 or lower, restart Wildfly on the support server. On 12.6.1 or above, Administration > Support, reload the Portal Application Gateway cache, then reload the AG service. [cite:3]
10. Webex CCE agents who should use Webex identity: Portal Common Identity phase 1, then Finesse. Peripheral moves: Administration Bulk Request. [cite:4]

CCX command lines as printed (0hd75db)
  java -jar uccx-to-webexcc-v3.4.jar -extract
  java -jar uccx-to-webexcc-v3.4.jar -zip
  download line on the same page: discovery tool v3.5
  omit port → 443

CCE copy (n2puc5z) — parameters, not the sample secret
  copy_tenant_data.cmd
  each class flag: 1 replaces that class on the target, 0 skips it
  audio files: not copied

1.0 coexistence (nb2ve0e)
  both desktops at once: refused
  transfer or conference across platforms: refused
  few users before every DN: required

Screenshot placeholder. The steps above are the articles, not a redraw of a tenant.

07 · Limits

Numbers the articles state

08 · Troubleshooting

Ten failures that follow from the articles

09 · Self-question ladder

Twelve rungs

10 · Lab

A paper cutover, because the jar needs a CCX server

• Goal: write a one-page cutover that names the source product first, then only the tool that article allows.
• Prereq: this room, T3-R01, and T4-R01. A lab tenant is optional. Do not run the CCX jar against a logger you do not own.
• Step 1. Pick a source card: Unified CCX, WxCC 1.0, Webex CCE portal, or UCCE/PCCE. Expected: the matching article is 0hd75db, nb2ve0e, n2puc5z, or “no import, Canon method.”
• Step 2. For a CCX card, list the CSV order and the 5000-row split. Expected: Users.csv is last among the printed names.
• Step 3. For a 1.0 card, list Pre-Upgrade, flow creation, a few users, one DN, then cleanup. Expected: simultaneous desktop login is refused.
• Step 4. For a CCE card, list the classes and write “1 replaces” next to each flag you would set. Expected: audio files called out as manual.
• Step 5. For a UCCE card, copy the crosswalk and leave the marked rows marked. Expected: no sentence that says a script node equals a flow activity.
• Evidence: the one-page sheet. Screenshot the article heading you used, not a production portal.
• Break it: add a line that says “dialed number = entry point” for a UCCE source. Recovery: delete that line and write the 1.0 DN–EP sentence with its product name.
• Reflection: which tool would have deleted the target routing controls if you had set the wrong flag.

11 · Quiz

Twelve questions

12 · Audio

Slots for Studio

13 · Interview

Oral answers

30 seconds. I separate Unified CCX, Webex Contact Center 1.0, and Webex CCE portal data. Each has a Cisco article. An ICM script does not have an import into Flow Designer, so that row stays marked.

2 minutes. CCX uses a discovery jar and a bulk workbook, with a 5000-row CSV cap and a printed import order. The 1.0 upgrade enrolls the tenant, copies admin configuration, and makes you rebuild routing strategies as flows. You move a few users, then a dialed number, and you do not leave agents on both desktops. The CCE portal tool copies routing controls and schedule skills, and a flag of 1 replaces the target class. Audio files are manual. Webex CCE can also move agents between peripherals without deleting skill groups, and Common Identity signs them into Finesse.

30 seconds, crosswalk. Skill group, peripheral, CUIC, Finesse, CVP, and a UCCE dialed number are printed in the room as marked rows. I will describe entry point, flow, queue, and team from the architecture article without renaming them.

2 minutes, cutover. For UCCE or PCCE into multi-tenant Webex Contact Center I use a Canon method: build the new entry points and flows beside the old estate, test a few agents, cut one number only after the flow answers, and keep CUIC until Analyzer has been compared by hand. That sequence is mine. It is not a Cisco logger runbook. The 1.0 article’s “few users first” rule is the habit I am borrowing, and I say so.

What you will not say. You will not say a dialed number is an entry point. You will not paste the CCE tool’s sample password. You will not run the CCX jar at a UCCE logger.

14 · Citations

1. Migrate Cisco Unified Contact Center Express to Webex Contact Center — help.webex — article 0hd75db — help.webex.com article 0hd75db — retrieved 2026-10-14. Download line says discovery tool v3.5. Command prints uccx-to-webexcc-v3.4.jar. Workbook WebexCC_Bulk_Upload.xlsx, prompts zip, Bulk Operations, 5000-row CSV limit, printed import order, Java 8, default port 443.
2. Upgrade from Webex Contact Center 1.0 to Webex Contact Center — help.webex — article nb2ve0e — help.webex.com article nb2ve0e — header September 08, 2024, retrieved 2026-10-14. Pre-Upgrade Setup, New Platform Setup, Post-Upgrade Cleanup under Contact Center > Settings. Routing strategies are not copied. Few users before every dialed number. No simultaneous desktop login. No cross-platform transfer or conference. Legacy Analyzer data and recordings after cleanup.
3. Webex CCE Tenant Data Migration Tool Guide — help.webex — article n2puc5z — help.webex.com article n2puc5z — retrieved 2026-10-14. Portal-to-portal copy: routing controls, access groups and collections, collection objects, role assignments, audio metadata, schedule skills. Flag 1 replaces that class. Audio files are not copied. Use cases include POD move, upgrade UCCE for a tenant, and sandbox to production. Sample command credentials are omitted from this room.
4. Webex Contact Center Enterprise administration what’s new — help.webex — article nhy3hvdb — help.webex.com article nhy3hvdb — retrieved 2026-10-14. Bulk Request migrates agents between peripherals, individually or by team, and identifies skill groups. Common Identity phase 1 lets agents and supervisors sign in to Finesse with Webex identity.
5. Webex Contact Center architecture — help.webex — article utqcm7 — help.webex.com article utqcm7 — retrieved 2026-10-14. Multi-tenant picture: entry point, flow, queue, team, Analyzer, Connect. No ICM import.
6. Introduction, migrate Unified CM to Webex Calling — help.webex — article nbedetf — help.webex.com article nbedetf — retrieved 2026-10-14. Cited so the calling migration stays in T6-R02.
7. Provision Emergency Calling in Webex Contact Center — help.webex — article nvfbjts — help.webex.com article nvfbjts — retrieved 2026-10-14. Header September 08, 2024. Not a step inside the CCX workbook.
8. Webex AI Agent Studio Administration guide — help.webex — article ncs9r37 — help.webex.com article ncs9r37 — retrieved 2026-10-14. Scripted and autonomous agents are created in AI Agent Studio. The CCX bulk workbook’s sheet list does not include a virtual-agent sheet.

15 · Re-engineer later

• Open questions: the software-download file name that matches v3.5 versus the printed v3.4 jar; whether a later article maps one ICM node.
• Open each legacy object in its own admin tool and the Webex object in Control Hub or Flow Designer. No cited article prints a field map for ICM script, CVP/VXML, skill group, precision queue, peripheral as a multi-tenant object, UCCE dialed number, call type, CUIC, Finesse gadget import, or dual desktop on one call, because the object names differ and each tool changes on its own. WebRTC emergency is nvfbjts and is not a CCX workbook step.
• Assets missing: bulk-operations screenshot, audio.
• Ideas for v1.0: a one-page crosswalk that drops a row only when a new Cisco article names both sides.
• Next review: re-check 0hd75db if the jar line and the download line are edited to match.