Can a Cloud Phone System Run Alongside Our Old One?
Yes, it can, and for many UK businesses it is the safest way to move. Running both systems for a while lets you test the new one with real calls, real staff and real problems, while the old system remains as a safety net.
It is not free of complications, though. Two systems means two sets of settings, possibly two bills and some confusion about who is on which. This guide explains the main ways to run in parallel, what to watch for and how to bring the overlap to a clean end.
Why Run Both at Once?
A cloud based phone system for business is usually simple to set up. The risk sits in the transition: numbers that must not go dead, staff who need to keep taking calls and equipment that may be tied to the old lines.
Overlap reduces that risk. You can prove the new system works before relying on it, train people gradually and keep a working fallback if something fails. The price is some extra cost and effort, which is usually small compared with a botched changeover.
Four Ways to Run in Parallel
1. Split by number
Keep your main numbers on the old system and put new numbers on the cloud one, for example a new direct line for a pilot team. Nothing existing is at risk, and you can move numbers across gradually as confidence grows.
2. Split by team
Move one department first, such as a small sales or admin team, and leave everyone else on the old system. This gives you honest feedback from real users without involving the whole business.
3. Connect the two systems
You can link them using a SIP trunk or SIP extension between the old PBX and the cloud platform. That lets staff on both systems call each other by extension and transfer calls across. It makes the overlap feel seamless, but it needs a compatible PBX and some configuration, so ask your supplier whether yours supports it.
4. Use the old system as a fallback
Keep the old lines or PBX live while the cloud system takes live traffic, ready to catch calls if the new one has an issue. This is more of a safety net than a long-term arrangement, so decide in advance how long it will stay.
Many businesses combine these, such as a team pilot with a connected PBX and a staged number port.
The Practical Issues to Plan For
Phone numbers
Numbers can only point to one place at a time. During the overlap, you decide which system answers which number. When you port numbers to the new provider, move them in stages if possible, and port your main number last. Keep the old service active until each port completes and you have tested calls. UK number porting is well established, but timelines vary, so ask for dates in writing.
Internal calling
If half the business is on each system, internal calls need a route. Without a link between them, colleagues may have to dial full external numbers to reach each other. Either connect the systems or keep the pilot group small and short-lived.
Caller ID
Outbound calls should show a consistent number. Check what each system presents, and avoid showing different numbers for the same team. Check Ofcom’s current guidance if you make outbound business calls.
Voicemail and call history
Messages will land in two places. Agree where staff should check, and forward voicemail to email where possible so nothing is missed.
Costs
Overlap means paying for both for a while: line rental or PBX maintenance on one side, licences and calls on the other. Set an end date and budget for it. Many cloud based phone systems for small business are billed monthly, which makes a short overlap easier to manage.
Contracts
Check when your old contract ends and what notice it requires. Overlap is easy to plan if your old agreement is expiring, and expensive if it is not. Look for early termination charges before committing to dates.
Equipment and attached devices
Alarms, card machines, lift phones and door entry systems may depend on the old lines. Do not cancel those until you have confirmed how each will work afterwards.
Staff confusion
Two systems means two ways to do things. Give pilot users a short guide, a named person to ask and a clear message about which handset or app to use for what.
A Phased Plan
A simple structure keeps the overlap short and controlled.
Phase 1: Prepare. Audit your numbers, devices and contracts. Check your internet connection, including upload speed and router settings.
Phase 2: Pilot. Set up the cloud system with a small group, using new numbers or a staged port. Test calls, voicemail, routing and mobile apps.
Phase 3: Connect and expand. Link the two systems if needed, and bring in more teams. Review issues and fix them while the old system still protects you.
Phase 4: Port and switch. Port remaining numbers, with the main number last. Test inbound and outbound calls straight afterwards, and set up call forwarding to mobiles as a fallback.
Phase 5: Retire. When everything works for an agreed period, cancel the old lines and PBX maintenance. Confirm what else depended on them first.
The timing matters. Openreach is retiring the copper-based phone network, with the current deadline set for January 2027, so if you rely on ISDN or analogue lines, check with your provider how much overlap time you actually have.
A Realistic Example
Consider a 35-person building services company in Leeds with an ageing on-site PBX and ISDN lines. The owner wants to move to a hosted telephony system, but fears missed calls during the change.
The company starts with a five-person estimating team, giving them new direct numbers on the cloud platform and connecting it to the PBX so everyone can still dial by extension. After three weeks of testing, it adds the finance team. The main number and reception follow later, ported on a quiet Saturday, with calls forwarded to mobiles during the changeover.
Throughout, the old PBX stays as a fallback. When calls have run smoothly for a month, the company cancels its ISDN lines and PBX maintenance. The total overlap costs a little more than a straight switch, but nobody noticed a dropped call.
When Parallel Running Is Not Worth It
Overlap is not always necessary. For a very small team with simple needs, a clean overnight switch, tested in advance, can be simpler and cheaper. For a tiny cloud phone system small business setup with a handful of staff, a weekend changeover and a mobile fallback may be enough. Parallel running is most valuable when:
-
Calls are business-critical
-
You have multiple sites or departments
-
Your old system is complex or poorly documented
-
Staff need time to adjust
-
You depend on attached devices that need separate checking
Questions to Ask Providers
-
Can you support a phased migration, with staged number porting?
-
Can the cloud system connect to our existing PBX for internal calls?
-
How long can we keep both systems running, and what does that cost?
-
What happens to our numbers during the overlap?
-
What help do you provide for testing and training?
-
How is failover handled if the new system has a fault?
Look for providers that treat transition as part of the service, not an afterthought. Anyone comparing a cloud phone system UK providers offer should ask how migration is handled, because the quality of the handover often matters as much as the features. A provider such as Wavetel Business, which works with UK organisations on VoIP and business communications, should be able to talk through how a phased move would work for your setup.
Frequently Asked Questions
Can I keep my old phone lines while I test a cloud system?
Usually yes. Many businesses keep existing lines and the old PBX live during testing, then cancel once the new system has proved itself. Check contract terms and any attached devices first.
Will staff on the old and new systems be able to call each other?
Only if the systems are connected or you use external numbers. Linking them with a SIP trunk or extension, where your PBX supports it, makes internal calling much smoother.
How long should I run both systems?
As short as is safe. For many businesses that is a few weeks to a couple of months, depending on size and complexity. Set an end date at the start.
Is it more expensive to run two systems?
Yes, for a while. You pay for the old and new systems at the same time. Monthly billing on most hosted VoIP systems keeps this manageable, but plan the budget.
Do I need new phones for the cloud system?
Not always. Many staff can use softphone apps, and some existing handsets may work. Check compatibility before buying anything.
Conclusion
A cloud phone system can run alongside your old one, and for many UK businesses that overlap is the most reassuring way to move. You can pilot with a small team, connect the systems for internal calls, port numbers in stages and keep the old setup as a fallback until you are ready.
Your practical next step: decide how you will split the move (by number, by team or both), set an end date for the overlap and check your old contract terms. Then ask your provider to outline a phased plan, including staged porting and a clear switch-off date for the old system.
- Art
- Causes
- Crafts
- Dance
- Drinks
- Film
- Fitness
- Food
- Jeux
- Gardening
- Health
- Domicile
- Literature
- Music
- Networking
- Autre
- Party
- Religion
- Shopping
- Sports
- Theater
- Wellness