Source record · tier 2 current vendor documentation

Migrate Unified CM data to Webex Calling

Publisher: Cisco Systems, Inc. (Webex Help Center)
URL: https://help.webex.com/en-us/article/x974bd/Migrate-Unified-CM-to-Webex
Published: 2026-04-27
Updated: unknown
Accessed: 2026-09-04
HTTP status: 200
License: Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

Cisco's Control Hub Unified CM to Webex Calling migration tells administrators to use the Unified CM Bulk Admin Tool to get the tar files and upload the .tar in Step 2: Import Data. in context
The migration tool's CSV import template includes a CUSTOM DEVICE POOL field, described as a tag for a set of devices or users (example value Location-NY). in context
The Control Hub migration tool for Unified CM to Webex Calling has a 'Map device pool to locations' step, where each Unified CM device pool is assigned a Webex Calling location or left undefined. in context
The migration tool can migrate only those Unified CM directory numbers that are mapped to a single device pool. in context
The migration tool maps locations per device pool, so a Unified CM device pool that spans several physical sites would send all its devices to one Webex Calling location. Such pools may need to be split on Unified CM before migration. inferred in context
Cisco's Control Hub article on migrating Unified CM data to Webex Calling states in its overview that the steps apply to Dedicated Instance also, and limits each migration task to 1000 users and 1000 devices. in context
PID A-FLEX-P-CALL provides temporary licensing for up to 18 months during the transition, with basic-level support on both calling environments. in context
Phones on Unified CM that are being migrated must run phone load version 14.1 or later. in context
The Control Hub Unified CM migration tool migrates at most 1000 users and 1000 devices per task; larger migrations need multiple tasks. in context
The Control Hub Unified CM migration tool moves users, devices, numbers and locations, up to 1000 users and 1000 devices per task, and needs all end users already provisioned as Webex users. in context
The Webex Calling migration tool maps Unified CM device pools to Webex Calling locations, and the mapping can be left undefined and completed later. in context
The Cisco migration tool article describes migrating users, devices, numbers and locations but does not describe migrating partitions, calling search spaces, route patterns or translation patterns, so the dial plan is likely rebuilt by hand. inferred in context
The migration CSV template carries the fields CUCM USER ID, EMAIL ID, DEVICE MAC, CUSTOM DEVICE POOL and USER AREA CODE. in context
Within the migration task, Unified CM device pools are mapped to Webex Calling locations or left as Undefined for later configuration, and warnings about devices mapped to multiple locations must be resolved before proceeding. in context
The data migration flow lists an active Webex Calling subscription with entitlement PID A-FLEX-P-CALL as a prerequisite, alongside organisation administrator access to Control Hub. in context
Data is loaded into the migration flow at Step 2 Import data by choosing Action then Import user list and uploading the Unified CM .tar file, and only on success does the Create a New Task button in Step 3 become enabled. in context
The post-migration manifest is applied on Unified CM through Bulk Administration Upload/Download Files, adding the CSV with Target set to Phone and Transaction Type set to Update Phone - Custom File, then running Bulk Administration, Phones, Update Phones, Custom File and monitoring the Job Scheduler. in context
The Unified CM data migration article documents no rollback or back-out procedure for a completed migration task, so reversal has to be planned as a manual re-registration of devices to Unified CM rather than as a supported product action. inferred in context
Selecting Prepare to Migrate at the Review step runs the pre-migration activities, which include creating a profile for each device in the Webex App. in context
A Unified CM data migration task requires a unique task name of at least 8 characters. in context
Webex identifies the users being migrated by the Unified CM email ID when numbers are assigned to users and workspaces, and workspaces are toggled manually. in context
Because a single data migration task caps at 1000 users and 1000 devices, a flash-cut of an estate larger than that is not one task but several tasks run inside one cutover window, which sets a practical floor on how long the window can be. inferred in context
To assign a Webex Calling Standard license during a Unified CM migration, the documented path is to use a user CSV file and then the Migrate features from the Unified CM tool rather than the data migration tool. in context
Users migrated from Unified CM to Webex Calling with the migration tool can be assigned only Calling Professional or CX Essentials licenses. in context
Workspaces migrated from Unified CM to Webex using the migration tool can be assigned Workspace or Professional Workspace licenses. in context
The Unified CM data migration flow is started in Control Hub under Services, Upgrades and Migrations, on the tile named Migrate Unified CM to Webex Calling. in context
Cisco states that 2 reports in the migration export zip, SharedlineGroupMigrationReport.csv and HuntGroup_CallQueue_CallPark_CallPickUpGroups.csv, should be used to identify which users are in relationship with each other for group features and should migrate together. in context
Cisco states that when users migrate from Unified CM to Webex Calling using the migration tool they can only be assigned Calling Professional or CX Essentials licenses, that an administrator needing to assign a Webex Standard license must not use that tool and should instead use a user CSV file followed by the Migrate features from Unified CM tool, and that a migrating workspace can be assigned Workspace or Professional Workspace licenses. in context
Clicking Complete migration downloads a manifest file in .zip format containing the MAC addresses of phones in a .csv file, which the administrator uploads on Unified CM through Bulk Administration Upload slash Download Files with the target set to Phone and the transaction type set to Update Phone - Custom File in order to start the migration. in context
Migration Insights, reached in Control Hub under Services, Upgrades and Migrations, is offered as the assessment step for deciding whether to migrate to Webex Calling. in context
The migration flow offers 3 documented number-assignment scenarios by the PSTN model of the Webex locations involved: where all locations are local gateway, Add numbers to location is enabled and Auto assign numbers is greyed out; where all locations are Cloud Connected PSTN or Cisco PSTN, Auto assign numbers is enabled and Add numbers to location is greyed out; and where the locations are a mix of premises-based PSTN and Cloud Connected or Cisco PSTN, both options are greyed out. in context
Phones on Unified CM that are being migrated must be running Phone Load version 14.1 or later. in context
All Unified CM end users must already be provisioned as Webex users, through Cisco Directory Connector or another mechanism, before the migration task runs. in context
A single Unified CM to Webex Calling migration task can migrate at most 1000 users and 1000 devices; larger estates require multiple migration tasks. in context

Cite this source record

APA

WarmTransfer. (2026, April 27). Migrate Unified CM data to Webex Calling. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-x974bd-migrate-ucm-data-to-wxc

BibTeX

@misc{warmtransfer-cisco-help-x974bd-migrate-ucm-data-to-wxc,
  title  = {Migrate Unified CM data to Webex Calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-x974bd-migrate-ucm-data-to-wxc},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-04}
}