Voice is often the last workload organizations move into Microsoft Teams. It’s also the one that causes the most disruption if handled casually.
A Teams Voice migration impacts call routing, phone numbers, emergency dialing, hardware, licensing, and network performance. It touches every department. If something fails, everyone notices.
Many IT teams focus on enabling the Teams Phone license first. The real work starts earlier, documenting calling features, auditing DIDs, deciding on PSTN connectivity, validating device compatibility, and confirming network readiness.
This checklist is built for IT leaders planning the move from legacy PBX or existing VoIP systems to Teams Phone.
It outlines the critical decisions that shape cost, user experience, and long-term scalability.
Before you port a single number, make sure these foundations are in place.
The Need for Teams Voice Migration
Organizations rely on voice for daily operations, but legacy phone systems create friction…
Teams Voice brings calling directly into Microsoft Teams, integrating calls with chat, meetings, and collaboration tools.
Key reasons to migrate:
- Seamless Calling Inside Teams: Users can make, receive, and transfer calls without leaving the Teams app, reducing context switching.
- Feature Alignment: Auto attendants, call queues, shared lines, and emergency dialing are managed centrally, making workflows consistent and easier to update.
- Flexible PSTN Connectivity: Teams supports Microsoft Calling Plans, Direct Routing, or Operator Connect, letting organizations choose the most cost-effective and reliable method.
- Device Optimization: Teams-certified phones, softphones, and headsets are supported natively, improving call quality and user experience.
- Centralized Management and Reporting: IT gains visibility over usage, call quality, and compliance from a single Teams admin portal.
Migrating to Teams Voice ensures calls are fully integrated into your collaboration environment and provides a scalable foundation for hybrid work and future growth.
We’ll dive into all pre-migration points in detail, explaining what matters and how IT leaders can plan a smooth Teams Voice migration.
1. Define Required Calling Features Before Migration
Before touching licenses or porting numbers, document how your current phone system actually works.
Start with auto attendants.
Map out call flows, business hours, after-hours routing, and holiday schedules. Include operator options to ensure callers can reach a live agent when needed. Identify which menus must remain and which can be simplified.
Next, review call queues and hunt groups.
Which departments rely on them?
How are calls distributed today? Round robin, longest idle, or simultaneous ring? Who monitors performance?
Then evaluate shared calling scenarios. Reception desks, executive assistants, and support teams, these setups need structured configuration inside Teams. They should not be improvised during deployment.
Emergency dialing is non-negotiable. Confirm how location-based routing will work. Remote users, branch offices, hybrid environments, each scenario requires accurate emergency address mapping.
Do not assume Teams will “replicate everything automatically.”
Document the current state. Identify gaps. Decide what to keep, improve, or retire. Migration becomes smoother when architecture decisions are made upfront instead of during cutover.
2. Audit Phone Numbers and Plan Porting Strategy
Phone numbers are a business identity. Mishandling them creates immediate disruption.
Break this phase into controlled steps.
Create a Complete DID Inventory
List every active number:
- User-assigned DIDs
- Toll-free numbers
- Main reception numbers
- Department lines
- Unused or legacy numbers
Validate ownership with your current carrier. Confirm which numbers are still under contract. Remove numbers that are no longer required before migration begins.
A clean inventory reduces porting delays and ongoing costs.
Review Carrier Contracts and Porting Timelines
Porting is not instant.
Check:
- Contract end dates
- Notice periods
- Porting documentation requirements
- Regulatory constraints (especially for multi-region organizations)
Align migration timelines with carrier release schedules. Avoid overlapping billing cycles where possible.
Plan the Porting Approach
Decide how numbers will move:
- Full cutover in one phase
- Department-by-department migration
- Pilot-first rollout
Test with a small group before porting high-visibility numbers like reception or support.
Number porting is operationally sensitive. Treat it as a structured transition, not an administrative task.
Validate Post-Port Configuration
After porting:
- Confirm inbound and outbound routing
- Test auto attendants and queues
- Validate emergency dialing
- Monitor call quality
Do not assume success after a confirmation email from the carrier. Validate in production conditions.
When number management is planned properly, migration feels controlled. When it’s rushed, recovery becomes reactive.
3. Define Your Device Strategy Early
Voice migration has an impact on how users physically make and receive calls.
Clarify the device model before rollout.
Desk Phones vs. Headsets
Decide how users will operate inside Teams:
Teams-Certified Desk Phones
- Familiar experience for traditional office users
- Suitable for reception desks and shared spaces
- Higher upfront hardware cost
Softphone + Headset (Teams App)
- Ideal for remote and hybrid users
- Lower hardware investment
- Easier to scale
User role should drive this decision. Executives, call handlers, and mobile staff may require different setups.
Check Compatibility of Existing Phones
If the organization already has IP phones, verify:
- Are they Microsoft Teams certified?
- Can firmware be upgraded?
- Do they support native Teams or only SIP gateway integration?
Not all legacy phones transition smoothly. Unsupported devices increase support overhead and reduce call quality consistency.
Budget and Lifecycle Planning
Hardware replacement is often underestimated in migration budgets.
Plan for:
- Replacement cycles
- Warranty coverage
- Device management policies
- Spare units for critical teams
Device decisions influence adoption and user satisfaction. Finalize this strategy before enabling voice licenses at scale.
Take the guesswork out of your Teams Voice migration and ensure every detail is covered.
4. Choose the Right PSTN Connectivity Model
Teams Phone still needs a path to the public telephone network. That decision affects cost and operational complexity.
There are three primary models to evaluate.
Microsoft Calling Plan (Pay-As-You-Go)
Microsoft acts as the carrier, offering several calling plan options:
- Microsoft Domestic;
- Microsoft Domestic + International;
- Microsoft Calling Plan (Pay-As-You-Go).
Pay-As-You-Go works well for small to mid-sized deployments and reduces infrastructure management, as there’s no need for an on-premises SBC.
Direct Routing
Direct Routing connects Teams to your chosen telecom provider through a Session Border Controller (SBC).
It fits scenarios where:
- You must retain an existing carrier
- You operate in regions not fully supported by Microsoft Calling Plans
- You require advanced routing customization
This model offers flexibility but increases architectural responsibility.
Operator Connect
Operator Connect sits between the two models.
Approved carriers integrate directly with Microsoft, simplifying provisioning while keeping your telecom provider involved.
It reduces technical overhead compared to Direct Routing, but still depends on regional carrier availability.
The right PSTN model depends on geography, compliance needs, cost structure, and internal expertise.
Make this decision early. It shapes architecture, licensing, and migration sequencing.
5. Align Licensing With User Requirements
Licensing decisions directly affect cost control. Over-licensing inflates budget. Under-licensing limits functionality.
Start by segmenting users based on how they actually use voice.
Identify User Profiles
Not every employee needs the same configuration.
Consider grouping users into categories:
- Full voice users who require inbound and outbound calling
- Departmental call handlers working within queues
- Executives with dedicated numbers
- Limited users who only need outbound capability
- Shared device users in common areas
Map features to roles before assigning licenses.
Understand Teams Phone Licensing Options
Review what is already included in your Microsoft 365 plans.
- Some enterprise plans include Teams Phone capability
- Others require the Teams Phone add-on
- Calling Plans may be additional depending on your PSTN model
Avoid assigning identical licenses across the board. Align features with function.
Plan for Scalability
Consider:
- Seasonal staffing changes
- Expansion into new regions
- Future call center requirements
Licensing should support growth without requiring redesign.
A structured licensing approach keeps costs predictable and ensures each user receives the correct level of voice capability.
6. Prepare the Network for Voice Traffic
Voice performance depends on network stability. If the network is weak, the user experience will suffer regardless of configuration.
Start with a structured assessment.
Evaluate Bandwidth and Latency
Measure:
- Available bandwidth per site
- Average and peak usage
- Latency between users and Microsoft services
- Packet loss and jitter
Voice traffic is sensitive to delay and instability. Baseline current performance before adding Teams calling at scale.
Configure Quality of Service (QoS)
Prioritize real-time traffic across:
- LAN
- WAN
- VPN connections
Without QoS, voice packets compete with general data traffic. That leads to inconsistent call quality.
Review Firewall and Microsoft Service Connectivity
Confirm that required Microsoft endpoints are accessible.
Inspect:
- Firewall rules
- NAT configurations
- Proxy settings
Misconfigured security appliances are a common source of audio issues.
Test Before Full Deployment
Run pilot deployments across different locations.
Monitor call analytics. Validate call quality metrics under real working conditions.
Network readiness determines whether migration feels stable or disruptive. Treat it as infrastructure validation, not a post-deployment fix.
7. Plan the Migration Rollout and Cutover Strategy
Enabling Teams Voice across the entire organization in one move increases risk. A phased approach reduces disruption and gives IT space to correct issues early.
Start with a controlled pilot.
Run a Pilot Deployment
Select users from different roles and locations:
- Office-based staff
- Remote users
- Call queue agents
- Leadership
Validate:
- Inbound and outbound calling
- Auto attendant routing
- Call queue behavior
- Device performance
- Emergency dialing accuracy
Collect feedback. Adjust configurations before wider rollout.
Decide on Phased vs. Full Cutover
Two common approaches:
- Phased migration: Department-by-department or site-by-site
- Full cutover: All users migrated within a defined window
Phased rollout lowers operational pressure. Full cutover may be required when retiring legacy PBX contracts.
Choose based on business tolerance for change and technical complexity.
Prepare Users Before Go-Live
Provide:
- Clear communication timelines
- Quick reference guides
- Device setup instructions
- Support contact details
Voice is a daily-use tool. Users must feel confident on day one.
Establish Post-Go-Live Support
Monitor:
- Call quality dashboards
- Support tickets
- Number routing issues
Have a rapid response process during the first weeks after migration.
Execution determines perception. A structured rollout prevents unnecessary escalation and protects business continuity.
8. Common Migration Risks to Avoid
Teams Voice migration is straightforward only if the planning checklist is followed. Ignoring critical steps leads to service disruptions and frustrated users.
Skipping Feature Documentation
Assuming Teams will replicate existing PBX features without a review is risky. Missing auto attendants, call queues, or shared lines creates immediate operational gaps.
Ignoring Number Inventory
Untracked numbers or outdated carrier contracts can delay porting or leave important lines inactive. Every number should be accounted for and tested.
Overlooking Device Compatibility
Legacy desk phones that aren’t Teams-certified cause poor call quality and increased IT support tickets. Verify hardware before deployment.
Misaligned PSTN or Licensing Decisions
Choosing the wrong PSTN model or license type inflates costs or limits functionality. Align decisions with user profiles and budget.
Neglecting Network Readiness
Voice traffic is sensitive. Insufficient bandwidth, high latency, or missing QoS configurations result in poor audio, dropped calls, and user frustration.
Following this checklist prevents reactive firefighting and ensures a smoother migration with predictable costs and user satisfaction.
The Final Word
Teams Voice migration is more than turning on a license. It touches calling features, phone numbers, devices, PSTN connectivity, licensing, and network infrastructure.
A structured approach prevents disruption, controls costs, and improves adoption.
Start by documenting current features, auditing numbers, defining devices, selecting the right PSTN model, aligning licenses, and validating network readiness.
Pilot carefully, roll out in phases, and monitor performance post-migration. When these foundations are in place, moving to Teams Voice becomes predictable, manageable, and scalable.
This checklist ensures IT leaders cover all critical decisions before making the switch.
WME Teams Voice Services
WME helps organizations plan, deploy, and optimize Microsoft Teams Voice with minimal disruption. Our approach covers the full migration lifecycle, from initial assessment to post-go-live support.
Assessment & Planning
- Feature mapping and call flow analysis
- Number inventory and PSTN strategy
- Device evaluation and network readiness
Deployment & Integration
- License assignment and provisioning
- Auto attendants, call queues, and shared line setup
- Teams-certified device rollout
Post-Migration Support
- Call quality monitoring and troubleshooting
- User adoption training and guides
- Ongoing optimization for scalability and cost efficiency
With WME, Teams Voice migration is structured and aligned with business needs. Our team ensures a smooth transition while maintaining high call quality and user satisfaction.
Don’t navigate Teams Voice migration alone. Get expert guidance tailored to your business.
