Plan a clean move of users, phone numbers, and devices from one Webex Calling location to another. Dependency checklist, downtime window, and rollback plan.
Office relocations, region splits, and PSTN provider changes all require moving users between Webex Calling locations. The challenge: location drives PSTN, E911 address, calling permissions, and routing prefix — changing it cascades into all four. This tool maps out the changes, orders them, and gives you a downtime-minimizing sequence.
Set fields, click Plan Move.
Number validation, E911, licenses.
Step-by-step in Control Hub.
Per-user and total window.
If cutover fails, how to revert.
The most common move failure is E911 mismatch. A user relocated to a new physical address, but their Webex location record still shows the old one. If they dial 911 from a softphone, the PSAP sends an ambulance to the wrong building. Always update the location's Emergency Address in Control Hub before the user moves their device, and re-validate with a test call (or simulated test via PSAP coordinator).
The second common failure is calling permissions drift. User moves to a new location with a different class of service — suddenly they can't dial international, or their access to premium-rate numbers changes. Audit the destination location's outbound permissions before the move; if they differ, create a CoS for the moved users that preserves their previous capability.
The third is number orphaning. You moved 40 users but forgot to move their DIDs; now the DIDs route to the old location (which may have nobody answering). Always move users and numbers together. In Control Hub, numbers are tied to the location, so you must re-assign each number to the new location before associating with users.
Hunt groups and AAs don't move automatically. If a hunt group's members are at the old location and you move the members, the HG itself stays at the old location. You'll need to recreate the HG at the new location (or leave it where it is and update the member list to include the new-location users). Phased cutovers make this worse — members split across two locations for a few days.
Yes — in Control Hub, unassign from user, re-assign number to new location, re-attach to user.
Extensions are tied to the user. If the location uses ESN routing prefix, the effective dialed number changes.
Yes, for a few minutes during re-assignment. Schedule in a low-traffic window.
Yes — devices re-register against new location settings. ~30 sec outage per device.
Half moves to a new satellite.
Office lease ends.
Absorb another org.
Our UC Modernization Sprint plans and executes location moves including PSTN porting, E911, and per-user cutover — no missed calls.