Carrier migration playbook
Switch carriers as a controlled operation.
A business wireless migration is more than a rate decision. Inventory, authority, ports, devices, exceptions, and verification determine whether the move is actually complete.
Neura field guide · Updated July 2026No provider can responsibly guarantee zero downtime in every carrier migration. A credible plan minimizes risk, preserves stop conditions, maintains ownership, and verifies each critical state before closure.
Establish a complete source inventory
Confirm every line, number, user, device, installment, contract commitment, account identifier, authorized contact, and dependency before selecting a cutover sequence.
Define authority and stop conditions
Decide who can approve commercial terms, number ports, device changes, exceptions, and final carrier release. Establish the conditions that stop or reverse the migration.
Plan number ports and device readiness
Validate porting data, sequence critical users, stage devices and enrollment, communicate user actions, and keep exception owners available during cutover.
Track execution as state—not email
Each request needs a target state, carrier identifier, timestamp, owner, retry history, and exception path. “Submitted” is not the same as live.
Verify before closing the move
Confirm service, calling, messaging, data, identity, device enrollment, and inventory state. Then verify final charges, credits, and expected financial changes on the relevant invoices.