VoIP Number Porting In The UK: Timeline, LOA, Common Delays & Business Cutover Checklist
Keeping your business number matters for trust, continuity, and inbound revenue. This UK guide explains what number porting is, how business ports usually move from data validation to cutover, why delays happen, and how to run a cleaner VoIP transition without avoidable disruption.
Fast answer: A successful business number port starts before the order is submitted: validate the exact current service record, identify linked services, prepare the authority paperwork properly, and only choose the port date once routing, users, and fallback handling are ready.
Businesses often think of number porting as an admin task that happens somewhere in the background. It is more important than that. Your phone number is part of customer trust, operational continuity, marketing identity, and inbound revenue flow. The best porting projects therefore treat the number move as a controlled business event, not a form-filling exercise.
Book a porting readiness review
This guide focuses on the UK number-porting process for business VoIP projects: what to prepare, how timing usually works, why ports fail or get delayed, and how to plan a safer cutover. It does not repeat provider ranking or general migration planning.
Table Of Contents
- What Number Porting Is And Why It Matters
- What To Prepare Before You Submit A Port
- Typical Porting Timeline For UK Businesses
- LOA, Account Data, And Validation Checks
- Delay Table: Common Causes And Fixes
- Cutover Day Checklist
- Multi-Site, DDI Blocks, And Higher-Risk Scenarios
- Common Porting Mistakes
- Frequently Asked Questions
- Related Reading
- Sources And Methodology
- Summary Block
What Number Porting Is And Why It Matters
Ofcom describes number portability as a regulated facility that allows customers to keep their numbers when changing provider. Ofcom has also said porting numbers should be a routine aspect of doing business for telecoms providers and that blocking or delaying a port can be unlawful. Those are strong regulatory foundations, but a well-run business port still depends on clean data, sensible staging, and good cutover management.
For a business, the number itself is more than a line item. It sits on your website, directory listings, stationery, ads, customer records, and often in staff habits built over years. That is why even a technically successful port can still feel messy if the timing, routing, or user preparation is poor.
Keeping the same number reduces friction for existing customers and protects the inbound trust signals attached to your business identity.
What To Prepare Before You Submit A Port
Most porting delays begin before the order is even raised. The basic principle is simple: the gaining provider can only move the number cleanly if the information submitted matches the losing side’s records closely enough to validate the request.
- Exact business name on the current service
- Service address and any site-specific address details
- Billing account or reference details where relevant
- Authorised contact information
- Clear list of numbers, number blocks, or DDIs in scope
- Understanding of any linked services that could be affected
A business asks to “port the number” without first confirming whether the number sits inside a wider service bundle, hunt group, number block, or linked legacy line arrangement that could create a partial cease or service impact.
Typical Porting Timeline For UK Businesses
There is no single universal porting timetable for every UK business scenario. A simple business number move can be relatively straightforward, while multi-site estates, DDI blocks, and linked legacy services need more coordination. The safest approach is to plan from the business cutover backwards rather than assuming the number move will happen instantly.
- Data gathering and validation
- LOA or equivalent authority paperwork
- Scope confirmation for numbers and linked services
- Port date confirmation
- Cutover runbook and fallback routing
- Live testing during and after the port
In other words, the timeline is not just “submit and wait”. A well-managed business port includes validation, service impact review, user readiness, routing preparation, and post-port acceptance testing.
LOA, Account Data, And Validation Checks
Many business ports still rely on a Letter of Authority, or LOA, to confirm the gaining side has permission to manage the transfer. The LOA is not a magic document that fixes weak data. It works best when the business has already confirmed the service name, address, account details, and scope of numbers in advance.
A practical rule is to treat the port pack like a legal or finance submission: small mismatches matter. If your business name, site address, or authorised contact data no longer matches the live service record, you should expect friction.
Ask for a full number inventory and validate the current-service record before you sign the LOA. That single step prevents a large share of avoidable rejections and delays.
Delay Table: Common Causes And Fixes
| Delay cause | What it looks like | Impact | Best fix |
|---|---|---|---|
| Account data mismatch | Business name, site address, or reference does not validate | Port rejection or rework | Match the live provider record exactly before submission |
| Wrong authorised contact | Authority cannot be confirmed cleanly | Delays and repeated paperwork | Use a clearly authorised contact tied to the service |
| Linked services not identified | Port affects broadband, alarms, or legacy services unexpectedly | Operational disruption | Review the full estate and dependency map before porting |
| DDI block complexity | Part-block moves or sequencing issues | Longer planning and higher risk | Plan block strategy and user mapping in advance |
| Unrealistic cutover date | Port is scheduled before routing, users, or support are ready | Chaotic go-live | Build from readiness backwards, not from wishful timing |
| No fallback routing | Main number becomes hard to answer during the transition | Missed calls and lost business | Define inbound failover and live test it before port day |
Cutover Day Checklist
Port day should feel controlled, not dramatic. That only happens when the number move is one step inside a larger runbook.
- Confirm all stakeholders, admin access, and carrier contacts are live before the window opens.
- Make sure the new routing design, users, queues, and devices are already built and ready.
- Define fallback handling for the main number if timing slips or behaviour is inconsistent.
- Test inbound and outbound calling as soon as the port lands.
- Validate main numbers, key DDIs, hunt groups, queues, voicemail, and any recorded announcements.
- Keep enhanced support coverage live until post-port acceptance is formally signed off.
Do not schedule a major business number port on the same day you are still teaching staff how to use the new call flow.
Multi-Site, DDI Blocks, And Higher-Risk Scenarios
Complex estates need more than a standard port request. Multi-site businesses, large DDI ranges, mixed PSTN and SIP histories, contact-centre routing, and linked services all increase coordination requirements.
In these situations, the safest route is often staged: pilot first, validate routing and support, then sequence the main-number and DDI moves in a controlled order rather than trying to collapse every dependency into one event.
- Multiple sites sharing number logic
- Large DDI blocks or mixed number ranges
- Legacy lines still tied to other services
- Reception, IVR, and queue-heavy workflows
- Port inventory signed off early
- Routing built before the date is fixed
- Fallback path ready for the main number
- Acceptance tests agreed in advance
Common Porting Mistakes
- Assuming all business ports are “just paperwork”
- Porting the main number before the new call flow is proven
- Ignoring linked services or partial cease risk
- Using incomplete or outdated account data
- Skipping post-port testing because the order shows as complete
- Treating number continuity as a telecom task instead of a business continuity task
Frequently Asked Questions
What is number porting?
Number porting is the regulated process that lets customers keep their telephone numbers when they switch provider.
Can most business numbers be ported to VoIP?
In many cases, yes, but the outcome depends on the current provider, number type, service structure, account data accuracy, and whether there are linked or partial cease risks in the existing estate.
Why do business ports get delayed?
The most common causes are incorrect account details, mismatched site information, linked services, wrong authorised contact data, partial cease risks, and unrealistic cutover timing.
What is an LOA?
An LOA is a Letter of Authority used in many porting processes to confirm that the gaining provider has permission to act on your behalf for the number transfer.
Should we port the main number first?
Usually not. Many businesses reduce risk by piloting first, validating routing and devices, then porting the main number in a controlled window once the design is proven.
Does Ofcom require providers to support number portability?
Yes. Ofcom says number portability is a regulated facility and providers must port numbers at the request of subscribers in the shortest time possible.
Does number porting automatically solve continuity?
No. Porting keeps the number; it does not replace the need for cutover planning, fallback routing, user readiness, or post-port validation.
Related Reading
Keep this page focused on porting process and cutover planning. Use the related pages below for migration strategy, resilience, and provider comparison.
- PSTN Switch-Off 2027 For Businesses
- Best Business VoIP Providers in the UK
- VoIP Power Cuts and Emergency Planning
- BT Digital Voice vs Business VoIP
- VoIP Cost UK: Total Cost of Ownership guide
Book a porting review Request a proposal
Sources And Methodology
This guide is written for UK business audiences and focuses on a distinct buyer or operational decision without drifting into the neighbouring topics already covered elsewhere on BhavPro. It combines BhavPro’s practical planning framework with current UK guidance, provider information, and telecom regulation relevant to this specific page.
- Ofcom: number portability
- Ofcom: number portability open letter
- Ofcom: porting charges under General Condition 18
- GOV.UK: UK transition from analogue to digital landlines
Our Commitment: To keep this guide useful for real buyers, the page stays tightly focused on one intent. It avoids drifting into provider rankings, broad migration planning, or pricing analysis unless that detail is directly necessary for the topic.
Summary Block
Decision-ready takeaways designed for quick reuse by business owners, operations teams, and IT stakeholders.
- Number porting is regulated in the UK and exists to let businesses keep their numbers when changing provider, but successful business ports still depend on clean data and cutover discipline.
- The most common causes of delay are mismatched account details, weak authority data, linked services, DDI complexity, and unrealistic cutover assumptions.
- A good business port starts with inventory, LOA readiness, and validation of the current service record before any date is requested.
- Port day should be treated as a controlled continuity event, with fallback routing and live acceptance testing in place.
- This page is intentionally focused on process and timing so it does not overlap with BhavPro’s broader migration, pricing, and provider-comparison content.
