August 18, 2026
Why Number Porting Takes Two to Four Weeks (And What Stalls It)
Phone number porting delays almost never come from the network. A port runs two to four weeks end to end because your current carrier validates the request against its own billing record, and any field that disagrees — business name, service address, account number — rejects the order and restarts the clock. Clean paperwork ports fast.
How long does it take to port a business phone number?
A port has three phases, and only the last one is technical.
Phase | Typical duration | Who controls it |
|---|---|---|
Gathering documents, matching the customer service record | 2–5 business days | You |
Carrier validation of the submitted request | 7–10 business days for a clean local port | Your current carrier |
Firm Order Commitment (FOC) date to cutover | 1–3 business days after the FOC issues | Scheduled jointly |
A port that goes right the first time lands around two weeks. Every rejection adds roughly a week, because a corrected request re-enters validation at the back of the queue rather than resuming where it stopped.
Toll-free numbers follow a separate process — a change of responsible organization rather than a local number port — and commonly run longer. Large multi-number ports and numbers riding on a PRI move slower still.
Why do phone number ports get rejected?
Nearly all rejections are records mismatches. The losing carrier compares what you submitted against what it has on file, and it does not interpret. It matches.
Rejection reason | What it actually is | How to fix it |
|---|---|---|
Name mismatch | The LOA says "Ridgeline Dental" and the billing record says "Ridgeline Dental Group LLC" | Copy the name character-for-character from the bill or the CSR |
Address mismatch | The record has the old suite number, or "Ave" where you wrote "Avenue" | Use the service address on the carrier's record, not the address on your letterhead |
Wrong account number or PIN | Retail accounts often carry a porting PIN separate from the billing login | Request it from the carrier before you submit |
Unauthorized signer | The person who signed the LOA is not the name of record | Have the account holder sign, or get the record updated first |
Number not on the account | A number you assumed was yours actually sits on a different account or a different carrier | Pull the CSR and reconcile it against your bill |
The countermeasure is to obtain a customer service record (CSR) from your current carrier before you submit anything. The CSR is the authoritative version of the data the port is validated against. A bill is a good approximation; the CSR removes the guesswork.
What is a partial port and why does it cause delays?
A partial port moves some of the numbers on an account and leaves others behind. It is legal, common, and slower.
Carriers treat partial ports as an account change rather than a closure, which usually means manual handling. If the number left behind happens to be the billing telephone number (BTN), some carriers reject the request outright until the BTN is reassigned — a separate ticket with its own timeline.
Two habits prevent most partial-port pain. Audit every number on the account line by line — the alarm line, the fax line nobody has used since 2019, the direct dial for a person who left — because numbers you fail to include get disconnected when you close the old account, and a disconnected number is often unrecoverable. And if you are leaving nothing behind, say so: a full port with an account closure request is a simpler transaction than a partial one.
Do pending orders on the account block a port?
Yes, and this is the stall people least expect. Any open order at the losing carrier — a pending disconnect, a scheduled address change, an upgrade a sales rep entered last month, a repair ticket that never closed — typically rejects the port with a "pending order" code. Carriers will not process two changes against one account at once.
Before you submit, call your current provider and ask one question: is there any open order or pending change on this account? Then wait for whatever they name to close.
The related trap is filing a disconnect notice ahead of the port to be efficient. A pending disconnect is exactly the kind of open order that blocks a port, and if it lands first the numbers return to the carrier's inventory. Cancel the old service after the port completes, never before. Our number porting guide covers the document set and the sequencing.
How do you pick a cutover date that survives a rejection?
Assume one rejection. Plan the date that absorbs it.
- Start the paperwork four to six weeks before the date you actually want. Two weeks is the clean-run timeline, not the plan.
- Pick a Tuesday or Wednesday morning. Ports complete during carrier business hours, and a Friday afternoon FOC leaves you troubleshooting on a weekend with a skeleton crew on both sides.
- Avoid the first and last three business days of the month, when month-end order volume slows carrier provisioning teams.
- Never schedule the port on the same day as an office move or an internet cutover. One variable at a time; if you are moving, read what to do about your phones when you move offices first.
- Build and test the new system on temporary numbers before the FOC date. Auto attendants, ring groups, voicemail boxes, and phone provisioning get finished in advance, so the port changes exactly one thing: where calls arrive.
That last point is what makes the timeline tolerable. With the system already built, a one-week slip is an annoyance rather than a crisis.
What happens on cutover day?
Service continues at the old carrier until the port completes, then inbound calls start arriving at Signal. There is no window where the numbers are dark, assuming nobody canceled the old account early.
On the day, work through the numbers one at a time: call each from an outside line and confirm it lands where you pointed it — the right auto attendant, ring group, or voicemail box. Check outbound caller ID from a few extensions. Keep the old service active until every number is verified.
E911 gets its own line on the checklist. Registration is per location and per number against a validated street address, so a ported number does not carry an emergency address with it. Confirm the E911 location record for every number and device before you call the cutover done.
Frequently asked questions
How long does it take to port a business phone number?
Two to four weeks end to end. A clean local port spends about 7–10 business days in carrier validation, plus a few days either side for document preparation and the scheduled cutover. Toll-free and large multi-number ports take longer, and each rejection adds roughly a week.
Why do phone number ports get rejected?
Almost always because the submitted information does not match the losing carrier's record exactly — business name, service address, account number, porting PIN, or authorized signer. Open orders on the account are the second most common cause. A customer service record eliminates most mismatches before you file.
What is a partial port and why does it cause delays?
A partial port moves some numbers off an account and leaves others active. Carriers handle these manually, and if the number you keep is the account's billing telephone number, the request may reject until that is reassigned. Audit every number on the bill before deciding what stays.
Can I pick my own porting cutover date?
You request a date; the losing carrier confirms one by issuing a Firm Order Commitment. Requests inside the standard validation window are generally honored, but the FOC is the date that counts. Ask for a mid-week morning and keep a week of slack before any hard deadline.
Will my phones stop working during a port?
No, if the sequence is right. Numbers keep working at the old carrier until the port completes, then calls arrive at Signal instead. The failure mode is canceling the old account early, which can lose the numbers permanently. See switching providers without downtime.
Planning a move off your current provider? Send us the numbers on your bill and the date you want to be live, and we will tell you what the port requires and where we expect it to stall.