Published on June 9, 2026
Number porting is the process of transferring an existing phone number from one telecommunications provider to another so that organizations can change carriers or move to a cloud phone system without losing the numbers their customers, vendors, and employees already use.
For IT teams managing a business phone migration, porting is often the most operationally sensitive part of the project. A number that's been in use for years carries real business continuity value — customers know it, it's printed on business cards, and it routes calls that drive revenue. Losing it or experiencing downtime during transfer can create measurable disruption.
Zoom Phone, part of Zoom Workplace, is built to handle both straightforward number transfers and complex enterprise porting scenarios through a unified admin interface that gives IT teams direct control and full visibility into every request.
Local number portability (LNP) is the regulatory framework that requires carriers to release numbers upon valid request. In practice, this means your new provider — not your old one — drives the process. Here's how it works, step by step.
Most cloud phone providers treat number porting as a support ticket. Zoom Phone treats it as an admin workflow — built directly into the Zoom Workplace platform so that IT teams can manage requests, track status, and configure routing from a single interface, without coordinating across multiple systems or waiting on a response from a carrier support queue.
The Zoom admin portal provides self-service porting tools that cover the full request lifecycle: portability checks, LOA submission, FOC date tracking, and post-cutover configuration. For organizations managing dozens or hundreds of numbers across sites, this unified view substantially reduces administrative overhead compared with fragmented, email-driven porting processes.
For complex migrations — large-scale multi-site deployments, legacy PBX conversions, or environments with highly customized dial plans — Zoom's Professional Services Organization provides dedicated porting support. Zoom professionals can port over existing numbers, assign new numbers, and work directly with carriers to resolve exceptions, so your internal IT team isn't the bottleneck.
Zoom Phone also delivers infrastructure-grade reliability during and after porting. According to the independent Zoom Phone Audio Quality Report 2025, Zoom Phone recorded the lowest end-to-end audio delay across macOS, Android, and iOS compared with all platforms tested, and retained a MOS score of 3.3 at 70% packet loss — meaning call quality holds up even under degraded network conditions, which is particularly relevant during the transition period of a migration. Zoom Phone is also built on enterprise-grade cloud infrastructure with compliance support across HIPAA, GDPR, and other regulatory frameworks relevant to multi-national IT environments.
For organizations that want to keep their existing carrier relationship, Zoom Phone supports bring your own carrier (BYOC), so number porting to a new carrier isn't the only path forward.
Porting a handful of numbers for a small office is straightforward. Porting hundreds of numbers across multiple sites, carrier relationships, and regulatory jurisdictions requires a more structured approach. Use this framework to evaluate readiness before you start.
Important question to ask any vendor: "What is your process for handling a rejected port request, and what is the average resolution time for enterprise accounts?"
Enterprise porting scenarios often involve more than just moving numbers — they require re-engineering the organization's telephony system. BNSF Railway is one example. By migrating to Zoom Phone and using Zoom APIs, BNSF reduced its total dialing rules from more than 60,000 to fewer than 200 — a 99% reduction — dramatically simplifying administration and accelerating its transition to a cloud phone environment. The complexity that once required tens of thousands of routing rules was replaced by a manageable, modern configuration that IT teams could actually maintain.
Number porting applies across a wide range of enterprise telephony scenarios. Here are the most common situations IT teams navigate.
Legacy PBX migration: Organizations moving from on-premises PBX infrastructure to a cloud phone system need to port existing numbers to avoid disrupting customer-facing and internal communications. Porting phone numbers to a cloud phone system enables a cutover without reissuing numbers or updating directories.
Carrier consolidation: Multi-site organizations often carry numbers across multiple legacy carriers. A business phone migration that consolidates to a single cloud provider reduces carrier management overhead and simplifies billing, while porting preserves existing numbers in the inventory.
Mergers and acquisitions: When two organizations merge their telephony environments, number porting allows the surviving entity to retain all acquired numbers without maintaining duplicate carrier relationships.
Post-acquisition IT standardization: IT teams tasked with standardizing a newly acquired subsidiary's communications stack can port existing numbers into the parent company's cloud phone environment, maintaining continuity for the acquired organization's customers and partners.
Unified collaboration platform adoption: Organizations moving to an integrated UCaaS platform — combining phone, meetings, and team messaging in one place — often port existing numbers as part of the broader platform consolidation. Post-migration, numbers are managed alongside the rest of the collaboration stack, including Zoom Meetings and Zoom Rooms for hybrid work environments.
Number porting is the process of transferring an existing telephone number from one service provider to another, governed by local number portability (LNP) regulations so that individuals and organizations can switch carriers without changing their phone numbers. The process applies to geographic numbers, toll-free numbers, mobile numbers, and most VoIP numbers. It requires authorization from the account holder, verification of account details against the losing carrier's records, and a coordinated cutover on a confirmed transfer date.
LNP regulations exist in most countries to prevent carrier lock-in and support market competition. From an IT perspective, number porting is a critical capability because business phone numbers represent an established communication identity — customers, vendors, and partners use them to reach your organization. Any interruption or permanent loss of a ported number carries real operational and reputational cost, which is why IT teams treat the porting process as a risk-managed migration event rather than a routine administrative task.
Zoom Phone manages number porting through a self-service workflow in the Zoom admin portal, where IT teams can check portability, submit LOAs, track port request status, and configure routing — all in one place, without opening support tickets or coordinating across separate systems. The admin portal provides visibility into the full request lifecycle, from submission through FOC date confirmation and cutover.
For organizations with complex porting needs — large number of inventories, multi-site deployments, or legacy PBX dial plans — Zoom's Professional Services Organization provides hands-on support. Zoom professionals work directly with carriers, manage documentation, and resolve exceptions so that IT teams can focus on broader migration planning rather than carrier coordination. Zoom Phone also supports bring your own carrier (BYOC) for organizations that want to retain their existing carrier relationship while moving to a cloud phone platform.
Number porting transfers an existing phone number from one carrier to another, preserving the number's identity and all established associations — business cards, directories, customer records, and inbound call routing built around that number. Getting a new number means acquiring a fresh number from your new provider, which requires updating every touchpoint where the old number appeared and accepting a period during which inbound calls to the old number may not reach you.
For most business migrations, number porting is strongly preferred because it eliminates the continuity risk of a number change. New numbers are typically only chosen when the existing number has no business value, when a number is not portable in a given geography, or when an organization is deliberately rebranding its contact identity as part of a broader initiative.
A Letter of Authorization (LOA) is a legally binding document that grants your new telephone service provider permission to request the transfer of your existing phone numbers from your current carrier on your behalf. It typically includes the account holder's name, billing address, account number, the specific numbers to be ported, and a signature from an authorized representative of the organization.
The LOA is the most common point of failure in the porting process. If any field in the LOA does not exactly match the records held by the losing carrier — including small discrepancies like abbreviations in an address or a mismatched account name — the carrier can reject the port request, adding days or weeks to your timeline. IT teams managing enterprise migrations should obtain a current carrier bill before completing the LOA to ensure all details match precisely.
Simple port requests — a single number or a small batch from a domestic carrier — typically complete in 5 to 10 business days once all documentation is submitted and validated. Complex ports involving multiple numbers, toll-free numbers, international numbers, or legacy carrier systems can take several weeks, particularly if documentation rejections require resubmission.
The timeline officially begins when the losing carrier issues a Firm Order Commitment (FOC) date, which is the confirmed cutover date for the transfer. IT teams should plan for a buffer between the FOC date and any hard go-live deadlines, and should maintain legacy service in parallel until porting is confirmed complete. Large enterprise migrations typically port numbers in batches rather than all at once, which allows for testing and rollback at each stage.
Yes, most enterprise VoIP providers support bulk number porting, which allows organizations to transfer large inventories of numbers in a single coordinated process rather than submitting individual port requests. Bulk porting is especially relevant for multi-site organizations, post-acquisition integrations, or migrations from large on-premises PBX environments with hundreds of DIDs.
Zoom Phone supports bulk porting through the admin portal, where IT teams can manage large number sets as part of the same unified workflow used for individual ports. When evaluating any provider's bulk porting capability, confirm the per-batch size limit, the expected processing timeline per batch, and the process for handling partial rejections — where some numbers in a batch are rejected while others proceed. Having a clear escalation path for rejected numbers in a bulk request is essential for keeping enterprise migration timelines on track.
During the porting process, your existing phone service remains active on the losing carrier until the FOC cutover date. No calls are dropped or interrupted during the submission and validation period. On the cutover date, the number is released by the old carrier and activated on the new platform, typically within a maintenance window that lasts minutes to a few hours, depending on the carrier and number type.
Best practice for IT teams is to configure and test the new phone system — including call routing, auto-attendants, voicemail, and integrations — before the FOC date arrives, so that the cutover is a clean switch rather than a live troubleshooting exercise. Keeping legacy service active for 48–72 hours after cutover gives you a practical safety net while you verify that all ported numbers are routing and functioning correctly on the new platform.
Number porting is a manageable process when IT teams approach it with the right preparation: a complete number inventory, accurate documentation, a tested configuration in the new system, and a clear escalation path for exceptions. For enterprise migrations — where the stakes include hundreds of numbers, multiple sites, and business continuity obligations — the choice of platform matters as much as the process.
Zoom Phone is built for exactly this environment. Its self-service admin portal, Professional Services support, and enterprise-grade infrastructure give IT teams the tools to manage porting at scale without the friction of legacy carrier workflows. Whether you're migrating a handful of DIDs or re-platforming an entire multi-site telephony environment, Zoom Phone is designed to make the transition straightforward.
See how Zoom Phone supports business phone migration at scale — explore Zoom Phone.
