BT phone line replacement UK — options and timing

For most UK firms the practical replacement for a BT PSTN/ISDN line is a SIP trunk or hosted VoIP service from BT Openreach or other carriers, and you should **start planning now** because the September 2027 stop-sell is the hard deadline to replace legacy lines.

Speed vs. porting risk

Fast migrations look tempting: fewer days offline, less training and a quick win for the accounting team. The trade-off is that moving quickly often means you run straight into operational bottlenecks — number porting, carrier scheduling and bespoke site integrations all create risk. If speed is your priority, plan for a staged cut-over (one site or one line at a time) and a short fallback window so customers can still reach you while numbers move.

In our experience, businesses that leave a PSTN migration until three months before the September 2027 stop-sell tend to hit two problems at once — carrier porting queues at that point are deeply backed up, and any bespoke alarm or lift integration takes eight weeks minimum to reprovision. Twelve months lead time is realistic if a site has any legacy analogue kit at all. That single observation explains why ‘fast’ can be false economy: a rushed migration can mean long delays for ports and surprise engineering work that forces a temporary return to old kit.

Practical signals that you’re prioritising speed but managing risk:

  • Keep at least one working PSTN line during the porting window.
  • Ask your supplier for a committed porting schedule and penalties.
  • Document each device that uses an analogue line (alarms, door entry, lifts) before ordering equipment.

Cost vs. call reliability

Replacing BT phone lines involves an obvious cost tension: low monthly price for SIP trunks versus the higher, more predictable cost of a managed hosted telephony service that bundles uptime and support. The trade-off is simple — cheaper services can be fine if your traffic is light and you have good internet resilience; higher-cost managed services buy you SLA-backed call quality and a vendor handling ports and failover.

Assess this by counting risk, not calls. If your reception, sales or compliance functions rely on crystal-clear inbound calls (high-volume contact centres, regulated practices, or firms that must record calls), then spend a little more on guaranteed uptime and call quality. If you primarily use phones for occasional outgoing work, a basic SIP trunk with proper QoS on your WAN can be adequate.

Checklist to compare costs against reliability:

  • Measure average concurrent call usage over a week — that defines trunk sizing.
  • Ask vendors how they handle internet outages (failover to mobile, PSTN breakouts, or secondary circuits).
  • Insist on jitter/latency tests and a trial period where possible.

DIY vs. managed migration

Doing it yourself saves on upfront costs but shifts risk onto your internal team: configuration, port management and resolving quirks in analogue integrations. A managed migration hands those headaches to a supplier in exchange for a monthly fee and, often, predictable timelines. The trade-off: control and potential savings versus reduced operational overhead and quicker problem resolution.

If you have internal networking skills and spare engineering time, a DIY route can work for a single office with modern handsets. For multi-site setups, legacy PBXs, or any analogue alarm/lift dependencies, managed migration is the safer choice — it reduces hidden labour costs and often shortens downtime.

Where to get help: compare quotes and services, and look at options for hosted voice and migration support such as business phone systems and VoIP options. When evaluating providers, ask for a line-by-line migration plan, exact porting windows and a list of any items they will remediate on-site.

Recommendation — if X matters more, then Y

If avoiding customer disruption matters more than saving a few hundred pounds, then choose a managed provider with clear SLAs and a staged porting plan. If monthly cost matters most and your traffic is low with resilient internet, then a self-managed SIP trunk with tested failover will usually be acceptable. Either way, treat the September 2027 stop-sell as a hard deadline and give yourself up to 12 months if you have any legacy analogue devices to reprovision.

Next step: schedule an audit of phone-connected devices, get two migration quotes (one DIY, one managed) and book porting windows now to lock in a realistic timeline and cost. Doing that preserves revenue, avoids emergency engineering call-outs, and gives your team breathing space.

Related reading

FAQ

How long does BT phone line replacement take for a small office in the UK?

Typical migrations run from a few days for a single modern IP line to **up to 12 months** if you have legacy analogue kit, because bespoke alarm or lift reprovisioning alone can require eight weeks or more.

Will my alarm or lift stop working after the PSTN switch-off?

It can — bespoke alarm and lift integrations normally need reprogramming or an ATA and then testing; expect **at least eight weeks** minimum to reprovision one-off integrations.

Can I keep my existing analogue handsets when replacing a BT line?

Possibly, using an analogue telephone adapter (ATA) or a gateway, but reliability can be worse than replacing with native IP handsets; test any ATA in your environment before committing.

When should I start the migration to avoid porting queues and delays?

Start planning immediately and book work so you have up to **12 months** lead time where analogue kit exists; leaving it until three months before September 2027 risks long porting queues and late reprovisioning work.