Microsoft Cloud guide

Microsoft Teams Phone: Complete Migration Guide

January 10, 2025 · 8 min read · Big Sky Dynamics

Step-by-step guide to migrating from legacy phone systems

Email me the PDF More free guides

Inventory before anything else

You cannot port what you cannot describe. Build a register of every number, its owner, its site, its device, its contract term and whether it is used for fax, alarm, elevator or other non-human traffic. Those last categories are where migrations actually fail, because they were never in the phone book.

Map call flows as well: main lines, hunt groups, auto attendants, queues, shared lines, and the two or three processes that quietly depend on a specific extension.

Choose the calling model

• Microsoft Teams Phone with Microsoft-provided calling plans: simplest operationally, fits organizations that want one supplier.
• Direct Routing with your carrier: keeps an existing contract or SBC and gives control over numbering and compliance.
• Operator Connect: carrier-managed numbers into Teams, a middle path that avoids running an SBC.

Numbers, dial plans and emergency calling

Confirm which numbers can port and the lead time per carrier. Build the normalization rules early: users dial ten, eleven and international formats interchangeably, and a missing rule shows up as a failed call, not a configuration error.

Emergency calling must be designed per site with verified addresses and a test plan. Review which devices can be moved between locations and how the address is updated; this is a compliance item, not a configuration checkbox.

Pilot and cutover

Pilot one site or one department for at least two weeks, including a reception or queue user, because shared-line and transfer behavior is where user expectations are most specific. Measure call quality, dropped calls and time-to-answer before and after.

Cut over in site-sized waves with a documented rollback: keep the legacy path active until the wave has completed a full business day, and port numbers only after the Teams side answers correctly.

Devices and the physical world

Inventory handsets, conference rooms, door phones and overhead paging separately. Not every legacy device has a Teams-native replacement that fits the same cabling and power. Budget for adapters or replacement rather than assuming a firmware update will do it.

Test the experience in a real conference room, not just on a laptop, and include a support path for users whose handset behaves differently on day one.

After cutover

The migration is not finished at cutover. Review call quality dashboards weekly for a month, check that voicemail and auto attendant usage matches the design, and retire the legacy system on a dated plan. Keep a small exception process for numbers discovered late, because there are always a few.