Phone Number Porting Checklist for Small Business

Phone Number Porting Checklist for Small Business IT

Phone number porting is the process of moving existing business telephone numbers from one carrier or provider to another so customers keep the same dial-in numbers while you change the underlying phone system — often onto VoIP trunks and softphones. For roughly 20–100 person companies, a good port is less about marketing “keep your number” slogans and more about inventorying every DID and hunt group, assembling a clean Letter of Authorisation (LOA) pack, timing the cutover so softphones and trunks are ready, and knowing what to do if a number rejects or a weekend fails. This playbook is a practical phone-number-porting checklist for IT managers: what to gather, how to run cutover day, and how US vs UK process differs at a high level — with a link to our UK-specific migration guide for Ofcom detail — without inventing timelines, rejection rates, or a hosted-PBX pitch.

What is phone number porting (and how is it different from getting new VoIP DIDs)?

Phone number porting moves telephone numbers you already own from a losing carrier to a winning provider. Callers keep dialling the same digits; your trunks, softphones, or desk phones change underneath.

Buying new VoIP DIDs is different: you get fresh numbers and optionally forward the old ones. Porting preserves the public dial-in identity. New DIDs are faster when you do not need legacy numbers, but they force customers and directories to change. Most SMB cutovers that care about the main line and key DIDs choose to port a phone number rather than abandon the estate.

Porting is not the same as SIP trunking (channel capacity), softphone setup (endpoint registration), or temporary call forwarding (a bridge while you wait). Those sit beside the port; they are not the move of the number itself.

Porting vs related phone work

• Topic: Phone number porting — Job: Move existing numbers to a new carrier/system — Not the same as: Buying brand-new VoIP DIDs
• Topic: SIP trunking — Job: Concurrent call paths / provider capacity — Not the same as: The regulatory move of the number itself
• Topic: Softphone setup — Job: App/device registration and day-one config — Not the same as: Keeping the public dial-in number
• Topic: UK porting guide (live) — Job: UK Ofcom / PAC / gaining-provider detail — Not the same as: This general SMB cutover playbook
• Topic: Call forwarding (temporary) — Job: Bridge old → new during transition — Not the same as: Completing the port

When should a small business port numbers vs keep the old lines and forward temporarily?

Port when numbers are how customers find you: main line, sales DIDs, support hunt groups, partner-published lines. Keep (or replace later) spare DIDs nobody dials and temporary project lines.

Temporary forwarding is a useful bridge: leave losing-carrier lines live, forward to new trunks or softphones, and prove inbound before the formal port completes. It is not a substitute for finishing the port if you intend to cancel the old account.

Decide early which special services stay put until verified: alarm lines, lift phones, fax if still required, and any complex ISDN remnants. Those often need a case-by-case check with both providers — criteria only.

What documents and inventory do you need before you submit a port (LOA pack)?

A rejected port usually starts with a messy pack. Before you ask the winning provider to submit:

1. Number inventory — main line, DIDs, hunt groups, fax (if still used), conference bridges, alarm/lift lines. Mark which must port vs can be replaced.
2. Owners — losing-carrier login, LOA signatory, cutover-day inbound tester, softphone/trunk owner.
3. Call-flow screenshots — auto-attendant, after-hours, queue targets. Rebuild on softphones/trunks; you do not “port” the IVR itself.
4. Contract awareness — early-termination risk on the losing carrier. Criteria only; not legal advice.
5. LOA / Letter of Authorisation — signatory matching the bill, legal name, billing address, account number, numbers in the winning provider’s required format.
6. Recent bill page showing the numbers (redact payment data). Name/address mismatches are a common reject reason — fix before submit.

Submit to the winning provider (the one you are moving *to*). Ask for the estimated port window and staging options. Keep old lines paid through cutover until inbound is proven on softphones.

For UK Ofcom / PAC / gaining-provider steps, use the live UK business phone number porting guide — this checklist is not a full UK deep-dive.

What does a practical phone number porting checklist look like for cutover week?

Use this extractable playbook as your runbook. Adjust owners and dates to your winning provider’s window — never invent a universal “X days” claim.

Week −2 to −1 — Inventory & owners

1. Export every number you care about: main line, DIDs, hunt groups, fax (if still used), conference bridges, alarm/lift lines — mark which must port vs can be replaced.
2. Name owners: losing-carrier login, LOA signatory, cutover-day inbound tester, softphone/trunk owner (link SIP trunk + softphone setup — do not rewrite those posts).
3. Screenshot or export current call flows: auto-attendant, after-hours, queue targets — rebuild on the new side.
4. Confirm contract / early-termination risk on the losing carrier — criteria only.

Week −1 — LOA pack & winning-provider submit

1. Assemble the LOA: signatory matching the bill, legal name, billing address, account number, numbers in the required format.
2. Attach a recent bill page that shows the numbers (redact payment data). Fix name/address mismatches before submit.
3. Submit to the winning provider. Ask for estimated port window and staging options.
4. Book a rollback window: keep old lines paid through cutover+N days until inbound is proven.

Cutover week — Softphone / trunk readiness

1. Softphones registered and tested with temporary/test DIDs first (softphone setup checklist).
2. SIP trunk / channels sized for busy hour (SIP trunk for small business); firewall/NAT and QoS checked (VoIP firewall ports + VoIP network requirements).
3. Rebuild attendant / forward rules on the new side before the port completes — do not wait until numbers flip.
4. Agree a go/no-go time with the winning provider; have a mobile forward fallback if the main number slips.

Cutover day + 48h

1. When numbers flip: test inbound from an external mobile to main + 2–3 DIDs; check CLI presentation outbound.
2. Spot-check hunt groups / queues; fix misroutes before telling the whole company “we’re done”.
3. Monitor for 48 hours: rejected DIDs, one-way audio (network/firewall — link those posts), wrong after-hours greeting.
4. Only then cancel or cease the losing-carrier lines you no longer need — keep alarm/lift/fax until verified.

How do softphones, SIP trunks, and firewall/network prep fit into the port?

Porting moves the numbers. Softphones, trunks, and network hygiene decide whether those numbers sound usable on day one.

• Softphones — register and prove audio on temporary/test DIDs before the port window; retest inbound after numbers flip. Softphones are optional for testing inbound after a port — not a hosted-PBX pitch. Trials stay on sessiontalk.io.
• SIP trunks — size channels for busy hour and confirm failover before you depend on ported DIDs (SIP trunk guide).
• Firewall / NAT — verify SIP/RTP paths so endpoints do not fail after the flip (firewall ports checklist).
• Network QoS / Wi-Fi — so cutover does not sound like a broken network (VoIP network requirements).

Broader migration context lives in cloud PBX migration with softphones. If desk phones remain, keep IP phone buying and business phone system requirements as planning links — not a rewrite of this checklist.

How does UK vs US business number porting differ at a high level?

Both regions share the same SMB IT shape: inventory → clean authorisation pack → winning-provider submit → softphone/trunk readiness → cutover tests → cease old lines only after inbound is proven.

At a high level (not legal advice, not invented timelines):

• UK — Ofcom-backed rules and gaining-provider workflows (including PAC-style mechanisms where they apply). For UK operational detail, use the port business phone number UK guide — this post does not clone that Ofcom/PAC deep-dive.
• US — typically carrier LOA packs and winning-provider coordination against losing-carrier records. Windows vary by carrier pair; use your winning provider’s quoted process, not a blog’s invented average.

Cross-border estates should run two packs and two cutover windows rather than assuming one LOA covers both jurisdictions.

FAQ

What is phone number porting?

Moving your existing telephone numbers from one provider to another so callers keep dialling the same digits while your phone system or softphones change underneath.

How long does business number porting take?

It varies by country, carrier, and how clean your LOA pack is. Use your winning provider’s quoted window; there is no universal “X days” figure that fits every SMB port.

Can we port landlines onto VoIP / softphones?

Often yes for standard geographic business lines. Special services (some alarm lines, complex ISDN setups) need a case-by-case check with both providers — criteria only, no invented success rates.

Do we still need the UK porting guide if we read this checklist?

Yes if you are porting UK numbers — use the UK porting guide for UK-specific steps. This post is the general SMB inventory/cutover playbook (US + UK high-level).

What usually causes a rejected port?

Mismatched company name/address vs the bill, wrong account number, numbers listed in the wrong format, or numbers not eligible (still in contract complexity, or not on the account you named). Fix the pack and resubmit — no invented rejection percentages.

A clean port is an inventory and cutover discipline problem, not a marketing slogan. Gather the LOA pack early, prove softphones and trunks before numbers flip, and keep the UK Ofcom detail on the dedicated UK guide. When you are ready to test inbound on softphones after the port, start from sessiontalk.io.