Problems & fixes · Business phone systems
Common problems when replacing a business phone system and how to avoid them
Last updated 25 October 2026 · 1 source listed · Reading time about 3 minutes
Short answer
Migrations most often go wrong over number porting delays, forgotten analogue devices, emergency call location, call flows rebuilt from assumption rather than reality, and untrained staff. Plan a staged cutover, document every number and device, test with real users, keep the old system until the port is confirmed, and prepare a rollback.
Who this is for: An organisation planning or mid-way through a phone system migration and wanting to anticipate the issues that most often disrupt calls, numbers and staff adoption.
What to evaluate
Inventory of numbers and devices
Forgotten lines for alarms, lifts, fax or card terminals are discovered only after cutover, often at the worst moment.
How to check: Walk every site and list each line, what it serves, and whether it can work through the new platform.
Porting plan and timing
Number transfers take coordination and can fail on mismatched account details, leaving callers unable to reach you.
How to check: Request a porting schedule, verify account information, and plan a cutover window with the old service still active.
Call flow documentation
Existing call handling often includes informal rules that no one remembers until they break.
How to check: Interview reception and support staff, document how calls are routed at different times, and test each flow before launch.
Emergency call configuration
Location data and routing for emergency calls must be correct from the first day.
How to check: Verify each extension's registered address and run approved tests of emergency routing where permitted.
Training and adoption
Staff who do not know how to transfer, park or retrieve voicemail create customer-facing problems.
How to check: Provide short role-specific guides and run a hands-on session before cutover.
Parallel running and rollback
A migration without a way back leaves the business exposed if the platform misbehaves.
How to check: Agree a rollback plan, keep the old system available for a defined period, and set criteria for deciding to revert.
Post-cutover monitoring
Issues often appear after the first busy day, when real call volumes test the setup.
How to check: Assign someone to watch call quality reports and collect staff feedback during the first weeks.
Comparison
| Approach | Good when | Watch out for |
|---|---|---|
| Single-day cutover | A small office with simple call flows | Any fault affects everyone immediately. |
| Staged by department | Medium organisations with distinct teams | Internal transfers between old and updated systems need a bridge. |
| Staged by site | Multi-site businesses with independent operations | Inter-site calling must work across both systems during the transition. |
| Parallel run with forwarding | Critical lines such as support or sales | Double administration and potential confusion about which system is active. |
| Pilot group then phased expansion | Organisations wanting to refine configuration first | Pilot users may not reflect the needs of the busiest teams. |
Decision worksheet
Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.
1. Have you checked each criterion?
0 of 7 criteria checked.
2. Compare options (0 = fails or unknown, 3 = meets it well)
| Criterion | |||
|---|---|---|---|
| Inventory of numbers and devices | |||
| Porting plan and timing | |||
| Call flow documentation | |||
| Emergency call configuration | |||
| Training and adoption | |||
| Parallel running and rollback | |||
| Post-cutover monitoring | |||
| Total (max 21) | 0 | 0 | 0 |
Questions to ask before you commit
- Can you provide a written migration plan with dates, responsibilities and rollback steps?
- Who is responsible for number porting and what happens if it is delayed?
- How will analogue devices be connected and tested?
- Can the old system stay active in parallel for a defined period?
- How are emergency calls tested and location data verified?
- What training do you provide and in what format?
- What support is available on cutover day and the days after?
- How will you report on call quality during the first weeks?
Typical trade-offs
Fast cutover or gradual rollout
- Upside
- A fast cutover shortens the period of running two systems.
- Downside
- Problems affect everyone at once, and recovery is more stressful.
Rebuild call flows to match current practice or redesign them
- Upside
- Matching practice reduces surprises for customers and staff.
- Downside
- You may carry over inefficiencies that a redesign would remove.
Keep old numbers or take the chance to simplify
- Upside
- Keeping numbers preserves customer familiarity and printed materials.
- Downside
- Legacy numbering can be messy and costly to maintain.
Common mistakes
- Cancelling the old service before the port completes, which can orphan numbers.
- Ignoring after-hours routing. Test evening, weekend and holiday settings.
- Not briefing reception staff, who face the first customer complaints.
- Skipping a test of the fax, alarm and lift lines.
- Switching everything on a Friday afternoon with limited support available.
Related questions
Why do number ports fail?
Common causes include mismatches between the account name, address or account number submitted and what the losing provider holds, expired authorisations, numbers attached to multiple services, or numbers with active contracts needing resolution. Port requests can be rejected and must be resubmitted, adding days. Collect a recent bill from the losing provider, verify every identifier, and ask the gaining provider to pre-validate details before the scheduled date.
How long should I keep the old system?
Keep it running until all ports have completed and you have confirmed stable operation through at least one full business cycle, including month-end or seasonal peaks if relevant. Check the contract for notice requirements on cancellation so that you are not forced to either overlap longer than needed or cancel too early. Having the old system available lets you revert quickly if the migration reveals a serious flaw.
What breaks most often after cutover?
After-hours routing, voicemail to email delivery, call forwarding rules and integrations with customer systems are frequent culprits, along with headset compatibility and users who are unfamiliar with transfer procedures. Many of these appear only under real use. Run a checklist covering each scenario and collect feedback from staff on the first days to resolve small problems before they become habits.
Should we involve staff in the planning?
Yes. Reception, support and sales staff know how calls actually flow and which features matter. Their input prevents the loss of informal practices that customers rely on. Involving them early also helps adoption, because people are more willing to use a system they helped shape and for which they have received appropriate training.
What if the new system performs badly after launch?
Use your pre-agreed criteria to decide whether to fix forward or roll back. Gather call quality data, identify whether the problem is network, configuration or platform, and escalate through the provider's support. If the old system is still available, switching routing back may be quicker than debugging under pressure. Document what went wrong so the next attempt avoids it.
Sources and further reading
These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.
- Consumer help center — Federal Communications Commission, retrieved 27 October 2026
Related guides
Comparison · Business phone systems
Hosted VoIP or on-premises PBX: choosing a business phone architecture
Hosted VoIP moves call control to a provider and charges per user, trading capital outlay and maintenance for dependence on your internet connection and the provider's platform. An on-premises PBX keeps control and local resilience but demands hardware, patching and in-house skill. Weigh staffing, site count, resilience needs, integrations and regulatory obligations.
How to choose · Business phone systems
How to choose a business VoIP or unified communications provider
Shortlist providers by how well they fit your call flows, not by headline feature counts. Examine reliability commitments, emergency calling, support quality, integration depth, security practices, admin tooling and contract terms. Run a pilot with real users, including call handling, mobile apps and headsets, before moving the whole organisation.
Requirements · Business phone systems
What your network must provide before moving to business VoIP
Reliable VoIP depends on sufficient upstream and downstream capacity, low delay and jitter, prioritisation of voice traffic, a router that handles real-time traffic well, power for handsets and, ideally, a second internet path. Audit the network, test under load, and plan for the electrical and cabling needs of desk phones.
Alternatives · Roaming and international
Home-plan roaming, travel eSIM or local SIM: how to stay connected abroad
Three main routes exist: use your home plan's roaming, install a travel eSIM that provides data from a foreign network, or buy a local SIM at the destination. Roaming keeps your number with minimal effort, an eSIM balances convenience and cost, and a local SIM can offer the most capacity but needs an unlocked phone and swaps your number.
Problems & fixes · Roaming and international
How to avoid a roaming bill shock and what to do if it happens
Bill shock abroad usually comes from background data, voice mail retrieval, ship or aircraft networks and destinations outside the included zone. Prevent it by disabling roaming or setting caps before departure, auditing apps, using Wi-Fi for heavy tasks, and checking usage mid-trip. If charges arrive, request an itemised bill and escalate formally.
Problems & fixes · Smartphones
Common smartphone problems: battery drain, full storage and slowdowns
Most slowdowns come from a short list of causes: an aged battery, nearly full storage, background apps and delayed updates. Work through them in order, starting with software and settings, then storage cleanup, and only then battery service or replacement. A factory reset after backing up is a reasonable last step before paying for repair.
Problems & fixes · B2B software
Common problems when migrating to a different CRM
CRM migrations fail less often on technology than on data quality, mapping and change management. Typical problems are duplicate and stale records, mismatched field types, lost relationships between contacts and accounts, broken attachments and activity history, and automations that do not translate. Reduce risk by cleaning before moving, mapping explicitly, migrating a trial subset first, and keeping the old system readable until the cutover is verified.