The fear is reasonable
Phones are the one system where failure is immediately public. A broken intranet is an annoyance; a phone that does not ring is a customer who called a competitor. Every business we have moved has asked some version of "what happens if it goes wrong on the day".
The answer is that a good migration is designed so the day is boring.
Parallel running is the whole trick
Your existing lines stay live while the new system is built alongside them. For a period, both work. Nothing is cancelled, nothing is released, and the new system is proven with real calls before anything depends on it.
That single decision removes most of the risk. If something is wrong, the old system is still there, still ringing, and the rollback is a routing change rather than an emergency.
What actually happens, in order
- Readiness assessment. Every site is measured — jitter, loss, upstream headroom, the router's behaviour. You
get the report whether or not you proceed.
- Design, on paper, with you. Who answers what, in what order, and what happens out of hours. Most problems
after a migration are dial-plan disagreements, not technical faults, and they are much cheaper to resolve in a conversation than in production.
- Build and configure. Handsets arrive already configured — they register themselves when plugged in.
- Pilot with a real team. One department, real calls, a week. This is where the dial plan meets reality.
- Port the numbers. Filed with your current carrier, on a date you choose. See
- Cutover. Usually minutes, in a window you pick. Old lines still live.
- Stay close. We watch call quality for the first weeks and come back to you with what we see, rather than
waiting for you to notice.
Ask for the rollback plan
Any provider can describe a happy path. The question worth asking is: if this goes wrong at 10am on cutover day, what specifically happens, who decides, and how long does it take to be back where we started?
If there is not a clear answer, the plan is optimism.
Do not cancel anything early
The most common self-inflicted problem in a migration is cancelling the old service to save a month's rental. Keep it until the port is confirmed complete. Cancelling early can release a number before it has moved, and recovering one that has gone back into a carrier's pool is slow and sometimes impossible.