Metaswitch to NetSapiens Migration
Move customers, numbers and call flows without rebuilding each account by hand.
Vox Matic helps service providers migrate customers, services, and configurations from Metaswitch to NetSapiens using Otto™, its proprietary automated migration framework. Otto automates repeatable migration tasks at scale, while senior telecom engineers oversee planning, exception handling, validation, testing, and cutover.
Automation first. Expert engineering where required.
Why Service Providers Are Planning Their Move From Metaswitch
Metaswitch still runs, and its owner says it will keep supporting it. The decision most providers face is not about a shutdown date. It is about where they want their customers in five years.
NetSapiens is built for service providers and now supports more than 8 million users worldwide. The hard part is moving thousands of existing customers. That is the part Vox Matic automates.
A changing platform landscape
Metaswitch has changed ownership twice since 2020, from Microsoft to Alianza in March 2025, and providers are deciding where their customer base should live long term.
One platform for growth
Consolidating on NetSapiens gives providers a single environment for new services, integrations and onboarding.
Simpler operations
Running customers on one platform removes duplicate licensing, hardware, support contracts and specialist skills.
What Moves From Metaswitch to NetSapiens
Each customer's configuration is extracted from Metaswitch and converted to the matching NetSapiens structure. Exact mapping is confirmed during discovery, because every Metaswitch environment has its own customizations.
IN METASWITCH
TYPICALLY BECOMES IN NETSAPIENS
Business groups and locations
→
Customer domains and sites
Subscribers and lines
→
Users and extensions
Phone numbers and DID ranges
→
Numbers routed to users, queues or auto attendants
Multi-line hunt groups and call pickup groups
→
Call queues and hunt groups
Auto attendants and schedules
→
Auto attendants and time frames
Voicemail settings, announcements and greetings
→
Voicemail boxes, greetings and audio files
Call forwarding, do not disturb and user features
→
Answering rules and user settings
Devices, device users and device customizations
→
Devices and device profiles
Settings that need a different treatment in NetSapiens are flagged for engineering review and rebuilt to match the provider's design.
How a Metaswitch to NetSapiens Migration Works
Vox Matic follows a six-step process for moving customers from Metaswitch to NetSapiens. Automation handles the repeatable work in each step. Engineers review, test and own the cutover.
01
Explore
Confirm the source environment, customer list and NetSapiens target. Review each customer at a high level and plan migration waves.
02
Gather
Extract each customer's data from Metaswitch: locations, numbers, users, devices, hunt groups, auto attendants, greetings and voicemail settings.
03
Review
Each data point is converted to the NetSapiens format and presented for review. Exceptions and features that need a different design are flagged for engineers.
04
Migrate
Approved configurations are built in NetSapiens through its APIs, in phased waves or in bulk.
05
Activate
Phones are redirected, number routing is updated in SBCs or with the carrier, and services are checked in real time.
06
Complete
Billing systems are updated, Metaswitch is decommissioned for those customers, and teams receive training and handoff.
The Biggest Risks in a Metaswitch Migration, and How Vox Matic Manages Them
Most migration problems come from small details missed at scale: one phone not redirected, one number still routed to the old switch, one greeting left behind.
RISK
HOW VOX MATIC MANAGES IT
Missed or incomplete configuration
Each customer's configuration is extracted and reviewed before anything is built.
Features that work differently on NetSapiens
Flagged during review and redesigned by engineers before cutover.
Lost voicemail, greetings or announcements
Audio files and voicemail settings are extracted and rebuilt as part of each customer's migration.
Phones that don't register after cutover
Device redirection is a planned cutover step, with registration checked in real time.
Calls still routing to Metaswitch
SBC and carrier routing updates are part of the cutover checklist.
Years of undocumented customizations
Discovery and review surface one-off settings, which are normalized or rebuilt on purpose.
Running two platforms for too long
Automation shortens the migration, so Metaswitch costs end sooner.
The result is a migration designed to protect the customer experience, with no noticeable downtime for end users as the goal.
Already Running NetSapiens and Metaswitch?
Consolidate on one platform
Many providers sell NetSapiens to new customers while older customers stay on Metaswitch, or they inherited a Metaswitch switch through an acquisition. Running both means maintaining two platforms, two sets of integrations and billing workflows, and two sets of operational knowledge.
Vox Matic moves the remaining Metaswitch customers into your NetSapiens environment so the legacy platform can be retired sooner.
See how Vox Matic supports NetSapiens consolidation on our NetSapiens page.
NetSapiens Ecosystem Partner
Real-World Migration Results
18 → 6
MONTHS: MANUAL ESTIMATE VS. ACTUAL
< 5
MONTHS TO REPORTED ROI
Fuse.Cloud estimated its BroadWorks-to-NetSapiens migration would take about 18 months manually. With Vox Matic, it was completed in about six months, with ROI reported in under five months.
BroadWorks migration. Results vary by environment.
See How Vox Matic Simplifies the Path to NetSapiens
Metaswitch to NetSapiens: Frequently Asked Questions
Plan Your Metaswitch to NetSapiens Migration
Tell us about your Metaswitch environment. A migration specialist will review your customer count, configurations and timeline, and outline a plan for moving to NetSapiens.
Accelerate adoption. Protect the customer experience. Retire Metaswitch sooner.
It's that simple!