PSTN Switch-Off 2027 For Businesses: Replacement Options & Migration Plan
The UK’s PSTN and ISDN retirement is not just a desk phone change. The biggest risk usually sits in hidden dependencies: alarms, lift phones, entry systems, payment fallbacks, fax, and legacy dial-out devices. This guide gives you a practical route comparison, a device audit you can run this week, and a staged migration plan that protects continuity.
Fast answer: The safest way to handle the PSTN switch-off is to audit every number and device first, pick the route that fits your estate, build power and connectivity resilience into the design, then pilot before any main-number port. The risk is rarely “phones stop working”; it is usually a hidden operational or safety dependency that nobody traced in time.
For most businesses, the change to digital voice is manageable. The disruption usually appears when a lift phone, alarm dialler, entry system, fax path, or legacy line is still relying on analogue assumptions. That is why the migration should be treated as a business continuity project, not just a telecom refresh.
This guide focuses on decision clarity, route selection, readiness, resilience, and a low-risk rollout path. Cost modelling and provider comparison are intentionally kept on separate pages so this article stays focused on migration planning.
Book a PSTN migration assessment
For most customers, the move away from analogue lines is expected to be complete by January 2027. GOV.UK also states that communications providers will not know which devices are connected to their network, so businesses need to review dependencies such as alarms, telecare devices, fax, and similar equipment themselves.
Table Of Contents
- What The PSTN Switch-Off Means For Your Business
- What Can Break And How To Find It
- Your Replacement Options
- Route Comparison Table
- Readiness Checklist
- 30/60/90-Day Migration Plan
- Power Cuts, Outages, And Emergency Calling
- Common Mistakes And Risk Register
- Real-World Examples
- Frequently Asked Questions
- Related Reading
- Sources And Methodology
- Summary Block
What The PSTN Switch-Off Means For Your Business
The UK is retiring analogue PSTN and ISDN services in favour of digital voice delivered over IP-based networks. For many businesses, the visible change will be simple: voice moves from a traditional wall socket model to a digital service running via broadband, fibre, or an IP voice platform. The less obvious change is that local power and network availability now matter much more than they did on many legacy lines.
In practice, that means your migration decision is no longer just about handsets. It affects resilience, network readiness, vendor coordination, emergency calling, and any device that assumed an analogue line would always be there in the background.
- Voice is delivered via digital infrastructure rather than legacy analogue lines.
- Local power for the router, ONT, and network equipment becomes part of the calling continuity model.
- Analogue-dependent devices may need replacement, reconfiguration, or a different connectivity path.
- Your existing business numbers can usually be retained through controlled porting.
- Call continuity can be protected with the right resilience design and staged migration.
- You can improve call routing, remote access, reporting, and governance as part of the move.
What Can Break And How To Find It Before It Fails
The most common migration failure is not the desk phone. It is a hidden dependency: a device nobody remembered until it needed to dial out. This is why the first serious task in a PSTN migration is a full dependency audit across every number, line, and site.
Devices That Are Frequently Overlooked
- Lift emergency phones and related building safety devices
- Intruder and fire alarm diallers that assumed analogue signalling
- Door entry, intercom, and gate systems with dial-out behaviour
- Telecare devices in mixed-use, care, or supported settings
- Card payment or EPOS fallbacks still using legacy paths
- Fax and modem-based workflows in regulated or older operational processes
- “Spare” lines that are not actually spare at all
- Export every active number and line from current bills or provider records.
- Walk each site and locate anything connected to a phone socket or labelled line, PSTN, or RJ11.
- Record make, model, location, maintainer, and whether the device is safety-critical or operationally critical.
- Ask each vendor to confirm whether the device will work without PSTN and what digital-ready replacement path is required.
- Document required downtime tolerance and backup expectations for each critical dependency.
| Device / service | Why it is risky during migration | Action to take now | Typical owner |
|---|---|---|---|
| Lift phone | Safety-critical and often analogue-assumed | Engage lift maintainer, confirm digital-ready route, define backup power | Facilities / building manager |
| Alarm dialler | Can fail silently if signalling path changes | Confirm IP or cellular upgrade path and testing requirements | Facilities + alarm vendor |
| Door entry / intercom | Often tied into building access control workflows | Validate compatibility and plan replacement lead time if needed | Facilities + security vendor |
| Telecare device | Requires continuity and careful fallback planning | Coordinate with provider and supplier to confirm digital support | Care ops / housing / IT |
| Fax or modem path | Can degrade or become unreliable on basic IP adaptors | Move to secure digital alternatives where possible | Ops + compliance |
| Legacy or “spare” line | Often supports an overlooked operational dependency | Trace each line before removal and label ownership clearly | IT + finance |
Your Replacement Options
There is no single best replacement for every organisation. The right route depends on your estate, governance capability, operational complexity, and whether you want simplicity, cloud flexibility, or more control over the voice stack.
1) Digital Voice
Smaller sites with straightforward calling needs and limited routing complexity.
Watch-outsAssuming a simple router-based transition covers every connected device. It often does not.
2) Hosted VoIP / Cloud PBX
Most SMEs that need queues, IVR, ring groups, remote work flexibility, and manageable cloud-based administration.
Watch-outsNetwork readiness matters. Weak LAN, Wi-Fi, or resilience planning can create avoidable quality problems.
3) SIP Trunking
Businesses that want to keep a supportable PBX while replacing legacy PSTN or ISDN connectivity with IP-based trunks.
Watch-outsYou keep more operational responsibility: lifecycle, security, monitoring, and disaster recovery routing.
4) Microsoft Teams Phone
Teams-first organisations that already live in Microsoft 365 and want calling integrated into that operating model.
Watch-outsPSTN connectivity design, policy governance, emergency calling approach, and handset strategy still need deliberate planning.
5) 3CX
Organisations that want more control over call flows, integrations, and hosting approach than a standard hosted platform usually offers.
Watch-outsControl only works well if updates, backups, access control, and support boundaries are properly managed.
Route Comparison Table
Use the table below to choose the right fit faster. Wrong-fit projects usually happen when teams choose a platform first and only later discover that the estate, support model, or resilience requirements do not match.
| Route | Best fit | What to confirm before committing | Typical pitfalls | Safe first move |
|---|---|---|---|---|
| Digital Voice | Basic calling and low operational complexity | Device compatibility, power backup, emergency fallback | Assuming simple migration means zero hidden dependencies | Complete the device audit before any cutover planning |
| Hosted VoIP / Cloud PBX | Most SMEs with modern call handling needs | LAN/Wi-Fi readiness, user setup, call flow design, resilience | Voice quality issues caused by weak network foundations | Pilot with a small team before main-number ports |
| SIP Trunking | Keep the PBX but replace legacy connectivity | PBX supportability, SBC/security, failover call routing | Retaining a PBX that is already near end-of-life | Validate lifecycle and support boundaries first |
| Teams Phone | Teams-led estates with internal governance maturity | PSTN path, emergency calling, site mapping, policies | Assuming Teams alone solves routing and continuity | Run a controlled pilot and policy test set |
| 3CX | More control and integration flexibility | Hosting model, update cadence, backups, admin ownership | Operational ownership gaps after go-live | Define the managed support model before rollout |
If your estate includes any safety-critical or operational dial-out device, do not treat migration as a simple number port. Validate the device path first, then stage the cutover around that reality.
Readiness Checklist Before You Port Any Numbers
The list below is where many rushed projects fail. If you cannot confidently tick these off, you are not ready for a main-number port yet. Fix the gaps first; it is cheaper and safer than handling avoidable disruption later.
- Internet performance is acceptable under peak usage conditions.
- Switching, cabling, and endpoint strategy have been reviewed.
- Wi-Fi has been assessed if any voice traffic will rely on it.
- Traffic prioritisation or QoS approach is defined where needed.
- UPS coverage exists for router, ONT, and essential network equipment.
- A fallback path exists for critical service continuity.
- Device audit is complete and vendor confirmations are logged.
- Call flows are mapped for business hours, after-hours, overflow, and queue handling.
- Number inventory is accurate across all sites and services.
- Emergency calling approach is documented per site.
- Support ownership is clear: changes, incidents, user admin, escalation.
- Cutover plan, communications plan, and rollback logic are documented.
30/60/90-Day Migration Plan
A staged migration is usually the most reliable path for SMEs. It gives enough time to identify device issues, validate resilience, and avoid a “big bang” switch that concentrates too much risk into one moment.
Days 0–30: Discover, Design, And De-Risk
- Build the full inventory of numbers, lines, users, and connected devices.
- Choose the best-fit migration route based on estate needs, not marketing labels.
- Assess broadband, LAN, Wi-Fi, and endpoint readiness for voice.
- Design backup power and failover or diversion logic for key numbers.
- Map call flows and identify pilot candidates for a low-risk first stage.
Days 31–60: Build And Pilot
- Provision users, endpoints, and administrative access.
- Build the required queues, IVR, ring groups, voicemail, and after-hours rules.
- Pilot with a small team or lower-risk location.
- Validate critical devices with vendors during the pilot, not after the main port.
- Simulate disruption scenarios and confirm fallbacks behave as expected.
Days 61–90: Port Numbers And Stabilise
- Schedule controlled number ports with named contacts and monitoring in place.
- Run go-live support coverage during and after the cutover window.
- Test inbound, outbound, queues, key DDIs, emergency processes, and critical devices.
- Resolve edge cases quickly and only decommission legacy services after sign-off.
- Confirm access to admin tools, carrier contacts, and escalation paths.
- Verify UPS and fallback routes are active before the port starts.
- Run a pre-port test pack on key numbers and flows.
- Monitor inbound and outbound call behaviour live during the port window.
- Validate critical operational devices immediately after the cutover.
- Run acceptance checks and capture evidence before sign-off.
Power Cuts, Outages, And Emergency Calling
One of the biggest differences between old analogue voice and modern digital voice is the resilience model. If your service relies on internet-connected voice, local power loss or broadband disruption can affect calling unless you have designed around that risk.
- Protect the router, ONT, and core switching with the right UPS coverage.
- If Wi-Fi calling or softphones matter, include access points in the power model.
- Document which services continue to function during a local outage.
- Define a backup path such as secondary access, 4G/5G failover, or prebuilt diversion.
- Make sure main numbers and queues have tested fallback behaviour.
- Run a planned simulation before your main-number migration.
GOV.UK’s resilience guidance states that communications providers must maintain uninterrupted access to emergency services, and for customers who rely solely on landlines they must guarantee access to emergency services for at least one hour during a power outage, free of charge. That requirement sits alongside broader resilience and outage-preparation obligations for providers.
Common Mistakes And Risk Register
The issues below cause a large share of avoidable migration pain. Treat them as risks to be assigned and mitigated, not just observations.
| Risk | What it looks like | Impact | Mitigation |
|---|---|---|---|
| Hidden dependency | Alarm, lift, or entry system stops working after the move | Operational or safety disruption | Device audit, vendor confirmation, and post-port validation |
| Power overlooked | Voice fails during a local power interruption | Continuity failure | UPS and documented fallback plan |
| Network not voice-ready | Choppy audio, jitter, or one-way audio | Poor customer experience and staff frustration | LAN/Wi-Fi remediation and structured testing |
| Rushed porting | Main numbers misroute or fail during cutover | Lost calls and reputational damage | Staged ports, monitored window, and rollback options |
| Unclear ownership | No one knows who manages routing or incidents | Slow recovery and ongoing friction | Define support roles and escalation paths before go-live |
| Wrong-fit platform | The solution works technically but creates daily operational friction | Higher change cost and poor adoption | Choose based on estate fit and governance maturity, then pilot |
Openreach announced staged WLR rental price increases for April, July, and October 2026 to encourage migration to newer digital alternatives before legacy services are switched off in January 2027. That means waiting can increase cost pressure as well as operational risk.
Real-World Examples
The same national switch-off requirement can lead to very different best-fit choices depending on the estate, device dependencies, and support model. These simplified examples show what a good migration outcome looks like in practice.
Single-Site Professional Services Firm
The business needs clean inbound routing, a stable main number, and occasional remote work support. A hosted VoIP route is often a strong fit, provided the network is checked first and the main-number port follows a short pilot rather than going live on day one.
Multi-Site Retail Or Hospitality Group
The operational requirement is consistent routing, overflow handling, and simple updates across sites. Entry systems and alarm paths can be the real trap. A good migration includes a site-by-site audit and tested fallback rules for each location.
Teams-First Organisation
The goal is a unified communications experience for staff already working inside Microsoft 365. Teams Phone can work well here, but only when PSTN design, emergency calling, and policy governance are handled deliberately rather than assumed.
Warehouse Or Light Industrial Site
Safety and operational continuity matter more than feature depth. Entry systems, alarms, and emergency lines usually need facilities-led vendor confirmation before any number migration starts.
- Every number and dependency is known and owned.
- Power and connectivity resilience are tested rather than assumed.
- A pilot happens before any critical number port.
- Support boundaries are documented before the first day of live use.
Frequently Asked Questions
When Is The PSTN Switch-Off For Businesses In The UK?
For most customers, the national transition is expected to be complete by the end of January 2027, although provider-specific timing can vary by product, contract, and migration window.
What Breaks Most Often During PSTN Migration?
Hidden dependencies create the biggest risk: lift phones, alarm diallers, intercom systems, telecare devices, and other legacy dial-out equipment that still assume an analogue line is present.
Do We Have To Change Our Phone Numbers?
No. In most cases your existing business numbers can be retained through controlled number porting, provided the move is staged properly and acceptance testing is built into the cutover window.
Will Calls Work During A Power Cut After We Move To Digital Voice?
Not automatically. Digital voice usually depends on local power for the router, ONT, switching, and sometimes Wi-Fi, so continuity requires a UPS plan and a tested fallback path.
What Is The Safest Migration Approach For An SME?
Start with the device audit, confirm the right route for your estate, run a pilot, validate resilience and critical devices, then move into a controlled main-number port with rollback logic in place.
Which Route Should We Choose First: Digital Voice, Hosted VoIP, SIP Trunking, Teams Phone, Or 3CX?
Choose based on fit, not marketing labels: Digital Voice for simple estates, Hosted VoIP for most SMEs, SIP trunking to retain a supportable PBX, Teams Phone for Teams-first environments, and 3CX where flexibility and control matter.
Why Is Acting In 2026 Usually The Safer Move?
Because waiting increases the risk of rushed migration decisions, tighter vendor lead times, and avoidable cost pressure as Openreach’s staged 2026 WLR rental price rises push more businesses toward the 2027 deadline.
Related Reading
Keep this page focused on migration planning. Use related guides for deeper dives into cost, provider comparison, and adjacent decision areas.
Book a PSTN migration assessment Request a proposal
Sources And Methodology
This guide is written for UK business audiences and focuses on continuity-first migration planning. It combines BhavPro’s practical migration framework with current UK guidance on the analogue-to-digital transition, connected-device risks, pricing pressure on legacy WLR services, and resilience expectations during outages.
- GOV.UK: UK transition from analogue to digital landlines
- GOV.UK: moving landlines to digital technologies
- GOV.UK: communication providers ensuring telecom services are resilient
- Openreach: price changes to encourage digital adoption
Our Commitment: To ensure objective planning, this guide remains vendor-neutral and focuses purely on migration readiness. We structure the digital transition into five key phases: Audit → Route Selection → Readiness → Staged Rollout → Resilience Validation.
Summary Block
Decision-ready takeaways designed for quick reuse by business owners, operations teams, and IT stakeholders.
- The PSTN switch-off is a business continuity project as much as a telecom project, because hidden dependencies often create the real migration risk.
- The safest migration path is to audit every number and connected device before choosing a replacement route.
- Hosted VoIP is often the best fit for SMEs, but the right answer depends on the estate, governance model, and support responsibility.
- Digital voice resilience depends on local power and network continuity, so UPS and failover planning must be explicit.
- A staged 30/60/90-day migration plan reduces risk far more effectively than a rushed “big bang” cutover.
- Planning in 2026 is sensible because operational risk rises as the 2027 deadline approaches and Openreach has announced staged WLR price increases through 2026.
