A business phone migration checklist from inventory to follow-up
A phone migration affects more than a subscription. Business numbers may appear in customer records, public listings and other systems, while employees rely on a particular call-handling routine.
Use this checklist to prepare the transition. Exact eligibility and transfer steps must come from the current and receiving providers for the actual number.
Before selecting a migration date
Confirm who owns the current service and who can authorize changes. Inventory numbers, users, devices, destinations and required message channels.
List dependencies on the existing number, including accounts or processes that receive calls or messages there. Keep sensitive account details in the appropriate secure system.
Ask the receiving provider to confirm eligibility. Do not assume that number availability, remote use and portability are the same question.
Define the destination process
| Item | Evidence to prepare |
|---|---|
| Staffed hours | Written coverage schedule |
| Routing | Intended team path and unanswered fallback |
| Shared ownership | Duty role and backup |
| Follow-up | Location for pending callbacks and promises |
| Devices and network | Representative pilot results |
| Historical information | Decision about what must remain accessible |
A migration should not preserve an unclear ownership process simply because the old number continues to work.
Test before the transfer
Use an appropriate temporary setup where possible. Test incoming and outgoing calls, voicemail, relevant messages, transfers and after-hours behavior.
Include an unavailable agent and a caller with an unresolved issue. Ask another colleague to continue the work from the available record.
If integrations matter, verify the destination fields and matching behavior. Do not assume old conversation history or CRM links will transfer automatically.
Coordinate the change
Follow the providers' agreed sequence and keep the current service active until its role in that sequence is complete. Choose a staffed period with someone responsible for checking results.
Document a fallback route for customer contact and who will communicate a problem. Avoid promising zero interruption without evidence for the actual transition.
For a new number, plan how existing customers and public references will be updated. For a transferred number, verify the same customer paths after the move rather than assuming continuity.
Verify and close
After the change, test each essential path from an external caller's perspective. Confirm outbound identity where relevant, incoming routing, messages and the next staffed review of pending work.
Record unresolved issues and keep them owned. Retire obsolete access or subscriptions only after the agreed transition requirements are satisfied.
Use the shared business-number workflow and business phone category for preparation. Provider-specific requirements should be checked in the selected product's official documentation and proposal. The checklist is complete when reachability, team coverage and outstanding commitments have all been verified.