00 · Header

T5 · Dedicated Instance

DI Migration Path

Gateway Dedicated Instance T5-R06 SitePeeringDedicated UCCalling
Illustrated scene for DI Migration Path. Original drawing, not a product screenshot.
Sequence · Site → Peering → Dedicated UC → Calling SitePeeringDedicated UCCalling 123
Color-coded sequence: Site → Peering → Dedicated UC → Calling. A packet moves along the arrows. Reduced motion keeps every step visible.

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.

Room T5-R06 Version v0.1 last-verified: TODO Difficulty L3 Est. time 90–110 min Prereq T5-R02 Reading 17 min

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]
Why it matters. People fail this move by treating the assistant as the migrator, by changing only one system during freeze, or by planning a cutover longer than ten hours in the scheduler.

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

Seven gates

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]

Impact table

No impact: initiation, discovery, planning. Minimum: implementation. Limited to operations processes: freeze. Direct: go live. [cite:1]

The assistant is not the migrator

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]

Two clocks

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

GateProduction impactWhat this pass can citeCite
Project Initiation, Discovery and Assessment, PlanningNo impactThe assistant’s readiness work sits in discovery. Configuration under Actions stays unavailable until Setup Assist approves the source readiness report.[cite:1] [cite:2]
ImplementationMinimumThe practice article points at activation, peering, directory sync, SSO, certificates, and intercluster integration in this phase. Peering rules stay in T5-R02.[cite:1]
FreezeLimited to operations processesMove 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 LiveDirectTAC 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 2The article points at operations documentsTier 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

SourceWhat the article recommendsCite
Unified CMActive 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]
UnityCisco Unity tools. The article recommends Cobras for Unity migrations.[cite:1]
Emergency ResponderManual, or bulk export and import.[cite:1]

Reports after the assistant’s schedule completes

ReportWhat it checksCite
Source readinessAssessment sheet, phone and gateway recommendation, credential policy, application users.[cite:2]
DI-readiness checkData for the Dedicated Instance cluster.[cite:2]
Post-migrationCompared data between source and Dedicated Instance clusters.[cite:2]
Post-registrationPhones registered to the Dedicated Instance cluster.[cite:2]
Device IP connectivityDevices 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

SitePeeringDedicated UCCalling This room
Mini map of the neighbors named on this room’s sequence. Orientation sketch, not a new product claim.

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

SisterWhat it isWhy it matters hereConfig touchpointTypical failureCite
Cloud-Connected UCThe 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 / SSONamed 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 calling911 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 / gatewaysTest 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 JabberFreeze 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]
TACGo-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 WFONot 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 splitAfter 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

FromToMechanismWhat movesCite
On-premises UCMControl Hub assistantCloud-Connected UCSource inventory and readiness, not the live cut.[cite:2]
Setup AssistSource reportMapping approvalAssessment, phone and gateway, credential policy, application users.[cite:2]
AdminNetwork questionnaireTrunk purpose and peering choiceTrunks prepopulated from the readiness report.[cite:2]
SchedulerDevice poolsFreeze dates and a cutover of at most ten hoursWhich pools register to Dedicated Instance.[cite:2]
DHCPPhonesOption 150TFTP of the Dedicated Instance cluster, after reset.[cite:1]
BATDedicated InstanceExport and importUnified CM configuration during freeze.[cite:1]
CobrasUnity ConnectionThe article’s Unity recommendationUnity migrations. Not CER. CER is manual or bulk.[cite:1]
Go-liveOn-premises UCMPartition and home-cluster bulk updateActive versus null partitions, advertisements.[cite:1]

Cross-platform bridges

This roomLegacyPeer orientationCite
Unified CM to Dedicated InstanceThe 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 toolsA 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 ConnectNot 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

SymptomLikely sister-system causeCheckFixCite
Assistant tile is absentSetup 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 greySetup 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 clusterOption 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 cutoverThe 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

StepFromToMechanismNotesCite
1AdminAssistantPrerequisitesDedicated Instance subscription, Cloud-Connected UC, deployment insights. Check the box. Ready to migrate.[cite:2]
2Setup AssistReportCluster mappingSource status moves to In Progress, then Download report after approval.[cite:2]
3AdminQuestionnaireTrunk purpose and peeringI agree, then submit. Status is In Review until Setup Assist approves.[cite:2]
4AdminScheduleFreeze and cutoverDestination region and source cluster. Cutover not more than ten hours.[cite:2]
5Data moveDedicated InstanceBAT, Cobras, or CER bulkDuring the recommended 2–3 week freeze. MACD on both systems.[cite:1]
6DHCPPhonesOption 150 and resetAfter a proactive TAC ticket.[cite:1]
7AdminBoth clustersBulk updateLines and route patterns, active versus null partitions, home cluster, advertisements. Gateways, SRST, hardware media.[cite:1]
8Test programRollback decisionListed callsIntra-site, inter-site, PSTN, MRA, 911, voicemail, applicable features. Rollback mirrors the procedure.[cite:1]

06 · Config

Scheduler clicks, then the cutover list

  1. Sign in to Control Hub. Open Services → Updates and Migration. Get Started on Pre-Migration Assistant for Dedicated Instance. [cite:2]
  2. Confirm the subscription, Cloud-Connected UC, and deployment insights. Select the prerequisites checkbox. Click Ready to migrate. [cite:2]
  3. 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]
  4. 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]
  5. 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]
  6. On go-live, open the proactive TAC ticket, change Option 150, reset, count registrations, then bulk-update partitions and home cluster. [cite:1]
  7. 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]
  8. 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

ItemValueSourceVerified?
Gates7[cite:1]Named in the article. Header date not in the retrieved markdown. re-check
Preparation versus changeRoughly 95 percent and 5 percent[cite:1]Quoted as the article’s framing. re-check
Freeze2–3 weeks recommended[cite:1]A recommendation. re-check
Cutover window in the assistantShould not exceed ten hours[cite:2]Quoted. Header October 22, 2025.
Scale the practice article claimsFrom 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 migrationNo[cite:2]Quoted
Source platforms namedBroadCloud, BroadWorks, Spark Calling, Unified CM, HCS, third-party PBX[cite:1]Quoted. No per-platform procedure in that sentence.

08 · Troubleshooting

Ten migration failures

SymptomLikely causeEvidenceFixCite
The team expects the assistant to move phonesThe 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 schedulerThe 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 clusterMACD 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 caseThe list starts with a proactive TAC ticket.Cutover steps.Open scheduled dispatch first.[cite:1]
Success is declared from the reset commandThe control is registration on the new system.Verification sentence.Count registered phones before bulk partition edits.[cite:1]
Rollback is a DRS restoreThe 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 sheetCobras 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 approvedConfiguration stays disabled until approval.Step 3.Download and approve the source report first.[cite:2]
Unreachable phones are discovered at resetThe 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 good911 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

Q1MCQ

How many gates does the practice article walk?

Answer

Seven. [cite:1]

Q2MCQ

Which gate has direct production impact?

Answer

Go Live. [cite:1]

Q3MCQ

Does the pre-migration assistant migrate the cluster?

Answer

No. [cite:2]

Q4MCQ

When is the assistant tile visible?

Answer

When Setup Assist is enabled along with Dedicated Instance. [cite:2]

Q5MCQ

What is the recommended freeze?

Answer

2–3 weeks. [cite:1]

Q6MCQ

What is the assistant’s cutover limit?

Answer

The window should not exceed ten hours. [cite:2]

Q7Scenario

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]

Q8MCQ

Which DHCP option does go-live change?

Answer

Option 150, then a phone reset. [cite:1]

Q9MCQ

Which Unity tool does the freeze section recommend?

Answer

Cobras. [cite:1]

Q10Scenario

Registration is partial and the window is ending. What is rollback?

Answer

The mirror of the cutover procedure, inside the maintenance window. [cite:1]

Q11Draw

Name the three reports available when the assistant status is complete.

Answer

DI-readiness check, post-migration comparison, and post-registration phones. [cite:2]

Q12MCQ

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.

sources.json for this page.