How to port a toll-free number to another provider

Ask your new provider to submit a RespOrg change while you keep your current service active. That is a change of the responsible organization that controls your toll-free in the SMS/800 registry (the industry database for toll-free numbers). You’ll sign an LOA (letter of authorization), get an FOC (firm order commitment) date, and pre-stage routing so calls keep flowing at cut-over. Done right, your published 800 number stays reachable the whole time, and the process takes business days, not hours.

Toll-free porting is a RespOrg change, not a local port

Toll-free numbers in the US and Canada live in SMS/800, the industry registry for 8XX numbers. The company that controls your number in that registry is the RespOrg (responsible organization). When you port a toll-free number, you don’t move a physical line. You move control of the number in SMS/800 from one RespOrg to another.

That’s different from local number portability (LNP) for geographic numbers. For locals you submit an LSR (local service request) tied to a service address and a rate center (the local area that defines which numbers are local to each other). For toll-free you submit a RespOrg change request. No service address match is needed, but your account details must still match the record the losing provider has for you.

If you’re outside the US or Canada, other countries use different terms and systems. This guide covers the US and Canada toll-free only. For toll-free basics and use cases, see our overview in Toll-free numbers: a practical guide.

Step-by-step: how to port a toll-free number to another provider

You’ll finish with an FOC date (and time window) from your new provider. Plan for business days, not hours, and avoid your peak call times for cut-over.

1. Collect a recent bill and, if you can, the CSR (customer service record).
   These show your legal business name, service address, and account number or BTN (billing telephone number). The LOA must match these. A recent bill also proves you control the number today. If you can’t get a CSR, a clear current bill often works.

2. Fill and sign an LOA (letter of authorization).
   Include your legal name, service address, contact email and phone, the list of toll-free numbers, and your current provider or RespOrg ID (the identifier of the organization controlling your toll-free) if you know it. A hand-signed or e-signed LOA both work if the new provider accepts them. Make sure the signer is an authorized contact on the account.

3. Provide any account number, PIN, or port-out passcode.
   Some providers set a port-out PIN for security. If you don’t know it, ask your current provider to set or reset it before you submit the request.

4. Submit the paperwork to your new provider and keep the number active.
   Do not cancel, remove features, or change routing with the old provider during porting. If the number goes inactive, the RespOrg change will fail.

5. Review the tentative FOC date and time window.
   Your new provider will return a proposed date after the losing provider responds. Ask for a window outside your peak hours. Confirm the time zone of the window, and set calendar holds for your team.

6. Pre-stage routing on the new platform and test on a temp number if you can.
   Build your queues, business hours, IVR (interactive voice response, a menu where callers press keys) options, and targets in advance. If the new provider offers a temporary test number, route it the same way and place test calls. Fix anything now, before cut-over. For routing ideas and patterns, see How toll-free call forwarding works.

7. On FOC day, verify live traffic as the window opens.
   Make test calls from at least two major mobile carriers and a landline. Watch real-time logs if your platform has them. Confirm the caller’s number (ANI, the number your system sees) passes through, recordings work if enabled, and analytics populate.

How to confirm it worked: inbound calls reach your new platform. Callers hit the right menu or queue, agents’ phones ring per your rules, and your logs and recordings show new traffic. If any test fails, use your overflow targets while you adjust routing.

What your current provider can and can’t block

If you authorize the RespOrg change and your details match their record, they must allow the port. You can still port even if you owe money or are in a contract. They may bill you fees or early termination under your agreement, but that does not stop the port.

They can reject a request if the LOA does not match their CSR, the number is inactive, the signer is not authorized, or a required PIN is missing. They can also control scheduling within business days and typical operating hours. Same-day releases are uncommon.

Do not cancel service or remove forwarding before the FOC date. That can make the number inactive and block the change. The FCC explains your portability rights here: FCC guide to number porting.

Toll-free number porting time: what’s realistic

Plan for business days, not hours. Small, clean requests move faster. Large batches and mismatched records take longer. The start-to-finish time depends on how quickly the losing provider validates your details and agrees on the FOC date.

The FOC date (with a time window) is the key milestone. It’s when control in SMS/800 switches to your new RespOrg. Ask the new provider to share the window in your time zone. Set your team to be on standby to test at the start of that window.

Most RespOrg changes do not cut over on weekends or major holidays. Pick a weekday window that is quiet for your business. If the status stalls or no one can tell you why, ask your new provider to request the specific rejection reason or the CSR from the losing provider. Clear, specific notes prevent repeat rejections.

If you manage many 8XX numbers, organize them by brand or campaign so you can move them in sensible groups and watch traffic closely. These tips pair well with the tactics in Managing multiple toll-free numbers.

Common toll-free port rejections and how to fix them

A name or address mismatch will trigger a reject. Your LOA must match the CSR or a recent bill. Ask the losing provider for the exact legal name and service address on file, update the LOA, and resubmit.

If the number is tied to the wrong account or not on the RespOrg you listed, the order will fail. Sometimes the number sits on a different account or RespOrg than you think. Ask your new provider to run a RespOrg lookup (and confirm the current provider name) and correct the request.

An unauthorized signer leads to a fast reject. The LOA must be signed by the listed admin or an authorized contact. Re-sign with the proper contact or add a letter naming the signer as an authorized agent.

Inactive or suspended numbers cannot move. If billing or service was cut off, restore service first, then re-submit the port.

Missing or wrong PINs or passcodes block releases. Many providers require a port-out PIN. Request or reset it with the losing provider and add it to the order.

Poor scans and stale bill copies cause delays. If your uploads are blurry or the bill is old, the losing provider may reject. Send a clear scan and a recent bill from the current cycle.

To read and clear a rejection, ask your new provider for the exact reject code and note, not a summary. Each note usually names the field that failed (name, address, account, PIN). Fix only that field and re-file. Re-submitting the same bad data repeats the delay.

Keep calls flowing on cut-over day

Pre-stage routing and a rollback plan

Before the FOC window, build the same or better routing on the new platform. Set your targets, round-robin or priority rules, business hours, queue with hold music, and voicemail fallback. Keep ring time per leg short, about 20 to 25 seconds, so calls move to the next target quickly. A short queue can catch callers while agents pick up.

If you had an IVR at the old provider, mirror the menu options and key presses. Place test calls to the temporary test number if offered. Confirm recordings, whispers, and analytics where used. Have overflow and failover targets ready in case one agent or endpoint is busy, and consider a backup SIP or browser endpoint if you rely on mobiles. For structured backup plans, see Failover call forwarding.

As the window opens, run your test plan. Make a call from two major mobile carriers and a landline, then a call from your office SIP phone if you have one. Check that the caller’s number shows in your logs, IVR selections route to the right place, and recordings (if enabled) save under the right campaign.

If something looks wrong after FOC, call both providers. Keep the old account active for a short time so they can forward the toll-free to a working destination while you fix routing. Not every provider will do this, but many will help if the RespOrg change is complete and you need a temporary bridge.

One short aside: if you’re moving to a cloud call-routing platform like CallFlow, you can prebuild queues, IVR menus, schedules, and overflow. The number is ready the second it ports.

If you route calls from outside the US

Owning a toll-free number for the US and Canada and sending calls to teams in India, the Philippines, Thailand, Bangladesh, or Pakistan is common. The RespOrg change rules still apply because the number itself is a toll-free number for the US and Canada. Your delivery path to agents (mobile, landline, SIP, or browser) is separate.

On FOC day, test both sides. Place test calls from US carriers into the toll-free, then watch delivery to your agent phones or softphones. Check time zones on schedules and IVRs so after-hours rules don’t start at the wrong local time. If you rely on SIP or a browser agent, confirm registration, codecs (audio formats your phones support), and answer time before the window.

What to do next

• Ask your current provider for the CSR. Gather a recent bill and the authorized signer’s name and email.
• Pick a weekday FOC window that avoids your peak hours. Put your test callers and agents on the calendar.
• Pre-stage routing, overflow, and voicemail with the new provider. Mirror any IVR options you use today.
• Set a test checklist: who calls, from which carriers, which menus to press, what to verify in logs and recordings.
• If you need queues, IVR, and analytics after porting, create a CallFlow account and set up your routes before cut-over. CallFlow provisions toll-free numbers from a prepaid wallet with usage-only billing, and forwards to phones, SIP, or browser agents.

Start configuring routing for your toll-free now — create a CallFlow account — or talk to us.