Quick answer
Often, yes. If your on-site phone system is SIP-capable, still supported by its manufacturer, and does what you need, you can keep it and feed it with SIP trunks instead of ISDN or analogue lines. Nothing changes for the people using it. That is usually the cheapest compliant route through the switch-off, because the hardware is already paid for. Keeping it stops making sense when the system is out of support, when nobody left in the business understands it, or when the paid upgrade needed to make it speak SIP costs a meaningful fraction of replacing it.
This is the question I get asked most often by businesses with a phone system in a cupboard, and it is usually asked apologetically - as if wanting to keep working equipment is somehow behind the times. It is not. Plenty of switch-off advice quietly assumes the answer is "replace everything", which is convenient for whoever is selling the replacement. The honest answer is that it depends on four specific things about your system, and you can establish all four in an afternoon. If you would like us to look at yours and tell you straight, get a no-obligation quote - we will say if it is worth keeping.
Yes, keeping it is genuinely an option
The switch-off retires the lines, not phone systems. Your PBX does not stop working on 1 February 2027 - the ISDN or analogue circuits feeding it do. Replace those circuits with SIP trunks delivered over your internet connection and the system carries on: same handsets, same extensions, same call flows, same short-code dialling, same voicemail that everyone has finally got used to.
That last point is worth more than it sounds. A phone system migration is not really a technical project, it is a change-management project. Every "press 4 for accounts", every hunt group, every out-of-hours divert, every habit your staff have built up - all of it survives if the system survives. When people talk about hosted migrations going badly, the failure is almost never the technology; it is that nobody documented the call flows before turning the old thing off.
The four questions that decide it
| Question | Keep it if… | Replace it if… |
|---|---|---|
| Is it SIP-capable? | It supports SIP trunks natively, or with a licence you already own | It needs a hardware gateway or a paid upgrade costing a real fraction of replacement |
| Is it still supported? | The manufacturer still issues firmware and security updates | It is end-of-life or end-of-support, so faults become "find a used part on eBay" |
| Who understands it? | You have a maintainer, or in-house knowledge, and documentation | The person who set it up left in 2019 and nobody has the admin password |
| How much life is left? | Realistically three or more years of useful service | It is already limping, or your headcount has outgrown it |
Four yeses means keep it. Four noes means replace it. A mix means do the sums, and weight the "who understands it" row heavily - a technically capable system that nobody can configure is not actually a capability.
How it works in practice
The change is narrower than most people expect:
- SIP trunks replace your lines. Instead of ISDN channels arriving on copper, call capacity arrives over your internet connection. You size it on peak simultaneous calls rather than on the block you were sold - see multi-line phone systems and channels.
- Something terminates the trunk. Either the phone system speaks SIP directly, or a small gateway sits in front of it and converts. Either way it sits behind your router alongside everything else.
- Your numbers port across. Main numbers and full DDI ranges move to the new trunk provider. See keeping your business landline number.
- Analogue devices go behind an adapter. An ATA (analogue telephone adapter) gives you a socket that behaves like the old wall socket, so existing analogue handsets and some analogue-fed equipment can carry on.
- Your connectivity becomes load-bearing. Voice quality now depends on the internet connection, so it needs headroom and ideally resilience - see internet speed for VoIP.
Point four comes with a firm caveat. An adapter is fine for handsets and for undemanding equipment. It is not a reliable answer for alarm signalling, lift emergency lines or telecare, all of which have their own requirements and should be arranged with the companies that maintain them. Anything safety-critical needs a proper solution, not an adapter and optimism.
Where keeping it clearly wins
- A recent, supported system with a maintenance contract. You have already bought the capability. Spending again to get the same capability is not an upgrade.
- Complex call flows that work. If you have years of accumulated routing that genuinely fits how the business operates, rebuilding it is a cost and a risk, not a benefit.
- A short runway. If you have left this late, SIP trunks are the fastest compliant move. Swapping the lines is a smaller project than replacing the system.
- Sites with heavy analogue estates. Where a building has many analogue extensions, keeping the system and adapting at the edges is often far cheaper than a handset-per-user replacement.
- You are mid-contract on the hardware. Finish the term, then decide properly.
Where replacing it wins
- Out of support. No firmware, no security patches, and spares from the second-hand market. This is a business-continuity problem dressed up as a saving.
- The upgrade costs a real fraction of replacement. Some older systems need a SIP card, a licence and professional services to accept SIP at all. Once that adds up, you are paying to prolong something with a known end.
- Nobody can administer it. If a simple change means calling someone who may or may not answer, you do not control your own phone system.
- You need capability it will never have. Softphones for home workers, mobile apps, integration with your CRM, call recording with sensible retention, real reporting. Bolting these onto an old PBX usually costs more than a platform that includes them.
- Multiple sites. Linking sites is where on-premises systems get expensive and cloud gets cheap. If you have several locations, read migrating multi-site and multi-line businesses before deciding.
Think in five-year totals, not monthly line items
The comparison people make - "SIP trunks are cheaper per month than hosted seats" - is usually true and usually incomplete. Over five years the honest comparison includes:
| Cost element | Keep the system + SIP trunks | Replace with hosted |
|---|---|---|
| Trunk or seat charges | Per channel, sized on concurrency | Per user, per month |
| Hardware | Already owned; any SIP upgrade | Usually included or reusable handsets |
| Maintenance contract | Ongoing, and it rises as kit ages | Included in the service |
| Firmware, patching, admin time | Yours to own | Provider's |
| Upgrades during the five years | Possible, and lumpy | Continuous, included |
| Cost when you eventually replace it | You will still pay this, later | Already paid |
That last row is the one that decides most of these. If your system has eight good years left, keeping it is straightforwardly the right call. If it has two, you are choosing to run this project twice - and the second time you will be doing it without a deadline forcing everyone to cooperate. For a full breakdown of migration spend either way, see what the PSTN switch-off costs a business, and for the on-premises versus cloud economics generally, hosted vs on-premise PBX.
The two risks nobody mentions
Security. Once your phone system is reachable over the internet, it becomes something attackers scan for. Toll fraud - where a compromised system is used to dial expensive international destinations, usually over a weekend - is a genuine and long-standing problem, and the bills are not small. It is entirely manageable with a properly configured firewall, strong credentials, international dialling barred by default and a spend cap on the trunks. But it is a task, and an unsupported system that cannot be patched makes it a much harder task.
Key-person dependency. An on-premises system means somebody has to be responsible for it. If that person is one individual, or an external engineer who is semi-retired, you have concentrated a business-critical function in a single point of failure. Write down the admin credentials and the call flows this week, regardless of which route you choose.
How to find out whether your system is SIP-capable
- Find the model number on the chassis or in the admin interface, and search it with "SIP trunk" - manufacturers publish this clearly.
- Check the support status on the manufacturer's site. "End of sale" is fine; "end of support" is the one that matters.
- Ask your maintainer two direct questions: can it take SIP trunks as it stands, and what would it cost if not?
- Count the analogue extensions you would need to adapt.
- Get the call flows documented while somebody still remembers them. Useful either way.
The bottom line
Keeping your existing phone system through the switch-off is a real, compliant and often cheapest option - and anyone who tells you otherwise without asking about your hardware is guessing or selling. Establish four things: SIP capability, support status, who administers it, and how many years are genuinely left. If the answers are good, replace the lines and keep the system. If they are not, the switch-off is a reasonable moment to stop maintaining something that has been quietly costing you more than it looks.
Send us the make and model and we will tell you which it is, with prices both ways: get a no-obligation quote or call 0333 006 9399.
Getting unknown calls on a business line? Our free UK phone number checker shows which network or provider Ofcom allocated any number to, and whether the range is in service — no sign-up.
Frequently asked questions
Can I keep my existing phone system after the PSTN switch-off?
Usually yes. The switch-off retires the lines feeding your system, not the system itself. If it is SIP-capable and still supported, SIP trunks delivered over your internet connection replace the ISDN or analogue circuits and everything else carries on unchanged - same handsets, same extensions, same call flows.
Do I need SIP trunks or a hosted system?
SIP trunks if you are keeping a capable on-site phone system; a hosted system if you are replacing it. SIP trunks are usually cheaper where the hardware is sound and has several years left. Hosted usually wins where the system is out of support, where you have multiple sites, or where you need home working and mobile apps.
How do I know if my phone system is SIP-capable?
Find the model number and check the manufacturer's documentation, or ask whoever maintains it. Most systems from roughly the last decade support SIP trunks natively or with a licence. Older ones may need a hardware gateway, which is fine if it is inexpensive and less fine if it costs a large fraction of replacement.
Can I keep my analogue handsets?
Often, yes. An analogue telephone adapter provides a socket that behaves like the old wall socket, so existing analogue phones carry on working. This does not extend to safety-critical equipment - alarm signalling, lift emergency lines and telecare need proper dedicated solutions rather than an adapter.
Is it cheaper to keep my phone system or replace it?
Over a five-year view, keeping it is usually cheaper if it has more than about three years of useful life, is still supported, and does not need an expensive SIP upgrade. If it has two years left, keeping it means running the same project twice - and the second time without a deadline to make everyone cooperate.
What are the risks of keeping an on-premises phone system?
Two that matter. Security: an internet-connected phone system is scanned by attackers, and toll fraud on a compromised system produces real bills, so it needs a properly configured firewall, strong credentials and international dialling barred by default. And key-person dependency: somebody has to own it, and often that somebody is one person with the only copy of the password.
Will my numbers and DDIs survive keeping the system?
Yes. Main numbers and full DDI ranges port to the new SIP trunk provider, and the mapping inside your phone system stays as it is, so nobody's direct number changes. Confirm the whole range is included in the port, and never cease the old lines before the numbers have moved.
