Cisco Unified Communications Manager (CUCM) is one of the most widely deployed enterprise PBX platforms in the world. If you're running it, you're in good company — and you're facing the same question every CUCM enterprise eventually faces: when do we move to Teams?

Cisco recommends migrating to cloud-based solutions. Your users already have Teams on their desktops. The economics favor consolidation. But the migration from CUCM to Teams is an engineering project — not a license swap.

This guide covers everything involved in migrating from Cisco CUCM to Microsoft Teams Phone with Direct Routing.

Why Cisco Enterprises Are Migrating to Teams

Three drivers:

1. Consolidation. Most Cisco enterprises already have Microsoft 365. Running voice on CUCM means maintaining two collaboration platforms — Cisco for voice, Microsoft for everything else. Moving voice to Teams eliminates a platform, a vendor relationship, and an infrastructure stack.

2. Cisco's cloud direction. Cisco's strategic investment is in Webex Calling, not CUCM. While CUCM is still supported, the product roadmap favors cloud. Enterprises reading the strategic tea leaves are moving to the platform that's getting investment — and if they're already on Microsoft 365, that platform is Teams.

3. Cost. CUCM licensing, Cisco UC infrastructure (IM&P, Unity Connection, Cisco Unity, Expressway), and the hardware to run it on represent significant ongoing costs. Teams Phone with Direct Routing can reduce total voice TCO by 40–60% compared to maintaining a full Cisco UC stack.

CUCM-to-Teams Migration: What's Involved

Dial-plan translation. CUCM uses route patterns, route groups, route lists, and translation rules for call routing. Teams uses voice routing policies with number patterns and PSTN usages. Every CUCM route pattern needs to be mapped to a Teams voice route. Translation rules (digit manipulation, number normalization) need to be replicated in Teams dial plans or SBC-level digit manipulation.

SCCP → SIP protocol translation. Many Cisco endpoints use SCCP (Skinny Client Control Protocol), not SIP. If you're keeping any Cisco endpoints during a transition period, your SBC needs to handle SCCP-to-SIP translation. For endpoints that are being replaced by Teams clients, this isn't an issue — but for lobby phones, conference room phones, or analog devices behind Cisco ATAs, it matters.

Directory synchronization. CUCM uses Cisco Unified Communications Directory (or LDAP integration with Active Directory). Teams uses Entra ID (formerly Azure AD). If your CUCM is already synced to AD, the directory migration is straightforward — users are already in Entra ID. If not, you need to ensure directory alignment.

Voicemail migration. Cisco Unity Connection voicemail needs to be migrated to Teams Voicemail (Exchange Unified Messaging or Microsoft Cloud Voicemail). Greetings, messages, and routing rules should be mapped. Some messages can be exported via IMAP; some cannot. Set user expectations about voicemail migration.

Hunt groups and call queues. CUCM hunt groups map to Teams call queues. Auto attendants map to Teams auto attendants. The configuration is different but the concepts translate. This is a design exercise — map every CUCM hunt group and auto attendant to its Teams equivalent.

SBC as the Bridge

During and after migration, your SBC is the bridge between any remaining Cisco infrastructure and Teams. Two approaches:

Cisco CUBE as a transitional gateway. If you have Cisco CUBE (Cisco Unified Border Element), you can use it as a SIP gateway between CUCM and Teams during the migration period. This allows users on CUCM to call users on Teams (and vice versa) during the phased migration. CUBE handles the SIP normalization between Cisco's SIP dialect and Teams' SIP requirements.

Dedicated SBC (AudioCodes or Ribbon) as the permanent bridge. For the long term, a Microsoft-certified SBC is the right architecture. CUBE is a Cisco product; if you're migrating away from Cisco, it doesn't make sense to depend on it long-term. Deploy AudioCodes or Ribbon as your Direct Routing SBC, and use it for both the transition period and the final state.

Analog and Specialty Device Integration

Cisco environments often have analog devices connected through Cisco Analog Telephone Adapters (ATAs) or VG series voice gateways. These need to be migrated to ATAs connected to your new SBC.

Cisco analog gateways → ATA through SBC. If you're using Cisco VG224 or VG350 analog gateways, those devices need to be replaced with AudioCodes MP-1xx ATAs (or equivalent) connected to your new SBC. The analog devices (elevator phones, paging, fax) move from the Cisco gateway to the new ATA.

H.323 devices. If you have H.323 endpoints (video conferencing systems, older IP phones), they may need to connect through the SBC for protocol translation (H.323 → SIP) during the transition period.

The Phased Approach

Phase 1: Discovery (2–3 weeks). Audit your CUCM configuration: route patterns, translation rules, hunt groups, auto attendants, voicemail, analog devices, E911 setup. Map every call flow. Document every analog line.

Phase 2: Design (3–4 weeks). Design the Teams Direct Routing architecture: SBC deployment, SIP trunk configuration, voice routing policies, dial plans, call queues, auto attendants, E911 routing. Design the analog integration plan. Build the lab environment.

Phase 3: Pilot (2–3 weeks). Migrate a single department or site. Test every call path: internal, external, emergency, analog, voicemail, hunt groups. Validate E911. Fix issues.

Phase 4: Production (2–4 weeks). Migrate remaining users in waves — site by site or department by department. CUCM stays running in parallel for rollback capability. Once all users are migrated, decommission CUCM.

Phase 5: Hypercare (2–4 weeks). Post-cutover monitoring, issue resolution, optimization. Transition to managed SLA support.

Common Challenges

Feature parity gaps. Not every CUCM feature has a direct Teams equivalent. Some advanced call center features, hunt group configurations, or shared-line appearances may work differently in Teams. Identify these gaps during discovery and plan workarounds before cutover.

Contact center migration. If you're running Cisco Unified Contact Center (UCCX or UCCE), that's a separate migration workstream from voice. Teams has its own contact center ecosystem (certified partners like Genesys, NICE inContact, Five9). Plan the contact center migration separately.

Complex route patterns. CUCM environments that have grown over years often have route patterns and translation rules that are poorly documented and partially redundant. The discovery phase is critical — don't skip it.

Cutover without parallel running. The temptation to cut over all at once is real. Don't. Phased migration with CUCM running in parallel gives you rollback capability and a safety net. Once you're confident, decommission CUCM.

Get your Cisco migration assessment — we'll audit your CUCM environment, map the migration path, and show you the timeline and ROI.