How to Move Your Business Phone System to VoIP: A Practical Migration Guide

Businesses replace their phone systems for practical reasons: the existing system has become costly to maintain, the company has outgrown it, staff now work from more than one location, or the current provider is no longer meeting expectations. Some are planning ahead of the wider industry move away from legacy copper-based services. Whatever the trigger, moving a business phone system to VoIP, hosted telephony or a cloud phone system is a project, not a product swap.

A successful VoIP migration starts with assessment and planning. Before any platform is chosen, the business needs a clear picture of its numbers, users, call flows, connectivity and contract position. Number porting, network readiness, call routing, testing and staff training all need consideration, and the right approach depends heavily on what is in place today.

This guide is written for businesses in Oxfordshire, Buckinghamshire and across the UK that are reviewing their phone system. It does not assume which system you use now, and it does not pretend every migration looks the same.

If you are reviewing your current business phone system, Fidelity Group can help you assess your requirements and identify the right migration approach.

Why replace an existing business phone system?

Most businesses do not replace a phone system for its own sake. Reviews usually start when one or more of the following becomes a problem:

• Maintenance cost or difficulty. An ageing on-premise system may depend on spare parts, specialist engineers or a support contract that is becoming harder to justify.
• Growth. Adding users, lines or a new site may be slow or expensive on the current system.
• Location flexibility. Staff may need to make and receive business calls from home, from client sites or from a second office.
• Limited call routing. The business may want queues, auto-attendant menus, time-of-day rules or overflow routing that the current system handles poorly or not at all.
• Reporting. Sales and customer-service leaders often want visibility of answered, missed and abandoned calls that older systems cannot provide.
• Integration. The current system may not connect to the CRM, helpdesk or Microsoft 365 environment the business relies on.
• Provider support. Slow responses, unclear billing or a lack of proactive advice are common reasons for switching provider even where the technology still works.
• Premises changes. Opening, closing or consolidating offices is a natural point to reconsider telephony.
• Legacy services approaching replacement. If the business still relies on analogue lines or ISDN, the provider may already have set out a migration plan as part of the wider transition to digital services.
• Future fit. The current system may simply not support where the business is heading over the next few years.

None of this means every legacy system is poor, or that VoIP is automatically cheaper. A well-maintained on-premise system can serve a business for years. The question is whether it still fits how the business works now and how it expects to work next.

Is VoIP suitable for every business?

VoIP suits a very wide range of organisations, but suitability should be assessed rather than assumed. A professional review before any platform or supplier is selected should cover:

• Size and user count. A five-person office and a 200-seat multi-site organisation have different needs, but both can usually be served by a hosted phone system with the right design.
• Locations. Multiple sites, home workers and field staff all affect the design and the connectivity needed at each location.
• Call volumes. High inbound volumes, particularly in sales or customer-service teams, place greater demands on queuing, reporting and network capacity.
• Internet and network suitability. VoIP depends on a stable IP connection and a well-configured internal network, not just a fast headline broadband speed.
• Mobile and remote working. If the business needs the same number and features on mobiles and laptops, this should shape the platform choice.
• Regulatory and emergency-calling considerations. Businesses should understand how emergency calls are handled from a VoIP service, including what happens during a power or internet outage, and any location-information requirements. Where specific rules apply, current Ofcom guidance and the provider’s own terms should be checked.
• Existing hardware. Some desk phones and headsets may be reusable; many will not be. This needs checking against the chosen platform.
• Integration requirements. CRM, Microsoft Teams and other software integrations vary by platform and licence tier.
• Budget and contract commitments. Existing contract end dates, notice periods and early-termination terms can affect timing as much as technology does.
• Resilience. Businesses that cannot afford to lose inbound calls may need backup connectivity, automatic call forwarding or both.

Step 1 – Audit your existing phone system

Before requesting proposals, document what you have today. A provider can only design a reliable migration if the starting point is accurate. The following pre-migration audit checklist is a good starting point:

Numbers – Main business numbers – Direct-dial (DDI) numbers for individuals and departments – Geographic numbers (for example, an 01865 Oxford or 01494 High Wycombe number) – Non-geographic numbers (03, 08 and similar ranges) – Any numbers used for fax, alarms or card terminals

Users and structure – Number of users, including part-time and shift staff – Number of sites and which users work at each – Departments and teams – Mobile users and remote workers

Call handling – Hunt groups – Call queues – Auto-attendant menus – Opening-hours rules and out-of-hours routing – Voicemail boxes and who monitors them – Call recording, including retention requirements – Call reporting currently used

Equipment and software – Existing handsets (make, model and quantity) – Headsets – Softphones already in use – CRM or software integrations – Emergency calling arrangements

Connected services – Alarm lines, lift lines, door-entry systems, payment terminals, franking machines or other devices that may use telephone connectivity

Commercial – Contract end date and notice period – Current support arrangements and response times

The connected-services point deserves emphasis. Devices such as lift alarms, intruder alarms and older payment terminals sometimes rely on an analogue line. These may need separate investigation, and possibly separate solutions, before the line is migrated or ceased.

Step 2 – Define your requirements

With the audit complete, translate it into requirements. This is the document that lets you compare proposals on a like-for-like basis. Cover:

• Number of users now and projected growth over the contract term
• Number of locations, including home workers
• Desk phone requirements by role
• Mobile app requirements
• Desktop softphone requirements
• Reception needs, including transfer and presence visibility
• Call queues for sales or customer-service teams
• Call recording, including which teams and how long recordings are kept
• Call reporting and who needs access to it
• CRM integration
• Microsoft Teams integration
• Multi-site working, such as internal dialling and cross-site overflow
• Out-of-hours routing
• Business continuity and failover expectations
• Admin permissions: who can change call flows and add users
• Training required for users, reception and administrators
• Support hours and escalation routes
• Compliance requirements relevant to your sector

Example requirement statement (illustrative only, not a recommendation):

We need a phone system for 20 users across two sites, with a main reception number, sales and service queues, mobile access, call recording for selected teams and the ability to add users as the business grows.

A statement like this gives a provider enough to propose a design. It also makes it obvious when a proposal has ignored something you asked for.

Step 3 – Assess broadband and network readiness

VoIP runs over an IP network, but call quality depends on far more than the headline download speed. A broadband speed test alone is not a VoIP readiness assessment. A provider should review:

• Download and upload performance, including at busy times
• Latency, jitter and packet loss on the connection
• The number of concurrent calls the business expects at peak
• Wi-Fi coverage and performance where softphones or wireless handsets will be used
• Wired network quality, including cabling and switch capacity
• Switches and power, including Power over Ethernet for desk phones
• Router and firewall configuration, including how voice traffic is prioritised
• Other business-critical traffic sharing the connection, such as cloud backups or video calls
• Backup connectivity, for example a secondary broadband line or a 4G/5G fallback
• Power resilience, since IP phones and routers stop working during a power cut unless protected

Bandwidth requirements are often quoted as a single figure, but the actual requirement depends on the codec used, the platform, the number of simultaneous calls and the other traffic on the network. The supplier should assess the specific environment rather than apply a generic threshold. A business may need to improve its connectivity or internal network before introducing VoIP, but this cannot be determined accurately without assessing the specific environment. Where a provider supplies both connectivity and telephony, both can be assessed together. Fidelity Group provides business broadband and connectivity alongside hosted telephony, so the voice service and the network it runs on can be reviewed as one requirement.

Step 4 – Choose the right VoIP model

“VoIP” covers several different deployment models. None is universally right; the choice should follow the requirements.

Hosted VoIP / hosted telephony. The phone system runs in the provider’s cloud and users connect over the internet with desk phones, apps or softphones. Suits small and mid-sized businesses, multi-site organisations and hybrid teams that want features without on-site equipment. Ask what is included per user, how call flows are administered, and what happens if the site’s connection fails.

Cloud PBX. Often used interchangeably with hosted telephony, though some providers use “cloud PBX” to describe a more configurable platform aimed at organisations with complex routing. Ask about admin controls, reporting depth and how multi-site routing is handled.

SIP trunking with an existing or new phone system. The business keeps (or buys) an on-premise or virtualised PBX and connects it to the public network over SIP trunks instead of ISDN or analogue lines. May suit organisations with a recent PBX investment or specific on-site requirements. Ask whether the PBX is SIP-compatible, how many concurrent channels are needed, and who supports the PBX itself.

Microsoft Teams telephony. Calling is added to Microsoft Teams so users make and receive external calls from the Teams client. Options generally include the vendor’s own calling plans, Operator Connect, or Direct Routing through a certified session border controller and a provider’s SIP trunks. Suits organisations already standardised on Teams, but licensing, call-centre depth and reception functionality vary. Ask which model is proposed and why, and how queues, recording and reporting will be delivered.

Mobile and desktop softphone solutions. Some businesses need very few desk phones and can operate mainly on apps. Ask how mobile users are reached when out of signal or data, and how presence and transfers work across devices.

Contact-centre platforms. Sales and customer-service teams with high volumes may need skills-based routing, wallboards, detailed reporting and quality management beyond a standard phone system. Ask whether this is a separate platform or a tier of the same one, and how the two interact.

Feature availability depends on the selected platform, configuration, supplier and commercial package. Do not assume a feature is included because it appears in a brochure; ask for it to be confirmed in writing against your requirements.

Step 5 – Plan business number porting

Number porting is the process of transferring your existing telephone numbers from your current provider to the new one, so callers continue to use the numbers they know. For most businesses, keeping the existing number is non-negotiable, which makes porting one of the highest-risk parts of a migration.

Key points:

• Eligibility must be confirmed. Not every number can be ported to every provider. Eligibility depends on the number range, the location, the service the number currently sits on and the arrangements between the losing and gaining providers. A provider should check each number before committing to a plan.
• Geographic numbers. Standard area-code numbers can often be ported, but the process depends on how they are currently delivered and whether they are single numbers, multi-line groups or DDI ranges.
• Non-geographic numbers. 03 and 08 numbers follow different processes and may sit with a different provider from your main lines.
• Direct-dial numbers. DDI ranges need to be listed accurately; a missing or mis-typed number in a range can cause a port to be rejected.
• Lead times. Porting has lead times that vary by number type and provider. Complex or multi-line ports generally take longer than single-line ports. A provider should give a realistic window rather than a promise.
• Data accuracy. The port request must match the losing provider’s records exactly, including the installation address, account holder and account number. Errors are a common cause of delay.
• Existing contract and billing. Check whether your current contract has a minimum term, and understand how billing overlaps during the port window.
• Temporary forwarding. Ask how calls will be handled if there is a gap between the new system going live and the port completing.
• Failure or delay planning. Agree in advance what happens if a port is rejected or delayed, and who owns the fix.

⚠️ Do not cancel your existing business phone service until your new provider has confirmed the porting plan, cutover date and fallback arrangements. Cancelling a line before the port completes can result in the number being lost.

Step 6 – Design your future call flows

Migration is a good moment to improve how calls are handled, rather than simply copying the old setup. Map out:

• Main number: what callers hear first
• Reception: whether calls are answered by a person, an auto-attendant or a combination
• Department options: which menu choices exist and where each leads
• Sales and customer-service queues: who is in each, how calls are distributed and what callers hear while waiting
• Hunt groups: for teams that need ring-all or sequential ringing
• Voicemail: which numbers have it and who is notified
• Out-of-hours messages and where calls go outside opening hours
• Holiday closures: how bank holidays and company shutdowns are handled
• Overflow routing: what happens when nobody answers within a set time
• Mobile users: whether mobiles ring simultaneously, sequentially or only when selected
• Multi-site routing: whether sites cover each other and how internal calls are dialled
• Emergency or priority contacts: routes for urgent callers or key accounts
• Call recording notifications, where recording is used and an announcement is required

Example:

A call to the main number might be answered by a welcome message, offered department options during opening hours, routed to an overflow destination after a defined period and sent to an out-of-hours message when the office is closed.

The precise capabilities available depend on the chosen system. Document the call flows as diagrams or tables so they can be tested line by line before cutover.

Step 7 – Decide on handsets, apps and accessories

The right device depends on the role, not on a blanket policy. Options generally include:

• Desk phones, from basic models to executive handsets with colour screens and busy-lamp fields
• Desktop softphones running on laptops and PCs
• Mobile VoIP apps that present the business number from a personal or company mobile
• Headsets, wired or wireless, for high-volume users
• Reception consoles or expansion modules for handling multiple calls and transfers
• Conference devices for meeting rooms
• Teams-compatible devices, where Teams telephony is part of the design

Example by role:

• Reception may need a desk phone or console with presence visibility.
• A sales team may prefer headsets and softphones.
• Field staff may need a mobile app.
• A meeting room may need a dedicated conference device.

Do not assume existing handsets are compatible with the new platform. Some can be re-provisioned; others cannot, or can only be reused with reduced functionality. Compatibility must be checked with the selected platform and supplier before the commercial proposal is finalised.

Step 8 – Test the system before cutover

Testing should involve representative users from each team and real working scenarios, not just a technician placing one test call. Use a testing checklist along these lines:

• Inbound calls to every ported and new number
• Outbound calls to landlines, mobiles and international numbers where relevant
• Caller ID presentation on outbound calls
• Number presentation for different teams or sites
• Internal transfers between users and sites
• Blind and attended transfers
• Call queues, including wait messages and agent distribution
• Hunt groups
• Auto-attendant menus, including every option and invalid-input handling
• Voicemail deposit, retrieval and notifications
• Call recording, including where recordings are stored and who can access them
• Call reporting output
• Mobile apps on the devices staff actually use
• Desktop softphones, including headsets
• CRM integration, such as screen-pop and click-to-dial
• Microsoft Teams integration, if relevant
• Out-of-hours rules
• Holiday routing
• Overflow routing
• Multi-site calls
• Audio quality under normal and peak load
• Failover or forwarding during a simulated connection loss
• Emergency-calling arrangements
• User permissions and admin access

Record the results. Any failed test should be resolved or formally accepted as a known issue before the cutover date is confirmed.

Step 9- Prepare employees and stakeholders

User adoption is part of the migration, not an optional afterthought. A technically perfect system that reception cannot operate on day one will still feel like a failed project. Plan for:

• User training on the basics: answering, holding, transferring and voicemail
• Reception training on consoles, presence and transfer etiquette
• Sales and customer-service workflows, including queue behaviour and wrap-up
• Admin training so someone in the business can change call flows and add users
• Call-recording responsibilities, including who can retrieve recordings and how retention is managed
• Mobile app setup on staff devices ahead of cutover
• Voicemail greetings and PINs
• Call transfers between sites and to mobiles
• Reporting: who receives it and what they should act on
• Support contacts: how users raise a problem and to whom
• Internal communication explaining what changes, when and why
• Cutover-day responsibilities so every team knows who is checking what

Short written guides or a one-page quick reference often do more than a single training session, especially for staff who were absent on the day.

Step 10 – Plan the cutover and fallback

The cutover plan is the document that turns preparation into a controlled go-live. It should record:

• Date and time of cutover
• Technical owner at the provider
• Supplier contact and escalation route for the day
• Internal business owner with authority to make decisions
• Porting status for every number
• User readiness, including devices issued and apps installed
• Call-flow confirmation against the design
• Device delivery and configuration status
• Testing results and any accepted known issues
• Communication plan for staff and, where appropriate, customers
• Fallback arrangements if the new service has a problem
• Temporary forwarding in place during any porting gap
• Escalation process if something goes wrong
• Post-cutover checks in the hours and days after go-live

There is no universally correct time to cut over. The best timing depends on business hours, call volume, porting requirements and the supplier’s process. A business with a quiet Friday afternoon may choose differently from one whose busiest period is the end of the week.

How long does a VoIP migration take?

There is no universal timeframe for a business phone system migration. Factors that affect it include the number of users and sites, number-porting requirements, the existing contract, platform complexity, hardware requirements, network changes, CRM or Microsoft Teams integration, call-flow complexity, training and supplier availability. Porting and any regulatory requirements can set the pace regardless of how quickly the rest of the project moves.

The stages, however, are broadly consistent:

Stage	Main activity
Discovery	Review the existing system, numbers, users and locations
Requirements	Confirm features, integrations and working patterns
Design	Build the proposed system and call flows
Preparation	Configure users, devices, apps and network
Testing	Validate calling, routing, integrations and resilience
Cutover	Move live services and confirm number arrangements
Optimisation	Review user feedback, call reports and outstanding issues

Ask any prospective provider to walk you through these stages for your specific project and to say which ones they expect to take longest, and why.

Common business phone system migration mistakes

• Selecting a provider only because of a low monthly price
• Failing to document existing numbers, particularly DDI ranges
• Not checking number-porting eligibility before signing
• Cancelling the old service too early
• Ignoring broadband, Wi-Fi or internal networking
• Assuming all existing handsets will work
• Forgetting out-of-hours call routing
• Not testing the auto-attendant from a caller’s perspective
• Not checking caller ID on outbound calls
• Failing to train reception and customer-service users
• Not planning fallback arrangements
• Not confirming what support looks like after cutover
• Forgetting alarm, lift, payment or other services that use telephone lines
• Not checking contract notice periods with the current provider
• Treating the project as a licence change rather than a business-process change

VoIP migration for businesses in Oxfordshire and Buckinghamshire

Businesses in Oxfordshire and Buckinghamshire may have different requirements depending on their premises, connectivity, workforce and existing phone system. A company in Oxford with a hybrid team may need a different approach from a multi-site organisation operating across High Wycombe, Aylesbury or Milton Keynes.

Connectivity is a good example. A business park on the edge of Bicester or Didcot may have full-fibre options that a rural premises near Thame, Witney or Henley-on-Thames does not, which affects whether backup connectivity should be part of the design. A professional-services firm in Abingdon or Marlow may prioritise call recording and Teams integration, while a distribution business in Banbury may care most about mobile apps for staff who are rarely at a desk. An organisation in Beaconsfield with staff who commute into London may need the same number to work in the office, at home and on the train.

Local relevance in a VoIP provider should mean something concrete:

• Understanding the service area and the connectivity typically available across it
• Being clear about which activities are handled remotely and which, if any, are carried out on site
• Assessing each customer’s actual location and network rather than assuming
• Supporting multi-site organisations whose offices span both counties or extend beyond them
• Providing accurate contact and service information so you know exactly who to call

Fidelity Group serves businesses across Oxfordshire, Buckinghamshire and the wider UK.  Based in Henley on Thames, Fidelity Group offer onsite scoping, demonstrations and installations with 1-2-1 training to ensure a smooth transition takes place to your new VoIP services

Questions to ask a VoIP migration provider

Put these to every provider you shortlist, including Fidelity Group:

1. What information do you need about our current system?
2. Can you assess our network and connectivity?
3. Can we keep our existing numbers?
4. Which numbers are eligible for porting?
5. What happens if porting is delayed?
6. What is included in design and configuration?
7. Are handsets included?
8. Are mobile apps and softphones included?
9. Can the system integrate with our CRM?
10. Can it work with Microsoft Teams?
11. What support is available during cutover?
12. What happens if we experience a problem after launch?
13. How are failover and forwarding handled?
14. What training is included?
15. Are there minimum terms or minimum user numbers?
16. What happens if we add users or locations?
17. What services may need separate investigation?
18. What information is required before the project begins?

A provider who answers these clearly, in writing, is showing you what the migration will actually be like.

Why speak to Fidelity Group about your phone system?

Fidelity Group is a UK-based business telecoms provider supporting business phone systems, VoIP and hosted telephony, alongside business broadband and connectivity, business mobile, contact-centre solutions and Microsoft Teams telephony options. Because voice, connectivity and mobile can be assessed together, the whole requirement can be reviewed rather than one part of it.

If your organisation is reviewing its current setup, Fidelity Group can discuss your users, locations, working patterns, connectivity, number-porting requirements and future plans before recommending an appropriate next step. The aim is a migration plan you understand and can hold us to, not a proposal built on assumptions.

Start planning your VoIP migration

Replacing a business phone system should begin with a review of your current numbers, users, call flows, connectivity and contract position. Whether your organisation is based in Oxfordshire, Buckinghamshire or elsewhere in the UK, a structured assessment can help identify migration risks before you commit to a new system.

If you are ready to move your business phone system to VoIP, or simply want to understand what a migration would involve for your organisation:

• Request a business phone system review
• Discuss a VoIP migration with a Fidelity telecoms specialist
• Check whether your existing numbers can be retained
• Review our hosted telephony options

Frequently asked questions

How do I move my business phone system to VoIP? Start by auditing your current numbers, users, call flows, equipment and contract. Define your requirements, have your network assessed, choose a deployment model, plan number porting, design the new call flows, test with real users, train staff and cut over with a documented fallback. The exact sequence and effort depend on your existing system and the platform chosen.

Can I keep my existing business number when switching to VoIP? Often, yes. Geographic, non-geographic and direct-dial numbers can frequently be ported to a new provider. Eligibility is not automatic, though: it depends on the number range, location, current service and the arrangements between providers. Ask your new provider to confirm eligibility for every number before you commit.

How long does a business VoIP migration take? There is no fixed answer. A single-site business with a handful of numbers and no integrations is a smaller project than a multi-site organisation with DDI ranges, call recording and Teams integration. Number-porting lead times often set the minimum timescale. Ask for a stage-by-stage plan for your specific project.

Will my current handsets work with a new VoIP system? Possibly, but it must be checked. Some IP handsets can be re-provisioned for a new platform; others are locked to a previous provider or lack required features. Analogue handsets generally need an adapter or replacement. Confirm compatibility with the supplier before assuming any equipment can be reused.

Does VoIP require faster broadband? Not necessarily faster, but suitable. Voice traffic is sensitive to latency, jitter and packet loss, and it competes with other traffic on the connection. The actual bandwidth needed depends on the codec, platform, number of simultaneous calls and other usage. A provider should assess the connection and internal network rather than rely on a speed test.

What happens if the internet connection fails? It depends on the design. Many hosted systems can automatically divert calls to mobiles or another site if a location drops offline, and some businesses add backup connectivity such as a secondary line or 4G/5G router. Ask exactly what happens to inbound and outbound calls during an outage, and test it before go-live.

Is VoIP suitable for small businesses? Generally, yes. Hosted telephony can give a small business features such as auto-attendant, mobile apps and call reporting without on-site equipment. Suitability still depends on the connection, the working pattern and the budget, so an assessment is worthwhile even for a small team.

Can a VoIP system integrate with Microsoft Teams or a CRM? Many platforms offer Microsoft Teams telephony options and CRM integrations such as screen-pop, click-to-dial and call logging. Availability and depth vary by platform, licence tier and the specific CRM in use, so name your systems during requirements and ask for the integration to be demonstrated.

What should I check before cancelling my existing phone service? Confirm in writing that every number has ported successfully, that the new system has passed testing, that fallback and forwarding arrangements are in place, and that any alarm, lift, payment or other devices on the old lines have been dealt with. Then check your existing contract’s notice period. Only then should the old service be cancelled.

Is VoIP migration available for businesses in Oxfordshire and Buckinghamshire? Yes. Fidelity Group supports businesses across Oxfordshire, Buckinghamshire and the wider UK with business phone systems, VoIP and hosted telephony. The right approach for a business in Oxford, High Wycombe, Aylesbury or Milton Keynes depends on its premises, connectivity, workforce and existing system, which is why the process starts with an assessment.