Migrate enterprise phone to Webex Calling phone firmware

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/en-us/article/n19c71/Migrate-Your-Phone-to-Webex-Calling

Published

unknown

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Cloud-Connected UC is the gate on the automated paths through the migration: without it the CDR-based usage reports in Migration Insights and the in-Control-Hub firmware migration are unavailable and the administrator falls back to BAT file exchange for every device change. inferred in context
• With Cloud-Connected UC enabled, phones can be migrated directly from Control Hub by selecting the TFTP server type and Unified CM TFTP load server and choosing Migrate Phones, which processes devices in batches of 200. in context
• Without Cloud-Connected UC, firmware migration is completed by downloading BAT files from Control Hub, uploading them on Unified CM under Bulk Administration Upload/Download Files with Target Phone and Transaction Type Update Phone - Custom File, then confirming completion back in Control Hub. in context
• Because the firmware migration article documents no procedure for reverting a phone from Multiplatform firmware back to Enterprise firmware, converting a phone should be treated as the point of no return for that device within a migration window. inferred in context
• Before running a device firmware migration task, locations must exist with PSTN assigned for each location, all Unified CM users must be imported into Control Hub, and phone firmware must be at version 14.1 or later. in context
• A single device firmware migration task supports a maximum of 1000 devices. in context
• The device firmware migration wizard classifies devices as Eligible, Ineligible, or Unknown eligibility, where Unknown means the tool has inadequate information and the migration may or may not succeed; devices with Unknown eligibility can optionally be included in a task. in context
• A firmware migration task offers Generate device license and add device, which generates licences and provisions the device, or Generate device license only, which requires the devices to already exist in Webex Calling. in context
• Automatic enterprise-to-MPP migration requires a wired connection and Cloud Connected UC, and Control Hub triggers it in batches of at most 200 devices. in context
• Control Hub's enterprise-to-MPP phone migration requires the phones to be on enterprise firmware 14.1 or later. in context
• Cisco IP Phone 8821 and 8831 are not eligible for enterprise-to-MPP migration. in context
• When wireless-capable phones are converted to MPP firmware they lose their Wi-Fi settings, so Cisco advises connecting them by Ethernet during migration and reconfiguring Wi-Fi afterwards. in context
• The Control Hub enterprise-to-MPP migration workflow runs: add devices via CSV template, verify device eligibility, prepare for migration (which generates licenses), complete migration automatically or manually, then monitor status in Control Hub. in context

Cite this source record

APA

WarmTransfer. (2026, September 16). Migrate enterprise phone to Webex Calling phone firmware. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-n19c71-migrate-phone-to-webex-calling

BibTeX

@misc{warmtransfer-cisco-help-n19c71-migrate-phone-to-webex-calling,
  title  = {Migrate enterprise phone to Webex Calling phone firmware},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-n19c71-migrate-phone-to-webex-calling},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-16}
}