Rules
Part of Business phone numbers: records, not lines
Business phone numbers migration: record checks and cutover
Business phone numbers migration starts with matching the losing provider’s account record, submitting an authorized request, and testing the cutover.
Business phone numbers migration is the visible part of a communications change: customers notice immediately if the move goes wrong. It is also the step often left until the week of the cutover. Which provider to move to belongs to provider comparisons; this guide starts once that is settled.
What to take away
- The transfer is checked against the record your current provider holds. Correct that record weeks in advance and most rejections never happen.
- Never cancel the old service to trigger a move. Canceling can release the number rather than transfer it.
- Test from an outside line on another network after the move, before you tell anyone it is done.
Fix the record first
A transfer request is compared, field by field, against the losing provider’s records.
A mismatch can trigger a rejection, and the reason given is often unhelpful. Before you request anything, get a copy of the Customer Service Record (CSR) and a recent bill, then check the fields below. Ask the provider which fields it uses to validate the request.
| Field | Common problem |
|---|
Fields that cause transfer rejections
- Account nametrading or former name
- Account numberdiffers from bill
- Service addressold suite or typo
- Authorized contactleft or contractor
- Number rangepartial block listed
Use this field-by-field checklist to compare your paperwork with the losing provider’s account record:
- Account holder or legal business name:Check spelling and whether the record uses a legal name or a DBA.
- Service and billing addresses:Match the addresses on file; do not assume they are interchangeable.
- Account number:Check every digit against the bill or CSR.
- PIN, passcode, or other security information:Confirm what the provider requires and that it is current.
- Billing telephone number (BTN):On a multi-line account, verify which number is listed as the main billing number.
- Authorized contact and signature:Make sure the person signing the Letter of Authorization (LOA) is authorized on the account.
- Numbers to transfer:List every number, including each number in a block, and identify any you are not moving.
Ask the losing provider to confirm the validated fields in writing. The FCC consumer guide Porting: Keeping Your Phone Number When You Change Providers explains the number-porting process and common failure points. The receiving provider supplies its Letter of Authorization (LOA); there is no single FCC porting form.
For local number portability, the FCC’s rules are in 47 CFR Part 52, including § 52.23. Number routing records are handled through the Number Portability Administration Center (NPAC), administered by iconectiv.
Submit and verify the port
Transfer sequence, in order
- Correct the account record
- Order new service on temporary numbers
- Build and test routing
- Submit transfer with exact number list
- Agree window and brief staff
- Let transfer complete, cancel nothing
- Test from outside immediately
- Confirm each number, then cancel
after the cutover. For a VoIP port, confirm any technology-specific submission requirements and the requested port date with the receiving provider.
First: Inventory every number, the service attached to it, and the account it is on.
Second: Request the CSR and a recent bill from the losing provider. Compare their account details with the checklist above.
Third: Correct mismatches with the losing provider before submitting a port request, and get confirmation of the corrected record.
Fourth: Confirm which numbers can move together, whether any are in a block, and whether your contract has a term or restriction that affects the move.
Fifth: Ask the receiving provider to submit the port request. Complete its LOA and provide the bill and account-holder verification it requires. A CSR is useful for checking the record; ask the receiving provider whether it needs a copy.
Sixth: Get the requested port date and the numbers included in the request in writing. Keep the old service active, and do not cancel or make account changes that could disrupt the transfer.
Seventh: On the cutover day, test incoming and outgoing calls to each number from outside your business network. Confirm emergency-call handling and the dispatchable location with the provider; do not assume a successful regular call verifies those details.
Eighth: Reconcile the results against your number inventory, resolve any missing or misrouted numbers, and cancel the old service only after the transferred numbers work.
Step eight is where blocks bite. Numbers frequently move in groups, and a missing one is invisible until a customer calls it. A written list with a tick per number is the only reliable check.
What can go with the number, and what cannot
What can go with the number
Advantages
- The number itself moves. That is the point.
Drawbacks
- Voicemail messages do not. Save anything you need first.
- Any service attached to the line does not: an alarm line, a lift phone, a card terminal, a fax machine somebody forgot. These need their own plan,
What moves with the number
Moves
- The number
- Yes
- Voicemail messages
- No
- Alarm, lift, card terminal
- No
- Landline texts
- Maybe
- Directory listings
- No
Does not move
- The number
- No
- Voicemail messages
- Yes
- Alarm, lift, card terminal
- Yes
- Landline texts
- Maybe
- Directory listings
- Yes
and they cause a safety problem rather than an inconvenience.
- Text messages sent to a landline numbermay or may not follow. Ask specifically if you have ever received them, and check what else on the account depends on the number; toll-free numbers are held in the Toll-Free Number Registry, administered by Somos. A Responsible Organization (RespOrg) manages the toll-free assignment, and numbers move under their own process.
- Directory listingsare a separate arrangement. They do not update themselves.
The week around the transfer
Keep the old service live throughout. Have somebody call the main number from
a mobile every hour on the day, and log the result. Watch for the failure that is easy to miss: calls succeed from inside your own building because they never leave your network, while outside callers reach nothing.
Confirm with the new provider how emergency calls will be handled from the moved numbers and what dispatchable location is registered. The FCC’s multi-line telephone system requirements implement Kari’s Law and Section 506 of the RAY BAUM’S Act. The FCC’s 2019 order, FCC 19-76, Implementing Kari’s Law and Section 506 of RAY BAUM’S Act, addresses direct 911 dialing, notification, and dispatchable location for multi-line telephone systems. Confirm the provider’s emergency-call settings rather than assuming they move with the number.
The business phone number account record is central to a transfer: match the account holder and details on file before submitting a request. For background on choosing a system, see business phone numbers software.
Common questions
How long does a transfer take?
FCC guidance gives one business day as the general timeframe for a simple wireless-to-wireless port. That is not a promised timeframe for a business wireline, VoIP, or multi-line transfer. Ask the receiving provider for the committed date in writing and keep the old service active until testing is complete.
Can we move some numbers and not others?
Often, and sometimes not if they sit in a block. Ask before you design a staged plan around it.
What happens if the transfer is rejected?
Read the reason, fix the record, resubmit. It is almost always administrative. Each round trip costs days, which is the argument for fixing the record first.
Can the old provider refuse to let us go?
They can reject a request that does not match their record, and your contract may still impose obligations after service ends. They cannot keep a number that is properly requested by the account holder. Confirm any transfer requirements with both providers before scheduling.
