Springtime last year, we broke a tail light.
It happened while parking under a slightly-too-low tree branch — a small crack in the rear casing, nothing dramatic. So we took the car to a local shop to have the light replaced. While we were there, the mechanic offered a “quick tune-up” — just to make sure everything else was running smoothly. “It’ll only take 45 minutes and won’t add much to the cost.”
Famous last words.
A few hours later, we got that call. “So… we found oil in your coolant.”
Now, I’m not a car expert, but I’m fairly sure engine oil doesn’t belong in the coolant system. Turns out the head gasket was failing, which meant they’d need to take the engine apart — and the repairs would cost more than the 12-year-old car was worth.
What started as a simple fix ultimately led to the expense of a whole new car.
And if you’ve ever tried to migrate voice services from one platform to another, this might sound familiar.
The Myth of the Seamless Migration
Voice vendors love to promise “seamless migrations.” It’ll be fast. It’ll be easy. Your customers won’t even notice.
And while we’d love that to be true… in reality, voice migrations often look a lot more like my trip to the mechanic. What seems like a simple process often reveals underlying complexity — configuration quirks, legacy setups, or customer-specific features that simply don’t map cleanly from one platform to another.
Under the hood, things are never as simple as they seem.
What Really Happens in a Voice Migration
When you migrate voice services — whether from Metaswitch to a UCaaS platform, or from one Class 5 switch to another — there are dozens of details that need to be captured and replicated correctly.
A few of the big ones:
- Phone configuration: Button mapping, speed dials, BLF settings — each phone model and firmware may behave slightly differently.
- Call flows and groups: You’ll need to replicate the structure of auto-attendants, IVR menus, hunt groups, and ring patterns.
- Greetings and prompts: Someone has to re-record business greetings, voicemail prompts, menu instructions, and other audio assets — and this often falls on the business owner or their staff.
- Feature behavior: The old system may have worked in a very particular way that the new system doesn’t replicate by default — requiring retraining or configuration tweaks.
These are not small tasks. And even with scripting and automation, there’s still a significant manual effort — often involving coordination with each business customer.
The Risk of Rushing
The biggest risk in all of this isn’t just the effort involved — it’s the customer experience.
For most small businesses, the phone system is something they don’t think about. It just works. And when it suddenly requires their attention — because they need to re-record messages, reconfigure phones, or relearn call flow behavior — it can lead to frustration.
In the worst cases, it leads to churn. “If I’m going to go through all this effort anyway,” a customer might think, “why not just switch providers entirely?”
And that’s the risk of aggressive, mass-scale migrations: they put all your customers into a state of disruption at once, and that’s when you lose people.
A Better Way: Slow, Parallel Migration
At Award Consulting, our strong recommendation is to take a slow, measured approach to voice migrations — and to run your old and new systems in parallel for an extended period of time.
Here’s how that works:
- New customers go on the new platform right away. This gives your team a chance to gain experience and build confidence.
- Existing customers stay on the current system until:
- They’re up for renewal
- They request new features not supported by the old platform
- Or they’re otherwise a good fit for a transition
- You migrate gradually, one business at a time, ensuring personal attention and smooth transitions.
Yes, there’s a cost to running two systems — but for most Metaswitch users, you already own perpetual licenses, and your team already knows the platform. That makes the incremental cost of maintaining the old system relatively small.
Compare that to the cost of customer churn, support tickets, and lost goodwill from a rushed migration — and the parallel approach starts to look like a bargain.
Final Thoughts
We all love the idea of a smooth, painless upgrade — whether it’s a tail light or a telecom platform. But in both cases, it’s what’s lurking beneath the surface that causes the real trouble.
A voice migration can be successful — even painless — if you take your time, plan carefully, and put the customer experience at the center of your strategy.
If you’re planning a migration — or just trying to figure out your long-term roadmap — we’d be happy to talk. Whether you need help evaluating platforms, planning a rollout, or building scripts and processes to support the work, we’re here to help make sure your transition doesn’t come with surprise engine work.
