Move Business Numbers to the Cloud UK: Number Porting, PSTN Dependencies and Migration Checklist
Keep critical business numbers, avoid porting delays and protect hidden PSTN-connected services before moving to cloud VoIP.
A practical UK guide for SMEs planning number porting, digital landline replacement, cloud call routing and PSTN dependency checks before the January 2027 digital voice transition.
Do not cancel first
Porting should be planned before any old line, PBX, ISDN or broadband-linked service is ceased.
Before You Move Numbers, Know What Those Numbers Support
This guide focuses on the part most businesses miss: protecting numbers, linked services, call routing and customer access before the port order is submitted.
Number Estate Protection
Map every main number, DDI, branch number, fax line, campaign number and dormant number before deciding what to port, retire or investigate.
PSTN Dependency Checks
Check whether any line still supports broadband, alarms, lifts, PDQ terminals, fax, door entry, fire panels or other business-critical services.
Cloud Routing Design
Plan how each number should route after migration, including IVR, queues, users, mobiles, voicemail, Teams Phone, 3CX or SIP-connected systems.
Cutover Testing
Validate inbound calls, outbound caller ID, voicemail, recordings, queue behaviour, emergency rules and after-hours routing immediately after porting.
Confirm billing records, linked services, call routing, broadband dependency, power-fail behaviour and post-port testing before approving the migration date.
Why Moving Business Numbers to the Cloud Matters Now
For many UK businesses, the phone number is not just a line on a bill. It is the number printed on vans, business cards, Google Business Profile listings, invoices, email signatures, appointment cards, call tracking campaigns, customer contracts and old supplier records. If that number is lost, delayed or routed incorrectly during migration, the business can lose calls, revenue and trust.
That is why moving numbers to the cloud should be treated as a controlled migration project, not a quick admin task. The UK move away from legacy analogue and ISDN voice services means businesses need to understand which numbers are still tied to PSTN-era lines and which services might depend on those lines. UK government guidance explains that most customers are expected to have moved to digital landlines by the end of January 2027, while BT Business says services such as ISDN, Featureline and certain broadband accesses must move to IP technology to keep working beyond 31 January 2027. GOV.UK digital landlines guidance and BT Business PSTN guidance both reinforce the need to prepare early.
The mistake many companies make is assuming number porting is just “keep the same number”. In practice, you need to know where the number lives, who owns it, which provider controls it, which services sit behind it, how it routes today, how it should route after migration and what happens if the broadband, power or mobile backup path fails. A port can be perfectly successful from a telecom perspective but still create operational problems if call flows, hunt groups, direct dials, out-of-hours messages or old analogue devices are not mapped properly.
What Moving Business Numbers to the Cloud Actually Means
Moving business numbers to the cloud means transferring your existing telephone numbers from a legacy line or current provider to a cloud VoIP platform. After the transfer, calls to those numbers are delivered over IP networks instead of a traditional copper or ISDN circuit. Users can answer calls on desk phones, softphones, mobile apps, browser-based calling tools, Microsoft Teams Phone, 3CX, SIP-connected PBX systems or a mixture of those routes.
The number itself usually stays the same from the customer’s point of view. What changes is the delivery path and the management layer behind it. Instead of a number being tied to one physical line in one building, it can route to a call queue, IVR menu, receptionist group, mobile app, overflow team, voicemail, emergency branch or out-of-hours provider. That flexibility is the main reason businesses move to cloud calling, but it also means the migration must be designed carefully.
Cloud number migration normally involves three layers. The first is the regulatory and provider layer: the losing provider releases the number and the gaining provider accepts it. The second is the technical layer: the number must be configured on the cloud platform, tested and pointed to the correct destination. The third is the business workflow layer: staff must understand how calls will arrive, which device should ring, how missed calls are handled and how customer-facing teams respond during the cutover window.
Ofcom’s business-customer protection guidance confirms that number porting is part of switching protections, and that customers should be able to port their number for at least one month after switching and must not be directly charged for porting their number. Businesses should still check contract terms, minimum commitments, cease charges, handset finance, broadband dependency and any linked service with their current provider before placing a port order. Ofcom business customer switching guidance.
Which Business Numbers Need to Be Audited?
The safest migration starts with a full number inventory. This should include every number that can receive calls, every number that is presented as caller ID and every number that might still be connected to a line even if nobody uses it daily. Many businesses discover old numbers only when a port fails, a broadband service disconnects or a payment terminal stops working.
| Number or line type | Why it matters during cloud migration | What to check before porting |
|---|---|---|
| Main business number | Usually the highest-risk number because it receives customer, supplier and sales calls. | Opening hours, IVR, reception routing, voicemail, holiday messages and failover path. |
| Direct dial numbers | Staff may rely on DDIs for clients, departments or legacy campaigns. | Owner, department, usage level, replacement routing and whether unused numbers should be retained. |
| Geographic numbers | Local numbers such as 01 or 02 numbers often appear in local SEO, directories and printed material. | Address records, losing provider details and whether the local identity should remain visible. |
| Non-geographic numbers | 03, 08 or other numbers may have special routing, billing or campaign use. | Call forwarding rules, call charges, campaign tracking and customer-service ownership. |
| Fax numbers | Fax use may be hidden inside healthcare, legal, finance, logistics or supplier workflows. | Whether fax should move to digital fax, secure email, portal upload or a specialist replacement. |
| Alarm, lift or door-entry lines | These services may be tied to analogue lines and cannot simply be ported like voice calls. | Speak to the alarm, lift, fire, telecare, access-control or facilities supplier before changing the line. |
| Backup or dormant lines | Some lines appear unused but still support broadband, card machines, alarms or emergency processes. | Usage history, billing references, physical labels, router connections and supplier dependencies. |
The goal is not to port everything automatically. The goal is to decide which numbers should be kept, which should be consolidated, which should be redirected, which should be retired and which should be handled by a separate specialist migration. That decision should happen before the losing provider receives a cancellation request.
Top 10 Market Routes for Moving Numbers to Cloud Calling
The UK market offers several ways to move business numbers into a digital phone environment. Some providers focus on all-in-one UCaaS. Some focus on Microsoft Teams calling. Others are better suited to contact-centre workflows, SIP connectivity, PBX control or low-cost hosted VoIP. A good comparison should not ask only “who is cheapest?” It should ask which route gives the business the right level of control, support, number management and migration safety.
| Business Need | Recommended Starting Route | Why It Matters |
|---|---|---|
| Replace ageing landlines | Digital landline or cloud VoIP | Keeps numbers working while moving voice to an IP-based service. |
| Support hybrid teams | Cloud phone system with mobile and desktop apps | Lets staff answer business calls from the office, home or on the move. |
| Keep existing PBX hardware temporarily | SIP trunking | Allows a phased migration from ISDN-style dependency to digital voice. |
| Use Microsoft Teams for calling | Teams Phone integration | Brings external calling into the Microsoft 365 environment. |
| Improve call visibility | AI call analytics and transcription | Turns call activity into searchable insight for sales, support and management. |
| Provider or route | Typical strength | Porting and migration gap to check |
|---|---|---|
| RingCentral | Broad UCaaS platform for calls, messages, meetings and business communications. | Check UK porting ownership, support model, contract terms and whether all call flows are migrated cleanly. |
| 8×8 | Cloud phone and contact-centre breadth for businesses that need voice plus analytics. | Check setup ownership, porting timelines and whether the package is right-sized for smaller teams. |
| Vonage | Unified communications, contact-centre and API-led communications capabilities. | Check whether your migration needs simple business VoIP or a broader communications/API stack. |
| bOnline | SME-focused VoIP with simple business-phone positioning and quick setup. | Check feature depth, support escalation and how complex number estates are handled. |
| BT Business | Strong incumbent context for existing PSTN, ISDN, broadband and business line estates. | Check whether legacy services, Featureline, ISDN or broadband dependencies need separate migration planning. |
| Microsoft Teams Phone | Teams-native calling through Calling Plans, Operator Connect, Teams Phone Mobile or Direct Routing. | Check emergency-location setup, licensing, operator ownership, call queues and whether Teams suits reception workflows. |
| 3CX | Flexible PBX-style control with hosted, self-hosted and SIP-connected deployment options. | Check hosting responsibility, SIP provider choice, number porting ownership and admin skills required. |
| Dialpad | AI-native voice, meetings and contact-centre style workflows. | Check UK number support, compliance needs and whether AI-led features justify the package for your team. |
| Aircall | Sales and support team calling with CRM integrations and contact-centre workflows. | Check suitability for general office telephony, reception routing and non-sales departments. |
| GoTo Connect or Voipfone | GoTo suits cloud communications breadth; Voipfone suits UK VoIP simplicity and hosted PBX-style requirements. | Check support depth, migration process, feature flexibility and total cost when scaling users or numbers. |
VoIPTelco’s angle is to make the route decision easier for UK SMEs that do not want to piece together number porting, business broadband, digital landline replacement, SIP, 3CX, Microsoft Teams Phone and AI call visibility from separate conversations. The best provider is not always the one with the longest feature list. It is the one that can move the right numbers, protect the right workflows and support the business after go-live.
Where Most Number-Porting Content Misses the Real Risk
Most number-porting pages explain that you can keep your number. That is true, but it is only the beginning of the decision. The real risk is not usually the number itself; it is what the number is connected to and what the business assumes will keep working afterwards.
The first gap is dependency mapping. Many websites tell businesses to port their number, but they do not ask whether the same line supports broadband, alarm signalling, a lift phone, a card machine, a door-entry panel, a fax machine, a fire system, a backup modem or an outbuilding. Porting or ceasing the wrong line can affect more than phone calls.
The second gap is routing design. A number moved to the cloud has to land somewhere. It might ring a receptionist, a hunt group, a call queue, a Microsoft Teams user, a 3CX extension, a softphone group or an overflow mobile. If that design is not documented, staff may discover after go-live that the main number rings the wrong people, voicemail is not monitored or out-of-hours calls disappear into an old mailbox.
The third gap is emergency continuity. Cloud calling depends on broadband, power and network equipment. A business should decide which users need backup power, mobile failover, alternative calling paths and accurate 999/112 location records. This is especially important for healthcare, legal, education, retail, construction, care, facilities and multi-site organisations.
The fourth gap is customer communication. The number may stay the same, but customers may notice changed call handling, new voicemail prompts, new caller ID, different opening-hour routing or different department choices. A migration plan should include staff briefing, customer-facing messages, call recording notices and post-go-live monitoring.
PSTN Dependencies to Check Before Porting Numbers
Before porting numbers to cloud VoIP, review every analogue service that may rely on a PSTN or ISDN line. In many UK businesses, these dependencies were installed years ago and are not always visible in IT documentation. Facilities, finance, operations and branch managers often know about services that the telecom bill alone does not reveal.
If any of these services exist, do not assume a VoIP port alone solves the issue. Some devices need replacement hardware, IP modules, mobile failover or specialist provider work. The number-porting plan should therefore be coordinated with facilities suppliers, security providers, broadband providers and internal stakeholders.
The Business Number Porting Process Step by Step
Every provider has its own operational process, but a safe number-porting workflow usually follows the same core stages. The purpose of the process is to reduce rejections, protect continuity and make sure that calls route correctly immediately after the port completes.
The most important rule is simple: do not cancel the old service before the port completes unless your provider has explicitly confirmed that cancellation is part of the correct migration sequence. Premature cancellation can create number loss, delays or service disruption.
What Causes VoIP Number Porting Delays?
Porting delays are usually caused by mismatched records or hidden complexity. A business may think it has supplied the correct address, but the losing provider may hold an old installation address, former trading name, old account number or parent-company billing record. A single mismatch can cause a rejection.
Another common issue is partial porting. If a business wants to move one number from a group but leave others behind, the losing provider may need specific instructions. Some number ranges, multi-line services and legacy configurations must be handled carefully to avoid breaking remaining services.
Delays can also occur when the business does not know the real losing provider. The bill may show a reseller, but the number may sit behind another network. This is why clear provider discovery is useful before setting a migration date.
Operational delays also happen when call routing is not ready. The number may port successfully, but if users, devices, queues or auto-attendant settings have not been configured, callers may reach the wrong destination. A good migration plan separates the porting task from the readiness task and checks both before go-live.
How to Design Cloud Call Routing After the Number Moves
Cloud calling gives businesses more routing options than traditional lines. That flexibility is valuable only if it is planned around real workflows. A main number might first reach an auto-attendant, then route to sales, support, accounts or reception. A branch number might ring local staff first, then overflow to a central team. A VIP customer number might route to an account-management group. Out-of-hours calls might go to voicemail, an answering service or an emergency mobile.
When designing routing, avoid copying old behaviour automatically. Traditional call flows may have existed only because the old PBX or line configuration was limited. Moving to the cloud is an opportunity to improve answer rates, caller experience and reporting.
| Routing decision | Old-line question | Cloud VoIP improvement |
|---|---|---|
| Main number | Who answers first today? | Use IVR, queue rules, overflow and voicemail-to-email. |
| Department calls | Are callers transferred manually? | Create sales, support, accounts and service queues. |
| Missed calls | Who checks missed-call logs? | Use alerts, analytics, callbacks and missed-call reporting. |
| Remote staff | Do customers call mobiles directly? | Use business caller ID through softphones and mobile apps. |
| Out-of-hours | Is the answerphone updated manually? | Use schedules, holiday rules and emergency escalation paths. |
| Management visibility | Can leaders see call performance? | Use dashboards, recordings, transcripts and call analytics. |
This is where cloud migration becomes more than a technical transfer. It gives the business a chance to reduce missed calls, standardise customer handling and improve visibility across offices, remote workers and mobile teams.
VoIPTelco’s Recommended Number Migration Framework
VoIPTelco approaches number migration as a business-continuity workflow. The aim is to protect the number, protect the customer journey and protect the services that may sit behind legacy lines.
The first stage is discovery. We map numbers, current providers, user groups, call routes, devices, lines and known dependencies. This stage is especially important for businesses with multiple branches, old fax numbers, 08/03 numbers, seasonal campaigns or historic telecom contracts.
The second stage is route selection. A business may need cloud VoIP for most users, SIP trunking for an existing PBX, Microsoft Teams Phone for Microsoft 365 users, a 3CX phone system for PBX-style control, or digital landline replacement for simpler line migration. The right route depends on users, support model, features, resilience, compliance and budget.
The third stage is configuration. This includes users, call groups, IVR, queues, voicemail, recordings, mobile apps, desk phones, emergency-location settings, outbound caller ID and any AI call-intelligence features. Configuration should happen before porting so that the number has a prepared destination.
The fourth stage is controlled porting and testing. We recommend a clear port window, named testers, inbound and outbound call checks, mobile and landline test calls, voicemail checks, queue checks, recording checks and call-quality validation.
The fifth stage is optimisation. After go-live, the business should review missed calls, answer times, call volumes, user feedback and customer experience. This is where AI-ready tools such as transcripts, call summaries and analytics can move the business from “the number works” to “the phone system is improving performance”.
Business Number Porting Checklist
Use this checklist before approving a number port or cancelling any existing service.
FAQs About Moving Business Numbers to the Cloud
Can a UK business keep its existing number when moving to VoIP?
In most cases, yes. UK businesses can usually port geographic and many non-geographic numbers to a cloud VoIP provider, provided the records match and the number is active. You should not cancel the old service before the port is complete.
How long does business number porting take?
Timescales vary by number type, losing provider, records accuracy and complexity. Simple ports can be faster, while multi-line, ISDN, number ranges or reseller situations may take longer. A clean inventory reduces avoidable rejection risk.
What information is needed to port a business number?
You normally need the current provider, account name, installation address, billing details, account reference, numbers to be ported and confirmation of any linked services. Exact requirements can vary by provider and number type.
Can number porting affect broadband or other services?
Yes, if the number is linked to a line that also supports broadband, alarms, lifts, card terminals, fax or other services. Always check dependencies before porting or cancelling a line.
What happens to calls on the port day?
During the port window, the number moves from the losing provider to the gaining provider. After completion, inbound calls should reach the new cloud routing. Businesses should test inbound calls, outbound caller ID, voicemail and queues immediately.
Can I port numbers into Microsoft Teams Phone?
Yes, businesses can use Teams Phone with PSTN connectivity through options such as Calling Plans, Operator Connect, Teams Phone Mobile or Direct Routing. The right route depends on licensing, operator choice, support ownership and call-flow needs.
Should I move fax numbers to cloud VoIP?
Not automatically. Fax should be reviewed carefully, especially in regulated sectors. Some businesses move to secure digital fax or replace fax with secure email, portal upload or document workflow tools.
How can VoIPTelco help with moving numbers to the cloud?
VoIPTelco helps UK businesses audit numbers, check PSTN dependencies, choose the right cloud VoIP route, configure users and call flows, manage porting, test cutover and optimise the system after go-live.
Ready to Move Your Business Numbers to Cloud VoIP?
VoIPTelco can help audit your number estate, check PSTN dependencies, map the right migration route and prepare your cloud call flows before port day.
