Plan the move before you move the phones.

Checklist

• List users, extensions, shared phones, cordless phones, reception phones, and remote workers.
• Confirm internet stability, upload capacity, router/firewall access, Wi-Fi coverage, and backup connectivity.
• Document existing numbers, hunt groups, call queues, voicemail boxes, and after-hours behaviour.
• Decide who signs off call flows, test calls, user training, and go-live timing.

Checklist

• Choose Cloud PBX when you need modern routing, remote users, easier changes, and lower on-site PBX dependency.
• Choose SIP trunking when your current PBX still works and you mainly need modern voice lines and call rates.
• Choose a staged migration when the PBX is still usable but users, branches, or support needs are changing.
• Compare total cost, support ownership, future changes, and number-porting risk before deciding.

Checklist

• Confirm the current account holder, service provider, number list, and latest invoice details.
• Do not cancel existing services before the port is complete and tested.
• Agree the preferred cutover window and who will test inbound and outbound calls.
• Prepare a fallback route for critical numbers if the porting window moves.

Checklist

• Record whether the issue affects one user, one site, all calls, inbound calls, or outbound calls.
• Check latency, jitter, packet loss, upload saturation, and whether traffic is sharing a busy link.
• Test from a wired handset or softphone on a stable connection before blaming the PBX.
• Keep timestamps, caller numbers, destination numbers, and examples for faster support investigation.

Checklist

• Power the router, ONT, switches, Wi-Fi access points, and desk phones with suitable backup power.
• Add LTE or 5G failover where inbound calls are business-critical.
• Use softphones or mobile app access for staff who can work away from the office.
• Define emergency routing to mobiles or another branch when a site goes offline.

Checklist

• Audit current extensions, numbers, devices, call flows, opening hours, recordings, and reporting needs.
• Design the new call flow before configuring phones so the system follows the business workflow.
• Run test calls for main numbers, departments, after-hours messages, voicemail, and failover routes.
• Schedule go-live around business risk, train users, and keep support close during the first week.

Checklist

• Send the latest voice bill, current PBX/support costs, and any known contract dates.
• We look for avoidable rentals, high call destinations, number sprawl, and unclear service lines.
• You get practical next steps, not a forced migration recommendation.
• Installation, hardware, connectivity, and support scope are quoted once the real environment is understood.