Switching to a new phone provider doesn’t have to mean starting over with new numbers. Number portability — the right to take your existing phone numbers with you when you change carriers — is a federal protection established by the Federal Communications Commission (FCC) and available to virtually all businesses. But knowing you can port your numbers and knowing how to do it successfully are two different things. Here’s what the process involves and how to avoid the most common problems.
What number porting is and why it matters
Local number portability (LNP) is the FCC-mandated ability to move a phone number from one service provider to another while keeping the number itself unchanged. Established to prevent phone numbers from locking businesses into carrier relationships, LNP covers local landline numbers, mobile numbers, and toll-free numbers (though toll-free numbers operate under a slightly different system called RespOrg, or Responsible Organization, which manages toll-free routing).
For businesses, maintaining existing phone numbers during a provider transition matters significantly. Customers, vendors, and partners have those numbers in their contacts. Marketing materials, directories, and websites reference them. Starting fresh with new numbers means managing a period of confusion and potential missed calls that can have real operational and reputational costs.
How the porting process works
A number port involves two carriers: the losing carrier (your current provider, whose network the number is leaving) and the winning carrier (your new provider, who will take over the number). The process begins when you submit a port request to the winning carrier, along with a letter of authorization (LOA), which is a signed document confirming that you own the numbers and authorize the transfer. The LOA must match the account details held by the losing carrier exactly; discrepancies in account name, address, or billing information are among the most common causes of port rejections.
The winning carrier submits the port request to the losing carrier, who validates the information and either approves or rejects it. Once approved, a Firm Order Commitment (FOC) date is set. The FOC is the scheduled date and time the numbers will transfer. On that date, the numbers move from the losing carrier’s network to the winning carrier’s, and the winning carrier programs them for use on their platform.
What can go wrong and what to do about it
Even straightforward ports can encounter problems. The most common is a partial port: some numbers transfer successfully while others don’t. This usually indicates a programming issue on the winning carrier’s side rather than a problem with the paperwork, and the winning carrier can typically resolve it quickly. Having a technical team on a live call with the winning carrier during the port window significantly reduces the time to resolution.
Numbers can also get stuck mid-port — neither active on the old platform nor live on the new one. This typically happens when the losing carrier hasn’t released the numbers correctly. Resolving it requires working with the losing carrier to release them and then with the winning carrier to locate and activate them in their system.
The snapback: The last resort option
If a port goes wrong badly enough that numbers simply can’t be brought up on the winning carrier’s platform, a snapback is the emergency option. A snapback reverses the port: the winning carrier releases the numbers back to the losing carrier, who restores them to their previous routing configuration. If executed quickly enough, the numbers typically return to their original routing tables before those tables are purged, minimizing downtime.
Toll-free and 8xx numbers generally snapback within 20 minutes to 2 hours when both carriers treat it as a priority. Direct inward dial (DID) numbers are slower, taking anywhere from 4 to 48 hours depending on carrier workloads and the complexity of the original routing. Because snapbacks take time, they underscore the value of two practices: porting in batches rather than all at once, and using tribute numbers (test numbers with no active traffic) to verify interoperability before committing to the full port.
How to set yourself up for a clean port
The single most important preparation step is verifying that your LOA information matches your account details with the losing carrier exactly, including billing name, service address, and account number. Beyond that, confirm your FOC date in writing, have technical resources available during the port window, test with a few numbers first, port in batches if you’re moving a large number of lines, and define in advance the threshold at which you’ll declare the port unsuccessful and initiate a snapback. Having that decision made before things go wrong removes the delay and confusion of making it in the middle of an outage.
Planning a phone system migration and want to make sure the number porting goes smoothly? Our team has experience managing complex ports and can guide you through the process from LOA to go-live. Get in touch before you start.