Number Porting Guide
Porting your business numbers is the step most owners worry about, and for good reason: your numbers are how customers reach you, and a botched cutover means missed calls. A well-run port, though, is predictable. Most single-line and simple business ports finish in about one to two weeks; larger or PRI-based ports take longer. This guide covers realistic timelines, the paperwork each port needs, and how a test-then-cutover approach keeps you from going dark.
The biggest factor in how fast a port moves is not the carrier on the other end. It is how accurate your paperwork is on day one. We do that legwork up front to get it right the first time, so your numbers move on schedule.
Timelines depend on the line type, the number of lines, and the losing carrier's process. Here is what to plan for.
A single number or a small set of standard business lines on a cooperative carrier usually completes within one to two weeks of clean paperwork. Most of that window is the regulated wait for the losing carrier to confirm the port date.
Larger number sets, multiple billing accounts, or numbers spread across several carriers add coordination time. Each account needs its own service record and authorization, which is the most common reason a bigger port runs long.
Porting numbers off a PRI, T1, or older trunk often means the carrier must first separate your numbers from the underlying circuit. These ports take longer and need extra runway plus a clear plan for the legacy line.
Toll-free numbers move through the Resp Org system rather than the standard local porting process, and they frequently complete in a few business days. Changing the controlling Resp Org can add a step.
A port becomes firm only when the losing carrier accepts it and returns a firm order commitment date. We give you a realistic estimate up front, then lock the exact cutover once that confirmation lands.
Most delays trace back to mismatched information. These are the details every port needs, and they must match your current carrier's records exactly.
Your signed permission to move the numbers. It lists the account holder and the numbers being ported, and the signing name has to match the name on file with your current carrier, not a newer or shortened version.
The official account snapshot from your current carrier: billing name, service address, account number, and the numbers on the account. We use it to make every field on the port request match the source of truth.
Many carriers require the account number plus a porting PIN or passcode before they release numbers. If you do not have these, request them from your current provider before the port starts.
The service address and authorized contact must match the carrier's records character for character. A missing suite number or a former owner still on the account will trigger a rejection.
Include every number you want to keep, such as fax lines, alarm or elevator lines, and rarely used DIDs. Numbers left off the request stay with the old carrier and can be hard to recover later.
The safest ports never flip everything at once. We stand up your new system and prove it works before any number moves.
We configure your new system, auto attendant, call routing, and devices on temporary numbers first. Your team places and receives real calls and confirms everything behaves before we touch a live number.
For larger sites, the old and new systems can run side by side during transition so staff get comfortable and routing gaps surface early. That turns cutover day into a simple, expected switch.
Ports complete on a confirmed date, usually within a defined window. We schedule that window with you, typically during lower-traffic hours, so the switchover lands when it disrupts the fewest calls.
Right after numbers port, we place inbound and outbound test calls across each line and feature to confirm calls land where they should. We stay engaged until the system is verified working, not just until the port confirms.
Carriers reject port requests for predictable reasons. Knowing them ahead of time is how we keep your timeline on track.
The most common rejection is information that does not match the losing carrier's records, often an outdated business name, a missing suite, or a wrong account number. Pulling the CSR first prevents most of these.
An unpaid balance, an order still in progress, or a port-out freeze on the account can block a port. These usually have to be cleared with your current provider before the numbers can move.
You can generally port a number even while under contract, but your old carrier may still bill remaining contract or termination fees. Knowing your obligations up front avoids surprises.
Keeping some numbers on a PRI or trunk while moving others forces a partial port, which is slower and can disrupt the remaining service. We plan partial ports carefully so lines you still rely on stay up.
Canceling the old account before the port completes can release your numbers back into the pool and lose them. Keep the old service active until the port is confirmed, then cancel.
Porting is one piece of a managed cutover. Here is how we protect call flow from start to finish.
We inventory every number, line type, and feature you depend on, then map it to the new system. That up-front work is what lets us submit a clean port instead of fixing rejections.
Where useful, we route calls to interim numbers or mobile devices so your team never goes dark, even if a carrier shifts a port date at the last minute.
As numbers move, we register accurate emergency-calling locations so 911 calls reach responders with the right address. It is easy to overlook in a rushed cutover, so we make it standard.
If you text customers from a business number, its A2P 10DLC registration has to follow the number to its new home so messages keep delivering. We coordinate that alongside the voice port.
The same team that scopes your project files the port, schedules the cutover, and verifies the result. You are not handed between a sales rep, a carrier, and a support queue.
Keep exploring
Checklist
FAQ
No. Your existing service runs right up to the scheduled cutover, and the actual switch usually takes only a brief window. Because we build and test the new system on temporary numbers first, calls keep flowing on your current setup until the new one is proven and the numbers move.
The most effective way is to submit accurate information the first time. Pull your customer service record and confirm the exact account name, service address, account number, and any porting PIN before submitting, since rejections cause most delays. The regulated carrier confirmation window cannot be skipped, but a clean request hits the short end of the timeline.
In nearly all cases, yes. Local and toll-free business numbers are portable, so you keep the numbers customers already know no matter which provider you move to. The main exceptions are numbers tied to a service area the new carrier cannot reach, or numbers that have already been disconnected.
A rejection is usually a fixable data mismatch, not a dead end. The carrier returns a reason, we correct the detail, such as an outdated business name or wrong account number, and resubmit. Your current service stays active throughout, so a rejection delays the date but does not interrupt your calls.
No. Keep the old account active until the port is fully confirmed. Canceling early can release your numbers back into the pool and lose them permanently. Once the new system is verified working, you can safely close the old account.
Not exactly. Toll-free numbers move through the Resp Org system rather than the standard local porting process and often complete in a few business days. If the controlling Resp Org has to change, that adds a step, but toll-free ports are generally straightforward.
Free Voice Assessment
Get a practical recommendation for hosted VoIP, on-site PBX, SIP trunking, handsets, business texting, and cutover planning — built around how your team actually works.
