00 · Header
T5 · Dedicated Instance
DI Migration Path
The Dedicated Instance move is seven gates, not a weekend copy. The Control Hub assistant assesses an on-premises Unified CM. It does not migrate the cluster. A certified provider tool does that work. Cutover in the assistant is capped at ten hours.
01 · Executive summary
Five lines, then why it matters
- The practice article says roughly 95 percent of engineering effort is preparation and 5 percent is the change. That sentence is the article’s framing, not a sizing formula. [cite:1]
- The assistant tile is visible only when Setup Assist is enabled along with Dedicated Instance. Prerequisites are an active Dedicated Instance subscription, Cloud-Connected UC, and deployment insights. [cite:2]
- Source readiness sheets cover assessment actions, phone and gateway upgrades, credential policy, and application users. [cite:2]
- Go-live changes Option 150, resets phones, checks registration on Dedicated Instance, then bulk-updates partitions, home cluster, and advertisements. [cite:1]
- The same framework names source platforms that include third-party PBX. It does not print an object crosswalk. That gap is T6-R05. [cite:1]
02 · Architecture map
Seven gates, one cutover
Mermaid source (not rendered)
flowchart LR A[Initiate] --> B[Discover] --> C[Plan] --> D[Implement] --> E[Freeze] --> F[Go live] --> G[Day 2]
03 · Core concepts
Gates, then the tool that only assesses
Project Initiation, Discovery and Assessment, Planning, Implementation, Freeze, Go Live, and Transfer to Day 2. Each phase has entry and exit criteria in the practice article. [cite:1]
No impact: initiation, discovery, planning. Minimum: implementation. Limited to operations processes: freeze. Direct: go live. [cite:1]
It gathers source data, checks prerequisites, and compares on-premises Unified CM with Dedicated Instance. Customers work with a partner who uses a Certified Migration Provider tool to complete the migration. The tile shows only if Setup Assist is enabled along with Dedicated Instance. [cite:2]
The practice article recommends 2–3 weeks of freeze. The assistant says the cutover window should not exceed ten hours. Those are different intervals. Do not call the freeze a ten-hour event. [cite:1] [cite:2]
What each gate is for
| Gate | Production impact | What this pass can cite | Cite |
|---|---|---|---|
| Project Initiation, Discovery and Assessment, Planning | No impact | The assistant’s readiness work sits in discovery. Configuration under Actions stays unavailable until Setup Assist approves the source readiness report. | [cite:1] [cite:2] |
| Implementation | Minimum | The practice article points at activation, peering, directory sync, SSO, certificates, and intercluster integration in this phase. Peering rules stay in T5-R02. | [cite:1] |
| Freeze | Limited to operations processes | Move data and validate. Recommended 2–3 weeks. MACD on both systems. Test Option 150, a test gateway, Webex App calling behavior, Jabber home cluster, on-net and VPN, MRA, PSTN, and 911. | [cite:1] |
| Go Live | Direct | TAC ticket, Option 150, reset, registration check, bulk partition and home-cluster updates, gateway and SRST changes, then the test program. Rollback mirrors the method of procedure. | [cite:1] |
| Transfer to Day 2 | The article points at operations documents | Tier 1, the service-request list, the partner operations guide, and the RACI. Those are T5-R04. | [cite:1] |
Data-move tools the freeze section names
| Source | What the article recommends | Cite |
|---|---|---|
| Unified CM | Active and inactive partitions. BAT export and import. It names external tools for UCM migrations like Yarnlab. This room does not describe Yarnlab beyond that phrase. | [cite:1] |
| Unity | Cisco Unity tools. The article recommends Cobras for Unity migrations. | [cite:1] |
| Emergency Responder | Manual, or bulk export and import. | [cite:1] |
Reports after the assistant’s schedule completes
| Report | What it checks | Cite |
|---|---|---|
| Source readiness | Assessment sheet, phone and gateway recommendation, credential policy, application users. | [cite:2] |
| DI-readiness check | Data for the Dedicated Instance cluster. | [cite:2] |
| Post-migration | Compared data between source and Dedicated Instance clusters. | [cite:2] |
| Post-registration | Phones registered to the Dedicated Instance cluster. | [cite:2] |
| Device IP connectivity | Devices that are not reachable from the selected Dedicated Instance cluster. The assessment article calls that a recommended action before migration. | [cite:3] |
04 · Ecosystem & sister technologies
Glossary, map, sisters, edges
Glossary
- Seven-gate framework
- The self-service Dedicated Instance migration sequence in the practice article. [cite:1]
- Pre-Migration Assistant
- Control Hub discovery and readiness for Unified CM to Dedicated Instance. It does not migrate. [cite:2]
- Certified Migration Provider tool
- The tool class the assistant article says the partner uses to complete the migration. [cite:2]
- Freeze
- Data move and validation. Recommended 2–3 weeks. Changes during freeze go on both systems. [cite:1]
- Cutover window
- In the assistant scheduler, it should not exceed ten hours. Phones in the selected device pools register to Dedicated Instance during that window. [cite:2]
- Option 150
- The DHCP option the practice article changes so phones learn the Dedicated Instance TFTP. [cite:1]
- Rollback
- A mirror of the cutover method of procedure, inside the maintenance window. [cite:1]
Mind map
Mermaid source (not rendered)
mindmap
root((DI migration))
Seven gates
Assistant
Provider tool
Option 150
Day 2
Sister-technology matrix
| Sister | What it is | Why it matters here | Config touchpoint | Typical failure | Cite |
|---|---|---|---|---|---|
| Cloud-Connected UC | The agent that extracts Unified CM data. | The assistant requires the org to be onboarded and deployment insights enabled. | Services → Updates and Migration → the Dedicated Instance assistant tile. | The tile is missing because Setup Assist or Dedicated Instance is not enabled. | [cite:2] |
| Identity / SSO | Named in the practice article’s implementation topics. | User sync behavior for a mixed estate is T5-R05. This room does not restate that SSO rule as a new sentence. | Read the directory-sync section of tf6kpq before cutover. | Phones move and users do not. | [cite:1] |
| Emergency calling | 911 is on both the freeze test list and the go-live test list. | CER data is manual or bulk. AMER-only CER deployment is T5-R02, not a new claim here. | Test 911 before you call the gate passed. | Option 150 succeeds and 911 was never in the test program. | [cite:1] |
| PSTN / gateways | Test gateway in freeze. Production gateway, SRST, and hardware media on go-live. | Templates are prepared during freeze. | Do not paste sample gateway passwords into the runbook. | SRST still points at the old call manager after reset. | [cite:1] |
| Webex App and Jabber | Freeze tests include a calling-behavior change for Webex App and a home-cluster change for Jabber. | Those are explicit moves, not a side effect of Option 150. | Control Hub calling behavior, and the Jabber login method the plan already defined. | Phones register and soft clients stay on the old cluster. | [cite:1] |
| TAC | Go-live starts with a proactive ticket, scheduled dispatch. | Day 2 support model is the Tier 1 article. | Open the ticket before the Option 150 change. | A failed reset with no case already open. | [cite:1] |
| Recording and WFO | Not given a Dedicated Instance migration procedure in these three articles. | Do not invent a recorder cutover. | Read the recording vendor’s own guide. TODO-verify a Cisco recorder step for this path. | Assuming Unity Cobras also moves the recorder. | [cite:1] |
| Multi-tenant split | After Dedicated Instance, users can be divided. | That steady state is T5-R05. | Do not split hunt groups across platforms. | Using go-live night to also split the user base. | [cite:4] |
Integration map
| From | To | Mechanism | What moves | Cite |
|---|---|---|---|---|
| On-premises UCM | Control Hub assistant | Cloud-Connected UC | Source inventory and readiness, not the live cut. | [cite:2] |
| Setup Assist | Source report | Mapping approval | Assessment, phone and gateway, credential policy, application users. | [cite:2] |
| Admin | Network questionnaire | Trunk purpose and peering choice | Trunks prepopulated from the readiness report. | [cite:2] |
| Scheduler | Device pools | Freeze dates and a cutover of at most ten hours | Which pools register to Dedicated Instance. | [cite:2] |
| DHCP | Phones | Option 150 | TFTP of the Dedicated Instance cluster, after reset. | [cite:1] |
| BAT | Dedicated Instance | Export and import | Unified CM configuration during freeze. | [cite:1] |
| Cobras | Unity Connection | The article’s Unity recommendation | Unity migrations. Not CER. CER is manual or bulk. | [cite:1] |
| Go-live | On-premises UCM | Partition and home-cluster bulk update | Active versus null partitions, advertisements. | [cite:1] |
Cross-platform bridges
| This room | Legacy | Peer orientation | Cite |
|---|---|---|---|
| Unified CM to Dedicated Instance | The source the assistant names. The practice article also lists BroadCloud, BroadWorks, Spark Calling, HCS, and third-party PBX as platforms the method has been used for. | No Avaya or Genesys object map in these pages. TODO-verify any crosswalk. T6-R05 holds that gap. | [cite:1] |
| Multi-tenant Webex Calling migration tools | A different Control Hub tile. T6-R03. The assistant article is Dedicated Instance. | Do not upload a multi-tenant task file and call it this assistant. | [cite:2] |
| Teams Phone or Amazon Connect | Not a source system in the assistant steps. | Equivalence is TODO-verify. The practice article does not print it. | [cite:1] |
Future-integration hooks
- Canon plan: T6-R03 is the Control Hub tool catalog for multi-tenant Unified CM migration. This room stays on the Dedicated Instance gates.
- Canon plan: T5-R04 is Day 2. The practice article’s last gate points at that RACI, Tier 1, and the service-request list.
- The practice article’s header date was not in the retrieved markdown. re-check the 2–3 week freeze and the 95/5 sentence before you quote them in a proposal. [cite:1]
Ecosystem troubleshooting
| Symptom | Likely sister-system cause | Check | Fix | Cite |
|---|---|---|---|---|
| Assistant tile is absent | Setup Assist is not enabled with Dedicated Instance, or Cloud-Connected UC or deployment insights are off. | Prerequisites on step 1. | Complete those three, then Ready to migrate. | [cite:2] |
| Configuration action is grey | Setup Assist has not approved the source readiness report. | Status is still In Progress. | Wait for approval. Download report, then approve. | [cite:2] |
| Phones reset and stay on the old cluster | Option 150 or the reset did not reach those subnets. | Registration count on Dedicated Instance. | The practice article treats that count as the control. Roll back if you miss the window. | [cite:1] |
| A device cannot be reached from the Dedicated Instance cluster before cutover | The assessment report’s device IP connectivity list. | That sheet. | Treat it as a customer action before migration. | [cite:3] |
05 · Flow
From Ready to migrate to a mirrored rollback
| Step | From | To | Mechanism | Notes | Cite |
|---|---|---|---|---|---|
| 1 | Admin | Assistant | Prerequisites | Dedicated Instance subscription, Cloud-Connected UC, deployment insights. Check the box. Ready to migrate. | [cite:2] |
| 2 | Setup Assist | Report | Cluster mapping | Source status moves to In Progress, then Download report after approval. | [cite:2] |
| 3 | Admin | Questionnaire | Trunk purpose and peering | I agree, then submit. Status is In Review until Setup Assist approves. | [cite:2] |
| 4 | Admin | Schedule | Freeze and cutover | Destination region and source cluster. Cutover not more than ten hours. | [cite:2] |
| 5 | Data move | Dedicated Instance | BAT, Cobras, or CER bulk | During the recommended 2–3 week freeze. MACD on both systems. | [cite:1] |
| 6 | DHCP | Phones | Option 150 and reset | After a proactive TAC ticket. | [cite:1] |
| 7 | Admin | Both clusters | Bulk update | Lines and route patterns, active versus null partitions, home cluster, advertisements. Gateways, SRST, hardware media. | [cite:1] |
| 8 | Test program | Rollback decision | Listed calls | Intra-site, inter-site, PSTN, MRA, 911, voicemail, applicable features. Rollback mirrors the procedure. | [cite:1] |
06 · Config
Scheduler clicks, then the cutover list
- Sign in to Control Hub. Open Services → Updates and Migration. Get Started on Pre-Migration Assistant for Dedicated Instance. [cite:2]
- Confirm the subscription, Cloud-Connected UC, and deployment insights. Select the prerequisites checkbox. Click Ready to migrate. [cite:2]
- After Setup Assist approval, download the source readiness report and approve it. Open Configuration, agree, and submit trunk purpose plus the peering choice. [cite:2]
- Add a schedule. Pick destination region and source cluster. Enter freeze start and end. Enter cutover start and end. Keep the cutover at or under ten hours. [cite:2]
- During freeze, move Unified CM with BAT, Unity with Cobras if you follow the recommendation, and CER manually or in bulk. Apply MACD on both systems. [cite:1]
- On go-live, open the proactive TAC ticket, change Option 150, reset, count registrations, then bulk-update partitions and home cluster. [cite:1]
- Run intra-site, inter-site, PSTN, MRA, 911, and voicemail tests. If you miss the window, roll back by reversing the same steps. [cite:1]
- When the assistant status is complete, open the DI-readiness, post-migration, and post-registration reports. [cite:2]
DI migration card (tf6kpq / r1ueuw / 9jw4mab). No customer secrets. gates: initiate, discover, plan, implement, freeze, go live, day 2 assistant migrates: no tile: Setup Assist enabled along with DI freeze: 2–3 weeks recommended cutover window: not more than 10 hours phone move: Option 150, then reset progress: phones registered on DI rollback: mirror of the cutover unity tool named: Cobras UCM tool class: BAT; external example Yarnlab, no further claim
07 · Limits
What is quantified
| Item | Value | Source | Verified? |
|---|---|---|---|
| Gates | 7 | [cite:1] | Named in the article. Header date not in the retrieved markdown. re-check |
| Preparation versus change | Roughly 95 percent and 5 percent | [cite:1] | Quoted as the article’s framing. re-check |
| Freeze | 2–3 weeks recommended | [cite:1] | A recommendation. re-check |
| Cutover window in the assistant | Should not exceed ten hours | [cite:2] | Quoted. Header October 22, 2025. |
| Scale the practice article claims | From single-seat to implementations exceeding 100,000 seats and hundreds of locations | [cite:1] | Quoted as the article’s scope sentence. Not a cluster sizing limit. re-check |
| Assistant performs migration | No | [cite:2] | Quoted |
| Source platforms named | BroadCloud, BroadWorks, Spark Calling, Unified CM, HCS, third-party PBX | [cite:1] | Quoted. No per-platform procedure in that sentence. |
08 · Troubleshooting
Ten migration failures
| Symptom | Likely cause | Evidence | Fix | Cite |
|---|---|---|---|---|
| The team expects the assistant to move phones | The article says it does not perform the migration. | Overview paragraph. | Use the certified provider tool the partner brings. | [cite:2] |
| Cutover is planned as a two-day window in the scheduler | The cutover window should not exceed ten hours. | Step 4 warning. | Shorten the window. Freeze is the multi-week phase. | [cite:2] |
| A user change during freeze lands on one cluster | MACD during freeze should be completed on both systems. | Freeze section. | Apply the change on source and Dedicated Instance. | [cite:1] |
| Go-live starts with the DHCP change and no case | The list starts with a proactive TAC ticket. | Cutover steps. | Open scheduled dispatch first. | [cite:1] |
| Success is declared from the reset command | The control is registration on the new system. | Verification sentence. | Count registered phones before bulk partition edits. | [cite:1] |
| Rollback is a DRS restore | The practice article says rollback mirrors the cutover. T5-R04 says DRS is not a change backout. | Both articles. | Reverse Option 150, resets, and partition edits. | [cite:1] |
| Unity is moved with the CER bulk sheet | Cobras is the Unity recommendation. CER is separate. | Freeze tool list. | Use the tool named for that application. | [cite:1] |
| Questionnaire submitted before the report is approved | Configuration stays disabled until approval. | Step 3. | Download and approve the source report first. | [cite:2] |
| Unreachable phones are discovered at reset | The assessment report already lists devices the Dedicated Instance cluster cannot reach. | Device IP connectivity. | Clear that list before migration. | [cite:3] |
| 911 is skipped because registration looks good | 911 is on the freeze list and the go-live list. | Test program. | Run it. A registration count does not replace it. | [cite:1] |
09 · Self-question ladder
Twelve rungs
L0What is the Dedicated Instance migration sequence?
Seven gates, ending in Transfer to Day 2. [cite:1]
L1Why does the assistant exist if it does not migrate?
It assesses readiness and compares clusters so a certified provider tool can do the move. [cite:2]
L2Which gates have no production impact?
Project Initiation, Discovery and Assessment, and Planning. [cite:1]
L2How long is freeze, and how long is cutover?
Freeze is a recommended 2–3 weeks. The assistant cutover window should not exceed ten hours. [cite:1] [cite:2]
L3How do you prove phones moved?
They are registered on Dedicated Instance. The assistant also has a post-registration report. [cite:1] [cite:2]
L3What DHCP change does the practice article name?
Option 150, then a reset from the on-premises call manager. [cite:1]
L4How is this different from the multi-tenant Unified CM tool?
That tool imports a tar and builds Webex Calling users. This assistant compares clusters and schedules a Dedicated Instance cutover. T6-R03 is the other tool. [cite:2]
L4Does the seven-gate article migrate a third-party PBX by itself?
It names third-party PBX as a source the method has covered. It does not print the object map. [cite:1]
L5Why is rollback not a restore?
The practice article says rollback mirrors the cutover steps and must finish inside the maintenance window. [cite:1]
L5What would you refuse to add to the test list?
A recorder cutover step these articles do not print. That stays TODO-verify. [cite:1]
L2Which Unity tool does the freeze section recommend?
Cobras. [cite:1]
L1When can you open the network questionnaire?
After Setup Assist approves the source readiness report and you agree. [cite:2]
10 · Lab
A paper lab. Do not click Ready to migrate on a customer org.
11 · Quiz
Twelve questions
How many gates does the practice article walk?
Answer
Seven. [cite:1]
Which gate has direct production impact?
Answer
Go Live. [cite:1]
Does the pre-migration assistant migrate the cluster?
Answer
No. [cite:2]
When is the assistant tile visible?
Answer
When Setup Assist is enabled along with Dedicated Instance. [cite:2]
What is the recommended freeze?
Answer
2–3 weeks. [cite:1]
What is the assistant’s cutover limit?
Answer
The window should not exceed ten hours. [cite:2]
A directory change is made only on the source during freeze. What does the article want?
Answer
Complete the required change on both systems. [cite:1]
Which DHCP option does go-live change?
Answer
Option 150, then a phone reset. [cite:1]
Which Unity tool does the freeze section recommend?
Answer
Cobras. [cite:1]
Registration is partial and the window is ending. What is rollback?
Answer
The mirror of the cutover procedure, inside the maintenance window. [cite:1]
Name the three reports available when the assistant status is complete.
Answer
DI-readiness check, post-migration comparison, and post-registration phones. [cite:2]
Which source platforms does the practice article’s scope sentence name?
Answer
BroadCloud, BroadWorks, Spark Calling, Unified CM, HCS, and third-party PBX. [cite:1]
12 · Audio
Slots for Studio
Transcript slot
Studio fills this. The prompt is the spoken outline, not a second article.
Transcript slot
Studio fills this. The prompt is the spoken outline, not a second article.
Transcript slot
Studio fills this. The prompt is the spoken outline, not a second article.
13 · Interview
Oral answers
30 seconds. Dedicated Instance migration is seven gates. Most of them do not touch production. Go-live does. The Control Hub assistant checks an on-premises Unified CM and schedules the window. A certified provider tool performs the migration.
2 minutes. Freeze is the recommended two to three weeks where data moves and you test failover. Changes during freeze hit both systems. Unified CM uses BAT. The article recommends Cobras for Unity and manual or bulk for Emergency Responder. Go-live opens a TAC ticket, changes Option 150, resets phones, and uses registration on Dedicated Instance as the progress count. Then you fix partitions, home cluster, gateways, and SRST. Tests include intra-site, inter-site, PSTN, MRA, 911, and voicemail. Rollback repeats those steps backwards before the window ends.
30 seconds, the two clocks. Do not call freeze a ten-hour change. Ten hours is the assistant’s cap on the cutover window. Freeze is the longer data-move phase.
2 minutes, scope. The practice article says the method has been used from a single seat to estates it describes as exceeding 100,000 seats, and from Unified CM, HCS, BroadWorks, BroadCloud, Spark Calling, and third-party PBX. That sentence is not a per-platform runbook. The assistant’s own steps are Unified CM to Dedicated Instance. Day 2 points at Tier 1, service requests, and the RACI.
What you will not say. You will not say the assistant moves the phones. You will not describe Yarnlab beyond the article’s example phrase. You will not add a recorder step these pages do not print.
14 · Citations
- Best practices in preparation and migration process to Webex Calling - Dedicated Instance — help.webex — article tf6kpq — help.webex.com article tf6kpq — retrieved 2026-10-14. The retrieved markdown did not print a header date. re-check Seven gates and the impact table. Roughly 95 percent preparation. Freeze 2–3 weeks. BAT, Yarnlab as an example, Cobras, CER bulk. Option 150 cutover and mirrored rollback. Source platforms include third-party PBX.
- Pre-migration assistant for Dedicated Instance using Setup Assist — help.webex — article r1ueuw — help.webex.com article r1ueuw — header October 22, 2025, retrieved 2026-10-14. The assistant does not migrate. Tile visibility. Four steps. Cutover window should not exceed ten hours. Reports after completion.
- Generate Assessment reports for Dedicated Instance migrations — help.webex — article 9jw4mab — help.webex.com article 9jw4mab — retrieved 2026-10-14. Source readiness, DI readiness, and post-migration validation. Device IP connectivity lists devices the selected Dedicated Instance cluster cannot reach.
- Dedicated Instance – customer deployment models — help.webex — article ny65x1bb — help.webex.com article ny65x1bb — retrieved 2026-10-14. Customers may migrate to Dedicated Instance first and then divide users. Group features stay on one call control. Detail is T5-R05.
15 · Re-engineer later
- Open questions: tf6kpq header date. What Yarnlab does beyond the example phrase. A Cisco-documented recorder cutover for this path.
- Facts still marked TODO-verify: a recorder migration step; an Avaya, Genesys, or Amazon Connect crosswalk.
- Facts still marked re-check: the practice article’s numeric framing, because the retrieval showed no header date.
- Assets missing: assistant screenshot, gate SVG export, audio.
- Next review: re-check the ten-hour sentence and the 2–3 week recommendation together so they are not merged.
Sources and go deeper
Checked links were opened this month. A confirm row has no address because that page was not opened.
- Wikipedia Webex (Wikipedia) last checked 2026-10
- Vendor doc Webex Help Center last checked 2026-10
- DevDocs Webex developer documentation last checked 2026-10
- DevDocs Webex developer getting started last checked 2026-10
- Community Webex community last checked 2026-10
- SRND Cisco Collaboration design zone last checked 2026-10
- RFC RFC 3261 SIP: Session Initiation Protocol last checked 2026-10
- Port table IANA service name and port number registry last checked 2026-10
- Port table Port reference for Webex Calling last checked 2026-10
- Release notes What's new in Webex Calling last checked 2026-10
- Vendor doc help.webex.com article tf6kpq last checked 2026-10
- Vendor doc help.webex.com article r1ueuw last checked 2026-10
- Vendor doc help.webex.com article 9jw4mab last checked 2026-10
- Vendor doc help.webex.com article ny65x1bb last checked 2026-10
sources.json for this page.