How to Port a Business Phone Number: A UK Migration Checklist

How to Port a Business Phone Number: A UK Migration Checklist

If you need to port a business phone number, the number itself is only one part of the move. Your company may also depend on call menus, hunt groups, caller identity, voicemail, out-of-hours routing and broadband services attached to the old account. A safe UK migration therefore starts with evidence and continuity planning—not with cancelling the current service.

Number portability allows customers to keep a telephone number when changing provider. In practice, the gaining provider normally coordinates the request using details that must match the losing provider's records. The safest approach is to keep the existing service active, build the replacement calling environment in parallel and treat the port date as a controlled cutover.

What a number port changes—and what it may leave behind

A port transfers the right to serve calls for an eligible telephone number from one provider to another. It does not automatically reproduce the phone system around that number.

For example, moving a geographic number such as 020, 0161 or 0131 does not guarantee that the following will move with it:

• the existing Interactive Voice Response (IVR) menu;
• call queues, hunt groups or overflow rules;
• voicemail messages and greetings;
• call recordings or historical call reports;
• fax, alarm, door-entry or payment-terminal services;
• Short Message Service (SMS) capability;
• directory listings;
• outbound caller line identification;
• the emergency location associated with a Voice over Internet Protocol (VoIP) user;
• broadband or other services billed on the same account.

Treat each item as a separate migration requirement. If an old line carries both broadband and a telephone number, ask both providers in writing what happens when the number leaves. Do not assume the connectivity will remain live, and do not cease the line yourself unless the gaining provider confirms that step.

The UK communications regulator Ofcom describes number portability as the facility that lets customers keep numbers when changing provider. That principle is useful, but eligibility, lead time, paperwork and service dependencies still vary by number type and providers. Get the proposed process and responsibilities in writing for your actual inventory.

Before you port a business phone number, map the estate

Start with a number register. A small company may advertise one main number while quietly using several others for direct dialling, marketing campaigns, card machines, lift lines, faxes or individual sites. Missing one can create an outage weeks after the apparent migration succeeds.

For every number or range, record:

• the full number in international and national format;
• the current provider and account number;
• the exact legal or account-holder name;
• the installation or service address on the bill;
• whether it is geographic, non-geographic, mobile or part of a block;
• whether customers call it, staff present it outbound, or both;
• its current destination and opening-hours behaviour;
• associated broadband, hardware or special services;
• the business owner who can approve changes;
• the evidence that will prove it works after cutover.

Do not rely on the receptionist's contact list alone. Compare invoices, provider portals, website contact pages, Google Business Profile entries, email signatures, printed material, vehicle graphics and recent call-detail records. A number with little traffic may still belong to an important supplier, longstanding customer or emergency process.

This inventory also prevents a common scope error: requesting one number from a range when the provider treats the numbers as a block. Ask whether the main number, direct-dial numbers and any dormant numbers must move together. If only part of a range can move, obtain an explicit explanation of what will happen to the rest.

If the port is part of a broader buying exercise, use the small-business phone-system requirements checklist to document call flows, resilience, user roles and security before selecting the destination service. Porting preserves a known contact point; it does not correct an unclear phone-system design.

Assemble evidence that matches the losing provider's records

Many delays begin with a small mismatch: a trading name instead of the account name, a head-office address instead of the installation address, or an account number copied from the wrong service. Build the evidence pack before submitting anything.

Include recent bills, the current account number, the exact account-holder name, service addresses, the complete number list and a named authorised contact. Your gaining provider may also require a signed Letter of Authority (LOA). Use its current form and follow its signing instructions rather than copying an old letter from a previous migration.

Run a two-person check. One person reads the request against the source bill; the other confirms that every number in scope appears on both the authorisation and the migration plan. Save the submitted version and note when and how it was sent.

Avoid making unrelated account changes while the request is open. Renaming the account, moving the service address, changing the number range or placing a cancellation can create conflicting records. If a change is essential, tell the gaining provider before it is made and ask whether the port request should be paused or resubmitted.

Ask for a rejection-resolution route before submitting

A credible gaining provider should explain who owns the request, how it reports a rejection and what evidence it needs to resolve one. Record:

• the provider's porting case reference;
• the named team or escalation channel;
• the submitted number list;
• the requested and confirmed cutover dates;
• any rejection code and plain-English explanation;
• the next action, owner and target update time.

This turns “the port failed” into a resolvable case. It also prevents several employees from sending different documents to different support agents.

Run the migration in seven controlled stages

Business number porting is safer when the team uses gates. Do not progress because a calendar date is approaching; progress because the required evidence is complete.

1. Confirm portability and scope

Ask the gaining provider to check every number and range. Confirm whether geographic, non-geographic and mobile numbers use different processes. Identify linked services and decide which ones must be rebuilt, replaced or ceased separately.

2. Freeze risky changes

Keep the losing-provider service active and paid. Freeze non-essential account edits, routing changes and cancellations. Tell finance not to reject final invoices simply because the new platform is being configured.

3. Build the destination before the port

Create users, extensions, call queues, opening hours, voicemail, announcements and failover routes on the new system. Assign least-privilege administration and test user removal as well as user creation. The practical small-business phone-system setup plan covers the wider rollout sequence.

4. Test with temporary numbers

Use temporary or test numbers to call every route without disturbing the published business number. Test office phones, desktop clients and mobile softphones over office Wi-Fi, home broadband and mobile data. Check transfer behaviour, Dual-Tone Multi-Frequency (DTMF) keypad input, queue announcements and voicemail delivery.

5. Submit one controlled request

Submit the validated evidence pack through the gaining provider. Log its acknowledgement and case reference. Do not submit duplicate requests through another reseller or carrier; competing orders can make ownership harder to diagnose.

6. Confirm the cutover command sheet

When the date is accepted, name a migration lead, a technical contact at the gaining provider, an internal tester and a customer-communications owner. Agree the test order, evidence format and escalation route. Avoid a cutover beside a product launch, payroll deadline or other period when staff cannot investigate calling issues.

7. Accept the service only after real tests

A successful inbound call from one mobile is not enough. Test from multiple networks where practical, run simultaneous calls, navigate the IVR, wait in the queue, transfer to office and mobile users, reach voicemail and return a call with the intended business identity. Log pass or fail for every critical route.

Keep customers reachable while the port is pending

The old service usually continues to receive calls while a port is pending, but your exact arrangements must be confirmed with the providers. Build continuity around uncertainty rather than promising the team an invisible switch.

Possible controls include:

• keeping trained staff available on both old and new endpoints;
• temporarily forwarding the old service to a tested destination, if supported;
• publishing a secondary contact route for priority customers;
• giving key suppliers a monitored email address;
• scheduling extra call monitoring around cutover;
• preparing a short website or status message that can be activated if needed.

Call forwarding can help, but it has limits. It may change the caller identity shown to staff, create additional charges, reduce control over queue behaviour or fail if the source service is ceased. Read the business call-forwarding guide and test the exact route before treating it as a recovery plan.

Your continuity note should be specific: who activates the alternative, where calls land, how staff recognise them, how long the route can remain, and who decides to remove it. “Use mobiles if there is a problem” is not an operational plan.

Why number ports are rejected or appear only partly complete

A rejection is not always a technical fault. Common causes include data mismatch, missing authorisation, an incorrect number range, an active order on the account or a service dependency that was not declared. Ask for the exact reason rather than repeatedly resubmitting the same pack.

Partial symptoms also need careful classification:

Inbound calls work, but outbound caller identity is wrong

The number may be serving inbound traffic while outbound presentation remains unconfigured or unauthorised. Ask the new provider to verify caller identity settings and any required evidence. Do not let users present a number they are not entitled to use.

Calls arrive from some networks but not others

Capture the calling number, called number, date, time, network and result for each test. This evidence helps the provider investigate routing propagation rather than treating the report as a vague intermittent fault.

Voice works, but text messages do not

Voice porting does not prove that SMS will transfer or be supported on the new service. If the number is used for appointment reminders, one-time codes or customer replies, make SMS a separate written requirement and test it independently.

The main number works, but direct dials fail

Check whether the full Direct Dial Inward (DDI) range was included and accepted. Compare the final provider confirmation with the original number register, then test the lowest, highest and representative middle numbers in each block.

The phone number moved, but another service stopped

This points back to a linked-service dependency. Use the pre-port inventory to show what shared the old account or access line. Escalate through both providers with timestamps and account references; do not place a second port request as a guess.

Use a day-of-port command sheet

Keep the cutover record short enough to use under pressure. It should contain the accepted number scope, provider references, contacts, expected window, temporary route, test sequence and decision owner.

Run tests in a fixed order:

1. Call the main number from at least two external services.
2. Confirm the greeting and opening-hours branch.
3. Select each important IVR option using keypad tones.
4. Prove queue entry, ringing, answer and overflow.
5. Transfer a live call between representative users.
6. Leave and retrieve voicemail.
7. Place outbound calls and check the presented business number.
8. Test direct-dial and non-geographic numbers in scope.
9. Confirm call history, missed-call ownership and notifications.
10. Record evidence and obtain business-owner acceptance.

For each failure, capture facts before changing configuration. A useful fault record includes the source, destination, timestamp with time zone, endpoint, network, expected result, actual result and any call identifier available from the provider. Change one variable at a time so the retest reveals something.

Worked example: moving a two-site service company

Imagine a maintenance company with a Manchester office, a Leeds office and technicians who answer calls on mobiles. Its website advertises one 0161 number, but invoices reveal a block of direct dials and a separate non-geographic campaign number. The old account also includes broadband at Manchester.

The team first marks the published number, number block and campaign number as separate scope items. It asks whether porting the 0161 range affects the broadband service and obtains the answer in writing. It then rebuilds opening hours, an emergency-repair queue and unanswered-call overflow on the destination system.

Before authorising the port, office staff and two technicians test temporary numbers. They prove incoming alerts on locked phones, transfers from office to mobile, DTMF selection, voicemail and outbound business identity. Finance checks that the old account remains active, while the migration lead submits one evidence pack with the precise account name and address.

On cutover day, testers call from different networks and exercise the entire emergency route. One direct dial fails, but the test log immediately shows that it was omitted from the accepted range. The business keeps the continuity route active while the gaining provider resolves that specific scope issue. The response is controlled because the team knows the difference between a route fault, a configuration fault and a missing port item.

Quick answers about UK business number porting

Can I use the number while it is being ported?

Normally the existing service remains in place until cutover, but confirm this for your request. Keep paying for and monitoring the old service. Do not cancel it merely because the gaining provider has acknowledged the order.

How long does it take to port a business number?

There is no safe universal answer for every business number. Timing can depend on number type, single number versus range, record accuracy, linked services and the providers involved. Ask for a written estimate after the gaining provider has validated the complete scope, then build contingency into your plan.

Who starts the port?

The gaining provider generally manages the transfer request. Follow its instructions and provide accurate authorisation. Avoid asking the losing provider to cease the number unless the agreed process explicitly requires an action from you.

Can I port a number to VoIP?

Many eligible business numbers can move to a VoIP service, but the gaining provider must confirm the specific number or range. Separately validate Session Initiation Protocol (SIP) endpoints, emergency information, caller identity, SMS requirements, hardware and network readiness.

Should I tell customers that the number is moving?

If the number stays the same, a broad announcement may be unnecessary. Tell staff and key stakeholders about the operational window, and prepare a customer notice for any service interruption. Update customers only with a useful alternative contact route and a realistic status.

Prove the endpoints before moving the public number

A number port should be the final traffic change, not the first full test of the new calling setup. Build the destination, rehearse with temporary numbers and keep a signed acceptance record. That sequence protects the contact details customers already know while giving your team evidence to diagnose problems quickly.

If desktop and mobile softphones are part of the migration, run a contained SessionCloud trial with representative office, remote and mobile users. Test managed SIP provisioning, locked-screen incoming calls, transfers, outbound business identity and user removal before the published number moves. Keep carrier eligibility, number porting and linked-service checks with the responsible providers; use the trial to prove the endpoint experience under real working conditions.

When the inventory, evidence pack, continuity route and acceptance tests are complete, you are no longer hoping the number will move cleanly. You are running a controlled business change with owners, proof and a recovery route.