Guide · 10 min read · September 19, 2026
Phone-system migration after a merger or acquisition
Inventory numbers, preserve customer reachability and phase call-flow changes when combining phone systems after a merger or acquisition.
After a merger or acquisition, migrate the phone estate in stages: inventory every number and dependency, decide which brand and routing each number should retain, secure carrier records and porting authority, build the combined design, and test it before moving traffic. Keep legacy numbers reachable during the transition, avoid changing carriers and call flows simultaneously where possible, and maintain a rollback route for critical lines.
Build an evidence-based number and dependency inventory
Do not treat the current invoice as a complete inventory. Collect bills, carrier records, receptionist lists, marketing pages and device configurations, then place test calls to uncertain numbers. Record the service address, carrier, billing account, published use, destination, language, owner and business criticality. Include toll-free numbers, fax, alarms, intercoms, paging and numbers embedded in advertising or customer portals.
Flag shared dependencies before cancelling anything. A main number may forward through an older service, or a door phone may share connectivity with an office line. Obtain current customer-service records and letters of authorization from the authorized business entity early. Porting data must match the carrier record, and organizational changes can make that paperwork harder if it is postponed.
- Keep, redirect, port or retire decision for every number
- Published brand and language presented to callers
- Current and future destination with named owner
- Criticality, acceptable outage and rollback path
Choose the future call model before the cutover
A merger does not require every caller to hear the new corporate structure on day one. Decide which acquired brands, local numbers and greetings should remain during the transition. A shared platform can still run separate menus, queues, hours and reports while teams, customer communications and legal names are consolidated on their own schedule.
Map duplicate departments and identify the actual owner of each queue. If two support groups become one, decide how priorities, languages, escalation and reporting will work before combining traffic. Do not copy both old menus into a larger tree. Use call data and staff interviews to remove obsolete branches, but preserve a route for known customer habits until communications have caught up.
Phase ports, validation and decommissioning
Pilot with internal users or a lower-risk number before moving the main lines. Validate inbound and outbound calling, caller ID, transfers, voicemail, emergency-address records, after-hours schedules and integrations. On a port date, monitor both the new system and the previous destination, and keep a documented escalation contact for the gaining and losing providers.
A successful first call is not the end of the migration. Watch for calls still reaching legacy forwarding, update directories and advertising in a controlled sequence, and keep the old account active until every number and dependency is reconciled. Obtain confirmation before cancelling services. Archive the final inventory and configuration so later teams know what moved, what was retired and who approved it.
Should all acquired numbers be ported at once?
Not automatically. A phased move reduces the impact of an inventory error and lets the team validate the new design. Numbers that share one carrier account or hunt group may impose practical constraints, so confirm the available sequence with the providers. Keep the business impact, dependencies and rollback options visible when selecting each batch.
Want to see your own call flow?
Three minutes of questions, a recommended setup.
Build My Phone System