Guide · 11 min read · June 3, 2026
VoIP migration checklist for Canadian businesses
A step-by-step VoIP migration checklist: number porting, 911 service addresses, bandwidth, network QoS, staff training and cutover day.
Inventory every number and every device first
Before anything else, build a list of every telephone number your business publishes or uses, and every device attached to a line. Numbers hide in more places than people expect: the main line, department direct-inward-dial numbers, a fax number nobody has answered in years, a toll-free number printed on old vehicle wraps, an alarm-panel line billed separately, and a modem line at a second site.
Do the same for devices. Desk phones, cordless handsets, a fax machine, an overhead paging amplifier, a gate or door intercom, an elevator emergency phone, a credit-card terminal on a dial line and an alarm panel are all candidates. Each one either moves, gets replaced by a service, connects through an analogue adapter, or is deliberately retired.
This inventory is the backbone of the whole migration. Numbers missed here are the ones that stop working three weeks after cutover when someone finally calls the fax line.
Start porting early and understand who controls the timeline
Number porting moves your existing numbers to the new provider. You will need a recent bill from your current provider, the exact account name and address as they appear on that account, and authorization from someone entitled to make the change. Mismatches between what you submit and what the losing carrier has on file are the most common cause of a rejected port.
Your existing line keeps working until the port completes, so there is no window where a number simply stops. Timelines, however, are set by the carriers involved rather than by you or your new provider, so plan around an estimate and avoid promising a specific date to customers.
Two practical rules: do not cancel your existing service before the port completes, because cancelling releases the number and can make it unrecoverable; and port your least critical number first if you want a low-stakes rehearsal of the process.
Register 911 service addresses for every location and device
On a traditional line, the emergency address is tied to the physical circuit. On VoIP it is not — emergency calling is configured with a registered service address per location and device, and that address is what emergency services receive.
Practically, this means three things. Every site gets its address registered. Devices that live at a specific desk or building are registered to that address. And people who take a device home or move between sites need a defined process for updating the address, whether that is a self-service field in the app or a request to your administrator.
Assign this to a named person before cutover. It is the one item on a migration checklist where a stale record has consequences beyond inconvenience, and it is easy to let slide because nothing appears broken day to day.
Check bandwidth and, more importantly, what shares it
Voice calls are not bandwidth-hungry compared to video or backups, but they are unforgiving about consistency. A connection that averages fine but stutters under load will produce choppy audio and dropped words even when a speed test looks healthy.
Look at upload capacity specifically, since that is what carries your voice outbound and it is usually the smaller half of a business connection. Then look at what else uses that connection: cloud backups running at 2 p.m., a video-heavy marketing team, guest Wi-Fi, or a security-camera system uploading continuously.
Test at your busiest hour rather than at 7 a.m. when the office is empty, and test at each site. If a location depends on a shared or wireless connection, plan the failover behaviour deliberately — usually calls forwarding to mobile apps or cell numbers if the site connection drops.
Configure the network: QoS, VLANs and firewall rules
Quality of service means telling your router to let voice packets go first when the connection is busy. Without it, a large upload can delay voice traffic enough to be audible. Most business routers support this; the work is in configuring it correctly rather than in buying anything new.
On larger networks, a separate voice VLAN keeps phone traffic logically apart from computers, which makes prioritization simpler and troubleshooting far easier. It also avoids situations where a single misbehaving workstation degrades every call in the building.
Firewalls need attention too. Aggressive SIP inspection features — often enabled by default under names like SIP ALG — are a frequent cause of one-way audio and calls that drop after a set interval. Identify who administers your network early, and get them into the conversation before cutover rather than during the first outage.
Train staff on the three things they will actually do
Training fails when it tries to cover everything. Most staff need three skills: answer and transfer a call, check and clear voicemail, and use the app on their phone or computer. Everything else can be learned later or looked up.
Do the training close to cutover — a week or less — so it is still fresh, and run it separately for the people whose jobs change most. Reception, whoever manages the auto attendant, and anyone in a queue need more depth than the rest of the organization.
Write down the two or three procedures that are genuinely specific to your setup: how to change the greeting for an unplanned closure, how to reach the on-call path, how to add someone to a ring group. One page beats a manual nobody opens.
Plan cutover day like an event, not a switch
Pick a low-volume day. For most businesses that means a Tuesday or Wednesday morning rather than a Friday afternoon or the first day of a month-end. Avoid your busiest season entirely, even if it delays the project by a few weeks.
Before the switch, run the new flow on a test number for at least a few days and call it yourself from outside the office: through the menu, into the queue, to voicemail, and after hours. Confirm that the greeting says what you think it says and that callers reach the people you expect.
On the day, have a short checklist: place a test call to and from each site, confirm emergency addresses are registered, verify voicemail delivery to email, check that faxes arrive, and walk the floor to test cordless and paging coverage if you have them. Then keep the first-week call reports open — the first real data usually reveals one menu option nobody uses and one queue that needs another person.
Want to see your own call flow?
Three minutes of questions, a recommended setup.
Build My Phone System