Teams Phone Migration
Replace your PBX or third-party VoIP service with Microsoft Teams Phone in four to six weeks. Number porting, auto-attendant and call queue design, hardware compatibility, cutover with a rollback plan that means we are not asking you to take it on faith.
Why most firms still pay twice for telephony.
Most mid-market firms still pay for a legacy PBX (on-premises hardware that needs maintenance) or a third-party VoIP service — RingCentral, 8x8, Vonage, Mitel Cloud, or one of the dozens of UK providers — alongside their Microsoft 365 licences. Teams Phone consolidates the cost and the experience. The Teams client your staff already use for chat, meetings, and collaboration becomes their phone too. The handset that has been on every desk for the past decade can be replaced by a USB headset, or kept as a Teams-certified phone if staff prefer.
The economics are usually clear. A 100-user firm paying £8 to £15 per user per month for a third-party VoIP is spending £9,600 to £18,000 a year on telephony Teams Phone could replace at a similar or lower marginal cost, with better integration and less friction. The migration is not free, but it usually pays back inside the first year.
What the migration covers.
Five workstreams that run in parallel across the engagement.
1
Number porting
UK porting from current carrier
Direct Routing or Calling Plans
Porting management end-to-end
Carrier-side coordination
2
Routing choice
Direct Routing economics
Microsoft Calling Plans fit
Hybrid scenarios
Sector-specific carrier picks
3
Call flow design
Auto-attendant scripts
Call queues by team
Out-of-hours routing
Multi-site design
4
User & hardware
Per-user provisioning
Hardware compatibility check
Teams Rooms (if relevant)
Adoption training
5
Cutover & rollback
Planned cutover slot
48-hour rollback option
Day-after standby
Soft launch pattern
Deliverables you can hold us to.
✓
Microsoft Teams Phone running across your business, numbers ported, users configured, call flows tested
✓
Documented call flow showing what happens when someone dials each of your numbers
✓
Number plan documenting which user has which number and how new numbers / leavers are handled
✓
Auto-attendant and call queue configuration aligned to your business hours and team structure
✓
Hardware recommendations and a refresh schedule for any incompatible kit
✓
User training material and a short adoption guide
✓
30 days of post-go-live support, including the day after cutover with us on standby
Mid-market firms running 30 to 500 staff on a legacy PBX, on a third-party VoIP service, or on a half-completed Teams Phone deployment that needs fixing. Especially valuable when the legacy contract is approaching renewal, the firm has consolidated through M&A and is running two telephony systems, staff complain about call quality, or the firm is moving to hybrid working and the office-based PBX no longer fits.
How it runs.
1
Discovery + design
Week 1. Map the current call flow, telephony patterns, existing hardware, and contracts. Design the new state and the cutover plan.
2
Porting + infrastructure
Weeks 2–3. Initiate number porting (slowest part of the engagement — typically 3–4 weeks of regulatory process). Set up Teams Phone infrastructure in test.
3
Config + pilot
Weeks 4–5. Configure each user; pilot with a small group for two to three days; refine based on what surfaces.
4
Cutover + bedding-in
Week 6. Cutover happens on a planned evening or weekend. Next morning we are on standby. Rollback option stays open for 48 hours.
The price band, and how it lands.
Up to 50 users, single site
£2,800
Calling Plans, straightforward routing
Up to 100 users
£4,500
Standard call flows, possibly Direct Routing
Up to 200 users, Direct Routing
£7,000
Carrier integration, complex queues
Up to 300 users, complex
£9,500
Multi-site, hardware refresh, Teams Rooms
Related work
Often paired with this accelerator.
Common questions.
Will we lose our phone numbers?
No. Numbers port from your current carrier to Microsoft (or to the Direct Routing carrier). The numbers stay the same. Porting takes three to four weeks of regulatory process, which is the gating factor on the overall timeline.
What about our existing handsets?
Teams Phone works with Teams-certified hardware (Poly, Yealink, Jabra, Logitech, EPOS), with USB headsets, and through the Teams mobile app. Existing handsets from a PBX typically do not work. We audit the hardware in discovery and tell you what works, what does not, and the refresh cost.
What happens if the cutover goes wrong?
The cutover plan includes a 48-hour rollback to the previous system. If something significant goes wrong on the day we can switch you back while we work out what happened. The rollback is rarely needed because the pilot week catches most issues, but it is there.
How does this compare to keeping our current VoIP provider?
For most mid-market firms Teams Phone is cheaper at the marginal cost per user, better integrated with the rest of M365, and simpler to administer. For firms with heavy contact-centre requirements, specialist providers (Genesys, Five9, Talkdesk) sometimes remain the right answer alongside Teams.
Do you support Microsoft Teams Rooms?
Yes. Teams Rooms is a common pairing with a Teams Phone migration. We can include conference room hardware setup at the upper end of the band.