Published by OttoCall Editorial Team · Published · Published automatically after quality, citation and claims checks
5 min read
A useful VoIP migration checklist connects the technical setup to the calls your business needs to handle. Start by documenting how calls should work, then agree on a transfer plan, test the new setup, and decide who can pause the move if an issue appears. Treat each item below as a decision to record, not just a box to tick.
Map the current calling setup
Before changing anything, make a working inventory of the lines and call paths you intend to move. For each business number, record its purpose, the team responsible for it, where incoming calls should go, and what should happen when they are unanswered. Keep the inventory in an appropriate internal location rather than putting actual numbers or personal details in a shared project template.
Include shared lines, individual extensions, call menus, voicemail, transfers, and any scheduled routing you use. Ask each affected team to review its entries. The aim is to distinguish a deliberate calling arrangement from a setting that no one intends to keep.
Finish this stage with a simple acceptance record: what must work on the new setup, who will check it, and what evidence will count as a successful test. Note any items still awaiting a decision.
Understand the technical handoff
The Session Initiation Protocol, or SIP, is an application-layer signaling protocol for creating, modifying, and terminating sessions, including internet telephone calls.[1] SIP invitations can carry session descriptions that help participants agree on compatible media types.[1] This distinction is useful when discussing a test: establishing a session and hearing the expected audio are separate things to check.
Ask the people configuring the new service to document the intended devices, calling applications, network connections, and relevant settings. Identify who owns each part of the setup and how the team will report an issue. Avoid treating an unanswered call, a failed connection, and a call with poor audio as the same problem; record the observed behavior separately.
Plan the number transfer
For each number you want to retain, ask the current and proposed providers what information and approvals they need for a transfer. Confirm the intended transfer date and how each party will communicate a change to that plan. Keep any account information in the appropriate internal system, not in the shared test notes.
Add a checkpoint before making changes to the existing service. The project owner should know which numbers are included, which are staying as they are, and who has confirmed readiness. If a transfer cannot proceed as planned, agree on the next action with the providers rather than assuming a particular outcome or timetable.
Prepare routing and devices
Use the inventory to build the intended call paths in the new setup. For each path, specify the entry point, the destination, the sequence of actions, and the expected outcome if nobody answers. Include any relevant business-hours and out-of-hours arrangements.
Prepare a test list for each device or calling application involved in the move. Check incoming and outgoing calls, answer and hang-up behavior, transfers, voicemail, and menu choices where those functions are part of the intended setup. Record the expected result next to the actual result so that a reviewer can identify the precise difference.
Assign an owner to each routing decision. If a test produces an unexpected destination, that owner can confirm whether the configuration or the original inventory needs to change.
Check audio separately from call setup
ITU-T identifies G.711 as a recommendation for pulse code modulation of voice frequencies.[2] Its published components also include an appendix describing a packet-loss concealment algorithm for G.711.[2] Ask the technical team which audio formats are intended for the migration and what information it needs when an audio test fails.
For each test call, check whether the call connects and whether participants can hear one another as expected. Repeat the check across the devices and calling paths in scope. If audio is missing or unclear, record the affected path, the observed behavior, and whether the issue can be repeated. Use that record for troubleshooting rather than changing several settings at once.
Do not turn one successful call into an acceptance decision for the whole migration. Compare results against the full test list, including any different destinations or devices the business plans to use.
Review emergency calling
Put emergency calling on the project checklist before the move. Ask the relevant provider how emergency calls are handled for the proposed setup, what information must be supplied, and how changes to that information should be managed. Identify an internal owner for keeping the documented process current.
Review applicable requirements with qualified advisers and the relevant provider. Agree on an appropriate verification approach before anyone places a test call, and communicate the resulting process to affected teams. Keep this review separate from ordinary routing tests: a successful call to a colleague is not a substitute for an emergency calling review.
Set the move plan and pause criteria
Choose a change window and write down the sequence of actions. Include who starts the change, who checks call paths, who communicates status, and who can pause the work. Make the plan accessible to the people performing those tasks without including personal details or credentials in the general project record.
Define pause criteria in advance. Examples include a missing approval, an unresolved emergency calling question, or a failed acceptance test for a required line. For each criterion, record who decides the next action and whom they need to consult. Ask the providers what options are available if the move must be delayed or adjusted; document the answer rather than presuming that a reversal is available.
Test, record, and hand over
Run the agreed acceptance tests after the change. Have the assigned reviewers compare actual results with the expected outcomes, record any open issues, and identify the person responsible for each follow-up. Repeat a failed test after a change and note the new result alongside the original observation.
When the required checks are complete, hand over the current routing map, device list, provider contacts held in the appropriate internal system, and unresolved decisions to the team that will manage the service. Schedule a review of open items and close them only when the agreed test result has been observed.
Sources
Contact OttoCall to discuss your VoIP migration.
Sources
- [1]IETF / RFC Editor. RFC 3261: SIP, Session Initiation Protocol. Accessed 2026-11-19.
- [2]ITU-T. G.711: Pulse code modulation (PCM) of voice frequencies. Accessed 2026-11-19.
This article is general information, not legal, compliance or financial advice. Check current rules and provider terms for your situation.
