PSTN Switch-Off 2027: What Businesses Must Do Before Analog Landlines Disappear

The UK's Public Switched Telephone Network (PSTN) is scheduled to be retired on 31 January 2027. For many business owners, that date sounds like a telecom-industry problem. It isn't. If your reception number, card terminals, lift phone, alarm line or fax still depends on copper, it is an operational deadline with real revenue and safety consequences.

Most coverage of the switch-off is technical, full of acronyms and light on what to actually do on Monday morning. This guide is a practical migration checklist for hotels, clinics and logistics teams. It covers number porting, DID numbers, IVR rebuilds, call routing and call recording, and shows how Lodgestory's cloud voice, virtual numbers and WebRTC softphone let you move off legacy lines without losing a single call.

What Is Actually Happening to the PSTN?

The PSTN is the circuit-switched, copper-based network that has carried UK voice calls since the late nineteenth century. ISDN, its digital overlay, powered many business phone systems. BT and Openreach have said the ageing network is fragile and expensive to maintain, and it is being replaced by IP-based voice delivered over broadband and full fibre.

A few facts every business owner should know:

• The date has already slipped once. The original target of December 2025 was extended to 31 January 2027 to protect vulnerable users such as telecare customers. Openreach has signalled that it does not expect further extensions.
• Many businesses face an earlier deadline. Under Openreach's stop-sell rules, once full fibre reaches more than 75% of premises on an exchange, providers get a year's notice that legacy copper services will stop being sold there. By August of the reporting year, stop-sell was active in 1,041 exchanges, covering 8.9 million premises, or 46.4% of Openreach's full fibre footprint.
• Plenty of lines remain. Ofcom's Connected Nations 2024 report found PSTN still accounted for roughly 27% of residential landline connections (about 5.2 million), with 8.6 million connections already on VoIP. Openreach estimated around 1.5 million copper lines were still live in mid-2024, about 350,000 of them at business premises.
• The easy migrations are done. Openreach has warned that what remains is the complex, often safety-critical work that needs planning, supplier coordination and testing.

The practical lesson is that your real deadline is whichever comes first: the national date or your local exchange's stop-sell and switch-off schedule. Waiting for a carrier letter is the riskiest strategy available.

The Hidden Dependencies: What Breaks When Copper Goes Dark

The most common misconception is that only desk phones are affected. In reality, anything that dials out or answers over a copper line stops working at cut-over:

• Main reception and departmental lines, including ISDN2, ISDN30 and Wholesale Line Rental circuits feeding a PBX
• Card payment terminals and chip-and-PIN devices
• Lift emergency phones and help-points
• Fire and intruder alarm communicators
• Door entry and building access systems
• Telecare pendants and care-alarm hubs
• Fax lines and legacy telemetry

Openreach has warned that unmigrated building systems could force commercial building closures or cause supply chain delays. That is why the first step of any migration is not buying software. It is finding out what you actually have.

The Practical PSTN Migration Checklist

Work through these steps in order. Most small and mid-sized organisations can complete the first four in a few weeks, then use the remaining months for porting, testing and staff training.

Step 1: Audit Every Line and Device

Walk every site and build a spreadsheet with one row per line or device:

1. Telephone number or circuit ID
2. What it connects to (PBX, handset, alarm, lift, terminal, fax)
3. Current provider and contract end date
4. Business criticality (revenue, safety, convenience)
5. Migration path (port to cloud, replace device, retire)

Ask your facilities team, not just IT. Lift phones and alarm lines are often managed by third-party contractors who are not on your radar.

Step 2: Inventory and Protect Your Numbers

Your numbers are brand assets. They appear on signage, invoices, vehicles, booking confirmations and Google listings. Ofcom's General Conditions give you strong protection here:

• Customers must be allowed to port numbers, and providers may not charge you directly for porting.
• You should be able to port for at least one month after terminating a contract.
• Loss of service during a switch must not exceed one working day where technically possible.
• If a port fails, the losing provider must keep the number active until migration completes.

Industry guidance suggests a single geographic business number typically takes 10 to 14 working days to port. The golden rule is to keep your existing service live until the port completes. Cancelling early is the fastest way to lose a number permanently.

Step 3: Map Your DID Numbers

Direct Inward Dialing (DID) lets one trunk present many numbers, one for each department, room block, depot or practitioner. If you currently have an ISDN30 with a DDI range, document every number and where it rings today. Our guide on what Direct Inward Dialing is and why modern businesses need it explains how DIDs map to departments and agents in a cloud setup.

In Lodgestory, each DID or virtual number can be tied to a specific IVR flow, department queue or individual agent. If you want new numbers for a new location or campaign while your ports are pending, virtual numbers can be provisioned without waiting for copper.

Step 4: Rebuild Your IVR, Don't Just Copy It

Migration is the best chance you will get to fix an IVR that callers hate. Many legacy menus have six levels, outdated opening hours and options nobody presses. Before you rebuild, review last quarter's call logs and keep only the options that callers actually use.

A good rebuild typically includes:

• A short greeting with no more than four or five options
• Language selection if you serve international guests or patients
• Time-of-day and holiday routing
• Self-service for common requests such as booking status, opening hours and directions
• A clear path to a human agent at every stage

Lodgestory's visual voice and IVR flows let operations teams make these changes without developer help. For design ideas, see the top IVR features powering omnichannel customer experience and the future of IVR in omnichannel communication.

Step 5: Redesign Call Routing

On a legacy PBX, routing is often hardwired: extension 201 rings on this desk, in this building. Cloud telephony removes that constraint. Calls can follow people, teams and shifts, wherever they are working.

Consider these routing patterns:

• Department queues: front desk, reservations, housekeeping, billing or dispatch each get their own queue
• Skill-based routing: language, specialty or account tier determines the destination
• Time-based routing: daytime calls go to the office, out-of-hours calls go to an on-call team or voicemail with a callback
• Overflow and failover: if a queue exceeds a threshold, calls spill to another team or site

Lodgestory supports department-based routing with queue logic, plus supervisor tools such as monitor, whisper, barge and transfer. If you want to go deeper, read smart call routing best practices and how automatic call distribution works.

Step 6: Plan Recording, Tagging and Compliance

If your old system recorded calls through an ISDN logger or an on-premise box, that capability needs a new home. Decide up front:

• Which lines and departments must be recorded
• How long recordings are retained
• Who can listen to them
• How consent announcements are played

Cloud call recording makes this much simpler. In Lodgestory, recordings, call direction, duration, status and agent attribution are captured in call logs. Add call tags and call dispositions and every conversation becomes searchable, auditable and useful for coaching.

Step 7: Replace or Re-Home Safety-Critical Devices

This is the step you cannot rush. For lift phones, alarm communicators, telecare hubs and payment terminals:

1. Ask each device supplier for written confirmation of IP compatibility
2. Request a replacement or upgrade quote where needed
3. Schedule installation well ahead of the cut-over window
4. Test end to end, including the alarm receiving centre

Note that some devices will not work reliably on standard VoIP without upgrades. Always get supplier sign-off rather than assuming.

Step 8: Build Resilience Into the Connection

Copper was line-powered and kept working during a power cut. Broadband-based voice does not. Plan for:

• A battery backup for routers and ONT equipment
• A secondary connection, such as 4G or 5G failover
• A mobile or softphone fallback so teams can answer from anywhere
• Documented procedures for power or connectivity outages

Because Lodgestory is cloud-hosted, calls can be answered from the browser or the mobile network even if the main office loses its connection.

Step 9: Test, Cut Over, Monitor

A safe cut-over looks like this:

Week -4  Audit complete, port requests submitted
Week -3  New IVR and routing built on temporary virtual numbers
Week -2  Pilot with one team, record and review test calls
Week -1  Staff training, softphones installed, failover tested
Day 0    Port completes, calls route to Lodgestory, legacy line kept as safety net
Day +7   Review abandonment, wait times, missed calls
Day +30  Cancel legacy lines once metrics are stable

How Lodgestory Helps You Move Without Missing a Call

Lodgestory is built so that voice is part of a unified workspace, not a bolt-on. The pieces that matter for PSTN migration are:

• Cloud voice and IVR: carrier-grade infrastructure with multi-region SIP trunking, so there are no on-site PBX boxes to maintain
• Virtual numbers and DIDs: give every department, location or campaign its own number
• WebRTC softphone: agents take and make calls from the browser with no desk phone, ideal for hybrid teams and multi-site operations
• Click-to-call: start outbound calls straight from a contact record or ticket
• Call recording and logs: a full audit trail for compliance and quality
• Supervisor controls: monitor, whisper, barge and transfer for live coaching
• Unified inbox and CRM: voice sits next to WhatsApp, email, SMS and Instagram, so every contact has one history

You can also pair voice with automation. AI call agents can handle routine inbound queries around the clock, and a human agent steps in only when needed. For a wider view of where cloud voice is heading, see six emerging CX trends for cloud telephony.

Sector Playbooks

Hotels and Resorts

Front desks lose hours to repetitive calls about check-in times, parking and room service. When migrating:

• Port the main reservations number and publish new DIDs for housekeeping, concierge and events
• Build an IVR that answers the top five FAQs automatically
• Route after-hours calls to a night manager's softphone
• Shift booking confirmations and pre-arrival messages to WhatsApp to reduce inbound call volume

See how properties are doing this in customer success stories from hotels using Lodgestory.

Clinics and Healthcare Providers

Healthcare adds a layer of urgency, because missed calls can mean missed care.

• Identify every patient-facing system on copper, including telecare, nurse-call and alarm lines
• Keep a priority route for urgent callers in your IVR
• Use appointment reminders and confirmations on WhatsApp or SMS to cut no-shows
• Record and tag calls to maintain quality and audit trails

If you support residents or patients who rely on telecare, coordinate with device providers and local authorities. The government's supported-journeys guidance exists precisely for these users.

Logistics and Transport

Dispatchers, drivers and customers all depend on fast, reliable voice.

• Give each depot its own DID and route to a shared queue so overflow is handled across sites
• Use click-to-call from the ticket or shipment record
• Mask numbers where driver privacy matters, as explained in our guide to call masking
• Send proactive delivery updates by message so fewer customers call to ask where their parcel is

Common Mistakes to Avoid

1. Cancelling the old line before the port completes. You can lose the number permanently.
2. Forgetting non-voice devices. Alarms, lifts and payment terminals are the most common casualties.
3. Copying a bad IVR. Migration is your chance to simplify.
4. Ignoring power and connectivity resilience. Plan for outages from day one.
5. Leaving it until 2026. Port queues, engineer availability and device lead times will all stretch as the deadline approaches.
6. Falling for scams. Be wary of unexpected calls claiming to be about your digital switchover. Verify through official provider channels.

Measure Success After the Move

Once you are live, track the metrics that tell you whether the migration improved service or just preserved it:

• Abandonment rate should fall as routing and queues improve
• Average speed of answer and average hold time should decline
• First call resolution should rise as agents get customer context in one workspace

Our contact center metrics guide covers the full set worth monitoring.

Your Next Step

The PSTN switch-off is a fixed date, but your migration does not have to be a scramble. Start with the audit this week, submit port requests early, and build your new IVR and routing on temporary numbers so you can test with real calls before cut-over.

Lodgestory gives hotels, clinics and logistics teams cloud voice, virtual numbers, a WebRTC softphone and a unified inbox in one platform, so retiring analogue lines becomes a service upgrade rather than a risk. Sign up with Free Forever Plan and start building your post-PSTN voice setup today.

Frequently Asked Questions

When exactly does the UK PSTN switch off? The national target is 31 January 2027, but local exchange stop-sell and migration schedules may affect you sooner.

Can I keep my existing business number? In most cases, yes. UK regulation requires number portability without direct porting charges, and a geographic number typically takes 10 to 14 working days to port. Keep the old service active until the port completes.

Will my card terminals and alarms still work? Only if they are IP-compatible or replaced. Ask each supplier for written confirmation well before the deadline.

Do I need desk phones in the cloud? No. With a WebRTC softphone, your team can take and make calls from a browser, and you can add IP handsets only where you need them.