The best UCaaS platform for migrating off a legacy PBX
Zoom Phone wins for PBX and carrier coexistence if the order confirms SBC setup, survivability, devices, porting and 911 responsibilities.
Zoom's migration guidance describes a transitional setup in which the cloud phone system and the on-premises PBX each resolve extensions on the other, and in its example a user keeps the same extension after moving to Zoom. That is why we crown Zoom Phone for an organization whose priority is extension dialing between its existing PBX and its migrated users while it keeps its carrier through a phased cutover, provided the order confirms the PBX and session border controller (SBC) configuration, the local survivability design, device compatibility, and who owns number porting and 911.
Cisco Webex Calling is the better pick for an estate already on Cisco Unified CM. Cisco documents converting eligible Cisco desk phones to Webex Calling firmware and a Survivability Gateway that listed Cisco endpoints register to when a site loses its connection to Webex, with outside calls dependent on a local PSTN circuit or trunk. Microsoft Teams Phone is the better pick where a qualifying Microsoft 365 E5 combination already includes the Phone System application and the phones on the desks appear on Microsoft's SIP Gateway device list.
What should a buyer leaving a legacy PBX weigh in a UCaaS platform?
Tarrant County, Texas, kept its incumbent vendors responsible for the existing phone environment until its migration finished while numbers moved in stages, and its 2018 UCaaS procurement asked bidders to explain how the dial plan would behave while some locations were still unconverted. A phased cutover leaves part of the staff on the PBX and part on the new platform, so the documented way a platform routes extensions and carrier calls between the two decides whether colleagues can keep dialing each other the same way during the overlap.
The FCC requires interconnected VoIP providers to tell customers what limits E911, broadband failure and loss of electrical power included. A cloud call-control outage and a carrier outage are further, separate failures, and a survivability device at the site covers only the ones it was designed for. Ask what keeps working at each site under each failure, and write an acceptance test for every case you need.
Kalispell, Montana, kept some analog services for fire-alarm and security panels in its UCaaS scope. Support for an analog phone on an adapter does not establish approval for an elevator phone or an alarm panel, so inventory each fax, paging, elevator and alarm line by location. Have the equipment owner and the relevant authority approve the exact replacement and how it behaves on backup power and during a network outage.
Federal number-porting rules set an interval of one business day for a simple port request and four business days for a non-simple one, and the same rule allows a longer requested interval. The port is one workstream inside the cutover, and each vendor's published range is an estimate that turns on the losing carrier. For 911, FCC rules assign E911 delivery to interconnected VoIP providers and direct dialing, on-site notification and dispatchable location to those who install, manage and operate a multi-line system, so the order should name who updates each site's location data and who tests each route.
Kalispell told bidders in an addendum that its existing phones would be reused. Reuse depends on the exact model, firmware and license of each handset, so the inventory comes before any comparison of vendors. A named migration is evidence for its own source system and scope, which makes the system the customer was leaving the first thing to check in any case study.
Zoom Phone, Webex Calling and Teams Phone during a phased cutover
| Zoom Phone | Cisco Webex Calling | Microsoft Teams Phone | |
|---|---|---|---|
| Route beside the PBX and the current carrier | BYOC-P for the carrier and BYOP-P for PBX extension dialing, through an SBC the customer runs | Premises-based PSTN through a Local Gateway, with trunks and dial plans toward the PBX | Direct Routing through a certified SBC placed between Teams, the carrier and the PBX |
| Site survivability | Local Survivability module on Zoom Node at the site; PSTN calls need an SBC and route groups | Survivability Gateway on a Cisco IOS XE router; third-party devices not supported; outside calls need a local circuit or trunk | Survivable Branch Appliance on Direct Routing sites; location not shared on emergency calls in that mode |
| Analog devices | Listed FXS adapters from AudioCodes, Cisco, Grandstream and Poly; fax described as best effort | ATA 191 and 192 and VG400, VG410 and VG420 gateways for analog phones, fax and overhead paging | Adapter supported by the SBC vendor on Direct Routing; no fax through Phone System or Calling Plan licenses |
| Published porting estimate | 4 to 21 days for orders of 99 numbers or fewer in North America | 1 to 35 business days to the earliest requestable date on Cisco Calling Plans | 7 to 14 days, up to 30, for Calling Plan ports in the US and Canada |
| 911 location tooling | Administrator-defined locations mapped to IP ranges and wireless access points; nomadic E911 in the US and Canada | RedSky account with an administrator-built wiremap; US, its territories and Canada | Emergency addresses matched to network identifiers; Direct Routing adds an emergency routing provider or ELIN |
| Desk phone reuse | Certified models and firmware from Poly, Yealink, Cisco, AudioCodes and Grandstream; used phones need a factory reset | 7800 and 8800 series converted to multiplatform firmware in Control Hub | SIP Gateway device list: Cisco multiplatform, Poly, Yealink and AudioCodes phones |
| Named migration | Gilead Sciences: staged BYOC deployment, seven sites | Brinks: from its own Cisco Unified CM, more than 4,000 users | Deutsche Bank: more than 130,000 workers provisioned |
Zoom Phone: one extension plan across the old PBX and the new system
BYOC-P, in Zoom's support pages, brings the existing carrier in through an SBC that the customer runs on its own premises, and BYOP-P joins the PBX and Zoom Phone for extension dialing. Zoom's dial plan article requires BYOC-P to be enabled on the SIP trunks before BYOP-P. One existing premises SBC can serve both, and the customer configures a dial plan that accounts for the PBX and Zoom Phone. The listed prerequisites include a customer-administered SBC with public SIP connectivity and a PBX with a logical connection to an SBC. Once the move is complete, the migration guidance says the old system can be decommissioned or put on standby.
A carrier-provided number assigned to a Zoom Phone user requires a Zoom Phone Pro license in the dial plan article, and Zoom's license overview puts desk phone registration and outbound PSTN calling in the licensed tier, with Common Area licenses for shared devices and analog ports. The certified hardware page lists SBC models and firmware by manufacturer. Have the order confirm that your PBX works with your SBC model and firmware under the proposed dial plan, and ask for the Zoom Phone and Zoom Node licenses, the carrier charges and the migration work as separate lines in the quote.
Zoom Phone Local Survivability runs as a module on Zoom Node, an on-premises appliance, and Zoom's survivability article says supported phones and clients register to it locally when Zoom Phone data centers are unreachable. One module can serve several buildings on the same Phone System Site while the campus network between them stays up, and a location whose campus link can fail gets its own module. Calls to and from the PSTN in that state need an SBC and route groups configured for the site. Zoom calls the result a reduced feature set, and a call in progress on the cloud has to be re-established after failover.
During an internet outage, calls to Zoom-provided numbers can be forwarded to BYOC numbers through the survivability SBC under a rule that is disabled by default. An administrator enables it during the outage, and the account's main company number is excluded. Zoom also requires the local internet path and the PSTN service to use separate network infrastructure, since a shared local loop can take both down. The SBC setup guide lists Zoom Phone and Zoom Node subscriptions among the survivability prerequisites.
The certified hardware page lists analog adapters from AudioCodes, Cisco, Grandstream and Poly by model and firmware, and it states that Zoom does not guarantee the performance of analog devices or applications connected to an adapter. Its paging entries are IP devices from Algo and CyberData. Zoom's fax article describes fax over VoIP as best effort and advises a business that routinely sends large, multi-page faxes to keep an analog line and a traditional fax machine.
Orders of 99 numbers or fewer take 4 to 21 days in North America, according to Zoom's porting instructions, which present the range as an estimate and confirm a firm date after the losing provider agrees. The existing carrier service has to stay active during the port, and Zoom does not cancel it afterward. For 911, an administrator defines locations with street addresses and maps them to network IP ranges and wireless access points, and a location a user reports becomes active only after an administrator approves it. A BYOC account also needs emergency call routing configured toward its carrier, and the license overview limits nomadic E911 to the US and Canada.
Zoom's phone provisioning page names Poly, Yealink, Cisco, AudioCodes and Grandstream device families, and a used phone has to be added to the Zoom portal and reset to factory settings before it provisions. Cisco support on the certified hardware page is limited to multiplatform phones, and Yealink phones made before 2019 fail the current provisioning requirements.
Gilead Sciences kept a staged BYOC approach because acquisitions had left it with multiple PBXs, TechTarget reported on June 10, 2021, in an account of Zoom Phone at seven sites across North America, central Europe and Australia. At one acquired site with three PBXs, the team split users between Zoom Phone and the legacy systems. Zoom's own BNSF Railway story says the railroad replaced an on-premises Skype for Business phone service across more than 10,000 phones, in seven months against a twelve-month budget.
An IT specialist at the West Virginia Conference of the United Methodist Church, an organization of 11 to 50 employees, wrote in a TrustRadius review dated September 3, 2025, that the first number port and office setup needed repeated corrections and clearer instructions. The same review, which TrustRadius tags as incentivized, describes phone service that moved in fall 2024 and then spread from the main office to other offices through number ports.
Cisco Webex Calling: Cisco phones converted and kept registered at the site
Each Webex Calling location takes either a cloud PSTN or premises-based PSTN through a Local Gateway, and Cisco's trunk and dial plan article presents the premises option as the route for keeping the current PSTN provider. Cloud PSTN serves Webex Calling users only, so a site that keeps its carrier for PBX users and cloud users alike is set to premises-based PSTN. The same trunks connect Webex Calling to premises PBXs. The location-level routing setting covers dialed strings of 2 to 10 digits and sends unknown extensions to a premises trunk or route group.
Registration-based trunks work only with Cisco's own CUBE border controller, and certificate-based trunks accept SBC models from Oracle, AudioCodes, Ribbon, anynode and Italtel, per Cisco's Local Gateway introduction. Its prerequisites include a license to operate the SBC and a premises PBX already set up to work with Webex Calling. Cisco's worked configuration is written for a CUBE gateway and has a separate section for an existing Unified CM, so a buyer whose PBX comes from another maker should have Cisco confirm the gateway design for that system before signing.
The Survivability Gateway is a Cisco IOS XE router on the site network. Endpoints that normally register to the Webex cloud switch to it automatically when the connection to Webex is lost and return after the connection is restored, Cisco's survivability article says. Outside calls in that mode, E911 included, need a local PSTN circuit or SIP trunk configured on the gateway. The router needs IOS XE 17.12.3 or later and platform licenses, and hunt groups, call forwarding and auto attendant need 17.18.2 or later.
Cisco's endpoint list for that mode covers Cisco multiplatform phones, the Webex App on Windows and Mac, and the Cisco VG400, VG410 and VG420 gateways with the ATA 191 and 192 adapters, and the article states that third-party devices are not supported with the gateway. Three-way calling and conferencing are unavailable while a site runs on it. Yealink, Poly and AudioCodes phones appear on Cisco's supported devices list for normal operation, where they need approval from the Cisco account manager before provisioning.
The ATA 191 and 192 each have two FXS ports and the largest VG420 configuration has 144, per Cisco's ATA article and its voice gateway article. The supported devices list describes these adapters as connections for analog phones, fax machines and overhead paging systems. For fax, Cisco says to connect the machine directly to the adapter and advises a dedicated PSTN line for best results, and the voice gateways offer a per-port T.38 setting for fax ports. FXO and ISDN interfaces on some of those gateway models are not supported with Webex Calling.
On Cisco Calling Plans, where Cisco is the PSTN provider, the earliest requestable port date ranges from 1 to 35 business days by country, carrier and order type, and the date is confirmed only when the losing carrier returns a Firm Order Commitment, Cisco's porting guidelines say. For a site keeping premises-based PSTN, have the current provider state in the order which numbers need porting and the schedule for those ports. For 911 in the US, its territories and Canada, RedSky is the default partner in Cisco's enhanced emergency calling article: the administrator enters buildings with dispatchable addresses and a wiremap of switches, access points and subnets in the RedSky portal, then tests by dialing 933 from each location. At a Local Gateway location enabled for that service, emergency calls go to the service, and at a location without it they go through the gateway.
A Control Hub wizard converts eligible 7800 and 8800 series phones from enterprise firmware to the multiplatform firmware Webex Calling uses and generates the device license, per Cisco's firmware migration article. Some 7800 models need a minimum hardware version, and the wizard does not migrate ineligible devices. Its source platforms are Unified CM on premises, Unified CM with Hosted Collaboration Solution and Spark calling.
Brinks moved from an on-premises Cisco Unified CM serving more than 4,000 users to Webex Calling branch by branch over a SIP trunk to the old system, and its senior VoIP engineer puts the work at under two months, in a Webex customer story dated March 10, 2026. The story counts more than 220 branches in the US and Canada.
Microsoft Teams Phone: a phone system inside a qualifying E5 license
Microsoft's Teams Phone licensing guidance lists Microsoft 365 E5 (no Teams) combined with Teams Enterprise, and a legacy E5 that includes Teams, as including the Phone System application. A user on either does not also need the stand-alone Teams Phone Standard license. A route to the public phone network is still required, through a Microsoft Calling Plan, an operator or a Direct Routing carrier.
Microsoft's PSTN overview describes Direct Routing through a certified SBC run by the customer, an integrator or a hosted Direct Routing provider. The Direct Routing planning guide names an existing carrier relationship and third-party PBXs or analog devices among the reasons to choose it, and its architecture sketch places the SBC between Teams and the carrier, the PBX and the analog devices. Its requirements include a Microsoft-certified SBC with carrier trunks, users homed online in Microsoft 365, a verified tenant domain and a trusted public certificate. Microsoft's dial plan overview says custom dial plans are typically used for extension or abbreviated dialing.
The planning guide's onboarding order runs from requirements through SBC pairing to validation, a high-level sequence. Ask your integrator for the user-wave plan and for the routing that lets PBX users and Teams users reach each other by extension, with the SBC vendor's confirmation for your PBX.
SIP Gateway lets compatible SIP phones sign in to Teams, and Microsoft's SIP Gateway planning guide names Cisco multiplatform phones and devices from Poly, Yealink and AudioCodes, with Avaya J100-series entries in its device table. Cisco phones on enterprise firmware have to be converted to multiplatform firmware first. Each user needs Teams, Phone System and PSTN connectivity licensing along with a phone number enabled for PSTN calling.
The Survivable Branch Appliance is Microsoft code that SBC vendors embed in their firmware or ship separately, and Microsoft's guide to it covers a Direct Routing branch that loses its internet connection to the Microsoft cloud while users can still reach the local SBC that provides PSTN. Setup runs through Teams PowerShell with a branch survivability policy for each user, and the SBC has to be configured for Media Bypass. The supported clients list names Teams for Windows and macOS desktop and Teams phones, and virtual machines and web clients are excluded. In that mode location is not shared on emergency calls and emergency call routing policies are not supported, so emergency numbers need a matching pattern on the regular voice routing policy.
An analog device on Direct Routing connects through an adapter that the certified SBC vendor supports, and phones behind it are not searchable from Teams, so users dial the number by hand, Microsoft's analog device guide says. The SIP Gateway device table carries its own list of adapters from AudioCodes, Poly and Cisco and SIP paging products from Algo and AXIS. On the Calling Plan route, Microsoft's porting guide says dedicated fax numbers can be moved but will not carry fax traffic afterward, since faxing is not offered through the Phone System or Calling Plan licenses.
The same guide gives 7 to 14 days as the typical time from submission to completion for Calling Plan ports in the US and Canada, and up to 30 days depending on the current provider. The losing carrier decides whether the requested date holds, and Microsoft states it cannot influence that decision. For 911, administrators create emergency addresses and match them to wireless access points, switches and subnets, and a Direct Routing customer also has to send location data from the SBC and connect to an emergency routing service provider or set up ELIN, per Microsoft's dynamic emergency calling guide.
Deutsche Bank replaced its earlier telephony system with Teams Phone, and its technology manager says more than 130,000 workers were provisioned over eight months with automation built alongside a Microsoft delivery team, in a Microsoft customer story dated November 14, 2023.
Which platform should you pick for a phased move off a legacy PBX?
We crown Zoom Phone for the organization that puts extension dialing between its existing PBX and its migrated users first and keeps its carrier through a phased cutover, on the condition that the order confirms the PBX and SBC configuration, the local survivability design, device compatibility, and assigned responsibility for number porting and 911. Zoom documents the carrier connection and the PBX extension link as two named steps in a set order, and its migration guidance works through a user who keeps an extension across the move.
Cisco documents a Control Hub conversion for its own enterprise desk phones and a defined list of Cisco endpoints that stay registered at a site. We give those controls priority for a buyer retaining eligible Cisco endpoints. For the buyer defined here, we weigh Zoom's documented PBX extension link more.
Cisco Webex Calling is the better pick when the system you are leaving is Cisco Unified CM and the priority is keeping eligible Cisco phones on desks with site survivability for them. Put the phone models and hardware versions, the router model with its IOS XE release and licenses, the Local Gateway design and the local PSTN circuit in the quote, because the conversion and the survivability list both apply model by model.
Microsoft Teams Phone is the better pick when a qualifying E5 combination already gives your users Phone System and your SIP phones appear on the SIP Gateway list. Have the order confirm the Teams and PSTN entitlement, each phone model and firmware, the certified SBC, and what a branch needs during an internet outage, including how 911 location is handled while the branch runs on the appliance.
Other UCaaS providers
| Provider | Website |
|---|---|
| RingCentral | ringcentral.com |
| 8x8 | 8x8.com |
| GoTo | goto.com |
| Dialpad | dialpad.com |
| Nextiva | nextiva.com |
| Vonage | vonage.com |
| Intermedia | intermedia.com |
| Gamma Communications | gammagroup.co |
| Sangoma | sangoma.com |
| Avaya | avaya.com |