Migrate devices and features from Unified CM to Webex Calling

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/en-us/article/d2lemv/Migration-of-Devices-and-Features-From-Cisco-unified-Communications-Manager(UCM)-to-Webex-Calling-Multi-Tenant

Published

2026-08-21

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

• The Control Hub migration upload accepts a Unified CM .tar of at most 350 MB. in context
• Cisco says the BAT .tar can be used to migrate auto attendants, devices, configured lines, device layout (speed dials and shared lines), virtual lines, call queues, hunt groups, call park and user call forwarding and monitoring data. in context
• The migration tool's ImportDataBulk.csv output contains data extracted from enduser.csv, phone.csv and device_pool.csv in the imported Unified CM tar. in context
• In the device and feature migration CSVs, the device pool column looks informational. The article gives no rule for turning it into a Webex Calling setting; location assignment is handled by the separate device-pool-to-location mapping step. inferred in context
• In the device and feature migration workflow, the DeviceBulk.csv, DeviceBulkError.csv and ImportedDataBulk.csv files each carry a column for the Unified CM device pool the device belongs to. in context
• The migration tool's export ZIP includes Auto-AttendantBulk.csv, which holds auto attendant provisioning data together with errors and notes for administrator review. in context
• If a Webex Calling location cannot be derived from the Unity auto attendant number, the location must be set manually in the migration CSV. in context
• The migration tool can report that an auto attendant configuration cannot be migrated because Webex Calling has no equivalent feature. in context
• If the Unity auto attendant number is already assigned to another user in Webex Calling, the migration output flags it and the administrator must supply an available number, location, language and time zone manually. in context
• When the auto attendant number from Unity cannot be determined in Webex Calling, the administrator must manually fill the phone number, extension, location, language and time zone columns of Auto-AttendantBulk.csv. in context
• In the Control Hub Unified CM feature migration workflow, uploading a Unity Call Handler .zip file is an optional step used for Auto-Attendant migration. in context
• Cisco's feature migration article directs administrators to the CallHandlerDataDump tool to create the Unity call handler file that the migration tool ingests. in context
• The Control Hub feature migration tool covers Auto-Attendant, Devices, Configured Lines, Device Layout (speed dial, shared line), Virtual Line, Call Queue, Hunt Group, Call Park and User Calling data (call forwarding and call monitoring); voicemail messages are not in that list. in context
• The Unity call handler .zip uploaded to the Control Hub feature migration tool may be at most 2 GB. in context
• The Unified CM export/import migration covers auto attendants, devices, configured lines, device layout including shared lines, virtual lines, call queues, hunt groups, call park and user call forwarding and monitoring. in context
• If the CSV files produced by the features migration tool contain errors, the uploaded .tar file can be removed with the Delete option and the upload repeated. in context
• Errors flagged in the exported feature CSVs must be resolved and the Errors and Notes columns removed before the CSVs are uploaded back to Control Hub. in context
• Cisco's Webex Calling migration path for Unity Connection auto attendants depends on a tool that Cisco Unity Tools marks as not TAC supported and lists only up to Connection 11.x. inferred in context
• The Control Hub migration from Unified CM to Webex Calling accepts an optional Unity Call Handler .zip file for Auto-Attendant, uploaded after the Unified CM .tar file. in context
• The Unity .zip file uploaded to the Control Hub migration can be at most 2 GB. in context
• The Webex migration article points administrators to Call Handler Data Dump to create the Unity Call Handler .zip file. in context
• Cisco's Unified CM to Webex Calling migration tool takes auto attendant input as a Unity Call Handler .zip file, built with the CallHandlerDataDump tool. in context
• The migration tool's auto attendant error list includes 'The greetings file cannot be found in WxC', marked as not migratable. in context
• Auto attendant greeting audio probably has to exist in Webex Calling before the migration tool runs, because the tool reports a missing greetings file as a failure rather than carrying the audio across. inferred in context
• Cisco lists the migration tool's scope as auto attendants, devices, configured lines, device layout, virtual lines, call queues, hunt groups, call park and user calling data (call forwarding and call monitoring); voicemail mailboxes are not on that list. in context
• Cisco's article on migrating devices and features from Unified CM to Webex Calling does not list paging among the migrated features, so paging configuration probably has to be rebuilt by hand. inferred in context
• Cisco states that the supplementary migration utility script creates CallPark.csv and CallPickupgroup.csv files for Webex Calling which the Migrate features from Unified CM tool does not currently support, while that tool does produce a CallParkExtensionBulk.csv containing provisioning data to configure call park extensions. in context
• 2 current Cisco help articles disagree on the Control Hub menu label for the migration area: the Unified CM data migration article says Services then Upgrades and Migrations, while the devices and features article says Services then Updates and Migrations. disputed in context
• The devices and features migration tool is reached in Control Hub under Services, Updates and Migrations, in the Migration utilities section, on the Migrate features from Unified CM card. in context
• The devices and features migration tool covers Auto-Attendant, Devices, Configured Lines, Device Layout including speed dial and shared line, Virtual Line, Call Queue, Hunt Group, Call Park, and user calling data comprising call forwarding and call monitoring. in context
• Cannot be migrated as there is no equivalent feature in WxC is one of 6 documented error and note values for the Auto-AttendantBulk.csv migration report, alongside a location that cannot be derived from the auto attendant number from UNITY, an empty extension column in the source data, a business schedule that does not exist in the location or organisation, a name that cannot be null, and a greetings file that cannot be found in Webex Calling. in context
• Cisco states that the devices and features migration steps also apply to Dedicated Instance, not only to Webex Calling multi-tenant. in context
• Cisco documents a python script named UserBasedUCMFeatureMigration that processes call detail record data collected on a server or Unified CM, filters the output of the Migrate features from Unified CM tool by a user list with an optional Location column override, identifies users who are part of group features but are not in that list, identifies directory numbers existing in multiple device pools and lists them in DNInMultipleDevicePool.csv in the insightDir folder, and creates CallPark.csv and CallPickupgroup.csv. in context
• The Unified CM .tar file uploaded to the devices and features migration tool is limited to 350 MB. in context
• An optional Cisco Unity Connection export produced by the CallHandlerDataDump tool may be uploaded as a .zip file up to 2 GB. in context

Cite this source record

APA

WarmTransfer. (2026, August 21). Migrate devices and features from Unified CM to Webex Calling. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-d2lemv-migrate-devices-features-ucm

BibTeX

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