What Actually Happens During a Number Port

Phone number porting is one of those things that sounds like it should be simple. You are moving a number from one carrier to another. The number does not change. The person using it does not change. It is a database update. And yet porting is the single most common source of delays, failures, and outages during carrier migrations.

Understanding the mechanics behind porting — the actual process, the systems involved, the specific points where things break — is essential for anyone managing voice infrastructure. This post walks through the entire process, from the regulatory framework that makes porting possible to the network-level routing changes that happen at activation.

Why porting exists

Phone number portability was not always a thing. Before 1996, your phone number belonged to your carrier. If you switched carriers, you got a new number. This created massive switching costs and effectively locked customers into their current provider.

The Telecommunications Act of 1996 changed that. It required all telecommunications carriers to support Local Number Portability (LNP), meaning customers could keep their phone numbers when switching providers. The intent was straightforward: remove the number as a barrier to competition so carriers would have to compete on price and service quality instead.

The FCC implemented this mandate in phases. Wireline LNP went live in the late 1990s. Wireless LNP followed in 2003. Today, all carriers — wireline, wireless, VoIP, and cable — are required to support number portability.

The players

A port involves several parties, and understanding their roles clarifies why the process works the way it does.

The winning carrier (also called the new provider or gaining carrier) is the carrier the customer is moving to. The winning carrier initiates the port request.

The losing carrier (also called the old provider or current carrier) is the carrier the customer is leaving. The losing carrier must validate and release the number.

The NPAC (Number Portability Administration Center) is the central clearinghouse that manages the master database of ported numbers. When a port is activated, the NPAC updates its records and distributes the routing information to all carriers. The NPAC is operated by iconectiv (formerly Telcordia) under contract with the FCC.

The LSMS (Local Service Management System) is each carrier's local copy of the NPAC data. Every carrier that originates or transits calls maintains an LSMS that receives updates from the NPAC. When a call is placed, the originating carrier queries its LSMS to determine where the called number is currently homed. This is the system that makes ported numbers actually work — without it, calls to ported numbers would still route to the old carrier.

The process, step by step

Step 1: Letter of Authorization (LOA)

The process starts when the customer signs a Letter of Authorization giving the winning carrier permission to port their number. The LOA includes the customer's name, the authorized numbers, the account number with the losing carrier, and the customer's signature.

The LOA is a legal document. It authorizes the winning carrier to act on the customer's behalf and tells the losing carrier that the port is legitimate. An incorrect or missing LOA is one of the top reasons ports fail.

Step 2: Local Service Request (LSR)

The winning carrier submits an LSR to the losing carrier through a standardized electronic interface. The LSR contains the information from the LOA along with technical details about the port: which numbers are being ported, the desired port date, the winning carrier's routing information, and the customer's account information as it appears on the losing carrier's records.

That last part — "as it appears on the losing carrier's records" — is critical. The name, address, and account number on the LSR must match the losing carrier's records exactly. Not approximately. Exactly. If the customer's name is "Robert Smith" in the losing carrier's system and the LSR says "Bob Smith," the port will be rejected.

Step 3: Validation and FOC

The losing carrier validates the LSR against their records. If everything matches, they issue a Firm Order Commitment (FOC), which confirms the port and specifies the activation date and time window.

If the information does not match, the losing carrier issues a reject. The reject includes a reason code that tells the winning carrier what was wrong. Common reject reasons include name mismatch, address mismatch, account number mismatch, and unauthorized request (the number is not on the account specified in the LSR).

The winning carrier corrects the information and resubmits. Each rejection-and-resubmission cycle adds days to the process. This is why pre-verifying the customer's account information with a Customer Service Record (CSR) before submitting the port is so important.

Step 4: Port activation

On the FOC date, during the agreed time window, the winning carrier activates the port in the NPAC. The NPAC updates its master database with the new routing information — specifically, the Location Routing Number (LRN) of the winning carrier's switch that will now handle calls to the ported number.

The NPAC then distributes this update to every carrier's LSMS. Once the LSMS updates propagate, calls to the ported number start routing to the winning carrier instead of the losing carrier.

The losing carrier simultaneously deactivates the number on their switch. The entire activation is supposed to happen in a coordinated window, but in practice the timing between these two events — the NPAC update propagating and the losing carrier deactivating — is where the gap problem lives, which we will get to shortly.

Why ports take so long

The FCC mandates that simple wireline and wireless ports should complete within one business day. In reality, simple wireless ports often take 1 to 4 business days. Wireline ports routinely take a week or more.

The delays are not technical. Updating a database record takes milliseconds. The delays are procedural and organizational. The losing carrier has to validate the request against their billing system. Their porting department processes requests in queue order. If there is a rejection, the resubmission goes back into the queue. Business day rules apply — weekends and holidays do not count.

Losing carriers also have limited economic incentive to expedite ports. Every day a customer remains on their service is another day of billing. The FCC has fined carriers for deliberately delaying ports (a practice called "port blocking"), but there is a difference between deliberate obstruction and simply not prioritizing porting operations with additional staff.

Why ports fail

Understanding the common failure modes helps you avoid them.

Name or address mismatch. The most frequent cause of rejection. The customer tells you their name is "John's Auto Shop" but the losing carrier has the account under "John A. Smith dba John's Auto Shop." The LSR gets rejected. The fix is to obtain a CSR from the losing carrier before submitting the port so you have the exact account information as it appears in their system.

BTN confusion. A business account often has one Billing Telephone Number (BTN) and multiple working telephone numbers. The BTN is the master number on the account. If you submit a port for a working number but reference the wrong BTN, or if the losing carrier's system requires the port to reference the BTN specifically, the port gets rejected. This is particularly common with PRI circuits where 23 channels share a single BTN.

Unauthorized requests. The LOA is missing, incomplete, or signed by someone not authorized on the account. Some carriers require the LOA to be signed by the exact person listed as the authorized contact on the account.

Partial ports. Porting some numbers off an account while leaving others is called a partial port. Partial ports are more complex because the losing carrier has to restructure the remaining service. If the BTN is one of the numbers being ported, the losing carrier needs to assign a new BTN to the remaining lines before releasing the ported number. This adds steps and opportunities for things to go wrong.

Wireless-to-wireline complications. Porting a wireless number to a wireline or VoIP carrier (or vice versa) involves additional validation because the number is crossing service types. The wireless carrier's porting process and system may differ from the wireline process, and the intercarrier communication sometimes hits edge cases that same-type ports do not.

Simple ports vs. complex ports

The industry distinguishes between simple and complex ports, and the distinction matters because it determines the timeline and process.

A simple port involves a single line with no complex features. One phone number, one carrier, no hunt groups, no ISDN PRIs, no special routing. The FCC's one-business-day requirement applies to simple ports.

A complex port involves any of the following: multiple numbers on a single request, numbers on a PRI or T1 circuit, toll-free numbers (which use a different portability system — the SMS/800 database), numbers with special features like hunt groups or remote call forwarding, or numbers where the losing carrier requires circuit disconnection coordination.

Complex ports do not have the same one-business-day mandate. They are negotiated between carriers on a case-by-case basis, with timelines typically ranging from one to four weeks. An office with 50 numbers on two PRIs, a toll-free number, and a hunt group is going to take significantly longer than porting a single cell phone number.

What happens at the network level

When a port activates, the actual call routing change is elegant in its simplicity.

Every phone number in the PSTN has a home switch — the switch where the number was originally provisioned. Before porting existed, calls were routed based on the NPA-NXX (area code and exchange) of the called number. Every NPA-NXX maps to a specific switch.

When a number is ported, the NPAC assigns it a Location Routing Number (LRN), which is the 10-digit identifier of the winning carrier's switch. The LRN looks like a phone number but it is a routing address, not a dialable number.

When someone calls a ported number, the originating carrier performs an LNP dip — a database query against its LSMS. The LSMS returns the LRN for the called number. The originating carrier then routes the call to the switch identified by the LRN instead of the switch identified by the NPA-NXX. The call arrives at the winning carrier's switch, which maps the called number to the customer's actual service (their SIP trunk, their PBX extension, their VoIP endpoint).

This LNP dip happens on every call to every number. For non-ported numbers, the LSMS returns no LRN, and the call routes normally based on NPA-NXX. For ported numbers, the LRN overrides the default routing.

The dip adds a small amount of latency to call setup — typically a few milliseconds. It is imperceptible to users.

The gap problem

The port activation is not truly instantaneous. There is a window — usually measured in minutes but sometimes longer — where the routing is in transition. The NPAC has been updated, but not every carrier's LSMS has received the update yet. Or the LSMS has been updated but the losing carrier has not deactivated the number on their switch yet. Or the losing carrier deactivated before the NPAC update fully propagated.

During this window, calls to the ported number may fail, ring at the old carrier with no one to answer, or reach a "number not in service" recording. The window is usually brief, but it exists, and for businesses that depend on inbound calls, even a 15-minute gap can be a problem.

This is why port activations are typically scheduled during low-traffic hours, and why go-live day planning is so important for business migrations. Knowing the activation window, having a plan for what happens during the gap, and communicating the timeline to the end users are all part of a clean migration.

Some carriers offer "flash cut" porting where they coordinate the activation tightly to minimize the gap. But even a flash cut is not zero downtime. If inbound call continuity is critical, having a temporary forwarding number or an announcement in place during the activation window is a reasonable precaution.

Best practices for smooth ports

Get the CSR first. Before submitting any port request, obtain a Customer Service Record from the losing carrier. This gives you the exact account name, address, BTN, and list of working numbers as they appear in the carrier's system. A carrier lookup can also help you confirm the current carrier and line type before you start the process. Use this information verbatim on the LSR. This single step eliminates the majority of port rejections.

Verify the LOA. Make sure the LOA is signed by an authorized contact on the account, includes all numbers being ported, and has the correct account number. Some carriers have specific LOA format requirements — check before submitting.

Time the port. Schedule the port activation during a low-traffic period. For most businesses, early morning or after business hours works well. Avoid Fridays — if something goes wrong, you do not want to be troubleshooting a failed port over the weekend with carrier porting departments closed.

Have temporary numbers ready. For critical inbound lines, provision temporary numbers on the winning carrier and set up forwarding before the port. If the port is delayed or the gap window runs long, callers can still reach the business.

Communicate the timeline. Tell the end users exactly when the port is scheduled, that there may be a brief interruption, and what to do if they notice problems. Set expectations early so a five-minute gap does not become a panicked support call.

Track the FOC. Once you have an FOC date, confirm it with both carriers. If the FOC date slips, you need to know immediately so you can adjust your migration plan and notify the client.

Porting in the VoIP world

VoIP-to-VoIP ports are often faster than traditional wireline ports. There are a few reasons for this.

VoIP carriers tend to have more modern, more automated porting systems. Many of them use electronic LSR submission and automated validation, which reduces the human-in-the-loop delays that slow down legacy carrier ports. Some VoIP carriers can complete ports in hours rather than days.

VoIP carriers also do not have the physical infrastructure complications of wireline ports. There is no copper pair to disconnect, no circuit to restructure, no truck roll to coordinate. The port is purely a database and routing change, which is what porting should have always been.

That said, VoIP ports are not immune to the same failure modes. Name mismatches, LOA problems, and partial port complications still apply. And porting between a VoIP carrier and a traditional wireline or wireless carrier still involves the slower carrier's process as the bottleneck.

If you are managing carrier migrations and want to understand how your vendor relationships affect the porting experience, the responsiveness of a carrier's porting department is one of the most practical indicators of their overall operational quality. Carriers that port quickly and cleanly tend to run clean operations in general.

Related reading

For more on managing number ports during office relocations, see Porting Numbers During an Office Move. If you are planning a VoIP cutover, Go-Live Day Planning covers the broader migration coordination, including how porting fits into the overall timeline. And for understanding the SIP infrastructure that ported numbers ultimately land on, see SIP Trunking.