Source note · CUCM to Teams Phone migration
Microsoft's Direct Routing documentation set defines no import path for an existing PBX dial plan and instead has the administrator rebuild routing as tenant dial plans, PSTN usages, voice routes and trunk translation rules; the only documented import is a Skype for Business Server dial plan exported to XML and recreated with New-CsTenantDialPlan.
inferred · Checked 2026-09-21
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- migration
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-21
- Status
- inferred
- Checked
- 2026-09-21
Sources
- Create and manage dial plans — Microsoft · tier 2 current vendor documentation · Using PowerShell > Using a PowerShell script, final script importing OPDP1
Cite this note
APA
WarmTransfer. (2026, September 21). CUCM to Teams Phone migration: source note cucm-to-teams-phone-migration-no-microsoft-tool. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-migration-no-microsoft-tool
BibTeX
@misc{warmtransfer-claim-cucm-to-teams-phone-migration-no-microsoft-tool,
title = {CUCM to Teams Phone migration: source note cucm-to-teams-phone-migration-no-microsoft-tool},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-migration-no-microsoft-tool},
note = {Source note cucm-to-teams-phone-migration-no-microsoft-tool, checked 2026-09-21}
}