Source note · CUCM to Webex Calling migration
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.
Checked 2026-09-16
Cannot be migrated as there is no equivalent feature in WxC.
- Vendor
- Cisco
- Product
- Webex Calling
- Subsystem
- Unified CM to Webex Calling migration
- Deployment
- multi-tenant, dedicated-instance
- Region
- not restricted
- Release range
- current as of 2026-09-04
- Checked
- 2026-09-16
Sources
- Migrate devices and features from Unified CM to Webex Calling — Cisco Systems, Inc. (Webex Help Center) · tier 2 current vendor documentation · Auto-AttendantBulk.csv column table, the errors and notes value list, read as cells
Cite this note
APA
WarmTransfer. (2026, September 16). CUCM to Webex Calling migration: source note wxc-mig-some-auto-attendants-have-no-equivalent. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxc-mig-some-auto-attendants-have-no-equivalent
BibTeX
@misc{warmtransfer-claim-wxc-mig-some-auto-attendants-have-no-equivalent,
title = {CUCM to Webex Calling migration: source note wxc-mig-some-auto-attendants-have-no-equivalent},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxc-mig-some-auto-attendants-have-no-equivalent},
note = {Source note wxc-mig-some-auto-attendants-have-no-equivalent, checked 2026-09-16}
}