Search Results
Search this site
50 results found with an empty search
- How to Choose a NetSapiens Migration Partner
Choosing a NetSapiens migration partner shapes how quickly you modernize, what the project costs, and how your customers experience the move. NetSapiens now supports more than 8 million users worldwide, and Crexendo reports the platform is growing at twice the rate of its competitors. Before you commit, ask these 12 questions. Key Takeaways Automation-led and manual migration produce different outcomes at scale. Know which one you are buying. Ask for specifics on data transformation, migration validation, sandbox testing, and cutover. NetSapiens-specific experience matters. General UCaaS experience does not cover the platform's architecture, domain structure, and provisioning model. Cutover is where customer disruption risk is most visible, so how a partner manages it deserves close attention. These questions apply whether you are migrating from Metaswitch, BroadWorks, or another legacy platform. Partner Evaluation at a Glance Evaluation Area What to Ask About What a Strong Answer Looks Like Automation and Methodology What is automated vs. manual; how data is extracted, transformed, and validated Specific answers about tooling, sandbox testing, validation steps, and repeatability across source platforms NetSapiens Experience Ecosystem Partner status; source platform history; how they track platform changes Named source platforms, a direct NetSapiens relationship, and fluency with domains, resellers, and configuration profiles Cutover and Customer Risk Cutover sequencing; rollback process; feature gap handling Clear rollback ownership, a sequenced cutover plan, and early identification of feature gaps Migration Economics Effect on engineering hours, elapsed timeline, legacy platform costs, post-migration support A clear explanation of how the methodology affects total cost and timeline Questions About Automation and Methodology This is where the specifics matter most: what is automated, what is manual, and why. 1. Is your migration process automated, manual, or a hybrid? Ask them to describe exactly what is automated and what requires human intervention. Manual-only approaches carry real limitations as subscriber volume and complexity increase. 2. How do you handle data extraction and transformation from legacy platforms? Configuration structures differ significantly between Metaswitch, BroadWorks, and NetSapiens, so data has to be transformed before it can be provisioned. Ask: How they extract data from your source platform How they map it into NetSapiens resellers, domains, users, and configuration profiles How they validate it before anything goes live 3. How do you validate migrated data before cutover? Ask for a defined migration validation process, including: Whether they test migrated configurations in a sandbox environment before anything goes live How provisioned data is checked against the source, including domain-level validation for customer-specific exceptions How discrepancies are caught, flagged, and resolved before cutover begins An experienced partner should be able to walk you through this clearly. 4. Can your approach scale to large or multi-platform environments? If you manage multiple legacy platforms, multi-tenant environments, or a large subscriber base, your partner's methodology needs to scale with you. Ask whether their process is repeatable across different source platforms and whether it has been applied in environments comparable to yours. Learn more about what automated telecom migration looks like at scale. Questions About NetSapiens Experience NetSapiens has its own architecture, provisioning model, and ecosystem. A partner with general UCaaS experience but limited NetSapiens exposure may spend part of your project getting up to speed. 5. Are you a NetSapiens Ecosystem Partner? Ask whether the partner has a formal relationship with NetSapiens, what that relationship involves, and how much direct experience they have migrating customers into the platform. 6. Which legacy platforms have you migrated from into NetSapiens? Metaswitch and BroadWorks are common source platforms, but their data structures and migration complexity differ. Direct experience with your source platform can help a partner anticipate platform-specific issues earlier. Ask for examples. 7. How do you stay current with NetSapiens platform changes? NetSapiens continues to evolve. Ask how the partner tracks platform updates and how those updates are reflected in their migration methodology. Questions About Customer Experience and Risk Your customers will not know or care about the platform change. They will notice if their service is disrupted. Cutover and rollback planning are where that risk is managed. 8. How do you manage cutover to minimize customer disruption? Cutover is a critical moment in any migration. Good telecom cutover planning should cover: How subscriber moves are sequenced, whether in stages, batches, or by customer group How rollback is handled if something goes wrong What communication is recommended for end customers Read more about what a smooth telecom cutover requires. 9. What does your rollback process look like? Ask what a rollback involves, how quickly it can be executed, and who owns the decision to initiate it. A clear answer here is a good sign. 10. How do you handle customer-facing features that do not map directly between platforms? Feature parity between legacy platforms and NetSapiens is not always one-to-one. Call recording, receptionist consoles, fax services, and contact center integrations are common examples that need careful review. Ask how your partner identifies gaps, communicates them, and resolves them before customers are affected. Questions About Economics and Outcomes Every week a legacy platform stays live has a cost. The right partner can explain specifically how their approach affects engineering hours, elapsed timeline, and the pace of legacy retirement. 11. How does your approach affect the total cost and timeline of migration? Ask them to explain how their methodology affects: Engineering hours required across the program Elapsed time from kickoff to full cutover The cost of maintaining legacy platforms during the migration window If you are carrying two platforms during migration, elapsed time can directly affect operating cost. Fuse.Cloud, for example, completed a BroadWorks to NetSapiens migration estimated at about 18 months of manual effort in roughly six months (read the case study). Understand the real cost of delayed migration before you commit to a timeline. 12. What does post-migration support look like? Migration does not end at cutover. Ask: What happens in the days and weeks after customers are moved Whether features are validated from the client side, including SNAPmobile and other end-user apps Who owns support during that period, and how issues are escalated and resolved Comparing Partners? The right partner should be able to answer all twelve questions with specifics about your environment, not general assurances. If you're comparing NetSapiens migration partners, ask Vox Matic the same 12 questions. We'll walk you through how we approach your environment, including how Otto™ automates the extraction, transformation, provisioning, and validation work that traditionally consumes the largest portion of migration effort, where our engineers step in, and what the path to cutover looks like. It's that simple! Frequently Asked Questions What is a NetSapiens migration partner? A NetSapiens migration partner is a company that specializes in helping service providers move customers, configurations, and data from a legacy telecom platform into NetSapiens. Strong partners combine platform-specific expertise with a defined methodology for discovery, data transformation, validation, cutover, and post-migration support. How is automated migration different from manual migration? In a manual migration, engineers extract, reformat, and provision data by hand, which introduces variability and limits how quickly the work can scale. An automated approach uses software to handle extraction, normalization, and provisioning, reducing manual effort, improving consistency, and shortening timelines. See how automated and manual telecom migration compare. What platforms can be migrated into NetSapiens? NetSapiens migrations commonly originate from Metaswitch and BroadWorks, though other legacy voice and UCaaS platforms are also migration sources. Complexity depends on the source platform's data structure, the size of the subscriber base, and the degree of customization in the existing environment. How long does a NetSapiens migration take? Timelines vary with the size and complexity of the environment, the source platform, and the methodology used. Automation-led approaches can significantly compress timelines compared to manual processes. A credible timeline should account for the actual environment, including subscriber volume, configuration complexity, and cutover requirements. What should I do before engaging a migration partner? It helps to have a clear picture of your current environment: the source platform, approximate subscriber count, any custom configurations or integrations, and your target go-live window. The more clarity you provide upfront, the more accurate the partner's scoping and planning will be.
- Telecom Migration Prep: How to Start Before You're Ready to Move
The short answer: Service providers often delay platform migration because moving thousands of existing subscribers feels difficult to organize. The solution is to separate preparation from execution. Discovery, inventory, data analysis, and migration planning can begin before a cutover date is established. Vox Matic’s proprietary automated migration framework, Otto™, supports this groundwork so the project is organized when the provider is ready to move. Key Takeaways Selecting a new platform and migrating existing subscribers are separate projects. Migration uncertainty is often a preparation problem, not a platform problem. Discovery and planning can begin well before migration execution. Early preparation provides greater visibility into scope, complexity, and potential exceptions. Otto™ automates repetitive migration work while senior engineers focus on planning, review, and validation. Why Service Providers remain on Legacy Platforms Many service providers know their legacy platform is no longer the best long-term option. Some have selected NetSapiens and are already placing new customers on it, while existing subscribers remain on BroadWorks, Metaswitch, or another legacy platform. The destination is clear. The challenge is determining how to move what is already there. That challenge can include thousands of subscribers, devices, configurations, dial plans, call flows, integrations, and feature settings. When viewed as a single project, the scope can feel overwhelming. This is not a technology problem. It is a preparation problem. NetSapiens continues to gain adoption. Crexendo reported in August 2026 that its platform supports more than 8 million users worldwide, representing growth of more than 370% since its acquisition of NetSapiens in 2021. (Crexendo, August 2026). Preparation helps service providers understand the work ahead, identify exceptions early, and create a realistic migration plan before execution begins. The difficulty of migration should not determine the platform decision. Yet many providers remain on Metaswitch, BroadWorks, or other legacy platforms because the path forward feels too large to start. Buying a New Platform Is Not the Same as Migrating to It There are two situations we see consistently in the market. Still Evaluating Already Using NetSapiens Platform decision Not yet made Made New customers Going to legacy Going to new platform Legacy subscribers Unmoved Unmoved Migration status Stalled at decision Stalled at execution Primary blocker Fear of the migration scope No organized migration plan What preparation does Removes migration fear from the platform decision Converts transition strategy into actual migration What Can Begin Before Migration? Powered by Otto™ Otto™ automates the repetitive work traditionally associated with telecom migrations and can significantly reduce project timelines, while making more effective use of valuable engineering resources. Senior telecom engineers remain focused on planning, oversight, review, and validation rather than manual data collection, conversion, and entry. Migration workflow: Discovery Data Extraction Transformation Provisioning Validation Audit the Existing Environment Identify subscribers, services, devices, DIDs, dial plans, feature configurations, call routing, integrations, and custom requirements. Clean and Validate the Data Find duplicate, missing, outdated, or inconsistent records before they become migration exceptions. Map Services to NetSapiens Determine how existing services and configurations will be represented on the target platform. Establish Transformation Rules Define how source data will be converted and provisioned consistently into NetSapiens. Validate the Process Where the target environment and testing setup are available, migration logic and configurations can be validated before live execution.oved. “Using Vox Matic, we reduced our migration timeline from 18 months to just 6." — Ben, COO, Fuse.Cloud Start Preparing Today A cutover date is not required to begin understanding the work ahead. Early discovery and planning help define migration scope, identify potential challenges, and create a practical roadmap before execution begins. Whether you are still evaluating platforms or already operating NetSapiens alongside a legacy environment, preparation helps turn migration from an unknown into a structured project. The providers that move most effectively are not the ones that skip steps. They are the ones that prepare early and automate the right steps. Prepare earlier. Migrate smarter. Move forward with confidence. It’s that simple! Frequently Asked Questions What is telecom platform migration preparation? Migration preparation is the work that happens before an MSP begins actively moving subscribers from one platform to another. It includes inventorying the existing environment, gathering and organizing subscriber and configuration data, identifying exceptions and edge cases, and validating migration logic and configurations before live execution where the target environment and testing setup are available. Can we start migration preparation before selecting a platform? Yes. Some migration preparation can begin before final platform selection. Inventory, environment analysis, subscriber data gathering, and identification of migration-relevant configurations can give the team a clearer picture of the work ahead. Target-specific transformation, provisioning, and validation depend on the destination environment. What is Otto? Otto is Vox Matic's proprietary automated telecom migration framework. It automates significant portions of discovery, data extraction, normalization, transformation, provisioning, and validation, reducing repetitive engineering work while expert telecom engineers handle complex exceptions and decisions where required. We already bought capacity. Do we still need preparation? Almost certainly. Purchasing capacity and routing new business to a new platform is a sensible first step, but it does not move existing subscribers. Many MSPs find themselves running two environments in parallel for months or years because the legacy migration never gets formally organized. Preparation is what converts that transition strategy into an actual migration with a defined scope, timeline, and plan. Will migration disrupt customers? Migration preparation helps identify configuration issues, exceptions, and other potential sources of disruption before cutover. Vox Matic combines automation, validation, testing, controlled execution, and expert engineering to reduce migration risk and minimize customer disruption. Exact customer impact depends on the environment and cutover requirements.
- Telecom Migration Data Integrity: How to Protect Subscriber Data During a Platform Migration
Subscriber data is one of the most valuable assets involved in a telecom migration. Moving from platforms such as Metaswitch or BroadWorks to NetSapiens requires more than transferring records. Subscriber profiles, feature assignments, routing rules, device configurations, and third-party integrations all need to arrive accurately and function as expected. Data integrity in a telecom migration means ensuring subscriber records, configurations, routing, features, and integrations remain accurate and functional throughout the migration process. A successful migration is measured not only by whether data appears in the target platform, but by whether services continue working as expected after cutover. Key Takeaways Protecting subscriber data starts with understanding and documenting the source environment before provisioning begins. Legacy platforms and NetSapiens use different data structures, so migration data must be normalized and mapped correctly. Pre-cutover validation helps identify discrepancies before they become customer-facing issues. Exceptions and non-standard configurations should be identified early and reviewed before migration. Otto automates repeatable migration work while senior engineers focus on planning, review, exceptions, and validation. How Do You Protect Subscriber Data During a Telecom Migration? Protecting subscriber data requires a structured process that begins before customers are moved. The goal is to understand the source environment, translate the data correctly, validate the target environment, and resolve exceptions before cutover. Establish a Complete Source Baseline Before provisioning begins, migration teams should document the existing environment. That includes: Subscriber accounts and users DIDs and extensions Feature assignments Hunt groups and call queues Voicemail settings Dial plans and routing rules Auto attendants Device configurations Relevant system integrations This inventory creates a reference point for the migration team. Once the target environment is provisioned, migrated data and configurations can be compared against the source to identify discrepancies before customers are affected. Normalize and Map Data Correctly Metaswitch, BroadWorks, and NetSapiens do not organize subscriber and configuration data in exactly the same way. Field structures, naming conventions, account hierarchies, and feature definitions can differ between platforms. Migration data therefore needs to be normalized and mapped before provisioning. Custom dial plans, specialized customer configurations, and platform-specific features should also be reviewed so they can be transformed appropriately or flagged for engineering review. This step helps ensure the migration preserves not just the record itself, but the service behavior associated with it. Validate Before Cutover Validation is one of the most important controls in a telecom migration. Before a migration batch is moved into production, subscriber accounts and configurations should be checked against the source environment. Depending on the migration, validation can include: Subscriber and seat counts DID assignments Device registrations Feature configurations Call routing Voicemail Auto attendants Integration connectivity Automated reconciliation can make this process more practical across large subscriber bases, while functional testing confirms that migrated services behave as expected. Issues identified during validation are generally easier to address than issues discovered after customers are live. Resolve Exceptions Early Most telecom environments contain configurations that do not fit the standard migration pattern. These may include undocumented routing rules, inactive records, custom customer configurations, or features that do not have a direct equivalent on the target platform. Finding these exceptions early gives the migration team time to decide how they should be handled before provisioning or cutover. Automation handles the repeatable work. Senior engineers focus on the cases that require judgment. How Otto Helps Protect Subscriber Data Vox Matic's Otto automated migration framework helps service providers manage the data and validation work involved in large-scale telecom migrations. Otto supports the migration process by: Extracting migration-relevant data from legacy telecom platforms Normalizing data for the target NetSapiens environment Applying consistent transformation and field-mapping rules Identifying exceptions for engineering review Provisioning validated migration data into NetSapiens Supporting automated reconciliation and validation at scale Senior telecom engineers remain involved throughout the process, focusing on planning, review, testing, exceptions, and decisions that require human judgment. That combination of automation and engineering oversight helps reduce repetitive manual work, improve consistency, and identify potential problems before they affect customers. Protect Subscriber Data Before Cutover Planning a migration from Metaswitch, BroadWorks, or another legacy platform to NetSapiens? Vox Matic helps service providers prepare, transform, provision, and validate migration data using Otto and experienced telecom engineering. By identifying discrepancies and exceptions before customers are moved, providers can reduce migration risk, minimize disruption, and create a more controlled transition to the new platform. Talk to Vox Matic about protecting subscriber data throughout your migration. Move your subscribers, not your migration problems. It's that simple! Frequently Asked Questions What is data integrity in telecom migration? Data integrity means subscriber records, feature assignments, routing rules, device configurations, and relevant integration data transfer accurately and continue functioning as expected in the target environment. A record appearing in the new platform does not necessarily mean the migration is complete if the associated service does not work correctly. What data moves from Metaswitch to NetSapiens? A Metaswitch to NetSapiens migration can include subscriber profiles, user and account information, feature configurations, dial plans, routing logic, device settings, DIDs, voicemail configurations, and relevant integration dependencies. The exact data involved depends on the source environment and customer configuration. How do you validate migration data before cutover? Pre-cutover validation compares migrated accounts and configurations against the source environment. This can include subscriber counts, DIDs, device registrations, feature assignments, routing, voicemail, auto attendants, and integration connectivity. Automation can support reconciliation at scale, while engineers review exceptions and functional results. What happens if subscriber data is corrupted during migration? Data integrity issues can appear as missing features, incorrect routing, device registration problems, or broken integrations. The appropriate remediation depends on the source environment, the affected configuration, and where the issue occurred in the migration process. Thorough discovery, transformation, and validation help identify these issues before cutover. Can you recover data after a failed migration? Recovery options depend on the source environment, migration stage, and nature of the issue. Maintaining accurate source data and validating migrated configurations before cutover gives the migration team a stronger reference point for identifying and correcting discrepancies.
- The Hidden Cost of Delayed Migration: When Acquisition Growth Creates Migration Debt
Migration debt is the backlog of customers, platforms, and processes that have not been moved after a telecom acquisition. Every deal that closes without a migration plan adds legacy infrastructure and old workflows to that backlog. The backlog does not stay flat. It compounds. Research from Infosys shows that operators carry 30 to 50 percent redundancy in spend while old and new systems run side by side. The longer that overlap runs, the costlier it gets. For telecom providers growing through acquisition, this is a specific and compounding problem. Each deal that closes without a consolidation plan adds another layer of platforms, vendors, and split engineering load. The question most teams ask is: what will it cost us to migrate these customers? The more important question is: what is it costing us not to migrate them? This article explains how migration debt builds, why it grows, and how a clear plan changes the economics. Key Takeaways Migration debt is the backlog of legacy customers, platforms, and infrastructure not yet moved after an acquisition. Delaying migration can look smart short term, but the cost of running parallel environments grows with every deal. The cap-and-grow trap leaves existing customers on legacy platforms while new customers go elsewhere, creating fragmentation that is hard to manage and hard to scale. Acquisition without migration is only partial integration. Legal and financial close does not equal technology integration. Duplicate platforms, vendors, engineering, support processes, and integrations often cost more than migration itself. Migration should be part of acquisition strategy from day one, not an afterthought. Automation reduces the manual effort of large-scale migration, making consolidation more practical and repeatable at scale. Why Telecom Providers Delay Migration After an Acquisition What Usually Happens Right After Close When a deal closes, the focus goes to finance, legal, and operations. Migrating customers comes later. There are real reasons for that. Migration is not simple. It needs engineers, planning, and testing. For a team that just closed a deal, those resources are thin. Why Delay Feels Safer The acquired customers are on a working platform. Revenue is flowing. The pressure to act fast is low. Leaving those customers in place feels like the safe call. It avoids disruption and lets the team focus on what feels urgent. The problem is not the delay itself. The problem is treating delay as a plan rather than a pause. When migration gets pushed back deal after deal, the backlog grows. Each new deal adds more platforms, more vendors, and more cost to carry. Each new deal makes the backlog harder to clear. What Is Migration Debt and How Does It Accumulate? Migration debt is the backlog of customers, platforms, and processes that have not been moved after an acquisition. It does not arrive all at once. It builds deal by deal. A provider buys a competitor. The customers stay on the old platform. Six months later, another deal closes. Same result. Now the team runs three or four environments, each with its own vendors and workflows. The backlog is not static. It grows on several fronts at once: Platform complexity: Each old environment has its own setup, integrations, and quirks that need ongoing care. Vendor costs: Every active platform carries license fees, support contracts, and renewal cycles. Engineering load: Running multiple platforms splits team focus and adds overhead. Customer fragmentation: Customers on different platforms get different experiences. That is hard to manage and hard to scale. Integration sprawl: Each legacy platform may tie into billing, provisioning, and CRM tools in ways that are unique and hard to untangle. The core dynamic: Acquisition happens faster than migration. The gap between the two is migration debt. Every month without consolidation is not neutral. The cost and complexity of migration keeps rising. The Cap-and-Grow Trap One of the most common patterns after an acquisition is the cap-and-grow trap. Here is how it works. After a deal closes, the provider leaves existing customers on the old platform and puts all new customers on the target environment. The old platform is capped. No new customers go on it. But the existing ones stay. On the surface, this looks fine. The old platform is not growing. New business goes to the right place. The problem is that those legacy customers do not go away. They still open tickets, need changes, and take up engineering time. The old platform must be maintained and licensed until they move. Some accounts may also span both environments. A customer that adds users after the deal can end up split across old and new systems. That is hard to support and hard to scale. The cap-and-grow trap does not fix the migration problem. It delays it. The longer the old platform stays on, the harder it is to shut down. Migration is the only exit. The real question is how long you wait before taking it. That decision carries real risk, but migration does not have to mean losing data, clients, or time if it is planned and executed well. Acquisition Without Migration Is Partial Integration When a provider completes an acquisition, the transaction closes. The financials consolidate. The legal entities merge. The customers appear on the books. By most measures, the integration looks complete. But technology integration is a different matter. Financial and legal integration can be done while acquired customers stay on a separate platform, run through separate processes, and billed through separate systems. The deal is done on paper. In practice, two businesses are still running side by side. Migration debt shows up on the balance sheet, not just the infrastructure diagram. The Synergies That Never Arrive Deals are sold on synergies: lower costs, shared systems, better margins, a stronger market position. Most of those gains depend on getting customers onto one platform. Same tools. Same processes. Same roadmap. When migration is delayed, those gains are delayed too. The deal assumed one platform. The reality is two businesses still running side by side. That gap costs money every month. Acquisition without migration is partial integration. The deal closed. The work did not. The Real Cost of Post-Acquisition Migration Debt Most providers ask one question when evaluating migration: what will it cost us to migrate these customers? That is the wrong question. The right one is: what is it costing us not to migrate them? Inaction has a price. It compounds with every month the old platform stays on. Here is what a provider is carrying for every legacy platform that stays active after an acquisition: Cost Category What It Includes Platform licensing Ongoing vendor fees for platforms that are no longer part of the growth strategy Engineering overhead Staff time required to maintain, support, and troubleshoot legacy environments Duplicate integrations Parallel connections to billing, provisioning, CRM, and support systems Training burden Support and operations teams trained across multiple platforms and workflows Provisioning complexity Manual processes that differ by platform, increasing error rates and cycle times Product limitations Customers on legacy platforms cannot access new features available on the target environment Opportunity cost Engineering time spent maintaining legacy infrastructure is not being invested in growth Every item on that list is a recurring cost that runs until the old platform is shut down. Industry estimates show legacy systems can consume 60 to 80 percent of a company's total IT budget (Aalpha, 2026). For providers running several old platforms at once, that figure grows with every deal. The longer migration is deferred, the wider the gap grows between what the business is spending and what it would spend on a consolidated environment. At some point, staying put costs more than moving. For many providers, that point has already passed. McKinsey finds that each year of delay can raise the cost of modernizing by 20 to 25 percent, as technical debt keeps building. How to Build Migration Into Your Acquisition Strategy Migration debt is not inevitable. It builds when providers treat migration as something to figure out after the deal closes rather than before it. Providers that plan before a deal closes start from a better place. Before close, there is time to understand what the move will take, what it will cost, and how long it will run. What Acquisition Due Diligence Should Include A solid plan treats technology with the same care as finance and legal. That means knowing: Platform inventory: What platforms are the acquired customers on? What versions and custom setups exist? Subscriber profile: How many customers, users, and seats are coming over? What services do they use? Migration needs: What does it take to move these customers to the target platform? What are the risks and dependencies? Target readiness: Can the destination platform handle the incoming volume and complexity? Timeline and resources: What engineering capacity is needed? What is a realistic timeline given current workloads? Legacy retirement plan: When and how will the old platform be shut down? What are the contract and operational steps? Total cost of integration: What is the full cost, including engineering, tooling, customer comms, testing, and the ongoing cost of delay? Answering these before close does not remove the complexity. But it removes the surprise. It lets the provider set a real timeline rather than leaving consolidation open-ended. Growth should reduce complexity, not accumulate it. Every deal should move the business closer to a unified, scalable environment, not further from it. How Automation Reduces Migration Debt at Scale Migration debt builds because manual migration is slow. Moving customers from an old platform means engineers must pull configs, move data, validate records, set up the new system, test each account, and manage the cutover. At scale, that work takes time, costs money, and carries risk. For providers running hundreds or thousands of seats across old platforms, the manual model caps speed. The backlog grows faster than the team can clear it. That changes when you bring in automation. Reducing the Manual Work of Migration at Scale When the repetitive parts of migration run on automation, the economics shift. Discovery, data handling, provisioning, and testing run on a system rather than by hand. That cuts engineering time per customer and lets migration move at the pace the backlog demands. This is the model that Vox Matic is built around. As an automation-led telecom migration and consolidation company, Vox Matic helps service providers move customers from legacy environments, including Metaswitch and BroadWorks, into NetSapiens and modern communications environments. The Otto automated migration framework cuts the manual engineering work that makes large-scale migration impractical for most teams. The result is faster migration, but also migration that holds up at scale. For providers with a big backlog, repeatability matters as much as speed. Manual migration made the backlog feel permanent. Automation is what actually clears it. For providers carrying a large backlog, the tools matter as much as the intent. Acquire. Integrate. Migrate. Consolidate. Grow. Acquisition is a growth strategy. But growth that adds complexity rather than cutting it is not a strong foundation. Providers that build lasting businesses through acquisition follow a clear progression: Acquire. Find and close deals that grow the customer base, reach, or market position. Integrate. Complete the financial, legal, and operational steps to bring the acquired business in. Migrate. Move acquired customers from old platforms to the target environment on a set plan and timeline. Consolidate. Retire old platforms, remove duplicate systems, and run from one unified environment. Grow. Scale from a clean foundation, with the efficiency and capacity that consolidation creates. The gap that creates migration debt sits between Integrate and Migrate. When that gap stays small and managed, migration debt stays in check. When it grows deal by deal, it becomes one of the biggest operational problems a provider will face. How much is waiting costing you? Ask it before the next deal closes. The goal is not to slow down. It is to stop leaving migration as an open item every time a deal gets done. That means building migration into the deal from the start, not scheduling it for later. For providers ready to act, the next question is execution: how to migrate without losing data, clients, or time. And for those still weighing the decision, the cost of doing nothing is rising with every quarter that passes. Frequently Asked Questions What is migration debt? Migration debt is the accumulation of customers, platforms, configurations, and operational dependencies that remain on legacy infrastructure after an acquisition. Like technical debt, the longer migration is delayed, the greater the complexity and effort required to complete it. Why do telecom providers delay migration after an acquisition? Migration needs engineers, planning, and testing. Right after close, those resources are thin. Leaving customers on their current platform feels like the safer call. But delay is not free. The cost of running two systems keeps adding up. What is the cap-and-grow trap? The cap-and-grow trap happens when a provider stops adding new customers to an old platform but leaves existing customers in place. The old platform is capped but not shut down. Those customers still need support, changes, and engineering time. The platform must be maintained and licensed until they move. Migration is the only way to close that gap. How does delayed migration affect acquisition synergies? Most synergies from a deal depend on consolidation: lower costs, shared support, and the same product for all customers. All of that requires customers to be on one platform. When migration is delayed, those synergies are delayed too. The deal closes, but the financial gains of consolidation stay out of reach. What should be included in a migration plan as part of acquisition due diligence? A solid migration plan should cover platform inventory, subscriber profile, migration needs, target readiness, engineering resources, a real timeline, a legacy shutdown plan, and the total cost of integration including the cost of delay. Covering these before close lets the provider set a defined migration timeline rather than leaving consolidation open-ended. How does automation help reduce migration debt? Manual telecom migration is slow at scale. Automation cuts the engineering effort per migration. Discovery, provisioning, validation, and testing can run on a system rather than by hand. That makes large-scale migration more repeatable and more scalable for providers working through a large backlog. What is the right framework for acquisition-driven growth? Acquire. Integrate. Migrate. Consolidate. Grow. The gap that creates migration debt sits between Integrate and Migrate. Providers that keep that gap small, build businesses that get more efficient with each deal. Those that leave it open find that complexity compounds faster than revenue does.
- STAY. MIGRATE. CONSOLIDATE?
Metaswitch: A practical cost comparison. Which path makes the most financial sense over the next 24 to 36 months? That is the decision facing every provider still using Metaswitch. Microsoft ended Metaswitch development on June 3, 2024, laying off the majority of its sales, engineering, and professional services workforce. Alianza acquired the platform on March 4, 2025. Two ownership changes in five years does not provide the stability needed for long-term platform planning. Staying has a price: licensing, engineering overhead, dual-platform support, and churn exposure. None of those appear as a single line item, which is why they accumulate undetected. This post gives you a framework to model that decision across three subscriber tiers: 500, 2,000, and 10,000. Key Takeaways Legacy platform costs are not just licensing fees. Engineering overhead, dual-platform support, and churn risk are often the larger line items. Manual migrations carry significant hidden labor costs that scale with subscriber volume. Automated migration with Otto reduces engineering hours, compresses timelines, and accelerates ROI. Automation can accelerate break-even by reducing engineering costs and retiring the legacy platform sooner. Consolidating onto NetSapiens via automation is the highest-ROI path for providers managing more than one legacy platform simultaneously. The Real Cost of Staying on Metaswitch Most providers spread Metaswitch costs across multiple budget lines. No single one triggers a review, which is how the total stays invisible. Six cost categories belong in any honest analysis: Legacy platform licensing and support fees: Maintenance contracts rarely decrease as the platform ages. In many cases, they increase as the vendor shifts investment elsewhere. Engineering overhead: CSPs spend over 60% of their budgets maintaining legacy infrastructure (Alianza white paper). Engineers working on a platform with no development roadmap are not working on growth. That cost does not show up as a line item. Dual-platform support: Providers already running a partial NetSapiens deployment are paying to maintain two environments simultaneously, and that overhead grows with each passing month. Integration debt: Legacy platforms require increasing customization to connect with modern UCaaS and analytics tools. That work is billed once but maintained indefinitely. Churn risk from feature gaps: Subscribers on legacy platforms do not have access to the same feature set as those on modern platforms, which creates competitive vulnerability over time. Deferred migration cost: Delaying does not eliminate migration expense. It defers it, and delayed migrations are almost always more complex and more expensive. These costs do not appear together on a P&L, which is why most providers only see the full number after the fact. Modeling Your Metaswitch Migration: Three Subscriber Tiers These are directional models. Apply your actual contract values and engineering rates to see where your numbers land. Five variables drive the model: Legacy platform annual support cost Engineering hourly rate (fully loaded) Hours per subscriber for manual vs. automated provisioning Duration of dual-platform parallel operation Churn risk premium from feature gaps Break-even formula: Total transition investment ÷ Monthly savings after legacy retirement = Months to ROI Tier Analysis: Where the Numbers Move 500 Subscribers 2,000 Subscribers 10,000 Subscribers Stay Support contract + 1–2 engineers + churn risk Growing integration debt, rising churn, meaningful support spend Substantial overhead on a legacy platform with an uncertain development path Manual move 20–40 hrs per 100 subscribers; dual-platform carry costs Parallel operation extends 6–12 months; disruption risk rises Engineering hours become the single largest project line item Otto-led transition Automates provisioning and cutover; shorter project duration Shortens parallel operation window; reduces per-subscriber effort Strongest ROI case: lower cost, faster retirement, earlier break-even Engineering labor and dual-platform carry costs are the two largest variables in any budget. Automation addresses both directly. Why Automation Changes the Economics Engineering labor and parallel platform duration are the two costs that determine whether a Metaswitch migration pays off quickly or drags. Vox Matic's Otto automated migration framework handles provisioning, data migration, and cutover work that consumes most engineering hours in a manual project. It reduces per-account effort from hours to seconds, which changes the economics in two key ways: Fewer hours billed reduces gross project spend. A shorter project cuts the months you run two platforms in parallel, which stops legacy fees from stacking. For most providers, that produces a lower total project cost and an earlier break-even. Explore the full scope of consolidation services at the Vox Matic network solutions page, or connect with our team to start building your own model. Frequently Asked Questions What is the biggest hidden cost of staying on Metaswitch? Dual-platform support. Providers running a partial NetSapiens deployment alongside Metaswitch pay to maintain two platforms, two engineering skill sets, and two support structures simultaneously. That overhead compounds every month the move is deferred. At what subscriber volume does automation make the most economic sense? Automation improves the economics at every tier, but the ROI case is strongest at 2,000 subscribers and above. For providers managing multiple legacy platforms simultaneously, the consolidation case is compelling at any scale. How long does a Metaswitch to NetSapiens migration typically take? It depends on subscriber volume, platform complexity, and whether the project is manual or automated. Manual projects at larger tiers can extend 6 to 12 months or more. Automated projects are designed to reduce that timeline by handling the repeatable work that drives most of the engineering hours. See our full Metaswitch to NetSapiens migration guide for a detailed breakdown. Build Your Own Model Apply your actual contract values, engineering rates, and subscriber volumes to the framework above. The numbers will point you in a direction. When you are ready to model the automated path, the Vox Matic team can work through it with you. Start at our network solutions page or review the Otto automated migration framework to see what the timeline and cost structure look like for your environment. It's that simple!
- How Executives Should Assess the Financial Impact of Migration Automation
When evaluating a platform migration, service providers often focus first on engineering requirements. A stronger assessment considers the broader financial impact: total cost, project timeline, parallel platform expenses, and engineering capacity diverted from growth. Key Takeaways Automation shifts engineers from repetitive execution to oversight, validation, and exception handling. Shorter timelines reduce ongoing legacy licensing, maintenance, and support costs. Fuse.Cloud completed its migration with Otto in six months versus an estimated 18 months manually. The business case depends on three factors: legacy costs eliminated, time to full operation on the new platform, and engineering capacity redirected to higher-value work. Traditional migrations rely heavily on engineers to move records, apply configurations, and validate results. Automation handles much of this repeatable work faster and more consistently, changing how migration costs and resources scale. The hidden costs of traditional migration (extended licensing, engineering overhead, remediation, and deferred revenue) are explored further in The Business Case for Retiring Legacy Telecom Platforms and The Most Expensive Migration Is the One You Delay. This article focuses specifically on how automation changes those costs. What Does Migration Automation Actually Change? Automation does not eliminate the need for telecom engineers. It changes where their expertise is applied. In a manual migration, engineers spend substantial time moving records, applying configurations, validating results, and correcting inconsistencies. Automation handles much of this repeatable execution, allowing engineers to concentrate on architecture, complex exceptions, testing, and oversight. This shift can reduce engineering hours, improve consistency, and support larger migration volumes without a proportional increase in staffing. Factor Manual Migration Automation-Led Migration Engineering hours required High; every step requires hands-on execution Lower for repeatable tasks; engineers focus on oversight, validation, and exceptions Timeline Extended by subscriber volume and manual throughput Typically shorter; repeatable tasks can be processed at greater scale Configuration consistency Variable; dependent on individual execution More consistent; defined rules are applied across the migration Legacy platform overlap Prolonged by timeline; licensing costs continue Shortened; faster cutover reduces the overlap period Scalability Requires proportional headcount increases Supports greater scale without requiring engineering effort to increase proportionally Senior engineer focus Consumed by execution tasks Available for architecture, validation, and growth work Why Reduced Engineering Effort Matters to the Business Reduced engineering effort can lower project costs, shorten the path to full cutover, and allow the legacy platform to be retired sooner. Three Economic Outcomes That Drive the Decision 1. Faster transition to the new platform Every additional month of migration extends the period during which the organization supports both the legacy and destination platforms. Fuse.Cloud reported full ROI in under five months after cutover. 2. Earlier retirement of legacy costs Legacy licensing, maintenance, infrastructure, and support costs continue until the old platform is retired. Shortening the migration timeline reduces the period of parallel spending and allows those costs to be eliminated sooner. According to a 2025 TXO industry report, maintenance costs at many large service providers have surged 30 to 40 percent over the past year alone. 3. Engineering capacity available for higher-value work Manual migration can consume substantial senior engineering capacity. Automation allows engineers to concentrate on architecture, validation, customer requirements, and complex exceptions while repeatable tasks are processed at scale. The business case can therefore be assessed using three inputs: the duration of parallel platform costs, the time required to complete cutover, and the engineering effort required to execute the migration. The most useful comparison is therefore total transition cost, not the engineering quote alone. How Otto Applies the Migration Model Otto is Vox Matic’s proprietary automated migration framework, built for service providers transitioning from legacy platforms such as Metaswitch and BroadWorks to NetSapiens. By automating high-volume, repeatable migration work, Otto can shorten timelines, reduce engineering effort, and support earlier retirement of the legacy platform. What Engineering Focuses On Otto does not replace telecom expertise. It redirects it. Vox Matic’s senior engineers remain central to each migration, managing architecture decisions, complex exceptions, validation, and cutover oversight. This allows engineering expertise to be applied where it provides the greatest value. Otto is designed to help minimize customer disruption throughout the transition. The platform changes. The experience does not. For a practical example of this migration model, see the Fuse.Cloud migration story. What Should Executives Ask a Migration Partner? Proposals may contain similar timelines and deliverables while relying on very different execution models. The following questions help reveal how a partner’s approach affects cost, scalability, risk, and customer continuity. On the Approach What percentage of migration execution is automated versus manual? The answer should clarify which activities are automated and which still require manual engineering. How does your approach scale as subscriber volume increases? A scalable migration model should accommodate higher volumes without requiring proportional increases in staffing, processing time, or project cost. How do you measure configuration accuracy and manage exceptions? A strong partner should identify exceptions during validation and follow a defined remediation process before cutover. On the Economics What is the total cost of the migration, including legacy platform overlap? A lower engineering quote that extends the timeline may cost more in total than a higher quote that compresses it. How does your pricing change if the scope increases mid-project? The pricing model should clearly explain how changes in subscriber volume, complexity, and engineering requirements affect total project cost. What is the expected timeline from kickoff to full cutover? Timeline is a direct driver of total migration cost. The partner should be able to explain the assumptions, dependencies, and variables that influence the proposed timeline. On Customer Impact How do you protect the customer experience during cutover? The partner should have a defined process for validation, controlled cutover, issue response, and service continuity. What is your process if a customer segment encounters issues post-cutover? The partner should have a documented process for identifying, isolating, and resolving post-cutover issues. Executives who evaluate migration partners on engineering quote alone are optimizing for the wrong number. The real measure is how fast the business reaches full operation on a modern platform, with the least disruption to customers along the way. Why the Migration Model Matters A platform migration affects more than the technology being replaced. It determines how long duplicate costs remain, how much engineering capacity is consumed, and how quickly the organization can retire its legacy infrastructure. Automation does not guarantee a successful migration. Discovery, planning, validation, and engineering judgment remain essential. What automation changes is the ability to perform repeatable work consistently and at scale. The most useful question is therefore not simply how many engineers a migration requires. It is which approach provides the clearest path to full cutover, legacy platform retirement, and measurable financial return. Build a Stronger Business Case for Migration The financial impact of migration automation extends beyond the initial project cost. Executives should assess: Parallel platform costs Time required to retire the legacy platform Engineering resources required Expected timeline to full cutover Potential savings from completing the transition sooner A structured assessment brings these factors together, giving decision-makers a clearer understanding of the migration’s total cost, resource requirements, and potential return. Vox Matic can help evaluate the existing platform, identify opportunities for automation, and develop a migration plan aligned with operational and financial priorities. FAQ How does migration automation reduce engineering effort? Automation handles repeatable activities such as data movement, configuration provisioning, and validation. Engineers remain responsible for architecture, complex exceptions, testing, and oversight. Does automation eliminate the need for engineers? No. It allows engineers to focus on work requiring platform knowledge and judgment rather than repetitive execution. Why does reduced engineering effort matter? It can lower project costs, shorten the migration timeline, and free specialized resources for customer, network, and growth-related priorities. How does Otto support this model? Otto is Vox Matic’s automated migration framework for moving service providers from legacy telecom platforms to NetSapiens while maintaining engineering oversight throughout the project. What should executives ask a migration partner? Executives should ask which activities are automated, how the model scales, how configurations are validated, how customers are protected during cutover, and what factors determine the total timeline and cost. It's that simple!
- The Business Case for Retiring Legacy Telecom Platforms
Retiring a legacy telecom platform is not only a technology decision. It is a business decision. For service providers still operating legacy platforms such as Metaswitch, BroadWorks, and BroadSoft, continued licensing, engineering overhead, fragmented operations, and delayed modernization can make the cost of waiting increasingly difficult to justify. The question is not whether to retire. It is how to do it without disrupting the business you have built. Key Takeaways Legacy platforms like Metaswitch and BroadSoft carry four distinct cost categories that compound over time: licensing, engineering, opportunity, and risk costs. Platform end-of-life announcements have accelerated the urgency of retirement decisions for many providers. The financial case for migration is strongest when modeled against a 24-36 month horizon, not a single-quarter budget. Automated migration tools have reduced the engineering effort required to move customers from hours per account to seconds, which changes the ROI calculation entirely. Providers who retire legacy platforms proactively report faster onboarding and lower support overhead. Fuse.Cloud reduced their migration timeline from 18 months to 6 and achieved full ROI in under five months. What Does It Actually Cost to Keep a Legacy Platform Running? Most providers underestimate the true cost of their legacy environment because the costs are distributed across departments and budget lines. Licensing shows up in one place. Engineering time shows up in another. Lost deals and slow onboarding rarely show up anywhere at all. To build an honest business case, costs need to be organized into four categories. 1. Licensing and Vendor Costs Legacy platforms from Metaswitch and Cisco BroadWorks carry ongoing licensing fees. Those fees have not declined as the platforms aged. In many cases, they have increased. Legacy platforms can remain operational while becoming increasingly difficult to justify from a cost and operational perspective. Ongoing licensing, specialized engineering requirements, integration maintenance, fragmented environments, and evolving customer expectations can all increase the cost of remaining on legacy infrastructure. For service providers, platform retirement is therefore not simply a lifecycle decision. It is a question of operating efficiency, modernization, and long-term economics. 2. Engineering and Support Overhead Legacy platforms require specialized engineering knowledge that is increasingly difficult to source. Every hour spent maintaining integrations or troubleshooting provisioning issues is an hour not spent on growth or customer experience. The overhead compounds fast. A provider running 5,000 seats across two or three legacy platforms does not have twice the complexity of a provider running 2,500. It has far more. The interdependencies multiply. Straightforward support tickets become cross-platform investigations. 3. Opportunity Cost This cost category rarely appears in a budget review. It is often the largest. Legacy platforms constrain what you can offer. Slower provisioning means longer onboarding cycles and higher early churn risk, a risk that careful cutover planning addresses directly. Feature gaps make it harder to compete for mid-market and enterprise accounts. Integration limits slow the development of bundled services that drive ARPU growth. Deals take longer to close. Customers churn when a competitor offers a smoother experience. Upsells never happen because the platform cannot support them. That is real revenue that never materializes. 4. Platform Risk This is the category that converts a financial discussion into a strategic one. Legacy platforms carry risk that grows over time in ways that are difficult to price but impossible to ignore. End-of-life risk: When a platform reaches end-of-life or end-of-support, providers lose access to security patches, bug fixes, and compliance updates. Running unsupported infrastructure in a regulated communications environment creates liability that no licensing fee can justify. Talent risk: The pool of engineers with deep Metaswitch or BroadSoft expertise is shrinking. When a senior engineer with institutional knowledge of your legacy environment leaves, that knowledge is difficult to replace. Vendor risk: Acquisitions, pivots, and sunset decisions by platform vendors can force a migration on a timeline you did not choose, under conditions you did not control. Why Do Providers Keep Delaying the Decision? The business case for retirement is usually clear on paper. The delay is rarely about the numbers. It is about perceived risk and organizational inertia. The three most common objections: Objection What It Actually Signals "Our customers are stable on this platform." Fear of disruption during migration, not satisfaction with the platform itself. "We do not have the engineering bandwidth to run a migration." The migration has been scoped as a manual project, not an automated one. "We'll address this after the next growth cycle." The decision is being deferred, not evaluated. Each deferral increases the cost. The first objection is a migration execution problem, not a retirement problem. If customers can be moved without service interruption, the stability argument disappears. The second is a tooling problem. Manual migrations are resource-intensive; automated migrations are not. The third is a planning problem, and it is the most dangerous because it tends to compound indefinitely. The providers who have completed platform retirement consistently say the same thing: the anticipation was harder than the execution. What they did not expect was how quickly the operational picture changed once the legacy environment was gone. How Does Automation Change the Retirement Calculation? The traditional objection to platform retirement was always about complexity. Moving thousands of customer accounts, each with unique configurations, dial plans, and integrations, has traditionally required significant manual engineering effort. For many providers, that perceived effort has been a primary reason to delay retirement. Automated migration changes that. Otto,is Vox Matic's proprietary automated telecom migration framework, built specifically to handle migration complexity across large customer bases. What Automation Actually Does Otto is Vox Matic's proprietary automated telecom migration framework. Vox Matic's model is automation first, expert engineering where required. Otto automates significant portions of discovery, data extraction, normalization, transformation, provisioning, and validation while experienced telecom engineers handle complex exceptions and decisions requiring human judgment. Discovery and data extraction: Automated tools read existing configuration data from legacy platforms without requiring engineers to manually document every account. Data transformation: Customer data is normalized and mapped to the target platform's schema automatically, eliminating the error-prone manual translation step. Provisioning: Accounts are created on the destination platform in bulk, without the manual effort traditional provisioning requires. Validation and testing: Automated checks verify that migrated accounts match the original configuration before cutover. Customer cutover: End-users are transitioned through controlled cutover windows designed to preserve service continuity. Engineering effort shifts from execution to oversight. The result is a migration program that is more repeatable, more consistent, and faster to complete than a manual approach. What This Means for the Business Case When migration is a multi-year manual project, the ROI horizon is long and the risk profile is high. When migration is an automated process supported by senior engineering expertise, the ROI horizon shortens dramatically. Fuse.Cloud, a Vox Matic customer, reduced its migration timeline from 18 months to 6 months using automated migration, and achieved full ROI in under five months. For a provider with a large installed base, that difference compounds directly into margin recovery earlier legacy platform retirement, and a faster path to ROI. The number that changes the conversation: model migration cost against an 18-24 month operational savings horizon, not a 5-year one. Most environments clear that bar with room to spare. What Does a Successful Platform Retirement Look Like? Platform retirement is not a single event. It is a phased program, and the providers who execute it successfully treat it that way from the start. Know What You Are Actually Dealing With The existing environment needs to be fully understood before any migration begins. This includes an inventory of all customer accounts, configuration types, feature dependencies, and integration points — the same foundation Vox Matic outlines in its MSP migration process. Automated discovery tools can complete this step far faster than manual audits, and the output becomes the foundation for migration planning. That output answers the question that stalls most retirement decisions: "How complex is what we actually have?" Sequence for Confidence, Not Just Convenience Not all customers need to move at the same time. Migration sequencing should be based on the provider's environment, customer complexity, dependencies, operational requirements, and cutover plan. There is no universal order — the right sequence is the one that reflects how your business actually operates. Let Automation Handle the Volume Otto automates significant portions of the repeatable migration work at scale, while Vox Matic’s approach remains automation first, expert engineering where required. Otto handles the repeatable work that would otherwise require significant manual engineering time per account. Engineering oversight shifts to exception handling: accounts with non-standard configurations, edge-case feature mappings, or integration dependencies that require human judgment. The balance between automation and engineering will vary by environment. Decommission and Capture the Savings The final step is the one that delivers the financial payoff: decommissioning the legacy environment and eliminating its associated costs. This is also the step that validates the business case. Licensing fees stop. Engineering overhead drops. The operational model simplifies. Fuse.Cloud's COO put it plainly: deployments got faster, overhead dropped, and customers barely noticed the change. Is Now the Right Time to Retire Your Legacy Platform? The timing question is the one most providers get stuck on. There is always a reason to wait: an upcoming contract renewal, a growth push, a team that is stretched thin. But the timing question has a structural answer that does not depend on current conditions. The right time to retire a legacy platform is before one of these three external events forces the decision: Vendor end-of-life announcement. When a vendor announces that a platform will no longer receive support or security updates, providers lose control of their timeline. Migration under deadline pressure is more expensive, more disruptive, and more error-prone than migration on a planned schedule. A significant customer loss tied to platform limitations. Losing a high-value customer because a competitor's platform offered capabilities yours could not is a recoverable event. Losing several is a trend. At that point, the cost of delay has already been realized. An acquisition that requires platform consolidation under pressure. Providers who grow through acquisition often find themselves managing three or four legacy environments simultaneously — a pattern Vox Matic covers in depth in The Hidden Cost of Delayed Migration. Consolidating under pressure, with integration deadlines and investor expectations bearing down, is a categorically different problem than consolidating on your own terms. None of these events are hypothetical. They are happening across the MSP and service provider market right now. The providers who retire on their own terms come out ahead. Lower cost, less disruption, faster ROI. The ones who wait get the same migration, just under worse conditions and on someone else's schedule. Retiring a legacy platform is ultimately a business decision. The longer the additional licensing costs, operational complexity, and platform risk remain in place, the greater the cost of waiting. With the right combination of automation and engineering expertise, providers can modernize on their own terms rather than on a vendor’s timeline. Earlier legacy platform retirement and a faster path to ROI. Request a migration assessment with Vox Matic and build your retirement plan before the decision is made for you. It's that simple! Frequently Asked Questions What is legacy telecom platform retirement? Legacy telecom platform retirement is the process of decommissioning an end-of-life or outdated communications platform, such as Metaswitch or BroadSoft/BroadWorks, and migrating all customer accounts and configurations to a modern replacement. It is a defined program, not a single technical event. How long does it take to retire a legacy telecom platform? The timeline depends on subscriber volume, configuration complexity, source environments, preparation, and cutover requirements. Automation can reduce repetitive engineering effort and help compress migration timelines. In one published example, Fuse.Cloud estimated that a manual migration would have taken approximately 18 months. Using Vox Matic, the migration was completed in approximately six months. That result is specific to the Fuse.Cloud engagement. What happens to customers during a legacy platform migration? Vox Matic designs migrations to minimize disruption and preserve the customer experience. Automation, validation, testing, controlled execution, and expert engineering help reduce migration risk and avoid noticeable downtime wherever possible. Exact customer impact depends on the environment and cutover requirements. Is it possible to migrate from Metaswitch or BroadSoft to NetSapiens without rebuilding everything manually? Yes. Automated migration tools are specifically designed to extract, transform, and provision customer data from Metaswitch and BroadWorks environments into NetSapiens without manual rebuilding. Configuration mapping, feature translation, and account creation are handled programmatically, with engineering oversight focused on exceptions rather than execution. How do I build an internal business case for platform retirement? Start by quantifying costs across four categories: licensing and vendor fees, engineering and support overhead, opportunity costs from platform limitations, and platform risk. Then model those costs against a 24-36 month horizon and compare them to the one-time cost of a structured migration. In most environments, the retirement case becomes financially clear within that window. What is the biggest risk of not retiring a legacy platform? The biggest risk is losing control of the timeline. Providers who delay retirement until a vendor end-of-life announcement, a significant customer loss, or a forced acquisition consolidation are migrating under pressure rather than on a planned schedule. Unplanned migrations are more expensive, more disruptive, and more likely to result in customer churn.
- How to Consolidate Telecom Platforms After an Acquisition
What Is Post-Acquisition Telecom Platform Consolidation? Post-acquisition telecom platform consolidation is the process of migrating customers, configurations, and services from an acquired company's legacy communications platform onto a single, unified UCaaS stack, then retiring the source system to eliminate the operational and licensing overhead of running two environments in parallel. In practice, this means moving customer accounts, provisioning logic, billing dependencies, routing rules, and device configurations from one environment into a consolidated UCaaS platform such as NetSapiens. The source platform cannot be switched off until every customer on it is confirmed live on the new stack. That dependency chain is what makes consolidation hard, and why teams without a structured approach are still running two platforms years later. Key Takeaways Running two platforms post-acquisition adds immediate duplicate licensing, support, and engineering costs on both stacks Discovery comes first: understanding what you inherited is the prerequisite to migrating any of it Automation reduces per-customer migration work substantially, making large-scale consolidation repeatable Every phase must be validated before the next begins - skipping validation is one of the most common causes of cutover failure Legacy platform retirement is the finish line: consolidation is not complete until the source system is decommissioned The acquisition is complete, but the real risk begins after the paperwork is signed. Every day two telecom platforms operate in parallel, costs increase, complexity grows, and the value of the acquisition remains unrealized. The moment ink dries on a telecom acquisition, you inherit something nobody put in the term sheet: a tangle of legacy platforms, duplicate billing systems, incompatible provisioning workflows, and customer data spread across environments that were never designed to talk to each other. According to the POPX State of MSPs 2025 Report, platform integration and data migration are the joint top challenge for 60% of MSPs post-acquisition, with nearly half reporting rising technology costs from slow consolidation. Dual licensing runs on both stacks from day one. Engineering teams stretch across two sets of tools. Customers expect uninterrupted service regardless of what is happening at the ownership level. What follows is the framework for doing that. Why Is Telecom Platform Consolidation So Hard After an Acquisition? Telecom platform consolidation after an acquisition is hard because you are merging live, always-on environments where any disruption affects paying customers immediately, while simultaneously reconciling incompatible data schemas, provisioning logic, and billing structures across two platforms that were never designed to interoperate. You cannot take the system offline, and you rarely have the luxury of slowing down to figure everything out. The scale compounds quickly. A typical MSP acquisition means inheriting a second full stack: separate UCaaS platforms, separate provisioning workflows, separate customer databases, and separate billing systems. None of it maps cleanly onto NetSapiens without deliberate transformation work. Industry data shows that operators carry 30-50% redundancy in combined infrastructure spend during the dual-platform window. Most consolidations stall for the same reasons: teams skip discovery and hit undocumented configurations mid-cutover, treat migration as a data problem rather than a platform re-mapping exercise, rely on manual execution that does not scale, or begin cutovers without a tested rollback path. The integration debt reality: Every month an acquired platform remains active, organizations continue paying duplicate licensing fees, maintaining duplicate operational processes, and supporting duplicate customer environments. Integration debt accumulates quickly, reducing the profitability gains that justified the acquisition in the first place. Consolidation is not merely a technology project—it is a business imperative. What Are the Benefits of Telecom Platform Consolidation? Successful platform consolidation delivers benefits that extend beyond cost savings. By bringing existing and acquired customers onto a single platform, service providers simplify operations, standardize service delivery, reduce legacy dependencies, and create a stronger foundation for future growth. Reduced licensing and infrastructure costs Simplified support operations Consistent customer experience Faster introduction of new services What Are the Right Priorities After a Telecom Acquisition? Early post-acquisition priorities should focus on understanding the acquired environment, defining the target state, identifying dependencies, and building a controlled migration plan before large-scale execution begins. Moving customers before that groundwork is complete is the most common reason consolidations stall. The POPX State of MSPs 2025 Report found that 39% of acquisitive MSPs reported delays in improving profitability and EBITDA directly attributed to slow integration. Acting quickly without a plan can be as damaging as moving too slowly. Priority 1: Discovery and Environment Analysis The starting point is understanding what you actually inherited, not what the due diligence deck said you inherited. These two things are frequently different. What to audit: Full inventory of both platform environments (Metaswitch, BroadWorks, or other legacy stacks) Customer data schemas: how are accounts, devices, users, and entitlements structured in each system? Custom configurations: non-standard dial plans, hunt groups, auto-attendant logic, call routing rules Billing system dependencies: how does provisioning data flow into billing on each platform? Licensing contracts: what are the exit terms and timelines for the legacy platform? The output of this phase is a consolidation map: a clear picture of what needs to move, what needs to be re-built in the target environment, and what can be retired. Priority 2: Target-State Planning and Preparation Before migrating any customers, the NetSapiens environment needs to be ready to receive them. If you want the broader platform context, this NetSapiens migration guide is a useful companion piece. This means configuring it to match the service structures of the acquired customer base, not the other way around. Critical preparation steps: Normalize data schemas between source and target environments Build and test transformation logic for provisioning records Configure the target platform's reseller hierarchy and feature packages Establish cutover procedures and rollback criteria Run a pilot migration with a small, low-risk customer group This phase is where automation earns its value. Manual preparation at this stage is error-prone and slow. Automated discovery and transformation tools accelerate preparation significantly by extracting, mapping, and validating configuration data programmatically. Example Consolidation Scenario A telecom provider acquires a regional MSP operating 2,500 seats on BroadWorks. Rather than manually rebuilding customer environments, the acquiring provider uses automated discovery and transformation tools to migrate customers in planned customer groups. The process reduces manual engineering effort, accelerates platform retirement, and minimizes customer disruption while consolidating operations onto NetSapiens. Priority 3: Controlled Migration and Validation With discovery complete and the target environment validated, migration begins in customer groups. Smaller, lower-risk customers move first. Each customer group is confirmed stable before the next begins. A phased approach protects you in three ways: Risk Manual Approach Phased Automated Approach Service disruption Affects all customers if cutover fails Contained to one customer group Data integrity Errors discovered post-migration Validated before each cutover Timeline Unpredictable; scales with headcount Predictable; scales with automation The size of the acquired environment, configuration complexity, and contractual dependencies on the legacy platform all determine how long this phase runs. What matters is that each customer group is confirmed before the next begins, not how fast the overall clock moves. How Does Automation Change the Consolidation Timeline? Otto is Vox Matic's automated migration framework designed specifically for consolidating legacy telecom platforms onto NetSapiens at scale. Developed from years of telecom migration experience, Otto automates the repetitive work involved in migrating customer data, configurations, and services from legacy environments into NetSapiens, allowing engineering teams to focus on planning, validation, testing, and customer experience rather than manual provisioning tasks. The result is a migration that scales with the size of the acquired environment rather than with headcount. Every additional month of dual-platform operation adds licensing fees, support overhead, and engineering complexity on both stacks simultaneously. That cost compounds the longer consolidation is delayed. The POPX State of MSPs 2025 Report found that 49% of MSPs reported rising technology costs due to slow migration, and 44% said integration delays directly hindered their ability to satisfy private equity investors. Those are not abstract risks. They are the measurable cost of running two platforms longer than necessary. How Do You Deliver a Seamless Customer Migration Experience? The goal of post-acquisition platform consolidation is to make it invisible to customers: 38% of MSPs reported client disruption during integration (POPX 2025), and churn triggered during an acquisition is the fastest way to destroy the deal value you just paid for. Keeping customers unaware requires three things working together, all of which must be in place before a single cutover is scheduled. 1. Cutover Timing and Communication Schedule cutovers during low-traffic windows - evenings or weekends. Notify affected customers in advance with a short, plain-language message. Focus on what will not change: their numbers, their features, their contacts. Leave the technical detail out of it. 2. Feature Parity Validation Before Cutover Validate feature parity before scheduling any cutover. Skipping it is the most common pre-cutover mistake. The result is customers who lose functionality they relied on and call support to report it as an outage. A pre-cutover feature parity checklist should cover: Hunt groups and call queues Auto-attendant menus and time-of-day routing Voicemail-to-email configuration Device registration and softphone settings Any custom dial plan logicm dial plan logic 3. Contingency Planning and Controlled Cutover Every cutover should have a defined response plan before it begins. That means knowing in advance what a failed validation looks like, who makes the call to pause, and how customers are protected while the issue is resolved. Phase-based migration limits customer impact by design. If a cutover does not go as planned, only that group is affected. The rest of the base remains on the source platform, uninterrupted, while the team investigates and reschedules. Start the Consolidation Post-acquisition consolidation is about reducing platform complexity, retiring duplicate infrastructure, and creating a more efficient operating model. Vox Matic combines Otto with senior telecom engineering to help service providers consolidate legacy environments onto NetSapiens. Whether you're integrating a recent acquisition or planning a multi-platform consolidation strategy, Vox Matic helps service providers migrate legacy environments to NetSapiens with less risk, less manual effort, and a faster return on your acquisition. Talk to Vox Matic to discuss your acquisition roadmap. It's that simple! Frequently Asked Questions How long does telecom platform consolidation take after an acquisition? There is no universal post-acquisition telecom consolidation timeline. Timing depends on subscriber volume, configuration complexity, and how many source environments need to be reconciled. Automation can reduce repetitive engineering work and help accelerate execution, but the appropriate timeline depends on the environment. What are the biggest risks in post-acquisition telecom integration? The biggest risks are service disruption to existing customers, data integrity failures during migration, and extended dual-platform costs. According to the POPX State of MSPs 2025 Report, 38% of MSPs experienced client disruption during integration and 49% saw technology costs rise due to slow consolidation. A phased, customer group-based migration with pre-cutover validation addresses all three. Should you migrate all customers at once or in batches? Migrate in batches. A customer group-based approach limits the impact of any cutover issue to a single group rather than your entire base. The POPX State of MSPs 2025 Report found that 38% of MSPs experienced client disruption during integration. Sequence phases deliberately based on your environment, validate each group before moving to the next, and maintain contingency plans throughout the process. What happens to legacy platform licensing during consolidation? Legacy platform licensing continues to run until all customers on that platform have been migrated and the platform is formally decommissioned. This dual-running cost is one of the strongest financial arguments for moving quickly. Industry data shows merged environments carry 30-50% redundant infrastructure spend during the integration window. Every month of delay extends that cost. How do you migrate from Metaswitch or BroadWorks to a modern UCaaS platform? Migrating from Metaswitch or BroadWorks requires extracting customer configuration data from the legacy platform, transforming it to match the target platform's schema, provisioning accounts and devices in the target environment, validating feature parity, and executing a controlled cutover. Otto automates significant portions of data extraction, transformation, provisioning, and validation, while senior engineers support planning, exceptions, testing, and cutover decisions, reducing manual engineering effort per customer and ensuring consistency across the entire migration.
- Telecom Migration Capacity Planning
Most telecom migration challenges begin long before the first subscriber is moved. Capacity planning—not the migration platform itself, is often what determines whether a program stays on schedule or falls behind. Not because of the platform. Not because of the team. Because nobody sized the program for the actual subscriber base. Waves get too large, exception work stacks up, and by mid-program the team is fighting fires instead of moving subscribers. The timeline that looked reasonable on paper is gone. The fix is a capacity plan built before the contract is signed—one that ties automation coverage to wave size, staffing, and a timeline that actually holds. Summary Wave size should be set by automation coverage, not by guesswork. A realistic plan separates standard subscribers from complex ones early. Exception handling and escalation design must be staffed before the first cutover. For providers moving off legacy platforms, planning before the contract is signed saves time, cost, and rework. Three questions need answers before the first subscriber moves: How many subscribers can move per wave without quality slipping? What does that require in staffing and automation? Where are the data and exception risks hiding? Providers who work through these early finish on schedule. Teams that skip this planning often encounter avoidable bottlenecks several waves into the program. Automation Is the Variable That Changes Everything A migration wave is a group of subscribers moved together in a single cutover window. Provisioning, validation, number porting, and configuration transfer all happen within it. Wave size depends on one variable more than any other: how much of the repeatable work your platform handles automatically. Manual migration caps wave size by engineering bandwidth. Automation raises that ceiling by reducing the engineering effort required for repeatable work. Automation Coverage Subscribers Per Wave Under 50% 20 to 40 50 to 80% 50 to 150 80%+ 200+ with a lean team Make the platform decision and the capacity plan together, since each influences the other. Automation coverage sets wave size. Wave size drives staffing and cost. Capacity Planning Timelines by Subscriber Volume Subscriber count is a starting point. The following examples illustrate potential planning ranges, though actual timelines depend on automation levels, subscriber complexity, data quality, and available resources. 200 Subscribers: 8 to 12 Weeks The risk at this scale is not volume. It is data quality and configuration variability. A two-week discovery phase and a pilot wave of 10 to 20 subscribers will surface most issues before they reach the full base. Teams that skip the pilot phase often encounter issues later in the program that could have been identified earlier. 2,000 Subscribers: 20 to 26 Weeks Complexity segmentation becomes critical here. Treating all subscribers identically creates bottlenecks. Separate standard subscribers from complex ones early and resource each tier differently. Program management becomes a distinct function at this scale—not a shared responsibility. 10,000 Subscribers: 40 to 52 Weeks This is a 12 month initiative requiring executive sponsorship and formal governance. A 2% exception rate is 200 subscribers requiring manual intervention. Exception handling is not an edge case. It is a parallel workstream that must be staffed independently from the main wave team. Four Factors That Shape Migration Capacity and Timelines Subscriber count is not the primary driver of program duration. These four variables are: Data quality. Legacy platforms collect years of inconsistencies. A data audit before planning is not optional—what it surfaces often reshapes the timeline before a single wave is sized. Complexity distribution. A base that is 80% standard subscribers moves very differently from one that is 40% complex. Segment early and resource each tier accordingly. Automation coverage. The most controllable variable in the plan, and the one most providers underinvest in. Higher automation means larger waves, a shorter program, and lower cost per migrated subscriber. Otto, Vox Matic's proprietary migration framework, is built to raise that coverage rate across every wave. Escalation design. Decide who resolves exceptions, what triggers a rollback, and who can authorize a cutover extension before the first production wave. Decisions made under pressure rarely go well. A clear cutover protocol is the difference between a managed delay and a subscriber-impacting failure. Organizations with successful migration programs typically define these variables before execution begins The Mistakes That Turn a Good Program Into a Difficult One Programs that go over budget and over schedule usually share one cause: capacity planning happened after the contract was signed. Three mistakes come up repeatedly: Skipping the pilot wave. A 10 to 20 subscriber pilot is not a delay. It is insurance against finding a systemic data issue on wave six. Treating complexity as uniform. A base with mixed tiers needs tiered resourcing. One-size-fits-all wave design breaks down fast. Underestimating exception volume. At scale, even a 1% exception rate creates a real manual workload. Plan for it from day one. While timelines and resource requirements vary by subscriber volume, the core planning principles remain the same. Capacity Planning Starts Before the Migration Begins Capacity planning is not a box to check. It is the work. Get it right and the program runs on schedule, on budget, without disrupting the subscribers you are trying to retain. Get it wrong and you spend the back half recovering. Start the conversation before vendor selection, not after. If you are moving from Metaswitch or BroadWorks, the migration planning considerations are worth reading before the first wave is sized. When you are ready to map your subscriber base to a program plan, talk to our migration team. It’s that simple!
- How to Migrate Telecom Customers to a New Platform Without Them Noticing
Service providers can migrate large customer bases from legacy platforms including Metaswitch, BroadWorks, and BroadSoft into NetSapiens while minimizing disruption to the end customer. The platform changes. The experience does not. Providers can execute the technical cutover correctly and still create churn risk if the customer experience is disrupted. The core insight: A technically successful migration can still create problems if customers experience disruption. The goal is not simply a clean cutover. It is a transition customers barely notice. The pressure to migrate is real. So is the risk of getting it wrong. Key Takeaways Customer-facing disruption can increase support demand and churn risk. Big-bang cutovers are high-risk. Staged, batched migrations dramatically reduce subscriber impact. Automation reduces repetitive manual work and improves consistency. Pre-migration validation helps identify issues before cutover. Fuse.Cloud migrated to NetSapiens with Vox Matic and their COO reported: "Our customers barely noticed the transition." Automation is what separates a repeatable migration process from a one-time engineering effort. Why Do Customers Notice a Migration in the First Place? Most migrations are planned as engineering projects. The subscriber experience is treated as a side concern, something to address if problems come up. That's exactly backwards. Customers may notice a migration because of issues such as: Credential resets: being forced to re-enter a password or re-authenticate an app App reinstalls: receiving an IT email asking them to download a new softphone Feature gaps: a call queue or voicemail behavior that worked differently on the old platform Degraded call quality: even a day of choppy audio during transition Lost call history or voicemail: data that wasn't carried over cleanly Any one of these is enough to prompt a customer to ask: "Why is this happening? Should I be looking at other options?" The migration isn't the risk. The visibility of the migration is. The Big-Bang Problem A "big-bang" cutover moves all subscribers at once on a set date. It's simpler to plan and feels cleaner on paper. The problem is it concentrates all the risk into a single window. If something goes wrong (a misconfigured call route, a failed number port, a device that doesn't register), every customer is affected simultaneously. Staged migrations solve this by moving subscribers in controlled batches. Issues surface in a small group first, get corrected, and the next batch proceeds with a cleaner configuration. By the time the bulk of subscribers migrate, the process is refined and migration risk is significantly reduced. What Does a Customer-Invisible Migration Actually Look Like? Each stage has a specific job to do. Phase 1: Automated Discovery Before Anything Moves Before a single subscriber is touched, the source environment needs to be fully understood. At Vox Matic, this is the first step in every engagement. Otto is Vox Matic’s proprietary automated telecom migration framework. Our approach is automation first, expert engineering where required. Automated data extraction captures subscriber records, service configurations, inventories, and migration-relevant platform data from the source environment at scale, normalizing that data and mapping it to the NetSapiens configuration model before provisioning begins. Learn more about Otto and the Vox Matic approach. Phase 2: Parallel Platform Provisioning The new platform is built and validated while the old one keeps running. Customers can remain on the legacy environment while the target environment is prepared and validated, helping minimize disruption before cutover. Meanwhile, the target environment is configured, tested, and verified against the discovered baseline. This parallel approach is what makes staged cutover possible. There is no artificial deadline forcing an early cutover. The migration proceeds when the environment is validated, not when a calendar date arrives. Phase 3: Controlled, Batched Cutover Subscribers move in controlled groups based on the provider's environment, migration plan, complexity, and cutover requirements. Each batch is monitored closely. If a configuration issue surfaces, it is resolved before the migration advances. Each migration phase should include a defined contingency approach based on the provider's environment and cutover requirements. Phase 4: Post-Migration Validation After each batch, verify: Check What to validate Call quality No reported degradation in audio quality from migrated accounts Device registration Endpoint types tested and confirmed registering to the target platform Feature parity Call queues, voicemail, hunt groups, and auto-attendants behaving as configured Routing behavior DIDs and call flows validated against the source configuration Support ticket volume Monitor inbound issues from migrated accounts for unexpected patterns Where Does Automation Change the Equation? At scale, manual migration requires engineers to recreate and validate large numbers of subscriber records, devices, features, and configurations. The volume is not the problem. The variability is. Automation changes this in three specific ways: 1. Improved consistency at scale. Subscriber accounts are provisioned using the same transformation logic. This reduces variability from engineer to engineer, minimizes missed fields, and helps prevent configuration errors that would otherwise surface during cutover.fix the links here. Not another Fuse quote but more generic 2. Speed that enables staging. Automation compresses repetitive migration work, making staged execution more practical at larger volumes. The slower manual provisioning is, the more pressure there is to consolidate batches, which increases risk. Automation removes that pressure and keeps the subscriber experience intact. 3. Pre-cutover conflict detection. Automated tools compare the source configuration against the target environment and flag mismatches before anyone moves. This helps identify issues that could cause disruption during cutover, so they are resolved during validation rather than after subscribers are affected. Together, these change what is realistically achievable. Migrations that would take well over a year of manual engineering can be compressed into months, not by moving faster through the same steps, but by removing the repetitive work that made the timeline long in the first place. The engineering effort shifts from data entry to exception handling and validation, which is where experienced telecom engineers actually add value. What Should You Tell Your Customers During a Migration? Most operators underinvest in it. The technical plan gets detailed attention; the customer communication plan gets a template email sent the night before. The goal of customer communication during a migration is to set clear expectations, reinforce continuity, and give customers a direct contact if anything feels different. A practical communication framework: Pre-migration notice (2-4 weeks out): Brief, plain-language message that a platform upgrade is coming. Focus on continuity, what is staying the same, and note any action required from the customer, if applicable. Cutover confirmation (day of or day before): Short note confirming the scheduled window, the expected timing, and a support contact customers can reach if they notice anything unexpected. Post-migration confirmation: A brief note that the upgrade is complete. Invite feedback and highlight any new capabilities available on the new platform. What to avoid: Sending communications that make the migration sound more complex or uncertain than it is. If customers are required to take action, such as downloading an app, resetting credentials, or reconfiguring a device, make sure that is communicated clearly in advance, with straightforward instructions and a support contact. A well-executed migration is designed to minimize the actions required from subscribers. When that goal is met, communication confirms a smooth experience rather than managing a disruption. The Migration Checklist: What to Verify Before Any Subscriber Moves Run through this before your first cutover batch. These are the items most likely to cause a visible disruption if missed. Routing behavior validated: DIDs and call flows have been tested and confirmed routing correctly on the target platform Device profiles confirmed: Endpoint types (desk phones, softphones, ATAs) have been tested and confirmed registering to the target platform Call flows validated: Hunt groups, auto-attendants, call queues, and IVR logic have been validated against the source configuration Voicemail functionality confirmed: Voicemail routing, greetings, and access have been tested and are functioning as expected Required features active: Platform features required by the customer (call recording, analytics, conferencing) have been tested and confirmed functioning Customer configurations reviewed: Complex or custom account configurations have been validated in the target environment prior to cutover Cutover contingency defined: A contingency approach has been documented and tested based on the provider's environment and cutover requirements Support team briefed: Your helpdesk knows the migration is happening, what to expect, and how to escalate quickly if needed Monitoring in place: Visibility into call quality, device registration, and provisioning status is confirmed for the cutover window Every environment has its own edge cases, but these are the items that generate the most subscriber-visible failures when missed. Frequently Asked Questions How long does a telecom customer migration typically take? Timeline depends on the size of the subscriber base and the complexity of the source environment. Vox Matic's engagement with Fuse.Cloud reduced their expected timeline from approximately 18 months to 6 months using the Otto automation framework. What is the biggest risk to the subscriber experience during a migration? Customer-facing disruption can result from configuration differences, feature gaps, device behavior, routing issues, or degraded service during cutover. Pre-migration validation and controlled, staged execution help identify issues earlier and reduce the likelihood of customer impact. Can we migrate without any downtime for customers? Vox Matic designs migrations to minimize customer disruption and avoid noticeable downtime wherever possible. Automation, validation, testing, and controlled cutover help reduce migration risk and preserve service continuity. Exact customer impact depends on the source environment, target configuration, and cutover requirements. How do we handle customers who have complex call flows or custom configurations? Automated discovery captures configuration data from the source platform, including routing logic, multi-site setups, and custom feature configurations. This data is used to inform target platform provisioning and validate configurations before cutover. What happens if something goes wrong after a batch moves? A well-designed migration includes a defined contingency approach for each phase, based on the provider's environment and cutover requirements. Issues that surface after a batch moves are corrected before the migration continues, which is one of the core reasons staged migration reduces overall risk compared to a big-bang cutover. Is customer communication required during a migration? Requirements vary by provider and environment. A brief pre-migration notice and post-migration confirmation are good customer service. They set expectations, demonstrate transparency, and give customers a contact point if they notice anything unexpected. A well-executed migration is designed to minimize the actions required from subscribers. When that goal is met, communication confirms a smooth experience rather than managing a disruption. The Bottom Line The cutover date is not the ultimate measure of success. The customer experience is. A migration that finishes on schedule but creates confusion, support tickets, or service disruption falls short of its objective. The most successful migrations are the ones customers barely notice. Otto is Vox Matic’s proprietary automated telecom migration framework. Combined with our approach of automation first, expert engineering where required, it helps service providers transition customers with confidence while preserving continuity throughout the migration journey. The platform changes. The experience does not. Talk to us about what a subscriber-invisible migration looks like for your environment. It’s that simple!
- Metaswitch to NetSapiens Migration: What Service Providers Need to Know
Migrating from Metaswitch to NetSapiens touches everything. The voice architecture, the customer management layer, the way the business scales going forward. Get it right and costs drop. Get it wrong and the engineering team spends months undoing damage while customers feel every bit of it. Speed is not the goal. Accuracy is. The providers who come out of this migration in good shape are the ones who planned for what they did not expect. We have run this migration many times. What follows is a straight account of what it actually takes. Key Takeaways Discovery is non-negotiable. A thorough inventory of subscribers, features, trunks, and routing logic must precede any migration work. Platform architecture differences are significant. Metaswitch and NetSapiens do not share the same data structures, and that translation requires deliberate planning. Customer configurations are the heaviest workload. Auto-attendants, hunt groups, routing rules, and device profiles must each be mapped and validated individually. Engineering capacity is finite. Manual migration at scale consumes engineering resources that should be focused on growth, not remediation. Automation changes the economics. Otto reduces the engineering hours per subscriber migrated, lowers error rates, and compresses timelines significantly. Validation before cutover is essential. Every migrated account must be confirmed as fully functional before live traffic moves. Batched cutover reduces disruption risk. Controlled migration waves protect customers and give the engineering team room to identify and resolve issues early. The Planning Phase Is Where Migrations Are Won or Lost Most migrations run into trouble before a single record moves. Metaswitch environments are heavily customized. Providers spend years building dial plans, routing rules, and trunk configurations. None of that translates to NetSapiens automatically. Discovery has to come first. Skip it and the rest of the project is guesswork. What Discovery Must Cover Start with a full inventory: Subscriber and seat counts across all accounts Feature utilization at the customer and user level - what is actually in use, not just provisioned Trunk configurations - SIP trunks, PSTN connections, and carrier relationships Dial plan complexity - custom routing rules, time-of-day routing, and call forwarding Auto-attendant and IVR configurations that must be rebuilt in NetSapiens Hardware dependencies - physical endpoints and ATA devices that need reconfiguration Billing and provisioning integrations that feed other systems Skipping it is why most migrations run late and cost more than planned. The biggest mistake providers make is treating migration as a provisioning project. It is a customer experience project that happens to involve provisioning. The Real Challenges of a Metaswitch to NetSapiens Migration Metaswitch and NetSapiens are built differently at a fundamental level. That gap is where most of the hard work lives. Platform Architecture Differences Metaswitch and NetSapiens have fundamentally different architectures. Subscriber organization, call routing, and feature logic do not map cleanly between the two platforms. Data has to be rebuilt in NetSapiens format. There is no clean export-import path. Configuration Normalization Customer configs on Metaswitch reflect years of changes. Some are clean. Many are not. Before data moves, it needs to be cleaned up. Find the gaps, fix the conflicts, and check that every setting works in NetSapiens. This takes time. It is also where most mistakes happen. The Volume Problem A provider with thousands of subscribers is not running one migration. They are running thousands of individual config migrations, each one needing to be right. At scale, the numbers compound fast: A 1% error rate on 10,000 subscribers means 100 broken customer configs Fixing each one takes engineering time, customer calls, and causes service disruption Errors stack up across batches and can overwhelm the team fast Most teams do not feel that pressure until they are already inside it. Customer Configurations: The Most Underestimated Workload Platform setup is straightforward. Trunks are manageable. Customer accounts are where the project actually lives or dies. Each account carries its own features, its own routing rules, and its own history. All of it has to be rebuilt in NetSapiens. What Makes Customer Configurations Complex No two customer environments are the same. In a typical Metaswitch deployment, providers will find: Multi-site customers with different configs at each location Hunt group and ring group logic that varies by customer Call recording, voicemail-to-email, and fax tied to specific users Time-of-day and day-of-week routing rules unique to each business Auto-attendant trees with multiple levels and branches Device settings for phones, ATAs, and softclients Each one must be mapped, translated, and confirmed working in NetSapiens before cutover. The Hidden Cost of Manual Configuration Work Manual work costs more than time. It costs accuracy. Different engineers read configs differently, and volume amplifies every mistake. One bad config at 100 subscribers is manageable. At 10,000 it is a support queue, a churn risk, and an unhappy customer. The goal is not just to migrate configurations. The goal is to migrate them right - at scale - without a wave of post-cutover issues that burns through engineering capacity and damages customer trust. Engineering Workload: What This Actually Demands From Your Team Most providers budget for the migration. Few budget for what it actually pulls their team away from. Many assume a small team can handle it. They think it can run alongside normal work. In practice, that leads to burnout. Migrations stall. The Scope of Engineering Involvement A full migration requires engineering across multiple workstreams at once: Workstream Description Data Extraction Pulling subscriber, configuration, and routing data from Metaswitch Data Transformation Normalizing and mapping data to NetSapiens schema Provisioning Building out the NetSapiens environment with migrated configurations Validation Testing each migrated account to confirm accuracy and functionality Cutover Coordination Managing the transition of live traffic for each customer batch Post-Migration Support Resolving issues that surface after cutover Each workstream needs engineers who know telecom. General IT staff will not cut it. The Opportunity Cost Problem Every hour spent rebuilding customer configurations is an hour not spent onboarding customers, launching products, or growing revenue. Migrations compete directly for engineering capacity. The longer they run, the more expensive that tradeoff becomes. How Automation Changes the Migration Equation Manual migration does not scale well. Each subscriber takes time. Each config needs an engineer to touch it. As the subscriber count grows, so does the timeline and the cost. Automation breaks that pattern. It removes the manual effort tied to each subscriber. What Otto Does Differently Otto, Vox Matic's proprietary automated migration framework. Otto was built specifically around real-world telecom migrations. It understands subscriber relationships, feature dependencies, routing logic, and customer structures that would otherwise require engineers to rebuild manually. Automated data extraction - pulls subscriber records, configs, and routing logic from Metaswitch at scale Intelligent data transformation - maps Metaswitch structures to NetSapiens with built-in normalization Automated provisioning - builds out customer accounts and features in NetSapiens without manual entry Validation and testing - confirms each account works before cutover is scheduled What would take an engineering team weeks or months to complete manually, Otto executes in a fraction of the time. The Business Impact of Automation The difference is not just speed. It is economics. Automation cuts engineering hours per subscriber. It reduces errors. It shortens how long Metaswitch stays live, which cuts operating costs directly. Providers have reduced migration timelines dramatically while maintaining accuracy and avoiding the engineering burden associated with manual provisioning. Customers barely notice. That is the point. Validation: The Step That Cannot Be Skipped Provisioning a customer account is not the same as confirming it works - validation sits between migration and cutover. It is the step most teams cut when the timeline tightens - and the one that causes the most post-cutover pain when it gets skipped. What Validation Must Confirm Before cutover, each migrated account must be checked across: Feature parity: every feature from Metaswitch is present and working in NetSapiens Routing accuracy: inbound and outbound calls route exactly as configured Device registration: all endpoints are registered and live Voicemail and messaging: voicemail-to-email, unified messaging, and fax are working Auto-attendant logic: IVR trees route callers correctly at every branch User-level settings: call forwarding, DND, and individual user configs are accurate Failures found after cutover cost far more. A customer who cannot make calls is a churn risk. So is one who cannot receive them. Automated Validation at Scale Manual validation of thousands of accounts is not realistic, so Otto checks every account, flags issues before customers feel them, and confirms each one is ready to cut over. Problems found here cost an hour to fix. Problems found after cutover cost customers. Managing Disruption: Protecting Customers Through the Transition Customer disruption is the risk that tends to get underestimated until it happens. Customers depend on voice, and an outage during cutover creates support calls, damages trust, and accelerates churn. The migration cannot be the reason a provider loses accounts. The Batched Cutover Approach The best way to manage disruption is to migrate in controlled batches, not one mass cutover. Batched cutover allows the engineering team to: Validate each batch before cutover begins Keep the volume of transitions at a level the support team can manage Fix issues in early batches before they affect later ones Keep Metaswitch live as a fallback for customers not yet moved This adds a little time to the overall timeline. But it cuts the risk of a large disruption affecting hundreds of customers at once. Communication as a Migration Tool Customers who know what is coming are more patient. Clear communication before cutover is not optional - simple instructions and a responsive support channel both matter. Providers who skip the communication side consistently see more post-cutover churn. A seamless migration is not just a technical win. It is a customer experience win. Providers who get the technical work right but ignore the customer experience still end up with churn. Providers who handle both the technical work and the customer communication see better results and less churn after cutover. The Vox Matic Approach: Automation-Led, Engineering-Supported Vox Matic was built specifically for this kind of migration. We pair Otto's automation with engineers who have run this migration many times. That means faster, cleaner work with less disruption for your customers. Our process covers every phase: Discovery and inventory of the full Metaswitch environment Data extraction and normalization to prepare configs for migration Automated provisioning of the NetSapiens environment at scale Validation and testing before any customer is cut over Batched cutover execution with engineering support at every step Post-migration verification to confirm every account is working We are a NetSapiens Ecosystem Partner. We know how Metaswitch data maps to NetSapiens, where the hard parts are, and how to get through them fast. The result protects customers. It preserves engineering capacity. It speeds up legacy platform retirement. Migration does not have to take years. Otto handles the volume, the team handles the edge cases, and customers stay on. It's that simple! Frequently Asked Questions What is involved in a Metaswitch to NetSapiens migration? A Metaswitch to NetSapiens migration covers discovery, data extraction, provisioning, validation, and cutover. The hard part is not moving records. It is preserving customer logic and feature behavior. Two very different platforms are involved. A Metaswitch to NetSapiens migration includes discovery, data extraction, provisioning, validation, and cutover. The challenge is not moving records. It is preserving customer functionality while translating configurations between two fundamentally different platforms. Why is discovery so important before migration starts? Discovery is where providers find subscriber counts, feature usage, routing logic, and hardware dependencies. Without it, teams cannot map what is in Metaswitch. They cannot know what needs to be rebuilt in NetSapiens. What makes customer configurations so difficult to migrate? Customer configurations are often highly customized. This is especially true in long-running Metaswitch environments. Auto-attendants, hunt groups, and routing rules all need to be translated. Voicemail settings and device profiles do too. Each one must work the same way in NetSapiens. How does automation reduce migration risk? Automation reduces manual data entry. It normalizes records at scale. It makes validation more consistent. That lowers engineering burden and reduces errors. Teams move faster. Post-cutover issues drop. So do support escalations and churn. How can service providers minimize customer disruption during cutover? Migrate in controlled batches. Validate each group before cutover. Communicate clearly with customers before and after. That keeps the load manageable. It is easier to fix issues before they affect a large portion of the base.
- BroadWorks to NetSapiens Migration: A Practical Guide for Service Providers
A BroadWorks to NetSapiens migration is a proven and achievable modernization project. The destination platform is rarely the challenge. The real complexity lies in extracting, transforming, validating, and rebuilding years of accumulated BroadWorks configuration data without disrupting active customers. Over time, service providers accumulate thousands of subscribers, devices, dial plans, policies, and custom configurations. Much of this data contains inconsistencies, undocumented changes, and operational drift that can complicate migration efforts. Attempting to rebuild these environments manually is time-consuming, expensive, and prone to error. With the right automation strategy, however, migrations become predictable, repeatable, and scalable. Automated data extraction, transformation, and provisioning dramatically reduce deployment timelines while improving accuracy and consistency across the subscriber base. This guide explains what a BroadWorks to NetSapiens migration actually involves, where providers typically encounter risk, and how an automated migration approach can accelerate deployment while protecting the customer experience throughout the transition. Key Takeaways BroadWorks and NetSapiens use fundamentally different configuration models, making direct data transfer impossible without transformation. The highest-risk phase of any migration is data extraction, normalization, and validation, where years of configuration drift and undocumented changes often surface. Automation can reduce per-subscriber provisioning time from hours to seconds, enabling providers to migrate large customer bases efficiently without increasing operational headcount. A phased migration approach with validation checkpoints minimizes customer impact and provides a controlled rollback path if issues arise. Accelerating migration timelines helps providers retire BroadWorks licensing and operational costs sooner, improving margins during the transition. NetSapiens creates opportunities for new service offerings, operational efficiencies, and revenue growth beyond what is practical on legacy BroadWorks environments. Why Are Service Providers Moving from BroadWorks to NetSapiens? The shift is being driven as much by economics and operational efficiency as by technology. BroadWorks remains a mature and capable communications platform, but its architecture, licensing model, and operational requirements were developed in a different era of service delivery. As customer expectations evolve and competition increases, service providers are under pressure to deliver new features faster, automate operations, and scale efficiently without significantly increasing costs. At the same time, many providers are evaluating their long-term platform strategy. As Cisco has moved toward a cloud-first portfolio, service providers running BroadWorks are increasingly looking to define their migration roadmap on their own timeline rather than waiting for future business, technology, or support decisions to dictate the pace of change. For many providers, that has triggered a re-evaluation of the platforms that support their business. The goal is not simply to replace BroadWorks. It is to reduce operational complexity, improve agility, and create a foundation for long-term growth. NetSapiens, now part of the Crexendo ecosystem, was designed specifically for service providers operating multi-tenant communications environments at scale. Key advantages include: Multi-tenant architecture designed for service provider resale and white-label deployments Lower total cost of ownership through reduced infrastructure and operational overhead Modern APIs that support automation, integration, and streamlined service delivery Faster deployment of new features and services across the customer base Opportunities to create differentiated service offerings and new revenue streams The business case for migration is often straightforward. The challenge is execution. Most BroadWorks environments contain years of accumulated customer-specific configurations, custom dial plans, provisioning exceptions, device templates, and undocumented changes. These dependencies are frequently business-critical, making manual migration both time-consuming and risky. As a result, the primary obstacle to migration is rarely platform selection. It is the ability to accurately extract, transform, validate, and recreate BroadWorks data within NetSapiens while maintaining service continuity for existing customers. What Does a BroadWorks to NetSapiens Migration Actually Involve? At its core, a BroadWorks to NetSapiens migration is a data transformation and re-provisioning exercise. Although both platforms deliver similar communications services, they use fundamentally different configuration models. BroadWorks and NetSapiens do not share a common data structure, making a direct migration impossible. Every object, including users, groups, dial plans, call features, devices, and routing rules, must be extracted from BroadWorks, transformed into a NetSapiens-compatible format, validated, and re-created in the target environment. The migration process can be broken down into four key phases: Phase 1: Discovery and Inventory Every successful migration begins with a complete understanding of the existing BroadWorks environment. Subscriber inventories, groups, dial plans, device profiles, trunks, call flows, and custom configurations must all be identified and documented before any migration work begins. This phase is critical because undocumented exceptions are common in mature BroadWorks deployments. Incomplete discovery can allow configuration gaps and special-case customer requirements to surface later in the migration process. Problems that are not identified during discovery often become service-impacting issues during testing or cutover. Phase 2: Data Extraction and Normalization Once the environment has been inventoried, BroadWorks data must be extracted and transformed into a format that NetSapiens can consume. This is often the most complex phase of the migration because BroadWorks and NetSapiens use different configuration models and object hierarchies. Key transformation tasks include: BroadWorks Object NetSapiens Equivalent Common Challenge Enterprise / Group Domain / Reseller Hierarchy mapping Auto Attendant IVR / Call Queue Feature parity gaps Hunt Group Ring Group Routing logic differences Device Profile Device Template Firmware and provisioning format Trunk Group SIP Trunk Authentication and routing alignment Every mapping requires careful validation. What works in BroadWorks does not automatically behave the same way in NetSapiens, making normalization and testing essential to a successful migration. Phase 3: Phased Provisioning and Testing Most service providers adopt a phased approach rather than migrating the entire customer base at once. Customers are provisioned and validated in controlled batches, allowing teams to verify configurations before moving additional subscribers to the new platform. Each migration group is tested for call routing, feature behavior, device registration, voicemail functionality, and overall service continuity. This approach minimizes risk and limits the impact of any issues that may be discovered during deployment. The goal is to keep the blast radius small. If a problem is identified in an early migration batch, it can be corrected before additional customers are affected. Phase 4: Cutover and Post-Migration Validation Cutover is the point at which live customer traffic moves from BroadWorks to NetSapiens. By this stage, subscriber configurations, devices, routing rules, and service features should already be provisioned and validated within the target environment. When preparation has been completed correctly, cutover becomes a controlled routing change rather than a complex deployment event. This significantly reduces migration risk and minimizes customer disruption. Following cutover, providers perform post-migration validation to confirm that call flows, voicemail, device registration, emergency services, and other critical features are operating as expected. Any issues are addressed before the BroadWorks environment is decommissioned, ensuring a smooth and reliable transition to the new platform. Why Do Manual BroadWorks Migrations Fail? Manual migrations fail for predictable reasons. Understanding these challenges is the first step toward avoiding them. Configuration Drift Is Hidden Until It Causes Problems Most BroadWorks environments have been evolving for years. Along the way, engineers create custom dial plans, feature overrides, routing exceptions, and one-off customer configurations to solve immediate business needs. Many of these changes are never fully documented, and the people who implemented them may no longer be with the organization. As a result, manual audits often miss critical dependencies that only become apparent during testing or after cutover. Manual Re-Provisioning Does Not Scale Every user, device, feature, and routing rule must ultimately be recreated in NetSapiens. Performing that work manually may be manageable for a small deployment, but it quickly becomes impractical as subscriber counts grow. A provider with thousands of subscribers can spend months manually rebuilding and validating configurations. During that period, engineering resources are stretched thin and operational costs continue to accumulate while both platforms remain active. Manual Testing Leaves Gaps Testing is often one of the first areas affected by project timelines and resource constraints. When migrations are performed manually, teams frequently rely on spot checks rather than comprehensive validation. As a result, edge cases involving call routing, feature interactions, device provisioning, or customer-specific configurations can go undetected until users begin reporting issues after cutover. Delays Increase Cost and Risk Lengthy migration projects extend the period during which providers must support both BroadWorks and NetSapiens environments simultaneously. Every month of overlap increases licensing costs, operational overhead, engineering workload, and project risk. It also delays access to the efficiency gains, new services, and revenue opportunities available on the NetSapiens platform. Real-World Impact: In one Vox Matic migration example, a task that took about 60 minutes manually was completed in about 15 seconds with Otto, Vox Matic’s proprietary automated telecom migration framework, followed by a brief verification step. The result was a dramatic reduction in provisioning time, improved consistency, and faster migration execution at scale. The Bottom Line Manual migrations are not inherently impossible. They are simply difficult to execute consistently at scale. The larger the subscriber base, the greater the risk of errors, delays, and escalating costs. This is why successful BroadWorks-to-NetSapiens migrations increasingly rely on automation to accelerate provisioning, improve accuracy, and reduce operational risk. How Does Automated Migration Change the Equation? Automation helps reduce the risk, effort, and time required to migrate from BroadWorks to NetSapiens. Automated discovery captures subscriber, device, and service data at scale, helping identify inconsistencies before migration begins. Automated transformation then applies consistent mapping rules to convert BroadWorks configurations into NetSapiens-ready provisioning data. Vox Matic’s proprietary migration framework, Otto, automates key migration tasks, including: • Object mapping and transformation • Configuration normalization • Numbering plan alignment • Device onboarding and redirection • License assignment and feature activation • Automated validation and deployment preparation The Bottom Line By eliminating manual re-entry, automation enables service providers to migrate thousands of subscribers with greater consistency and significantly less engineering effort. Most importantly, validation becomes part of the process. Configurations, devices, and call flows can be verified before cutover, helping identify issues before they impact customers. What Happens to Customers During the Migration? This is often the first question service providers ask, and the answer is simple: the goal is a seamless transition. Customers are migrated in controlled batches, not all at once. Configurations, devices, and call flows are validated before cutover, helping identify issues before they affect users. Where adjustments are needed, they are made before production traffic moves. While every environment is different, the objective remains the same: move customers to NetSapiens with minimal disruption and a consistent user experience. As one Vox Matic customer put it: “Our customers barely noticed the transition. Manual vs. Automated Migration Timelines The impact of automation becomes most apparent during provisioning. While discovery, planning, and validation remain essential, automation dramatically reduces the time required to migrate customers at scale. Migration Approach Per-Customer Provisioning 1,000-Subscriber Timeline Manual 45-90 minutes per customer Months to over a year, depending on environment size Automated (Vox Matic / Otto) Seconds per customer Weeks, depending on discovery and validation scope Manual migrations are not just slower per customer. They require sustained engineering effort across a much longer project timeline, often while teams continue supporting the live BroadWorks environment. Automation dramatically compresses the provisioning phase, while still allowing time for proper discovery, planning, and validation. Once the environment has been inventoried and transformation rules have been established, provisioning and testing can proceed at a pace manual processes cannot match. The fastest migrations are not the ones that skip steps. They are the ones that automate the right steps. Time invested in discovery and planning pays dividends throughout every subsequent phase of the migration. What Should You Look for in a Migration Partner? Choosing the right migration partner can have a significant impact on project timelines, risk, and customer experience. Look for a partner that offers: BroadWorks expertise to handle platform-specific configurations, feature mappings, and edge cases. Automation at scale, not just scripts that support a largely manual process. NetSapiens ecosystem experience and direct familiarity with platform best practices. A phased methodology with validation built into every stage of the migration. Post-migration support including training, documentation, and ongoing engineering assistance. Vox Matic is a NetSapiens Ecosystem Partner with an automation-first migration framework purpose-built for service providers transitioning from legacy platforms, including BroadWorks and Metaswitch. By combining automation with platform expertise, migrations follow a repeatable, validated process that reduces risk and accelerates deployment. Frequently Asked Questions Can I migrate only some customers from BroadWorks while keeping others? Yes. The phased migration approach allows migration in phases. BroadWorks remains active for customers who have not yet been migrated, while selected customer groups are moved to NetSapiens in a controlled manner. What is the customer experience during a BroadWorks to NetSapiens migration? The goal is to minimize disruption. Configurations, devices, and call flows are validated before cutover, helping ensure a smooth transition. While every environment is different, well-planned migrations often require little or no noticeable change for end users. What happens to BroadWorks features that NetSapiens does not support in the same way? Feature differences are identified during discovery, not at cutover. Where direct equivalents exist, configurations are mapped automatically. Where they do not, alternative configurations or workflows are documented and reviewed as part of the migration plan. How is data integrity protected during the migration? Automation reduces the manual data entry errors that commonly occur during large migrations. Validation checks throughout the process help confirm that configurations are migrated correctly before customers are moved to the new platform. Does Vox Matic support migrations from other legacy platforms as well? Yes. The Vox Matic migration framework includes BroadWorks, and other platforms including Metaswitch, BroadSoft, and mixed multi-platform environments. What does the engagement look like after the migration is complete? Every migration begins with understanding the details. Subscriber volume, active features, device inventory, dial plans, and custom configurations all influence the migration approach, timeline, and level of effort required. A structured assessment helps identify potential challenges early and provides a clear roadmap for a successful transition from BroadWorks to NetSapiens. Request a consultation to discuss your requirements, evaluate your migration options, and identify the most effective path forward. It's that simple!












