What Is Otto? How Vox Matic Automates Telecom Migration
Updated: Sep 13
Telecom migration is one of the most complex operational projects a service provider can undertake. Moving customers from Metaswitch or BroadWorks to NetSapiens means pulling data, mapping settings, building out users, and checking everything before go-live. All while keeping the customers who depend on those services completely unaware.
For most of the industry's history, that work was done by hand. Engineers went through each account one at a time. Slow, costly, and hard to scale.
Vox Matic was built around a different idea: the most repetitive parts of a migration can be automated. Otto is the framework that makes it happen.
Otto, Defined
Otto is Vox Matic's proprietary automated telecom migration framework and the technology that powers our automation-first approach to moving service providers from legacy voice platforms to NetSapiens.
The simplest way to think about it:
Traditional migration: Engineers manually rebuild customer settings one account at a time.
With Otto: Significant portions of that repetitive work are automated, making the process faster, more consistent, and easier to scale.
Otto does not replace telecom engineers. It changes what they spend their time on. Instead of repeating the same steps across hundreds of accounts, engineers focus on edge cases, testing, and the decisions that need human judgment.
Key Takeaways
Otto is Vox Matic's proprietary automated migration framework, purpose-built for telecom platform migrations.
Otto automates significant portions of the migration workflow, including discovery, configuration normalization, data transformation, provisioning, and validation.
The Vox Matic model is automation first, expert engineering where required. Otto handles the repeatable work; experienced engineers handle complex exceptions, testing, and architecture.
Otto supports migrations from legacy platforms including Metaswitch and BroadWorks into NetSapiens.
Automation through Otto makes migrations faster, more consistent, and more scalable, enabling providers to run migration programs at greater scale without adding more engineers.
Faster migrations mean earlier legacy platform retirement, lower operating costs, and a faster path to ROI on the new platform.
The goal throughout is minimal customer disruption. Customers should experience no noticeable change in how their services work after cutover.
The Problem with Traditional Telecom Migration
Platforms like Metaswitch and BroadWorks have powered service providers for decades, and they work. But they are aging, and the industry has moved on. Modern platforms like NetSapiens now supports over 8 million users globally, up more than 370% since 2021. They offer more flexibility, better economics, and a cleaner path forward. The hard part is getting from one to the other.
Manual Migration vs. Automated Migration
Traditional Manual Migration | Otto-Automated Migration | |
Engineering effort | High: every account rebuilt by hand | Reduced: repetitive steps automated |
Consistency | Variable: depends on individual engineers | Standardized: same logic applied every time |
Scale | Difficult: headcount grows with volume | Practical: automation enables higher migration volume without proportional staffing increases |
Error risk | Higher: fatigue and oversight compound at scale | Lower: automated validation catches issues early |
Migration speed | Slow: weeks or months per cohort | Faster: automation compresses timelines |
Legacy retirement | Delayed: long migrations mean longer parallel costs | Earlier: faster migrations retire legacy sooner |
Customer disruption | Minimized: controlled cutover with automated testing |
What Manual Migration Actually Looks Like
Traditional migration is a heavy engineering project. For every customer, engineers must pull subscriber records (users), phone numbers, device configurations, and feature settings, then reformat and map that data to the new platform, provision subscribers, hunt groups, auto attendants, and call routing rules, and test each setup before cutover.
Multiply that across hundreds or thousands of customers, each one different, and the scope adds up quickly. High-volume migrations can take months, sometimes years, and the risk of errors grows with every manual step. Many providers end up stuck on legacy platforms longer than planned, still paying to run systems they have already decided to leave.
Why Variability Makes It Harder
No two customer setups are the same. A customer on an old platform for ten years may have hundreds of custom settings: call rules, phone layouts, recorded greetings, years of routing logic. Manual work struggles with that kind of variety. The more complex the setup, the higher the risk of mistakes. That is the problem Otto was built to solve.
How Otto Changes the Migration Process
Otto takes a different approach. Instead of having engineers rebuild every account by hand, Otto automates significant portions of the migration work. The process gets faster, more consistent, and easier to repeat at scale.
A Vox Matic migration can cover a wide range of steps: discovery, data extraction, environment analysis, configuration mapping, data transformation, provisioning, validation, testing, cutover, verification, and post-migration support. Otto automates the parts of that workflow that consume the most engineering time.
Automation First. Engineering Where It Matters.
This is the core of Vox Matic's model. Otto handles the work that repeats; engineers handle the rest. That means edge cases, design calls, test oversight, and anything else that needs human judgment. The result is a faster, more reliable process without cutting corners on the work that matters.
The model is not automation instead of engineering. It is automation that makes engineering more effective.
Migration on the Provider's Terms
Otto also supports a more controlled migration model.
Rather than forcing a one-size-fits-all approach, Vox Matic aligns the migration to the provider's setup and timeline. Providers can migrate in phases or execute a full-scale cutover based on their operational requirements. The migration process is aligned to the provider’s timeline, not the other way around.
Consistency at Scale
One of the most important benefits of automation is consistency.
Manual work varies by person. Engineers have good days and bad days, and fatigue creates real risk when the same steps repeat hundreds of times. Otto applies the same logic to every account, every time. That consistency reduces errors and means quality does not degrade as volume increases.
What Gets Automated
Within the Vox Matic migration process, Otto's automation capabilities are applied across several of the most labor-intensive activities, including:
Automated discovery: Capturing users, features, call flows, routing logic, and settings from the source platform, whether Metaswitch, BroadWorks, or another legacy system.
Data mapping and transformation: Converting source platform data into the right format for the NetSapiens environment.
Intelligent customization: Tailoring the target platform to each provider's business rules, device types, and user profiles, automatically and consistently rather than by hand.
Building out the new environment: Setting up users, phone numbers, device settings, call routing rules, voicemail, auto attendants, hunt groups, and other services.
Automated testing: Running structured pre-launch checks to confirm everything is working. Anything out of spec is identified and addressed before go-live.
The goal throughout is that when a customer's team comes in the next morning, their phones and services work exactly as they did before. The platform underneath has changed. The experience has not.
What This Means for Migration Economics
The operational benefits of automation are real. But the bigger story is what they mean for the business case.
Manual migrations are costly. They require a lot of engineering hours, long timelines, and careful coordination at every step. For providers with thousands of customers, moving them by hand can make the whole project feel out of reach. That is part of why so many providers have waited longer than they should.
Otto changes that.
Less Manual Work Means Lower Costs Per Migration
When automation handles the repetitive steps, the engineering effort per migration shifts.
Engineers stop doing the same tasks over and over. Instead, they watch the process, handle edge cases, and step in where it matters.
That means lower costs per move. More migrations can run at once without adding staff.
Faster Migrations Mean Earlier Legacy Retirement
Speed matters for a simple reason. The longer a migration takes, the longer a provider pays to run a legacy platform alongside its replacement. Every extra week is an unnecessary cost. Faster migrations mean providers can retire legacy platforms sooner, start billing on the new NetSapiens environment earlier, and compress the time spent running two systems at once.
Less manual work. Faster migrations. Earlier legacy retirement. Lower operating costs.
Scalability Without Linear Cost Growth
Manual migration scales with headcount. Twice the customers means roughly twice the engineers. Automation breaks that link.
With Otto, Vox Matic can run migrations at a scale that would not be practical by hand. Providers with extensive user bases, or those merging many platforms into one NetSapiens setup, can move far more quickly.
The business impact is reflected in customer results. Fuse. Cloud reported reducing its migration timeline from 18 months to 6 months while maintaining a largely seamless customer experience. Their COO noted they hit full ROI in under 5 months.
Speed and continuity together. That is what the automated approach delivers.
For a deeper look at the financial case, the Vox Matic blog covers why the cost of delaying migration keeps rising and the migration economics argument for moving sooner rather than later.
Frequently Asked Questions
What is Otto?
Otto is Vox Matic's proprietary automated telecom migration framework. It is the core technology behind the company's automation-first approach to moving service providers from old platforms into NetSapiens. Otto automates significant portions of the migration process that have traditionally required repetitive manual engineering effort, making the whole process faster, more consistent, and easier to scale.
What legacy platforms does Otto support migration from?
Vox Matic's strongest expertise is in migration from Metaswitch and BroadWorks to NetSapiens. Other legacy voice platforms are also supported. Otto is set up for each provider's specific source environment, so it is not tied to a single platform.
Does Otto replace telecom engineers?
No. Otto cuts the volume of repetitive manual work, but it does not replace engineering expertise. Vox Matic's model is automation first, expert engineering where required. Engineers are still essential for edge cases, design calls, test oversight, and post-migration support. Otto changes what they spend their time on, not whether they are needed.
What parts of the migration process does Otto automate?
Otto automates the most repetitive and data-heavy steps. This includes:
Automated discovery of the source platform
Data mapping and transformation
Customization of the target NetSapiens environment
Building out users and services
Pre-launch testing and checks
Experienced engineers oversee the process and handle what needs human judgment.
How does Otto handle unique customer setups?
Otto captures each provider's setup, device types, and user profiles, then applies that across the whole migration. Custom call flows, device settings, routing logic, voicemail configurations, and other operational requirements are captured, transformed, and recreated within the target environment as part of the migration process.
How much disruption do customers experience during migration?
The goal is no disruption. Otto captures and rebuilds each customer's setup so that most customers notice no change after go-live.
The platform changes. The experience does not.
How does automated migration improve the business case for moving off a legacy platform?
Automation cuts the engineering hours needed per migration, lowers per-customer costs, and lets migrations run faster and at greater scale. Providers can retire old platforms sooner, start billing on the new platform earlier, and avoid long periods of running two systems at once. The result is a more profitable process and a faster path to ROI.
Does Otto support NetSapiens consolidation as well as new migrations?
Yes. Otto supports both moves from legacy platforms into NetSapiens and scenarios where a provider is merging multiple platforms or subscriber bases into a single NetSapiens environment. The same automation that makes migration at scale practical applies equally to consolidation projects.
Comments