Plan a Cisco Unified CM to Webex Calling migration
A migration succeeds or fails on what was found before the cutover. This is the planning sequence we use, whichever tool does the provisioning.
1. Inventory what exists
Export users, lines, devices, hunt groups, call queues, auto attendants, voicemail boxes, pickup groups, shared lines and call forwarding. Note which numbers are direct inward dial numbers and which are internal extensions only. Unused devices and unassigned numbers are common; decide now whether they move.
2. Decide how calls reach the PSTN
Webex Calling can use a cloud-connected carrier, Cisco's own calling plans where offered, or a local gateway you operate. Keeping your existing carrier through a local gateway avoids number porting on cutover day, at the cost of running that gateway. This choice shapes the whole schedule, so make it first.
3. Map locations and the dial plan
Unified CM organizes calling with partitions and calling search spaces. Webex Calling organizes it by location, with internal dialing and outbound permissions per location. Map each site to a location and write down which calling restrictions must survive.
4. Check the devices
Some Cisco phone models can be moved to Webex Calling and some cannot. Sort the inventory into phones that convert, phones to replace, and users who will move to a soft client. Order hardware before you set a date.
5. Map the features that do not translate directly
Hunt lists and line groups become hunt groups or call queues. Call handlers become auto attendants. Features such as intercom, extension mobility and complex shared-line layouts need a decision each. List them and get a sign-off from the people who use them.
6. Migrate in groups
Start with a small group that covers one of everything: a queue, an auto attendant, a shared line, an analog device. Verify calls in every direction, including to users still on Unified CM, before widening.
7. Keep a way back
Record what was created for each group so it can be removed. Keep the Unified CM configuration intact until the group has run cleanly for an agreed period.
The inventory is the plan. Anything not found before the cutover is found by a user after it.
Where Vector helps
Vector reads the Unified CM inventory through an on-site collector, shows what will and will not carry over, provisions Webex Calling in groups, verifies the result, and records each change so it can be rolled back.