Source record · tier 2 current vendor documentation
Best practices in preparation and migration process to Webex Calling - Dedicated Instance
- Publisher
- Cisco Webex
- URL
- https://help.webex.com/en-us/article/tf6kpq/Best-practices-in-preparation-and-migration-process-to-Webex-Calling-Dedicated-Instance
- Published
- 2026-05-14
- Updated
- unknown
- Accessed
- 2026-10-01
- HTTP status
- 200
- License
- Cisco proprietary; no-redistribution; short excerpts and locators only
Source notes citing this source
- Dedicated Instance provisioning sizes for three active devices per Knowledge Worker and accommodates the Flex agreement reserve of 15% or 20%. in context
- For Unified CM data, Cisco names Bulk Administration Tool export and import with scripting, or external tools such as Yarnlab Wrangler, as the migration tools. in context
- Cisco Emergency Responder data is moved to Dedicated Instance by manual or bulk export and import. in context
- Before migration, CallManager.pem, ITLRecovery.pem and the intermediate and root CA certificates are exchanged in both directions between the on-premises cluster and Dedicated Instance, so phones can move between clusters and back without a factory reset. in context
- Webex App users are moved by changing their calling behaviour in Control Hub, and Jabber users by the defined login method and a change of home cluster. in context
- For Unity Connection voicemail data, Cisco recommends COBRAS from the Cisco Unity Tools collection. in context
- On cutover day, devices are moved by changing DHCP option 150 on all affected subnets and resetting the phones on the on-premises Unified CM. in context
- Cutover also bulk-updates line and route pattern configuration between active and null partitions, updates home cluster settings and advertisements on both systems, and modifies gateway, SRST and hardware media configuration. in context
- After go-live, changes such as DNS entries, firewall updates, firmware uploads, cloud connectivity, UC application management and DI-MT interop trunks are requested from Cisco through service requests. in context
- Discovery should check the device inventory against the compatibility matrix for deprecated and end-of-support phones, with special restrictions noted for the 7925, 7940 and 7960. in context
- In the Dedicated Instance E911 model, on-premises phones are tracked by Cisco Emergency Responder and Webex App users by RedSky using HELD+. in context
- Webex Edge Connect for Dedicated Instance requires two links; four links are optional, are used in pairs without crossing, and traffic prioritisation between links is not supported. in context
- Enhanced Survivability Nodes are licensed per region through an ESN Flex SKU, allow up to 8 ESN nodes per cluster, and the customer provisions the virtual resources and installs the Medium OVA publisher. in context
- Cisco recommends a freeze phase of two to three weeks, during which data is moved from the source to the target Dedicated Instance and validated for cutover. in context
- Cisco recommends setting up the intercluster trunk between the on-premises cluster and Dedicated Instance early, to support testing, cross-integration and phased migration. in context
- For Dedicated Instance directory synchronisation, synchronisation should be enabled within 18 hours of creating the agreement. in context
- Dedicated Instance MRA capacity is initially deployed at 20% and can be expanded to 100% through a TAC ticket. in context
- In Dedicated Instance, SNMP monitoring is not allowed except for Emergency Responder and InformaCast by service request, and there is no external SFTP access. in context
- Cisco's Dedicated Instance migration best practice runs through project initiation, discovery and assessment, planning and implementation, freeze, cutover or go-live, and Day 2 operations. in context
- The Pre-Migration Assistant in Control Hub gathers source cluster data and checks prerequisites, reporting nodes, versions, SIP trunks, devices, route groups, partitions, device pools and database replication health. in context
- Cisco's cutover preparation is to open a proactive, scheduled TAC ticket for the cutover window. in context
- For Dedicated Instance E911, Cisco provides the proxy information and LUA script, while the customer or partner sets up the RedSky account and configures ELINs and parameters. in context
- Rollback mirrors the cutover method of procedure by reverting every executed action, and the procedure should have a deadline so rollback fits inside the maintenance window. in context
- SSO is not mandatory for Dedicated Instance itself but is mandatory for Webex Common Identity and Webex App use, and the SAML SSO process is the same as for on-premises Unified CM. in context
- Cutover testing covers intra-site and inter-site calls, PSTN, MRA, 911, voicemail and other applicable features. in context
- During the freeze, a test group of phones is repointed to the Dedicated Instance TFTP, manually or through DHCP option 150, and both migration and rollback are tested once certificates are consolidated. in context
- Checking which phones are registered on the new Dedicated Instance cluster is the recommended way to control cutover progress. in context
- Webex Virtual Connect for Dedicated Instance has a maximum bandwidth of 250 Mbps and is not supported for Enhanced Survivability Node deployments. in context
- Configuration elements in Dedicated Instance whose names begin with 'x' must not be renamed because automation, serviceability and analytics integrations use them. in context
- A customer planning Enhanced Survivability Nodes would peer with Edge Connect or Partner Connect rather than Virtual Connect, since Virtual Connect is not supported for ESN. inferred in context
- A phone rollback to the on-premises cluster without factory resets depends on completing the two-way certificate exchange before any production phone is moved. inferred in context
- Because Cisco's Dedicated Instance best-practice article names BAT with scripting, Wrangler and COBRAS as the freeze-phase tools, the Control Hub multi-tenant migration task should not be assumed to be the primary path for moving a cluster into Dedicated Instance. inferred in context
Cite this source record
APA
WarmTransfer. (2026, May 14). Best practices in preparation and migration process to Webex Calling - Dedicated Instance. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-tf6kpq-di-migration-best-practices
BibTeX
@misc{warmtransfer-cisco-help-tf6kpq-di-migration-best-practices,
title = {Best practices in preparation and migration process to Webex Calling - Dedicated Instance},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/cisco-help-tf6kpq-di-migration-best-practices},
note = {Cisco Webex, accessed 2026-10-01}
}