Skip to content
AI Dialer

Operations

Porting a business phone number: how it works and what goes wrong

  • 7 min read

By Last updated

The short answer

Porting moves a phone number from one provider to another while keeping the number itself. You submit a request to the gaining provider with proof you control the account; the losing provider validates it and releases the number on an agreed date. Most rejections are caused by details that do not match the current account exactly.

Number portability is a right, not a favour: in most countries a provider cannot refuse to release a number simply because they would rather keep your business. What they can do is reject a request that does not match their records, and that is where essentially all porting pain comes from.

What actually happens

  1. 1

    You ask the gaining provider to port in

    Not the losing one. Telling your current provider you are leaving before the port is submitted invites a retention call and, occasionally, account changes that break the port.
  2. 2

    You supply proof of control

    A recent bill, the account number, the service address, and a Letter of Authorisation signed by the account holder. The details must match the losing provider's records character for character.
  3. 3

    The losing provider validates

    They check the details against the account. Any mismatch is a rejection, and rejection messages are often unhelpfully terse.
  4. 4

    A firm order commitment date is agreed

    This is the cut-over date and time. Once set, it is a scheduled event rather than a moving target.
  5. 5

    The number cuts over

    Routing changes at the agreed time. In practice the switch takes minutes, not hours; the long part was the paperwork.

The four reasons ports get rejected

Rejection causes, in rough order of frequency
CauseWhat it looks likeFix
Details do not matchBusiness name, address, or account number differs from the losing provider's recordCopy them verbatim from a current bill, including abbreviations like “St” vs “Street”
A port-out lock or PINThe account has porting protection enabledRequest the port-out PIN from the current provider before submitting
Pending account changesA plan change, address update, or open ticket freezes the numberLet anything in flight complete first, then submit
Unpaid balance or contract termThe account is in arrears or inside a minimum termSettle it: the number still ports, but early termination charges may apply

The single best predictor of a clean port

A copy of the most recent bill, and typing every field from it exactly as printed. More ports fail on “Suite 4” versus “Ste 4” than on anything technical.

How long it takes

Timelines vary by country and number type, and anyone quoting a single figure is guessing. Broad expectations:

  • Simple ports (a handful of numbers on one account with clean details) typically take a few business days.
  • Toll-free numbers usually move faster, because they are administered through a shared national database rather than by a local carrier.
  • Complex ports (many numbers, multiple accounts, or a legacy PRI) take longer, and are best done in batches rather than all at once.
  • International ports vary enormously by regulator, and some markets require documents that take time to obtain.

Add buffer. A port scheduled the day before a campaign launch is a port that will slip.

Avoiding downtime on cut-over day

The number itself moves in minutes. What causes outages is everything around it being unprepared.

  1. 1

    Build the new setup before the port

    Users, queues, routing, greetings, and business hours configured and tested on a temporary number. Cut-over day should change one thing only: where the number points.
  2. 2

    Test the temporary number end to end

    Call it, let it ring out, leave a voicemail, transfer it. Whatever is broken there will be broken on your real number too.
  3. 3

    Set the cut-over for a quiet hour

    Early morning on a weekday, not Friday afternoon. You want the team available if something needs adjusting.
  4. 4

    Keep the old service alive for a week

    Do not cancel the old account on port day. If anything routes oddly you want the fallback, and cancelling early can strand numbers you did not port.
  5. 5

    Re-register CNAM after the port

    Caller ID name records do not always follow the number. Check what displays on a real handset within a day or two; see CNAM.

What ports and what does not

  • The number ports. That is the whole point, and it is a regulatory right.
  • Reputation and history follow the number, which is usually good: an established number with a clean record keeps its standing.
  • CNAM often does not follow. Re-register it and verify.
  • Voicemail messages do not port. Download anything you need to keep beforehand.
  • Call history and recordings do not port. Export them from the old provider first; access usually ends when the account closes.
  • 10DLC registration does not port. Messaging campaigns must be re-registered with the new provider; see the 10DLC guide.

Export before you cancel, not after

Once the old account closes, call records and recordings are frequently unrecoverable. If any of it has a retention obligation attached (regulated industries especially), export it while you still have a login.

Porting out, and why you should ask about it early

The question worth asking a prospective provider is not “can I port in?”; everyone says yes. It is “what does porting out look like?” How long does it take, is there a fee, is there a port-out lock by default, and how do I export my call records?

The answer tells you what renewal negotiations will feel like in two years. A provider that makes leaving easy is a provider confident you will not want to, and that confidence is worth more than most feature comparisons.

Porting several numbers at once

A single number is straightforward. A block of thirty, spread across two accounts and a legacy PRI, is a project, and treating it like a bigger version of the simple case is how businesses end up with a week of partially working phones.

  1. Inventory first. List every number, which account it sits on, what it currently does, and whether anyone still calls it. Most businesses discover numbers nobody can account for, and porting those is pure cost.
  2. Group by account, not by department. Ports are validated per losing account, so numbers split across two accounts are two ports whatever your org chart says.
  3. Port the least critical group first. It surfaces the paperwork problems on numbers whose brief disruption nobody notices.
  4. Never split a billing telephone number from its block unless you have confirmed the losing provider supports partial ports. Removing the main number on an account can close the account and strand everything else.
  5. Keep a written cut-over runbook, with the order, the times, and who verifies each number afterwards.

Partial ports are where projects go wrong

Moving some numbers from an account while leaving others behind is supported by most carriers but not all, and the failure mode is severe: the account closes and the remaining numbers are released. Confirm support in writing before submitting a partial port.

What to verify the day after cut-over

The port completing is not the same as the phone working. Run a short checklist on each ported number rather than waiting for a customer to report the gap.

  • Inbound rings the right place, including outside business hours and when the first destination is busy.
  • Outbound presents the right caller ID. Ports frequently complete with the outbound identity still pointing at a default number.
  • The caller ID name displays, checked on a real handset rather than in the admin console.
  • Voicemail answers and delivers. Confirm the message actually arrives where someone will see it.
  • Texting works, if the number is text-enabled, and remember that messaging registration does not port.
  • Emergency calling is registered to the right address, which is a legal requirement in many jurisdictions and is easy to forget on a number that moved.

Do this on the day, not at the end of the week. Every one of these is cheap to fix immediately and awkward to explain after a customer has run into it.

Frequently asked questions

How long does it take to port a phone number?
A few business days for a simple port with clean details, longer for large or complex ones. Toll-free numbers usually move faster because they are administered through a shared national database. International timelines vary widely by regulator, so build in buffer rather than scheduling a port right before a launch.
Will my phone service be down during a port?
The cut-over itself takes minutes. Outages come from the new setup not being ready, so build and test routing, greetings, and users on a temporary number first, so cut-over day changes only where the number points.
Why was my port request rejected?
Almost always because a detail did not match the losing provider's records exactly: business name, service address, or account number. Other common causes are a port-out lock, pending account changes, or an unpaid balance. Copy every field verbatim from a current bill.
Can my provider refuse to release my number?
In most countries, no: number portability is a regulatory right. They can reject a request whose details do not match their records, and they can bill an outstanding balance or early termination charge, but they cannot simply keep the number because you are leaving.
Does my caller ID name port with the number?
Often not. CNAM records live in a separate database and are frequently not carried across, so re-register the name with your new provider and verify what actually displays by calling a real handset a day or two later.
Should I cancel my old service before porting?
No, never. Cancelling releases the number back to the carrier and the port will fail. Keep the old account active until the port completes, and for about a week afterwards as a fallback.

Sources

  1. Telemarketing Sales Rule — Federal Trade CommissionDo-not-call obligations, abandonment-rate limits for predictive dialing, and required call disclosures.
  2. 47 U.S.C. § 227 — Restrictions on the use of telephone equipment — Cornell Legal Information InstituteThe Telephone Consumer Protection Act itself — the consent requirements, calling-hours limits, and private right of action.
  3. National Do Not Call Registry — Federal Trade CommissionThe registry that outbound calling lists must be scrubbed against.

See it working: cloud call centre

Cloud call centre software runs your inbound and outbound phone operation from a browser: queues, routing, dialling, recording, and reporting, with no on-premise hardware. AI Dialer prices it by usage rather than per seat, so cost tracks call volume instead of headcount.

  • No subscription
  • Numbers in 100+ countries
  • Compliance built in
Get early accessBring your numbers with you