business phone · 6 min read
Business Number Porting Guide 2026: Timelines, Costs & Pitfalls
Business number porting explained: how LNP works, typical timelines, costs, required paperwork, common port-out rejections, and how to avoid service interruption.
Porting phone numbers between providers is one of the most anxiety-inducing parts of switching business phone systems — and it’s also one of the most automatable. The LNP (Local Number Portability) process is standardized across US carriers, but real-world delays still happen when paperwork is wrong or the losing carrier drags its feet. This guide covers the timeline, costs, required documents, and how to avoid the common pitfalls.
What is number porting?
Number porting moves a phone number from one service provider (the “losing carrier”) to another (“winning carrier”) without changing the number itself. The physical routing instruction changes, but the number stays the same from the customer’s perspective.
Federal regulations (US: FCC rules under the Telecommunications Act of 1996) guarantee the right to port any number. Carriers cannot block a port legally, though they can reject the specific port request if paperwork is incorrect or the account has unresolved issues.
Typical timeline
For most business ports:
- Simple local number (small business, single location): 2-5 business days
- Toll-free number: 3-10 business days (separate process)
- Multi-location or multi-carrier business port: 5-15 business days
- Enterprise port (1,000+ numbers): 10-30 business days with project management
- International number port: highly variable, 7 days to 12+ weeks depending on country
Porting completes on a specific “port date” pre-scheduled between carriers. On that date, at a specific time, routing changes and the number starts ringing at the new carrier. There’s a short window (minutes) where calls may briefly fail mid-swap.
What a port costs
For most US business porting:
- Losing carrier port-out fee: $0-$50 per number (legally capped, often waived for contracts ending)
- Winning carrier port-in fee: usually free as a customer-acquisition incentive. DialPhone, Dialpad, RingCentral, Zoom all port numbers for free on all plans.
- Expedited port fee: some losing carriers charge $15-$50 for faster turnaround
- Toll-free RespOrg change: typically $10-$25 per toll-free number
Most business ports end up completely free because winning carriers waive their side. Always confirm this in writing.
Documents you need to port
Every port requires a Letter of Authorization (LOA) signed by the authorized signatory on the account. The LOA authorizes the winning carrier to pull the number from the losing carrier.
LOA requires:
- Account number with the losing carrier
- Billing telephone number (BTN) — main number on the account
- Service address — matches exactly what’s on file with the losing carrier
- Authorized signatory name — typically the account owner or admin of record
- Signed signature (wet or electronic)
Provide a recent bill (within 30 days) from the losing carrier to verify account details.
This is where most ports get rejected. If your service address on file is “123 Main St” but your LOA says “123 Main Street” or your suite number is missing or your account has an old contact name, the losing carrier rejects the port request. You have to fix and resubmit, losing 3-5 business days.
Fix before starting the port: log in to the losing carrier’s admin portal and confirm:
- Exact service address (including unit/suite)
- Billing telephone number
- Account number (sometimes shown as “BAN” — Billing Account Number)
- Authorized signatory on file
- No outstanding balance or open work orders
Steps in a port
- Request — winning carrier collects the LOA, bill, and number list
- Submit — winning carrier submits FOC (Firm Order Commitment) request to losing carrier via an industry database (NPAC in the US)
- Validation — losing carrier validates LOA against account records. 1-3 business days.
- Acceptance or rejection — if accepted, the losing carrier commits to a port date. If rejected, the winning carrier gets a reason code and you fix and resubmit.
- Port date scheduled — both carriers agree to a specific date and time (usually 4-10 business days after FOC).
- Port executes — at the scheduled time, routing changes. Calls to the number start ringing at the winning carrier.
- Old service deactivates — typically a few hours to a few days after port; confirm with losing carrier.
Common rejection reasons
- Address mismatch — most common
- Account number incorrect — check both BAN and account number variants
- Authorized signatory not on account — LOA signer must match carrier records
- Past-due balance — pay it first
- Active contract with early-termination — port proceeds but you may owe the contract balance
- Unresolved trouble ticket — close open tickets first
- Recent SIM swap fraud alert — carriers sometimes freeze ports for 24-72 hours after account changes
If rejected, the winning carrier passes the reason to you. Fix and resubmit — usually takes another 1-3 business days.
Parallel running: avoiding service interruption
The classic port mistake: cut over on port date, discover something is broken, can’t roll back immediately.
Avoid by running parallel for 30-60 days:
- Keep the losing carrier’s service active with call forwarding to the new number
- Port the number to the new carrier
- New provider answers the call; if anything fails, unport or re-forward
- After 30-60 days of clean operation, cancel the losing carrier
The 30-60 day parallel doubles your phone cost for that window — but eliminates the “something broke, can’t reverse” nightmare. On large deployments, mandatory.
What’s different for toll-free numbers
Toll-free (800, 888, 877, 866, 855, 844, 833) numbers don’t go through the LNP process. They’re managed by a RespOrg (Responsible Organization) in the SMS/800 database.
Process is similar:
- LOA signed by authorized signatory
- Winning RespOrg submits change to SMS/800
- Takes 1-5 business days typically
- Routes change on the agreed date
Most business phone vendors (DialPhone, RingCentral, 8x8) act as RespOrgs and handle this transparently.
What’s different for MS Teams and on-premises PBX
Microsoft Teams numbers can be:
- Microsoft Calling Plans — ported to/from Microsoft following standard LNP
- Operator Connect — number stays with the operator (DialPhone, AT&T, etc.); minimal process on the customer side
- Direct Routing — number stays with your SIP trunking provider; change the SBC config
On-premises PBX (Avaya, Mitel, NEC) — numbers typically ride on SIP trunks from a carrier (Verizon, AT&T, Bandwidth, DialPhone SIP). Port the trunks; the PBX keeps running until the customer chooses to replace the PBX itself.
How DialPhone handles porting
On every DialPhone plan:
- Free port-in fee (all plans)
- White-glove migration project manager for teams of 25+ seats
- Dedicated porting ops team handles LOA, bill, address validation
- Parallel-running support included at no charge during cutover
- Typical ports complete in 2-5 business days for US local numbers
- Enterprise batch porting (100-5,000 numbers) handled by Professional Services
See the DialPhone pricing page for plan details.
Checklist before you start a port
- Identify every number to port (main, DIDs, toll-free, fax)
- Confirm exact service address on losing carrier
- Confirm account number and billing telephone number
- Confirm authorized signatory
- Pay any outstanding balance
- Close open trouble tickets
- Collect a recent (within 30 days) bill
- Sign LOA with the winning carrier
- Agree on port date
- Keep losing carrier active for 30-60 days after port
Related resources
- DialPhone pricing — free number porting on all plans
- Choose a business phone system (8-step guide)
- Number porting glossary
- Start a 14-day trial
Number porting failure is usually caused by paperwork, not the technical port. Fix the address, account number, and signatory up-front and 95% of ports go through clean on the first try.
About the author
Business Communications Research Team
The DialPhone Content Team researches and writes comparative analyses, how-to guides, and technical explainers covering AI-native business communications. Every comparative claim on DialPhone is verified quarterly against the competitor's public pricing and feature pages, with source URLs published on the article. The team works alongside DialPhone product managers, compliance officers, and customer success leaders to ground articles in real deployment experience across 500,000+ businesses and 46+ countries.