Replace a legacy PBX in stages: a migration roadmap for busy teams

Discover what the old system actually does

Inventory numbers, extensions, recordings, queues, schedules and devices. Ask reception about routines that may not appear in configuration exports, such as a temporary diversion during meetings. Check fax, alarms, door entry and other specialist connections separately. Assign each dependency an owner who can confirm that the replacement works.

Design the target call journeys

Do not reproduce every historic menu simply because it exists. Keep familiar extension patterns where helpful, but review obsolete destinations and duplicated queues. Write down after-hours and overflow behaviour. Compare this design with Telfron’s current modules and the selected plan before ordering equipment or scheduling porting.

Pilot a representative group

Include reception, a heavy phone user and a remote user if remote calling matters. Test inbound and outbound calls, transfers, voicemail and audio under normal load. Use a temporary number when practical. Provide short training focused on the tasks each role needs, including how to recover from an unsuccessful transfer.

Make cutover responsibilities explicit

Agree the carrier window, who changes routing and who validates the main numbers. Publish a contact route for staff during the change. Define the checks that must pass before declaring completion and the point at which the team escalates or uses an alternate routing plan. Number porting may constrain rollback, so verify carrier options in advance.

Keep a stabilization window

Review reports and user feedback after cutover. Look for missed destinations, unusual outbound failures and devices that were overlooked. Keep old configuration records and approved recovery arrangements until the acceptance checklist is complete. Retire the old system only after owners sign off the relevant services.

Worked example: pilot before number porting

An illustrative office keeps its existing reception number active while a small group tests the new PBX on a temporary number. The pilot includes reception, sales and one remote worker. The team compares the agreed call-flow worksheet with real inbound, outbound and transferred calls. Only after the critical journeys pass does the project owner request a number-porting window.

This sequence separates a PBX configuration problem from a carrier-porting problem. It also lets staff practise on the new endpoints without asking every customer to tolerate an unfinished deployment. The old system remains available only under the agreed plan; the team does not assume that a completed number port can be instantly reversed.

Prepare a cutover worksheet

Write the steps in execution order and put a named owner beside each one. Include the start condition, expected result and escalation contact. A reception sign-off is different from an installer confirming registration: both may be needed. Define the checks for every public number and critical endpoint, including the specialist devices found during discovery.

Set a decision point at which the team either proceeds, pauses or activates an approved alternate route. Make that decision based on critical service checks, not on whether most of the configuration appears finished. Keep a record of any accepted limitation and the person responsible for resolving it after cutover.

Remove old dependencies deliberately

After stabilization, review old carrier subscriptions, unused extensions, administrator accounts and equipment monitoring. Cancelling a line without checking its purpose can break a specialist service that receives few calls. Confirm ownership before retiring it. Archive the old configuration and the final number inventory in an approved location.

Provide staff with a short guide for routine tasks and a support route for anything else. Review call failures and missed destinations during the first operating period, then hand the system to normal administration. A migration is complete when people can perform their work and the remaining exceptions have accountable owners.

Example cutover run sheet