Decision guide

PBX to cloud migration checklist

Plan the dependencies, tests and approvals that take a PBX migration through cutover.

Migration gates and recovery pathsInventory dependencies, run old and new platforms in parallel, approve cutover and verify calls. Recovery uses agreed diversions and carrier action; port reversal is not necessarily immediate.MIGRATION / ACCEPTANCE GATESINVENTORYOLD PBXCLOUDPARALLEL RUN / TEST BOTHCUTOVERRecovery plan: agree before portingMigration gates and recovery pathsInventory dependencies, run old and new platforms in parallel, approve cutover and verify calls. Recovery uses agreed diversions and carrier action; port reversal is not necessarily immediate.MIGRATION / ACCEPTANCE GATESINVENTORYOLD PBXCLOUDPARALLEL RUN / TEST BOTHCUTOVERRecovery plan: agree before porting

In short

Number porting, parallel running and planned cutovers with rollback plans. Turn those steps into a migration acceptance checklist: inventory dependencies, agree porting details, test the new service, rehearse recovery and get the business owner’s cutover approval.

Key facts

Purpose
Decision framework
Next step
Free solution design. No obligation.

Last updated

01 / Decision framework

Prepare and prove the new service

What must be checked before a port is ordered?

Inventory every number, range, bill, site and account detail. Identify fax, lift phones, alarms, EFTPOS and other devices that may rely on the old service; arrange suitable alternatives with their suppliers. Confirm emergency calling addresses and requirements. Do not cancel the existing service before port completion is confirmed.

  • Confirm all numbers, ranges and carrier account details.
  • Identify alarms, fax, payment and other dependent devices.
  • Confirm emergency calling details and keep existing services active.

What should parallel running prove?

Build and test with temporary numbers where appropriate. Check inbound and outbound calls, caller ID, hunt groups, queues, voicemail, opening hours, CRM and recording permissions. Test internet capacity, Wi-Fi or cabling, handsets and power arrangements. Train reception and nominate someone to sign off each workflow.

  • Test reception routing, queues, voicemail and opening hours.
  • Test caller ID, CRM, recording permissions and devices.
  • Train users and record workflow sign-off.

02 / Decision framework

Approve cutover and closure

How do you plan a cutover and recovery?

Agree a carrier port window, decision owner, contact tree and recovery triggers. Record what can be reversed locally and what needs carrier action. A completed number port cannot necessarily be reversed immediately; agree temporary diversions or alternate contact numbers in advance. Keep recovery instructions available outside the phone system.

  • Name the cutover decision owner and escalation contacts.
  • Record recovery triggers, diversions and alternate numbers.
  • Approve the port window and recovery plan before proceeding.

What happens after the new service is live?

Test calls from more than one external network, verify published numbers and check charges against the order. Monitor busy-period usage, resolve defects and only retire the old equipment and services after dependencies and billing are confirmed. Use the existing migration article for the broader journey; this checklist is the acceptance gate, not a promised timetable.

  • Verify calls from multiple external networks.
  • Review busy-period usage and invoices.
  • Approve decommissioning only after all dependencies are cleared.

How do the options compare?

Swipe to see all options →

StageEvidence to keepGo/no-go owner
InventoryNumber list and device dependenciesBusiness service owner
Parallel testCall-flow and device test resultsReception and IT
CutoverPort confirmation and recovery contactsNamed cutover lead
ClosureSuccessful calls, billing and decommission approvalBusiness service owner

Frequently Asked Questions

Should we cancel the old carrier first?

No. Confirm port completion and dependent services before requesting cancellation.

Is rollback instant?

Not necessarily. Number-port reversal depends on carrier processes. Agree practical recovery options before the cutover.

Free solution design. No obligation.

Tell us your requirements so we can scope a design around your business.