Search Results
Search this site
50 results found with an empty search
- What Is Otto? How Vox Matic Automates Telecom Migration
Telecom migration is one of the most complex operational projects a service provider can undertake. Moving customers from Metaswitch or BroadWorks to NetSapiens means pulling data, mapping settings, building out users, and checking everything before go-live. All while keeping the customers who depend on those services completely unaware. For most of the industry's history, that work was done by hand. Engineers went through each account one at a time. Slow, costly, and hard to scale. Vox Matic was built around a different idea: the most repetitive parts of a migration can be automated. Otto is the framework that makes it happen. Otto, Defined Otto is Vox Matic's proprietary automated telecom migration framework and the technology that powers our automation-first approach to moving service providers from legacy voice platforms to NetSapiens. The simplest way to think about it: Traditional migration: Engineers manually rebuild customer settings one account at a time. With Otto: Significant portions of that repetitive work are automated, making the process faster, more consistent, and easier to scale. Otto does not replace telecom engineers. It changes what they spend their time on. Instead of repeating the same steps across hundreds of accounts, engineers focus on edge cases, testing, and the decisions that need human judgment. Key Takeaways Otto is Vox Matic's proprietary automated migration framework, purpose-built for telecom platform migrations. Otto automates significant portions of the migration workflow, including discovery, configuration normalization, data transformation, provisioning, and validation. The Vox Matic model is automation first, expert engineering where required. Otto handles the repeatable work; experienced engineers handle complex exceptions, testing, and architecture. Otto supports migrations from legacy platforms including Metaswitch and BroadWorks into NetSapiens. Automation through Otto makes migrations faster, more consistent, and more scalable, enabling providers to run migration programs at greater scale without adding more engineers. Faster migrations mean earlier legacy platform retirement, lower operating costs, and a faster path to ROI on the new platform. The goal throughout is minimal customer disruption. Customers should experience no noticeable change in how their services work after cutover. The Problem with Traditional Telecom Migration Platforms like Metaswitch and BroadWorks have powered service providers for decades, and they work. But they are aging, and the industry has moved on. Modern platforms like NetSapiens now supports over 8 million users globally, up more than 370% since 2021. They offer more flexibility, better economics, and a cleaner path forward. The hard part is getting from one to the other. Manual Migration vs. Automated Migration Traditional Manual Migration Otto-Automated Migration Engineering effort High: every account rebuilt by hand Reduced: repetitive steps automated Consistency Variable: depends on individual engineers Standardized: same logic applied every time Scale Difficult: headcount grows with volume Practical: automation enables higher migration volume without proportional staffing increases Error risk Higher: fatigue and oversight compound at scale Lower: automated validation catches issues early Migration speed Slow: weeks or months per cohort Faster: automation compresses timelines Legacy retirement Delayed: long migrations mean longer parallel costs Earlier: faster migrations retire legacy sooner Customer disruption Higher risk: more manual steps, more chances for error Minimized: controlled cutover with automated testing What Manual Migration Actually Looks Like Traditional migration is a heavy engineering project. For every customer, engineers must pull subscriber records (users), phone numbers, device configurations, and feature settings, then reformat and map that data to the new platform, provision subscribers, hunt groups, auto attendants, and call routing rules, and test each setup before cutover. Multiply that across hundreds or thousands of customers, each one different, and the scope adds up quickly. High-volume migrations can take months, sometimes years, and the risk of errors grows with every manual step. Many providers end up stuck on legacy platforms longer than planned, still paying to run systems they have already decided to leave. Why Variability Makes It Harder No two customer setups are the same. A customer on an old platform for ten years may have hundreds of custom settings: call rules, phone layouts, recorded greetings, years of routing logic. Manual work struggles with that kind of variety. The more complex the setup, the higher the risk of mistakes. That is the problem Otto was built to solve. How Otto Changes the Migration Process Otto takes a different approach. Instead of having engineers rebuild every account by hand, Otto automates significant portions of the migration work. The process gets faster, more consistent, and easier to repeat at scale. A Vox Matic migration can cover a wide range of steps: discovery, data extraction, environment analysis, configuration mapping, data transformation, provisioning, validation, testing, cutover, verification, and post-migration support. Otto automates the parts of that workflow that consume the most engineering time. Automation First. Engineering Where It Matters. This is the core of Vox Matic's model. Otto handles the work that repeats; engineers handle the rest. That means edge cases, design calls, test oversight, and anything else that needs human judgment. The result is a faster, more reliable process without cutting corners on the work that matters. The model is not automation instead of engineering. It is automation that makes engineering more effective. Migration on the Provider's Terms Otto also supports a more controlled migration model. Rather than forcing a one-size-fits-all approach, Vox Matic aligns the migration to the provider's setup and timeline. Providers can migrate in phases or execute a full-scale cutover based on their operational requirements. The migration process is aligned to the provider’s timeline, not the other way around. Consistency at Scale One of the most important benefits of automation is consistency. Manual work varies by person. Engineers have good days and bad days, and fatigue creates real risk when the same steps repeat hundreds of times. Otto applies the same logic to every account, every time. That consistency reduces errors and means quality does not degrade as volume increases. What Gets Automated Within the Vox Matic migration process, Otto's automation capabilities are applied across several of the most labor-intensive activities, including: Automated discovery: Capturing users, features, call flows, routing logic, and settings from the source platform, whether Metaswitch, BroadWorks, or another legacy system. Data mapping and transformation: Converting source platform data into the right format for the NetSapiens environment. Intelligent customization: Tailoring the target platform to each provider's business rules, device types, and user profiles, automatically and consistently rather than by hand. Building out the new environment: Setting up users, phone numbers, device settings, call routing rules, voicemail, auto attendants, hunt groups, and other services. Automated testing: Running structured pre-launch checks to confirm everything is working. Anything out of spec is identified and addressed before go-live. The goal throughout is that when a customer's team comes in the next morning, their phones and services work exactly as they did before. The platform underneath has changed. The experience has not. What This Means for Migration Economics The operational benefits of automation are real. But the bigger story is what they mean for the business case. Manual migrations are costly. They require a lot of engineering hours, long timelines, and careful coordination at every step. For providers with thousands of customers, moving them by hand can make the whole project feel out of reach. That is part of why so many providers have waited longer than they should. Otto changes that. Less Manual Work Means Lower Costs Per Migration When automation handles the repetitive steps, the engineering effort per migration shifts. Engineers stop doing the same tasks over and over. Instead, they watch the process, handle edge cases, and step in where it matters. That means lower costs per move. More migrations can run at once without adding staff. Faster Migrations Mean Earlier Legacy Retirement Speed matters for a simple reason. The longer a migration takes, the longer a provider pays to run a legacy platform alongside its replacement. Every extra week is an unnecessary cost. Faster migrations mean providers can retire legacy platforms sooner, start billing on the new NetSapiens environment earlier, and compress the time spent running two systems at once. Less manual work. Faster migrations. Earlier legacy retirement. Lower operating costs. Scalability Without Linear Cost Growth Manual migration scales with headcount. Twice the customers means roughly twice the engineers. Automation breaks that link. With Otto, Vox Matic can run migrations at a scale that would not be practical by hand. Providers with extensive user bases, or those merging many platforms into one NetSapiens setup, can move far more quickly. The business impact is reflected in customer results. Fuse. Cloud reported reducing its migration timeline from 18 months to 6 months while maintaining a largely seamless customer experience. Their COO noted they hit full ROI in under 5 months. Speed and continuity together. That is what the automated approach delivers. For a deeper look at the financial case, the Vox Matic blog covers why the cost of delaying migration keeps rising and the migration economics argument for moving sooner rather than later. Frequently Asked Questions What is Otto? Otto is Vox Matic's proprietary automated telecom migration framework. It is the core technology behind the company's automation-first approach to moving service providers from old platforms into NetSapiens. Otto automates significant portions of the migration process that have traditionally required repetitive manual engineering effort, making the whole process faster, more consistent, and easier to scale. What legacy platforms does Otto support migration from? Vox Matic's strongest expertise is in migration from Metaswitch and BroadWorks to NetSapiens. Other legacy voice platforms are also supported. Otto is set up for each provider's specific source environment, so it is not tied to a single platform. Does Otto replace telecom engineers? No. Otto cuts the volume of repetitive manual work, but it does not replace engineering expertise. Vox Matic's model is automation first, expert engineering where required. Engineers are still essential for edge cases, design calls, test oversight, and post-migration support. Otto changes what they spend their time on, not whether they are needed. What parts of the migration process does Otto automate? Otto™, Vox Matic's proprietary automated telecom migration framework, automates the most repetitive and data-heavy steps. This includes: Discovery of the source platform configuration Data mapping and transformation Validation checks throughout the workflow Customization of the target NetSapiens environment Building out users and services Pre-launch testing and checks Otto gathers each customer's setup, including call flows, device settings, routing logic and voicemail configurations, and recreates supported items in NetSapiens. Records that do not fit the agreed mapping are assigned to the appropriate owner for review and resolution, and experienced engineers handle exceptions and decisions that need human judgment. What is reviewed before Otto builds the customer in the destination environment? Otto™, Vox Matic's proprietary automated telecom migration framework, first gathers and presents the source configuration for review. It then translates the information into the NetSapiens structure for a second review. The production build begins only after the required review and approval steps are complete. How much disruption do customers experience during migration? The goal is to minimize disruption and protect the customer experience. Otto™, Vox Matic's proprietary automated telecom migration framework, gathers and rebuilds supported customer configurations so the NetSapiens setup follows the source as closely as the two platforms allow. Some customers may still need to restart or reprovision phones, use a different portal or receive updated credentials, depending on the source environment, device types and cutover plan. The platform changes. The experience does not. How does automated migration improve the business case for moving off a legacy platform? Automation can reduce the engineering hours needed per migration and allow migrations to run faster and at greater scale, which may let providers retire legacy platforms sooner and shorten the period of running two systems. License savings may contribute to the business case, but they are rarely the entire justification. Broader value can come from consolidating engineering, service delivery, support and training around one platform; reducing repetitive configuration work and the associated risk of omissions; and integrating acquired customers sooner, so the platform change can be coordinated with their move to a new company name, invoice and portal. Senior engineers can also be redirected to architecture, security, integrations, complex exceptions and service development. Any projected savings or per-line margin improvement should be calculated using the provider's own costs, timelines and operating assumptions. Does Otto support NetSapiens consolidation as well as new migrations? Yes. Otto supports both moves from legacy platforms into NetSapiens and scenarios where a provider is merging multiple platforms or subscriber bases into a single NetSapiens environment. The same automation that makes migration at scale practical applies equally to consolidation projects. Can several team members run migrations at once, in batches or on a schedule? Yes. Otto™, Vox Matic's proprietary automated telecom migration framework, is designed to support concurrent users and migration activity, and migration waves can be prepared and coordinated in batches. Depending on the engagement, and where suitable access and supported integration options are available, API or scheduling options may also be used to create, initiate or coordinate migrations. Practical throughput may depend on source- and destination-platform API capacity, rate limits, system performance and the provider's review process. Automation requirements and approval controls are defined during discovery, and approvals remain with the provider's team. How does Otto connect to our platforms, and who owns the migration data? The connection design is agreed with the provider's engineering and security teams. Access to Otto™, Vox Matic's proprietary automated telecom migration framework, may be restricted to approved static egress addresses. Where inbound access is not appropriate, a locally deployed agent may provide a controlled connection between the provider's network and Otto. The final design should use restricted credentials and be reviewed before production access is granted. The provider and its customers retain ownership of their data. Vox Matic uses the information as required to perform the agreed migration and related services, and access, retention, storage and deletion requirements are documented in the project's security and data-handling terms.
- Telecom Migration in 2027: Five Shifts Service Providers Should Plan For
Five shifts are shaping service provider platform decisions for 2027: legacy platforms managed release by release, the cost of running more than one platform, consolidation onto NetSapiens, the challenge of finishing migrations already underway and automation moving from migration projects into daily operations. None establishes a platform shutdown date, but together they change the operational and financial cost of waiting. BroadWorks and Metaswitch remain supported, so the question for many providers is less whether to move and more what it costs to run them alongside NetSapiens in the meantime. This outlook examines each shift, what it may mean for margins, platform strategy and migration planning, and the readiness questions providers can take into 2027. Figures are as reported through November 2026. For platform-specific detail, see our BroadWorks to NetSapiens migration and Metaswitch to NetSapiens migration pages. Key Takeaways Legacy voice platforms remain supported, but each release cycle creates another decision point on whether to upgrade, maintain or migrate. The duplicate cost of running two platforms is spread across teams, which makes it easy to underestimate. NetSapiens passed 8 million users in August 2026, and Crexendo reported six Metaswitch migration wins in the first nine months of 2026. For many providers already using NetSapiens, the remaining challenge is completing the migration and retiring the legacy environment rather than selecting a destination platform. Automation is moving beyond migration projects into onboarding, provisioning and billing. 1. How Are Legacy Voice Platforms Changing? There is no shutdown date for BroadWorks or Metaswitch. Cisco continues to ship BroadWorks releases, and Alianza, which completed its acquisition of Metaswitch from Microsoft in March 2025, has said it will continue to support Metaswitch’s existing product offerings. What is changing is how these platforms are managed. Cisco’s product bulletin planned BroadWorks Release 27 for general availability in August 2026, signaling the end of maintenance for Release 24 at the end of July 2026. Providers on an older release decide again with each cycle whether to upgrade, stay or move. Legacy network retirement is moving in parallel, though it is a separate decision. In the US, the FCC adopted rules on March 26, 2026 that streamline copper retirement and give carriers blanket authority to grandfather legacy voice services, so those services are no longer offered to new customers. In the UK, Openreach has told providers that its PSTN switch-off deadline of January 31, 2027 will not be moved. Neither development requires a provider to leave BroadWorks or Metaswitch. A provider can modernize its network and keep the same voice platform. Both do point customer expectations in the same direction, toward IP-based services and cloud features. What it means for 2027: treat platform retirement as a planned program with a target date, even if that date is a few years out. Each release cycle is a natural point to revisit it. 2. Why Does Running More Than One Platform Squeeze Margins? Many providers did not set out to run several voice platforms. An acquisition brings a Metaswitch base, a BroadWorks deployment stays live for a few large customers and new business goes onto NetSapiens. Each platform keeps its own support knowledge, provisioning steps, billing feed, device configurations and integrations. The fixed cost of keeping a platform healthy does not fall in step with its customer count. A platform serving a fraction of its former base may still need maintenance, monitoring, specialist knowledge and a working billing integration. These costs sit in different budgets, so they rarely appear as one number. Acquisitions keep this on the agenda. A provider that buys a company on a different platform carries a second environment until those customers move. Timing matters here too. Acquired customers are already adjusting to a new company name, invoice and portal, and moving their platform during that transition can avoid putting them through a second major change later. Our guide to post-acquisition telecom consolidation walks through that scenario. A simple way to size the issue: Cost of the dual-platform period = monthly cost of the legacy platform × months until its last customer moves The monthly figure should include maintenance and support contracts, hosting, specialist staff time, duplicate integrations and training. Shortening the second number reduces the total, which is why migration speed is a financial question as much as a technical one. License savings may contribute to a migration business case, but they are rarely the entire justification. Much of the value sits in the operating model: engineering, support and training organized around one platform, fewer configuration errors from manual rebuilding, acquired customers integrated sooner, and senior engineers redirected from routine rebuilding to architecture, security and integrations. Any projected margin improvement should be calculated separately using the provider’s own costs, timelines and operating assumptions. What it means for 2027: measure what each platform costs per year, not just what it would cost to leave it. 3. Why Are Providers Consolidating onto NetSapiens? Providers consolidating need a destination that is built for service providers and still growing. Crexendo, which owns NetSapiens, announced on August 11, 2026 that the platform supports more than 8 million users worldwide, about one million more than eight months earlier and more than 370% growth since its June 2021 acquisition. It reported more than 250 licensees and 11 new licensees in the first half of 2026. Crexendo’s Q3 2026 earnings call adds detail closer to migration. The company reported 16 new NetSapiens licensees through the third quarter. Two of the five added in Q3 migrated from Metaswitch, and year to date the company had won six Metaswitch migrations and one from Cisco BroadWorks. These are Crexendo platform figures, not Vox Matic projects. For a provider choosing where to consolidate, a larger ecosystem may provide access to more supported devices, integration partners and engineers already familiar with the platform. What it means for 2027: if part of your base already runs on NetSapiens, the platform decision has largely been made. The open question is how and when the remaining customers move. 4. Why Is Finishing the Move Harder Than Choosing the Platform? Many providers place new customers on NetSapiens years before they finish moving the existing customer base. The destination is decided, but the remaining migration work can stall because the final accounts are often the most complex and must compete with ongoing operational priorities: The remaining customers are the complex ones. Standard configurations tend to move first. Accounts with custom call flows, integrations or contractual sensitivities get deferred, so the last stage has fewer customers but more review per customer. Exceptions wait for decisions. Features without a direct equivalent, incomplete records and one-off setups need the provider’s approval on how each is handled. Our guide to migration exception management covers how those decisions are made. The same engineers run operations. Migration work competes with tickets, outages and new customer onboarding, so it tends to slip when the day gets busy. Feature behavior has to be confirmed, not assumed. Settings that need a different treatment in NetSapiens are flagged for engineering review, and changes in user experience are identified so customers can be guided through them. Customers have steps of their own. Depending on the provider’s process, end customers may need to confirm a cutover window, restart or reprovision phones, receive new portal credentials and check key call flows after activation. Automation can reduce rebuilding effort, but it does not remove the need for customer communication and coordination. The amount of repetitive work is what makes manual migration slow at scale. Vox Matic’s white paper model illustrates it: at about five lines per engineer-hour of manual rebuilding, 15,000 lines represent about 3,000 engineering hours. Scheduled alongside operations, testing and customer coordination, the model’s manual timeline runs to about 23 months, against about eight months in the automated scenario. It is a model, not a benchmark, and actual timelines depend on team capacity, data quality, feature complexity and agreed scope. In one real example, Fuse.Cloud moved its business customers from BroadWorks into a unified NetSapiens environment. A manual migration was estimated to take approximately 18 months; working with Vox Matic, the migration was completed in approximately six months. Results reflect that specific engagement and will vary by environment and project scope. Read the case study. Otto™, Vox Matic’s proprietary automated telecom migration framework, automates repeatable data extraction, transformation and provisioning work. Automated validation checks applied throughout the workflow help identify discrepancies, so records that do not fit the agreed mapping can be flagged for review before cutover. For a stalled migration, that can mean engineering time goes to the deferred decisions and complex accounts rather than to re-entering standard ones, and service-delivery teams have more time for the scheduling, communication and support that customers notice. Our comparison of manual vs automated telecom migration covers the trade-offs in more detail. What it means for 2027: list the customers still outside NetSapiens, group them by complexity and decide which exceptions need provider decisions before any migration stage is scheduled. 5. How Is Automation Moving Into Daily Operations? Once customers are on one platform, the recurring work around them becomes the next opportunity. Onboarding, provisioning, billing updates and carrier orders continue long after a migration ends. In many providers, a new order still passes through several hands. A deal closes in the CRM, someone re-enters it into the ticketing system, an engineer builds the account on the voice platform, another team places the carrier order and finance sets up billing. Each handoff adds time and a chance for systems to disagree. Connecting those steps may help shorten time to revenue, reduce billing mismatches and allow the same team to support more customers. Forge™, Vox Matic’s custom automation and workflow development service, is designed to automate or coordinate ongoing operational workflows while approvals, exceptions and judgment-based decisions remain with the provider’s team. Where suitable access and supported integration options are available, Forge can coordinate information and supported actions across systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. What can be automated depends on the provider’s systems, approved business rules and agreed project scope. What it means for 2027: map one customer order from signature to first invoice, identify each manual handoff, and start with the step that repeatedly causes delays, duplicate data entry or rework. A 2027 Readiness Check Use these questions to find where to look first. The aim is two numbers your finance and engineering teams can agree on: the annual cost of each legacy platform and the estimated months until it can be retired. Shift Question for your team First step in Q1 2027 Release-managed legacy platforms Do we have a target retirement date for each legacy platform? Set a date and work back from it Multi-platform margins What does each platform cost per year in people, licenses and tools? Build a cost-per-platform view with finance Consolidation onto NetSapiens Which customers are still outside NetSapiens, and why? Group them by size, complexity and contract dates Finishing the move How much remaining migration work is manual rebuilding, and which exceptions await a decision? Inventory users, devices and call flows, and list open exceptions with an owner Automation in daily operations How many manual handoffs sit between a signed order and a billed service? Map one order from signature through activation and first invoice Planning Your 2027 Migration Roadmap? A useful question entering 2027 is not only which platform to run. It is how long the remaining legacy customers will take to move, what the dual-platform period costs in the meantime, and how much repeatable migration and operational work can be automated or coordinated. Answering those questions gives providers a firmer basis for budgeting, engineering allocation, migration sequencing and legacy-platform retirement. As a NetSapiens Ecosystem Partner, Vox Matic uses automation and experienced telecom engineering to help providers move remaining customers from BroadWorks, Metaswitch and mixed legacy environments into NetSapiens. A Migration Assessment can help identify: Which customers remain on legacy platforms and what makes them complex Where automation can reduce manual work Which exceptions and dependencies need decisions before scheduling A realistic path and timeline to retiring the legacy environment Request your Migration Assessment. It’s that simple! Frequently Asked Questions What are the main telecom migration trends for 2027? Five stand out: legacy platforms managed release by release, the cost of running more than one platform, consolidation onto NetSapiens, the challenge of finishing migrations already underway and automation moving into daily operations. Copper retirement in the US and the UK PSTN switch-off are related network changes rather than platform deadlines. Are BroadWorks and Metaswitch being shut down in 2027? No. Cisco continues to release BroadWorks updates under its maintenance policy, and Alianza has said it will continue to support Metaswitch’s existing product offerings. The pressure to plan a migration comes from release cycles, customer expectations and the cost of running more than one platform rather than a shutdown date. Does legacy network retirement mean we have to leave our voice platform? No. US copper retirement and the UK PSTN switch-off concern access networks and legacy services, while platform migration concerns where customers’ voice services run. A provider can do one without the other, though both reflect the same move toward IP-based communications. How long does it take to migrate off a legacy platform? It depends on line count, data quality, feature complexity, exceptions and available engineering capacity. Vox Matic’s white paper model estimates about 23 months for a manual 15,000-line migration against about eight months with automation. A realistic schedule is confirmed after discovery. Can the final stage of a migration be automated? Partly. Otto™, Vox Matic’s proprietary automated telecom migration framework, can automate repeatable extraction, transformation, validation and provisioning work. Records that do not fit the agreed mapping can be flagged for review, allowing engineers to focus on complex configurations, exceptions and decisions requiring judgment. Customer-affecting decisions remain with the provider. We already run NetSapiens. Is migration still relevant to us? Often, yes. Many providers run NetSapiens for new customers while older customers stay on BroadWorks or Metaswitch. Moving those remaining customers allows the legacy environment, and its related ongoing costs, to be retired once it has been fully decommissioned and the associated obligations have ended. Can Forge work with our existing systems? Yes. Forge™, Vox Matic’s custom automation and workflow development service, can be designed around the provider’s existing environment. Where suitable access and supported integration options are available, Forge can coordinate information and supported actions across systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Does automation still matter after a migration is finished? Yes. Completing a migration can remove the complexity of operating multiple voice platforms, but ongoing operational workflows remain. Customer onboarding, order management, provisioning, billing updates, carrier coordination and reporting may continue to involve repeatable manual work. Forge can automate or coordinate suitable workflows while approvals, exceptions and judgment-based decisions remain with the provider’s team. Metaswitch and BroadWorks are trademarks of their respective owners. NetSapiens is a trademark of Crexendo, Inc. Otto™ and Forge™ are trademarks of Vox Matic. Other product and company names are the property of their respective owners. References are for identification and interoperability purposes only.
- Telecom Provisioning Automation: Reducing Manual Work From Order to Activation
Telecom service provisioning automation coordinates an approved order through configuration, validation, activation and verification. Where suitable access and supported integration options are available, supported changes can be applied across the relevant voice and operational systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Exceptions and non-standard requests are routed to the appropriate person for review. This guide covers day-to-day service provisioning after an order has been approved. The preceding stages—request intake, validation and approval—are covered in our guide to telecom order management automation. Provisioning carried out during a platform migration works differently, as covered below. Key Takeaways Provisioning automation starts once an order is approved and ends when the service is active and verified. Pre-activation validation can identify missing information, unavailable numbers, plan mismatches and configuration conflicts before supported changes are applied. Exceptions, such as failed checks or non-standard requests, are routed to an owner with the reason, rather than forced through. Dependent steps, such as number ports, E911 records and devices, may involve other teams, vendors or carriers. Ongoing provisioning workflows are distinct from the provisioning performed during an Otto-assisted migration. What Happens Between an Approved Order and Activation? Provisioning typically follows these steps: Prepare: The approved order’s details, such as users, numbers, features, sites and devices, are gathered into the configuration the service needs. Validate: The configuration is checked against agreed rules before anything is changed. Apply: Where suitable access and supported integration options are available, approved changes can be applied to the relevant voice and operational systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Coordinate dependencies: Steps that rely on others, such as number ports, E911 records, device shipping or billing, are completed through supported integrations or as tasks for the responsible team. Verify: The result is checked against the order, with essential functions tested where required. Close: The order is marked complete, records are updated and the customer is informed where the provider chooses. In a manual process, each of these steps may involve a different person and a different tool. As order volumes grow, the same configuration work is repeated many times a week, and small inconsistencies become harder to spot. Which Validation Checks Help Before Activation? Pre-Activation Checks at a Glance Check What It Confirms Required details The order includes every field the service type needs Number availability Requested numbers are available, or the port has been scheduled Service address The required service-address information is present and has been processed according to the provider’s approved E911 service and operational requirements. Plan and features The requested features match the customer’s plan or contract Device compatibility Requested devices are supported models with a known configuration Duplicates and conflicts The user, extension or number is not already in use Naming conventions Names follow the provider’s agreed standards Checks like these can run automatically, helping identify missing information, unavailable numbers, plan mismatches and configuration conflicts before supported changes are applied. How Should Provisioning Exceptions Be Handled? Some requests will not pass through the standard path. Common provisioning exceptions include: A failed validation check A request for a non-standard configuration An integration error from a connected system A dependency that is not ready, such as a port that has not completed Exceptions are assigned to an identified owner for review and resolution rather than allowing an unsupported or non-standard request to proceed automatically. Where the provider’s approved rules permit, unaffected steps may continue while the exception is reviewed. Decisions involving non-standard configurations, failed validations or other judgment-based issues remain with the appropriate person. Migration exceptions follow a related but separate process, covered in our guide to telecom migration exception management. How Is Ongoing Provisioning Different From Migration Provisioning? Provisioning happens in two different contexts, and each is handled differently. Migration and Ongoing Provisioning at a Glance Question Migration Provisioning With Otto™ Ongoing Provisioning With Forge™ When does it happen? During a platform migration, before cutover During day-to-day operations, whether following a migration or within another environment where suitable access and supported integration options are available What triggers it? The migration plan and its stages Approved service orders Where does the data come from? Existing services extracted from the legacy platform Details from the approved order What is the typical volume? Many existing customers moved in planned stages Individual orders as they arrive What is the goal? Recreate validated customer and service configurations in NetSapiens Activate new or changed services consistently Otto™, Vox Matic’s proprietary automated telecom migration framework, automates repeatable extraction, transformation, validation and provisioning work when moving from BroadWorks, Metaswitch and other mixed legacy environments into NetSapiens. Otto is used for migration work, including recreating validated customer and service configurations in the target NetSapiens environment. Forge™, Vox Matic’s custom automation and workflow development service, supports ongoing operational processes such as provisioning approved orders, coordinating dependent steps and routing exceptions. Where suitable access and supported integration options are available, Forge can coordinate supported actions across the provider’s systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Forge can be used following an Otto-assisted migration or within another environment where the required systems provide suitable access and supported integration options. How Does a Provisioning Automation Project Start? A practical provisioning automation project usually begins with one repeatable, high-volume service type rather than attempting to automate every service at once. Adding users, activating a standard service package or applying a common feature change can provide a manageable starting point. Forge projects can follow four practical stages, depending on the workflow and agreed project scope: Identify: The provisioning steps that require the most repeated effort, and the people who carry them out today Design: The validation rules, exception routing and systems involved Build and validate: The workflow, validated against agreed operational scenarios before deployment Deploy and support: Deployment into the approved environment, with support or refinements according to the agreed scope Where Is Manual Provisioning Slowing Your Team Down? Vox Matic builds provisioning workflows around a provider’s existing environment, with validation and exception handling designed around the team that runs it. A Forge Consultation can help identify: Which provisioning steps your team repeats most often Which validation checks could run before activation Where exceptions should be routed and who should own them Which systems offer suitable access and supported integration options Request a Forge Consultation. It’s that simple! Frequently Asked Questions What is telecom service provisioning automation? It is the use of automated workflows to carry an approved service order through to activation, including preparing configuration details, validating them, applying supported changes and verifying the result. Can provisioning be fully automated? Some provisioning workflows can be highly automated when requests are standardized, the required information is available and the provider has approved the applicable business rules. Where suitable access and supported integration options are available, supported changes can be applied across the relevant systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Non-standard requests, failed validations and steps involving carriers, vendors or on-site work generally require human coordination or review. Automation does not force an exception or unsupported request through the provisioning process. What happens when a provisioning request fails validation? The affected steps are paused, and the request is routed to the appropriate person with the reason it failed. It is tracked until it is corrected or rejected. Is Forge used to provision services during a migration? Otto handles the repeatable migration activities required to recreate validated customer and service configurations in NetSapiens. Forge supports ongoing operational workflows, including provisioning approved orders after go-live or automating provisioning processes within another suitable environment. Which systems does provisioning automation connect to? That depends on the provider’s environment. Typical systems include the voice platform, number inventory, E911 service, device provisioning and billing, where they offer suitable access and supported integration options. Metaswitch and BroadWorks are trademarks of their respective owners. NetSapiens is a trademark of Crexendo, Inc. Otto™ and Forge™ are trademarks of Vox Matic.
- Telecom Order Management Automation: From Customer Request to Approved Service Change
Telecom order management automation coordinates a customer request from intake through validation and approval, then manages its handoff to the teams and systems responsible for completing the service change. Where suitable access and supported integration options are available, approved information and actions can be passed to the relevant systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. The order can continue to be tracked through provisioning, billing and closure, while approval decisions remain with the provider’s designated team. Order management coordinates intake, validation and approval before a service is changed, then tracks the approved order as it moves through fulfilment and closure. Key Takeaways This guide focuses on order intake, validation, approval, handoff and status tracking. The next stage—applying and verifying the approved service change—is covered in our guide to telecom service provisioning automation. Delays often come from incomplete requests, approvals waiting in inboxes and handoffs that lose details. Approval rules can route each request type to the right person, while the decision itself stays with people. Approved orders can be passed to provisioning, carrier and billing steps through supported integrations or as tasks for the responsible team. A shared status for each order helps operations and customer-facing teams see where a request stands. What Happens Between a Customer Request and an Approved Change? Orders typically move through the same stages, whatever the request type. Order Stages at a Glance Stage What Happens Where Manual Work Often Sits What Automation Can Change Intake The request arrives from a customer, administrator or sales team Requests arrive by email, phone or ticket in different formats A structured request with the required fields for each request type Validation The request is checked against the customer’s account, plan and contract Staff look up account details in several systems Checks against available account data, with gaps flagged Approval The appropriate person approves or rejects the request See 1) Approvals wait in email or chat Requests routed to the right approver with a clear status Handoff Approved details pass to the teams and systems that carry out the changeSee 2) Details re-typed into tickets or other tools Validated details passed through supported integrations or as tasks Tracking Each step is monitored until the change is complete Status kept in spreadsheets or individual inboxes A shared status for each order and its steps Closure The order is confirmed complete and records are updated Billing and account records updated later, or missed Closure steps, such as billing updates, triggered on completion Automation can manage the routing, reminders, escalation and recordkeeping around an approval. The underlying commercial or operational decision remains with the provider’s designated approver unless the provider has explicitly established an approved rule allowing a defined request type to proceed automatically. Carrier requests can be prepared through the workflow. Where suitable access and supported integration options are available, the requests may also be submitted to the applicable carrier system. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Carrier approvals, processing requirements, responses and timelines remain with the carrier. Where Do Orders Typically Get Stuck? Delays tend to cluster at the points where a request changes hands: Incomplete requests: Missing details lead to back-and-forth with the customer before work can start. Approval delays: Requests remain in an inbox or queue without a clear response time, reminder or escalation path. Handoffs that lose detail: Information captured at intake is re-entered, summarized or dropped before it reaches the team carrying out the change. No shared status: Customer-facing teams cannot see where a request stands without asking someone. Incomplete closure: The service change is made, but billing or account records are not updated. As request volumes grow, each of these adds up. Individually, these delays may appear small. Across recurring orders, however, repeated follow-up, data entry and status checks can consume significant operations and engineering time. How Should Order Approvals Work? Approval rules define which requests need approval, who approves them and what happens when no one responds. A practical set of rules typically covers: Request types: Which changes need approval, such as new services, contract changes or changes above an agreed value Approvers: Who approves each request type, with a backup approver where needed Escalation: What happens when a request waits longer than an agreed time Records: Who approved each request and when Automation can manage the routing, reminders, escalation and recordkeeping around an approval. It does not make the underlying commercial or operational decision unless the provider has explicitly defined a request type that may proceed under an approved rule. Some providers choose to let defined low-risk request types proceed without manual approval. That decision, and the rules behind it, stay with the provider. How Do Handoffs to Provisioning, Carriers and Billing Work? Once a request is approved, the order workflow passes validated details to the next step. How that happens depends on the systems involved: Provisioning: Where suitable access and supported integration options are available, approved details can be passed to the relevant provisioning systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible provisioning team. Carriers: Carrier requests can be prepared through the workflow. Where suitable access and supported integration options are available, the requests may also be submitted to the applicable carrier system. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Carrier approvals, processing requirements, responses and timelines remain with the carrier. Billing: Where suitable access and supported integration options are available, supported billing updates can be passed to the relevant billing system. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible billing team. Order management automation coordinates these steps. It does not need to carry out every service change itself, and some changes will continue to be completed by people in the provider’s existing tools, with the workflow tracking them to completion. How Is Order Status Tracked? Each order, and each step within it, can carry a status that operations, support and account teams can see. This helps teams answer customer questions without chasing colleagues and makes stalled orders visible early. Where the provider chooses, customers can also receive updates at key stages, such as approval and completion. A coordinated order status does not require every system to be replaced. Where suitable access and supported integration options are available, status information can be collected or updated across the provider’s existing environment. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Where Does Forge Fit? For one client, Vox Matic developed a coordinated operations workspace that brought together available customer and account information, approvals, carrier coordination, user and plan management, and operational search capabilities. The solution was designed around the client’s systems, requirements, approved business rules and project scope. Forge™, Vox Matic’s custom automation and workflow development service, is designed around the provider’s operational requirements rather than requiring the provider to adopt a fixed workflow. Forge projects can follow four practical stages, depending on the workflow and agreed project scope: identifying the order types that require the most repeated effort, designing the approval rules and handoffs, building and validating the workflow against agreed operational scenarios, then deploying and supporting it. Where Is Your Order Process Losing Time? Vox Matic designs order workflows around a provider’s existing systems, with approvals and decisions kept with the people responsible for them. A Forge Consultation can help identify: Which order types your team handles most often Where approvals or handoffs create delays Which steps can be integrated and which should be assigned and tracked as tasks for your team A practical first order workflow to automate Request a Forge Consultation. Frequently Asked Questions What is telecom order management? Telecom order management coordinates a request through intake, validation and approval, then manages its handoff and status as the approved change moves through fulfilment. Provisioning applies and verifies the service change in the relevant systems. Can order approvals be automated? The routing and administration around an approval can be automated, including reminders, escalation and recordkeeping. The commercial or operational decision remains with the provider’s designated approver unless the provider has established an approved rule allowing a defined request type to proceed automatically. Does order management automation submit carrier orders? Carrier requests can be prepared through the workflow. Where suitable access and supported integration options are available, they may also be submitted to the applicable carrier system. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Carrier approvals, processes, timelines and responses remain with the carrier. How is order management different from provisioning? Order management coordinates the request through intake, validation and approval, then manages the handoff and tracks the order through fulfilment. Provisioning applies and verifies the approved service change. The two processes connect when the approved and validated order is handed to provisioning. Do we need to replace our existing systems? Not necessarily. Forge™, Vox Matic’s custom automation and workflow development service, can be designed around a provider’s existing systems and operational rules. Where suitable access and supported integration options are available, the workflow can coordinate information and supported actions across those systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Metaswitch and BroadWorks are trademarks of their respective owners. NetSapiens is a trademark of Crexendo, Inc. Otto™ and Forge™ are trademarks of Vox Matic.
- Telecom Automation Use Cases: 7 Workflows Service Providers Can Automate
Telecom service providers manage many repeatable workflows across customer, billing, voice, carrier and operational systems. Automating or coordinating these workflows can reduce duplicate data entry, improve consistency and give teams clearer visibility from the initial request through completion. Common opportunities include customer onboarding, adds, moves and changes, number requests, E911 address updates, billing updates, disconnects and recurring reporting. Approvals, exceptions and judgment-based decisions remain with the appropriate people. This guide looks at the workflows themselves: what triggers each one, where the manual work sits and what automation can change. For the broader case for automation, see our article on why workflow automation is essential. Key Takeaways Strong automation use cases are workflows that run often, follow clear rules and touch several systems. Each workflow keeps human decision points, such as approvals and exception reviews, while routine steps around them can be automated. Where systems offer suitable access and supported integration options, information captured once can be validated and passed between compatible systems rather than repeatedly re-entered. Carrier steps can be coordinated where supported integrations are available, but carrier processes and timelines remain with the carrier. Starting with one high-volume workflow gives the team a working example before automation is extended. Which Workflows Can Service Providers Automate? These seven workflows are common across service provider operations and are often strong candidates for automation because they occur repeatedly, follow defined business rules and require information to move accurately between multiple systems. Seven Workflows at a Glance Workflow Typical Trigger Systems Often Involved Customer onboarding A signed order or new account CRM, billing, voice platform and number inventory Adds, moves and changes A customer or administrator request Voice platform, billing and device provisioning Number requests and port coordination A request for new numbers or a port-in Number inventory, carrier portals or integrations and the voice platform E911 address updates A new site or a user changing location Voice platform, E911 service and CRM Billing updates after service changes A completed service change Billing system, voice platform and CRM Disconnects and offboarding A cancellation or service removal Voice platform, billing, number inventory and device records Recurring reporting and reconciliation A scheduled reporting period Voice platform, billing and CRM What Does Each Workflow Involve? 1. Customer Onboarding Onboarding a new business customer usually means entering the same company, site and user details into several systems, including the CRM, billing system, voice platform and number inventory. Each re-entry is a chance for a mismatch. With automation: Customer, site and service details can be captured and validated once. Where suitable access and supported integration options are available, the information can then be used to create or update records across CRM, billing, voice and operational systems through a coordinated workflow. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Kept with people: Order approval, non-standard configurations and customer-specific design decisions. 2. Adds, Moves and Changes Adding a user, changing a plan or moving a seat to a new site happens often, and each change is small and easy to get slightly wrong. The change may be made in the voice platform but missed in billing, or applied to the wrong site. With automation: Requests can be captured with the required customer, user, site and service information. Where suitable access and supported integration options are available, approved changes can be coordinated across the relevant voice, billing and operational systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Kept with people: Changes outside the customer’s contracted services and requests that fail validation. 3. Number Requests and Port Coordination Ordering new numbers or porting existing ones often involves separate carrier portals, document collection and status tracking in spreadsheets or email. With automation: Requests are captured with the required information, and supporting documents are checked for completeness. Where suitable access and supported integration options are available, submissions can be coordinated through the workflow. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Carrier approvals, processing requirements and timelines remain with the carrier. Kept with people: Rejected requests, port exceptions and any carrier-side follow-up. Carrier processes and timelines remain with the carrier. 4. E911 Address Updates When a customer opens a new site or a user moves, the service address may need updating in more than one system. If one is missed, the address associated with a number may no longer match where the user is. With automation: The required address information can be captured and processed according to the provider’s approved E911 services, systems and operational requirements. Where suitable access and supported integration options are available, approved updates can be passed to the relevant systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Kept with people: Addresses that fail validation and any change the provider’s E911 process requires staff to confirm. 5. Billing Updates After Service Changes Billing is often updated after the service change, by a different team, from a different record. Gaps between the two can lead to unbilled services or incorrect charges. With automation: Where suitable access and supported integration options are available, completed service changes can generate supported billing updates. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible billing team. Kept with people: Credits, adjustments, pricing exceptions and anything that changes a customer’s contracted rates. 6. Disconnects and Offboarding Removing a customer or service involves several steps across systems: removing users, handling numbers, stopping billing and recording devices for return. A missed step can leave numbers active or billing running after the service has ended. With automation: A disconnect request can trigger a coordinated checklist covering the required service, billing, number and device activities. Where suitable access and supported integration options are available, supported actions can be coordinated across the relevant systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Kept with people: Disconnect approval, number retention or port-out requirements and customer disputes. 7. Recurring Reporting and Reconciliation Monthly reporting often means combining exports from the voice platform, billing system and CRM in spreadsheets. Reconciliation, such as checking active users against billed seats, may only happen when someone has time. With automation: Where suitable access and supported integration options are available, reports can be assembled on a schedule using information from the relevant systems. Mismatches, such as active users that are not billed, can be flagged for review. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Kept with people: Investigating and resolving variances. How Do You Choose Which Workflow to Start With? The best first workflow is usually not the largest or most complicated. A repeatable, high-volume workflow with clear rules and identifiable exceptions can provide an effective starting point. It gives the team a practical result, exposes integration and data considerations and creates a model that can be extended to other workflows. Before automating, map how the workflow runs today: who starts it, which systems it touches, where approvals sit and what happens when something does not fit. Our guide to automating service provider operations after a NetSapiens migration covers what to check before automating a workflow. Where Does Forge Fit? Forge™, Vox Matic’s custom automation and workflow development service, typically begins with one clearly defined workflow. Depending on the provider’s requirements and agreed scope, Vox Matic identifies the repeated work, designs the workflow and exception paths, builds and validates the automation, and supports deployment into the approved environment. Where suitable access and supported integration options are available, Forge can coordinate information and supported actions across the provider’s systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Forge can support these workflows whether or not the provider is undertaking a NetSapiens migration. For providers moving from BroadWorks, Metaswitch or other mixed legacy environments into NetSapiens, Otto™, Vox Matic’s proprietary automated telecom migration framework, supports the migration itself, while Forge supports the operational workflows that continue afterward. Which Telecom Workflow Should You Automate First? Vox Matic helps service providers automate or coordinate operational workflows around their existing systems, with approvals and exceptions designed around the teams that run them. A Forge Consultation can help identify: Which workflows your team repeats most often Which systems each workflow touches and what integration options they offer Where approvals and exceptions should stay with your team A practical first workflow to automate Request a Forge Consultation. It’s that simple! Frequently Asked Questions What are common telecom automation use cases? Common use cases include customer onboarding, adds, moves and changes, number requests, E911 address updates, billing updates, disconnects and recurring reporting. Each involves repeatable steps across several systems. Can Forge work with our existing systems? Yes. Forge™, Vox Matic’s custom automation and workflow development service, can be designed around the provider’s existing environment. Where suitable access and supported integration options are available, Forge can coordinate information and supported actions across systems. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team Which workflow should a service provider automate first? Start with a workflow that runs often, follows clear rules and touches several systems. A simple, high-volume workflow can show value sooner than a complex one that runs occasionally. Can automation handle carrier requests? In part. Requests can be prepared and checked through the workflow. Where suitable access and supported integration options are available, submissions can also be coordinated through the applicable carrier system. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Carrier approvals, processes, timelines and responses remain with the carrier. Does automation replace the operations team? No. Automation is designed to reduce repetitive operational work, not remove the people responsible for the process. Approvals, exceptions and judgment-based decisions remain with the appropriate team, while supported routine steps are automated or coordinated around them. Do we need to be on NetSapiens to automate these workflows? No. Workflows can be developed around other platforms and systems where suitable access and supported integration options are available. Where direct integration is unavailable, the workflow can create, assign and track a task for the responsible team. Metaswitch and BroadWorks are trademarks of their respective owners. NetSapiens is a trademark of Crexendo, Inc. Otto™ and Forge™ are trademarks of Vox Matic.
- What Happens to Voicemail and Greetings During a NetSapiens Migration?
During a NetSapiens migration, voicemail settings are typically recreated, while greetings, announcements and other audio files may be transferred or re-recorded. What can be moved depends on the source platform, file accessibility and the agreed migration scope. For providers migrating from Metaswitch, BroadWorks or other mixed legacy environments into NetSapiens, the first step is identifying what can be recreated automatically, what can be transferred and what customers may need to set up again. Key Takeaways Voicemail settings, greetings, stored messages, announcements and call recordings are different assets, each with its own migration considerations. Settings are usually recreated in NetSapiens, while audio files depend on what the source platform makes accessible. Supported and accessible assets are identified for extraction or recreation during discovery, based on the agreed scope. Customers should know in advance if anything, such as greetings or PINs, needs to be set up again. Auto attendant announcements need their own testing, since they are often the first thing callers hear. Which Voicemail and Audio Assets Are Involved? Voicemail and Audio Assets at a Glance Asset Typical Treatment What to Confirm During Discovery Voicemail box settings Recreated in NetSapiens Mailbox options, notification settings and voicemail-to-email Personal greetings and name recordings Transferred where supported and accessible, or re-recorded Whether greeting files can be exported from the source Stored voicemail messages Depends on source access and agreed scope Whether saved messages need to be migrated, retained separately or archived before cutover Auto attendant announcements Transferred where supported and accessible, or re-recorded Which announcements are in use and who owns them Music on hold and other audio Transferred where available, or replaced File availability and format Call recordings Usually handled separately from voicemail Where recordings are stored and how long they must be retained Exact mapping is confirmed during discovery, because every environment has its own customizations. What Is the Difference Between Recreating and Transferring? Recreating means rebuilding a configuration in NetSapiens based on the source settings. Voicemail box options, notification preferences and supported voicemail-to-email or transcription settings may be recreated in NetSapiens according to the agreed design. Transferring means moving an actual audio file, such as a greeting or announcement, from the legacy platform into NetSapiens. Whether this is possible depends on whether the source platform makes the files accessible, and in which format. Where files cannot be transferred, greetings and announcements can be re-recorded, and customers should be told in advance which recordings will need to be made again. What About Stored Messages and Call Recordings? Stored voicemail messages and call recordings often need a specific decision. Stored voicemail messages: Some providers ask customers to save important messages before cutover. Existing messages should be retained, archived or removed according to applicable requirements and the agreed migration plan. Call recordings: Recordings are often stored separately from voicemail and may be subject to retention requirements. Decide where existing recordings will be kept and how they can be accessed after the legacy platform is retired. Settling these questions early can help avoid issues after go-live. How Do You Protect the Customer Experience? Voicemail and audio changes can be noticed by both end users and their callers. A few practices can help: Tell users what will change: Explain whether greetings, PINs or saved messages will carry over. Prioritize auto attendants: Announcements and menus are often the first thing callers hear, so test them for each customer. Check voicemail access: Confirm users can reach voicemail from desk phones and supported end-user applications. Verify notifications: Confirm voicemail-to-email and transcription work as expected where they are in use. Depending on the environment and agreed project scope, migrated configurations can be reviewed and validated before cutover. Our guide on how to migrate telecom customers without disrupting service covers the wider customer-experience picture. Careful planning can help minimize customer-facing changes and reduce the risk of unexpected disruptions to voicemail and call handling. As Ben, COO of Fuse.Cloud, said of the company's BroadWorks to NetSapiens migration with Vox Matic: "Our customers barely noticed the transition." Results reflect that specific engagement and will vary by environment and project scope. Read the case study. Where Does Automation Help? Voicemail work combines settings, which follow repeatable patterns across users and customers, with audio files, whose handling depends on what the source platform makes accessible. Otto™, Vox Matic's proprietary automated telecom migration framework, automates repeatable data extraction, transformation and provisioning work. Automated validation checks applied throughout the workflow help identify migration discrepancies for review before cutover. Configuration exceptions are flagged for engineering review, while unavailable audio files are identified so re-recording and customer communication can be planned before go-live. Planning a Migration? Start With What Your Customers Hear. As a NetSapiens Ecosystem Partner, Vox Matic uses automation and experienced telecom engineering to help providers move voicemail configurations, audio requirements and other subscriber services from BroadWorks, Metaswitch and mixed legacy environments into NetSapiens. A Migration Assessment can help identify: What can be extracted, recreated or transferred Where automation can reduce manual work Which audio files or customer actions require advance planning The most effective approach for a controlled migration Request your Migration Assessment. It's that simple! Metaswitch and BroadWorks are trademarks of their respective owners. NetSapiens is a trademark of Crexendo, Inc. Otto™ and Forge™ are trademarks of Vox Matic. Frequently Asked Questions Do voicemail greetings transfer to NetSapiens? Greetings can be transferred where they are supported and accessible on the source platform. Where files cannot be transferred, greetings can be re-recorded, and customers should be told before cutover. Will users keep their saved voicemail messages? That depends on source access and the agreed migration scope. Some providers ask customers to save important messages before cutover, and existing messages should be retained, archived or removed according to applicable requirements. Do voicemail PINs carry over? It depends on what the source platform makes available. If PINs cannot be carried over, users may need to set a new PIN, and that should be communicated before cutover. What happens to auto attendant announcements? Announcements are transferred where supported and accessible, or re-recorded. Because they are often the first thing callers hear, auto attendants should be tested for each customer before and after cutover. What happens to call recordings during migration? Call recordings are often stored separately from voicemail and may have retention requirements. Providers should decide where existing recordings will be kept and how they will be accessed before the legacy platform is retired.
- NetSapiens Device Migration Guide: Desk Phones, ATAs, Softphones and Provisioning
Device migration is one of the most visible parts of any BroadWorks or Metaswitch to NetSapiens migration. While platforms, databases and configurations run in the background, users immediately notice when a phone, ATA or softphone is not working after cutover. Proper planning, device mapping and automated migration workflows help ensure a smooth transition with minimal disruption. For many end users, their phone or app is a highly visible part of the service. If an endpoint does not register or work as expected after cutover, users may experience a service issue even when the rest of the migration has gone to plan. That makes endpoint planning an important part of a Metaswitch or BroadWorks to NetSapiens migration. This guide covers the planning side of device migration: what to inventory, which decisions to make and how desk phones, ATAs and softphones differ. Key Takeaways An accurate device inventory, including models, ownership and customizations, provides the basis for endpoint planning. Compatibility decisions help determine which devices are reused, reconfigured or replaced. Standard device configurations can make endpoint provisioning more consistent across customers and device types. Redirection methods vary by device and environment, and some steps may require provider or on-site involvement. Desk phones, ATAs and softphones each need their own testing approach. What Should a Device Inventory Include? Device planning starts with an accurate view of what is in the field. In large BroadWorks and Metaswitch environments, device records are often spread across multiple systems or contain historical inconsistencies. Device inventory validation before migration helps reduce provisioning issues and cutover delays. A useful inventory captures: Make and model of each endpoint Ownership: Whether the device is provider-owned, leased or customer-owned Device users: Which users and line appearances each device serves Customizations: Programmable keys, busy lamp fields, shared lines and other device-specific settings Location: Which customer site the device sits in, for redirection and E911 purposes Provisioning method: How the device currently receives its configuration Depending on the source platform and available data, Vox Matic can extract device records, user associations and supported configuration details for mapping into NetSapiens devices and applicable provisioning configurations. Settings that cannot be extracted or mapped directly may require engineering review. The BroadWorks to NetSapiens migration page shows how devices typically map at a glance. Which Devices Can Be Reused? Compatibility decisions can affect both the budget and the cutover plan. Device Decisions at a Glance Decision When It Applies What to Confirm Reuse without replacement The model is compatible and can continue operating after the required provisioning or registration changes Supported firmware and provisioning method Reuse with changes The model is supported but needs updated device configuration settings or a firmware update Firmware update responsibility and timing Replace The model is not supported or is due for replacement Replacement timing, shipping and on-site support Retire The device is no longer in use Removal from the inventory and billing Firmware compatibility and updates are typically handled by the provider or its device vendor and should be planned before cutover rather than during it. How Do Standard Device Configurations Help? Device configurations define how each device type is set up, including registration settings, line keys, feature buttons and display options. A standard set of device configurations can help keep endpoint provisioning consistent across customers and may make troubleshooting easier after go-live. A migration can also provide an opportunity to reduce device-by-device customization. Customer-specific settings, such as programmed keys or shared line appearances, should still be preserved where they are part of the agreed customer requirements. Device standardization also creates opportunities for ongoing operational efficiency. Forge™, Vox Matic's provisioning automation platform, can help service providers maintain consistent device deployment standards after migration while reducing manual provisioning activities. How Are Devices Redirected to NetSapiens? Redirection is the step that moves an endpoint from the legacy platform to NetSapiens. For large service providers with thousands of deployed endpoints, coordinating device redirection manually can significantly increase project timelines and operational overhead. Depending on the device type and environment, it may involve: Updating provisioning server settings so devices pick up their new configuration Using a device vendor's redirection service, where available On-site or user-assisted steps for devices that cannot be redirected remotely Redirecting IP phones at the customer location can be part of the migration workflow, depending on the environment and agreed scope. After redirection, registration and essential calling functionality should be verified, with a plan for endpoints that do not work as expected. How Do Desk Phones, ATAs and Softphones Differ? Desk Phones Desk phones are often the largest group. Testing should cover registration, inbound and outbound calls, line keys, busy lamp fields, voicemail access and any shared line appearances. ATAs Analog telephone adapters often support fax machines, analog lines and other connected devices that customers may still depend on. Fax and analog services should be identified during inventory and tested specifically, since they can behave differently from standard voice calls. Softphones Softphones and mobile apps typically depend on user credentials and sign-in rather than physical redirection. Any changes for users should be identified in advance, so they can be guided through them. Where required, the provider or customer may also complete client-side testing in end-user applications to confirm that users can place and receive calls after cutover. For the wider set of checks after go-live, see our post-migration verification playbook. Where Does Automation Fit in Device Migration? Device migration frequently involves thousands of phones, ATAs and softphone users across multiple customers and locations. Manually collecting device information, validating records, mapping users and preparing provisioning data can consume significant engineering resources and increase project risk. Otto, Vox Matic's proprietary migration automation framework, automates the extraction, transformation and validation of supported device records, user associations and migration data. Automated validation checks help identify exceptions before cutover, improving migration consistency while reducing manual effort during Telecom Migration. Combined with Forge provisioning automation, service providers can accelerate both migration and post-migration operations while maintaining consistent device deployment standards. Planning a BroadWorks or Metaswitch Device Migration? Vox Matic has successfully migrated thousands of subscribers from BroadWorks and Metaswitch platforms as a NetSapiens Ecosystem Partner, using its automated migration framework. Whether you're evaluating endpoint compatibility, provisioning requirements or large-scale device migration strategies, our team can help identify the fastest and lowest-risk path forward. Request your Migration Assessment: Discuss your current platform, migration objectives and target timeline. Identify automation opportunities, device compatibility requirements, project risks and the most effective migration approach. It's that simple! Metaswitch and BroadWorks are trademarks of their respective owners. NetSapiens is a trademark of Crexendo, Inc. Otto™ and Forge™ are trademarks of Vox Matic. Frequently Asked Questions Can we reuse our existing phones when moving to NetSapiens? Often, yes. Devices that are supported for NetSapiens endpoint provisioning can typically be reused after the required provisioning or registration changes, sometimes with updated device configuration settings or a firmware update. Unsupported or older models may need replacement. Who handles firmware updates during a device migration? Firmware updates are typically handled by the provider or its device vendor. Compatibility should be confirmed and updates planned before cutover. How are phones redirected to NetSapiens? Depending on the device and environment, redirection may involve updating provisioning server settings, using a vendor redirection service or on-site steps. Registration and essential calling functionality should then be verified for each device. Do ATAs need special attention during migration? Yes. ATAs often support fax machines and analog lines, which can behave differently from standard voice calls. These services should be identified during inventory and tested specifically. What changes for softphone users? Softphone and mobile app users typically sign in with new credentials or settings rather than having a device redirected. Clear communication about any changes and, where required, client-side testing can help guide users through the transition. Can Device Migrations be automated? Many aspects of device migration can be automated, including extraction of supported device records, user associations, validation checks and provisioning preparation. Physical activities such as hardware replacement or certain on-site tasks may still require human involvement.
- How Long Does a Metaswitch or BroadWorks Migration to NetSapiens Take?
Migration timelines are one of the first questions telecom executives ask, and one of the hardest to answer without context. There is no universal timeline for a Metaswitch or BroadWorks migration to NetSapiens. Any estimate provided before understanding your environment is unlikely to be reliable. The direct answer: Migration duration depends on subscriber volume, data quality, feature complexity, integrations, validation requirements, exception handling, wave design, and cutover strategy. These variables must be understood before a reliable timeline can be developed. What follows breaks down each factor so you can build a realistic picture of your own project before the first scoping call. Key Takeaways Migration duration depends on the provider’s environment, not simply the source platform. Subscriber volume establishes scale, while data quality, exceptions, and feature complexity often determine pace. Automation accelerates repeatable migration work, but discovery, engineering oversight, validation, and cutover planning remain essential. Structured discovery provides the information needed to build a reliable timeline. Why There Is No Standard Migration Timeline Every Metaswitch and BroadWorks environment is different. Each platform uses distinct data structures and provisioning models, and individual providers may have years of custom configurations, integrations, and operational exceptions layered into their environments. Moving into NetSapiens requires data mapping, validation, exception handling, and controlled cutover. How long each stage takes depends on what is being migrated, how the source environment has been configured, and the operational requirements of the project. The source platform matters less than most executives assume. A smaller provider with clean data and relatively simple feature sets may require a very different timeline from a larger provider with complex bundles, multiple integrations, and inconsistent records, regardless of the legacy platform involved. What Actually Drives Migration Duration? Each of the following variables can compress or extend your project. Assess them honestly before you build a timeline. Subscriber Volume More subscribers means more data to extract, map, validate, and provision. Volume also determines wave design. Higher subscriber volumes generally require more extraction, transformation, validation, and provisioning activity. They may also require multiple migration waves to manage operational load and support controlled validation. Data Quality Legacy platforms accumulate inconsistent records, deprecated configurations, and incomplete data over years of operation. All of it needs to be audited, cleaned, and normalized before active migration begins.The source data should be assessed before migration, with material inconsistencies corrected, normalized, excluded, or addressed through defined exception rules.Poor data quality can generate exceptions that require additional review, remediation, or specialized transformation rules. Feature Complexity Hunt groups, call queues, auto-attendants, custom ring strategies, and complex bundles each need to be mapped to their NetSapiens equivalents. A more varied feature environment generally requires additional mapping, testing, and validation before cutover. Integration Depth In-scope billing, OSS/BSS, CRM, provisioning, and other third-party integrations must be evaluated to determine what needs to be retained, modified, replaced, or tested before cutover. Unresolved integration dependencies can delay migration readiness or cutover. Exception Volume Exceptions are records or configurations that fall outside standard mapping rules and need manual review. Exceptions can result from data inconsistencies, custom configurations, feature differences, unsupported objects, integration requirements, or records that fall outside standard transformation rules. The volume and complexity of exceptions can materially affect engineering effort, validation, and migration-wave readiness. Validation and Wave Design Each migration wave should include defined validation requirements, test cases, acceptance criteria, and rollback provisions appropriate to the project. Wave size must balance migration speed, validation capacity, operational readiness, and the potential impact of an issue. The use of phased waves, parallel operation, defined maintenance windows, and rollback provisions also affects project duration and complexity. How Do You Estimate Your Migration Timeline? A credible timeline begins with a structured review of the source environment, migration scope, and operational requirements. That means a structured discovery engagement before the project starts. Discovery typically covers: Subscriber audit: Subscriber and account volumes, segmented by service type, configuration, and complexity Data quality assessment: Gaps, inconsistencies, and records requiring remediation Feature mapping: Which features are in use and how they translate to NetSapiens Integration inventory: All third-party systems that interact with the legacy platform Exception modeling: Likely volume and type of records requiring additional transformation, review, or remediation Wave design: Logical migration groups with defined readiness, validation, cutover, and rollback criteria Once discovery is complete, you have the inputs to build a timeline grounded in your actual environment. Otto, Vox Matic’s proprietary automated telecom migration framework, handles high-volume, repeatable processes including data extraction, transformation, provisioning, and validation. That reduces operational burden and supports faster legacy platform retirement. The provider’s engineers manage the migration workflow, with Vox Matic specialists available to assist with complex configurations, exceptions, validation issues, or cutover planning when required. Discovery and validation still take time. Otto reduces repetitive manual effort and supports a faster, more consistent, and scalable migration process. Frequently Asked Questions Does the source platform affect migration duration? Yes. Metaswitch and BroadWorks structure subscriber, service, and configuration data differently, which affects extraction, transformation, and provisioning. However, subscriber volume, data quality, feature complexity, integrations, exceptions, and validation requirements often have a greater effect on the overall timeline. What is the difference between BroadSoft and BroadWorks? BroadSoft was the company that developed BroadWorks, its service-provider communications platform. Cisco acquired BroadSoft in 2018, and the platform is now generally referred to as Cisco BroadWorks. In migration planning, the relevant factors are the BroadWorks version, deployment architecture, configurations, integrations, and data quality. What commonly causes migration delays? Delays often result from data-quality issues, undocumented configurations, complex integrations, unresolved exceptions, or validation problems discovered later than expected. Structured discovery and source-data assessment help identify these issues before they affect migration waves. When should we start planning our migration? Planning should begin early enough to complete discovery, data assessment, feature mapping, integration review, validation planning, and wave design before the proposed cutover period. Even if cutover is months away, early scoping can identify risks and dependencies that may affect the schedule. Ready to Scope Your Migration? The right timeline starts with an honest look at your environment. If you are planning a Metaswitch or BroadWorks migration to NetSapiens, Vox Matic can help you assess the environment and establish a realistic path forward. Vox Matic is an automation-led telecom migration company. Our Otto framework and senior engineering team have scoped and executed migrations across a range of provider sizes and platform configurations. We provide a practical assessment based on the realities of your environment, migration objectives, and operational requirements. Contact Vox Matic to start your migration scoping conversation. It's that simple!
- How to Reduce Churn During a Telecom Migration
To reduce churn during a telecom migration, service providers should segment customers by risk, communicate before each cutover, prepare customers for feature differences, and follow up quickly after go-live. Migration-related churn can come from more than the technical cutover itself. A migration can go well on the platform side and still cost customers if nobody told them what was changing, a feature they relied on behaved differently, or a support ticket sat unanswered in their first week on the new platform. "Our customers barely noticed the transition." Ben, COO, Fuse.Cloud — following their BroadWorks to NetSapiens migration with Vox Matic Results like that come from treating retention as its own workstream, running in parallel with technical execution. Whether you are moving from Metaswitch, BroadWorks, or another legacy platform into NetSapiens, the customer experience belongs in your NetSapiens migration planning from the start, with the same attention as the cutover itself. Key Takeaways Churn risk during a migration often comes from surprises, feature differences, and slow support, even when the technical cutover goes well. Segmenting customers before migration helps providers sequence waves and focus attention on higher-risk accounts. Proactive communication before each cutover reduces confusion and inbound support volume. Feature mapping and sandbox testing help ensure customers are not caught off guard by behavioral differences. Post-migration outreach and a clear escalation path protect retention in the weeks after cutover. Why Do Customers Churn During a Platform Migration? Much of the risk sits in how the move feels to customers, even when the platform side goes smoothly. Common customer-experience risks include: Surprise. Customers were not told what was changing or when, so the first sign of the migration was disruption. Feature differences. A workflow they relied on behaved differently on the new platform, with no guidance on how to adapt. Support friction. They raised a concern and could not reach anyone who understood the migration. Loss of confidence. Together, these signal that the provider is not in control, which can push customers toward cancellation. That is why retention needs its own plan alongside the technical work. How to Segment Customers Before Migration Begins Churn risk varies across your customer base. Segmenting customers early in NetSapiens migration planning helps the team plan waves and put support and communication where they are needed most. Segment Factor Why It Matters for Churn Risk Account size and revenue Larger accounts have more at stake and more stakeholders to manage Product complexity Customers using advanced features need more preparation and validation Support history Accounts with frequent tickets are more likely to escalate during migration Contract proximity Customers approaching renewal are already evaluating their options Technical sophistication Less technical customers need more guided communication and support Sequencing Waves Around Risk One approach is to move higher-risk accounts in later waves, once the process has been proven on lower-risk customer groups. That gives the team time to refine communication and support before the most valuable relationships move. In multi-tenant environments, organizing waves by domain or reseller can also make each move easier to manage and verify. Customers approaching contract renewal deserve extra attention before and after cutover, since they are already evaluating their options. What Customer Communication Should Look Like During a Migration Communication works best when it arrives before customers have a reason to worry. Unhappy customers often do not complain before they leave, and the decision not to renew may have been made weeks earlier in a moment of confusion nobody addressed. For each migration wave, customers should hear from you at four points: Pre-migration notice. Sent well before cutover. Explain what is changing, when it is happening, and who to contact with questions. Keep it plain and reassuring. Feature change summary. If anything will look or behave differently on the new platform, say so explicitly. Customers who discover changes without warning tend to read them as problems. Cutover confirmation. Sent on migration day, confirming the move is complete and providing a direct support contact for the days that follow. Post-migration check-in. A short message after cutover asking whether everything is working as expected. It can surface issues before they become cancellation decisions. How to Maintain Feature Continuity Across a Migration Feature continuity means customers are prepared for any difference they will notice, even when a feature does not work identically on the new platform. Before each migration wave, map the features that customer group actually uses: Which features are active on the legacy platform (call recording, receptionist consoles, hunt groups, fax, voicemail-to-email) How those features are configured in NetSapiens Behavioral differences customers are likely to notice, including in end-user apps such as SNAPmobile What guidance or training customers need before or after cutover Test Before You Migrate Testing migrated configurations in a sandbox environment before cutover helps confirm features behave as expected and surfaces differences while there is still time to prepare customers. When a difference exists, communicate it clearly, share a short resource explaining the new behavior, and flag the account for a check-in. Customers who notice an unexplained change tend to assume something went wrong, while those told in advance usually adapt. Prepare Your Support Team in Parallel Feature mapping also prepares your support team. If you know which features are likely to generate questions, you can pre-build responses and brief the team before those tickets arrive. That shortens resolution time and keeps support friction from becoming a churn driver. What Post-Migration Service Validation Looks Like The weeks after cutover are when customers form their first impressions of the new platform. A clean migration that goes silent afterward leaves customers to draw their own conclusions. Service validation confirms that everything works from the customer's perspective as well as the platform's: Immediate check. Confirm core services are active and reachable, and let the customer know. Early outreach. Follow up shortly after cutover to ask whether customers have seen any issues. For higher-risk accounts, a call can land better than an email. Visible escalation path. Customers should know exactly who to contact if something is not right, whether that is a named contact or a dedicated migration support line. Ticket monitoring by wave. Track post-migration tickets by customer segment and wave. If several customers in the same wave report the same issue, address it before it reaches the broader base. How quickly and visibly you respond to early issues shapes how customers remember the migration. A poorly managed migration can become a churn event. A well-managed migration is often barely noticed by customers. The difference is usually not the destination platform, but the methodology used to get there. Manual migration approaches can introduce variability, extend timelines, and increase the opportunity for configuration errors. Automation-supported migrations enable consistent validation, faster execution, and more predictable outcomes, reducing the likelihood that customers experience the disruptions that undermine confidence and increase churn risk. Where Automation Protects the Customer Experience Many customer-facing problems during a migration trace back to configuration errors: a user setting that did not carry over, a call flow rebuilt incorrectly, a device profile that never reached the phone. At scale, manual work makes those errors harder to avoid and harder to catch. Otto, Vox Matic's proprietary automated telecom migration framework, automates the extraction, transformation, provisioning, and validation work that traditionally consumes the largest portion of migration effort. More consistent, validated configurations mean fewer surprises for customers, and engineers have more time for the accounts that need individual attention. The platform changes. The experience does not. Ready to Protect Retention Through Your Migration? Vox Matic helps service providers move from Metaswitch, BroadWorks, and other legacy platforms into NetSapiens using automation, sandbox testing, and experienced telecom engineering. As a NetSapiens Ecosystem Partner, we help with NetSapiens migration planning on both sides: the technical migration and the customer experience around it. Talk to our team about your environment. It's that simple! Frequently Asked Questions How do telecom providers reduce churn during a platform migration? Combine customer segmentation, proactive communication, feature continuity planning, and structured post-migration validation. Migration-related churn often comes from customers feeling surprised or unsupported, so treating the migration as a customer experience event protects retention more effectively than focusing on cutover mechanics alone. Can customers be migrated without interrupting their phone service? Migrations can be designed to minimize service interruption, with cutovers scheduled in low-traffic windows and configurations tested and validated before go-live. Whether customers feel interrupted also depends on communication and support readiness. How should providers handle customers approaching contract renewal during a migration? Renewal proximity is a higher-risk signal, because these customers are already evaluating their options. Flag them during segmentation, consider moving them in later waves once the process is proven, and give them dedicated account attention before and after cutover. How should a support team prepare for migration-related ticket volume? Brief the team on the features being migrated in each wave, the differences customers are likely to notice, and the escalation path for issues that cannot be resolved at first contact. Pre-built responses for predictable questions shorten resolution time and keep support friction from turning into churn. How long does churn risk last after a migration cutover? There is no fixed window, but the first weeks after cutover matter most, while customers form their impressions of the new platform. Keep outreach, ticket monitoring, and escalation readiness in place until support volume and customer feedback return to normal. Customers who raise a concern and receive a fast, competent response are more likely to stay.
- What Happens After Go-Live? Telecom Migration Support Explained
Post-migration support helps service providers identify and resolve issues after cutover, confirm that customer services are stable, and move the new platform into normal operations. The exact support arrangement depends on the migration and should be agreed before cutover. Go-live is an important milestone, but the work does not always end there. Provisioning exceptions may surface, call flows can behave differently under live traffic, and end users may report issues that were not apparent during sandbox testing. For providers migrating from Metaswitch, BroadWorks, or other legacy platforms to NetSapiens, understanding what happens after cutover is as important as preparing for it. This guide covers support ownership, exception handling, and reporting. For the technical checks to run once customers are live, see the Post-Migration Verification Playbook for NetSapiens. Key Takeaways Post-migration support includes the agreed activities used to verify and stabilize the new environment after customers have completed cutover. Escalation responsibilities should be agreed before cutover, with clear roles for the provider, the migration partner, and the platform vendor. Tracking exceptions and their resolutions helps keep unresolved issues from becoming ongoing operational problems. Post-cutover reporting gives teams visibility into completed waves, outstanding issues, service stability, and remaining follow-up activities. A migration should move into normal operations once agreed acceptance requirements have been met. What Does Post-Migration Support Include? Post-migration support is the work involved in stabilizing a new environment after customers have moved. Some providers call the initial period of additional support hypercare. Whatever the term, the purpose is to identify problems early and make sure they reach the right people. Depending on the environment and the agreed scope, support may include: Service verification: Confirming that calling, routing, devices, voicemail, and important customer features such as call recording, receptionist consoles, and fax are operating as expected, including client-side checks in end-user apps such as SNAPmobile. Exception management: Investigating provisioning gaps, endpoint provisioning issues, configuration mismatches, and unexpected feature behavior. Technical troubleshooting: Resolving migration-related problems that require additional engineering expertise. Escalation coordination: Making sure issues reach the appropriate team when they cannot be resolved directly. Operational handover: Documenting outstanding migration-related issues and confirming the transition to the provider’s normal support and operations processes. These responsibilities should be agreed before cutover. Otherwise, the provider may discover that some support activities were never included in the migration engagement. Who Handles Problems After Cutover? When something goes wrong after migration, the first question is often who should handle it. A customer may report that calls are forwarding incorrectly, a device is not registering, or a feature is behaving differently from the source platform. Some problems can be resolved by the provider's normal support team. Others may require assistance from migration engineers familiar with how the source configuration was transformed for NetSapiens. Platform-level issues may need involvement from NetSapiens or another vendor. Post-Cutover Responsibilities at a Glance Issue Type Example Typical First Owner Routine user requests Voicemail PIN resets, user setting changes Provider support team Migration-related configuration A call flow, hunt group, or answering rule that does not match the source; a device with the wrong configuration profile Provider engineering, with migration-partner assistance when required Domain or reseller-level setup Dial plan or routing settings affecting a customer group Provider engineering, with migration-partner assistance when required Carrier and number routing Numbers still routed to the source platform in an SBC or carrier platform Provider, with the carrier Platform behavior An issue that reproduces outside the migrated configuration Platform vendor, coordinated by the provider This is an illustrative division of responsibilities. Actual ownership depends on the provider’s operating model and the agreed migration and support scope. Responsibilities should be confirmed before go-live. Before cutover, clarify: Who receives and investigates migration-related support requests? Which issues remain with the provider's internal team? When should the migration partner become involved? How are issues escalated when additional technical support is required? Who communicates updates to the affected customers? What information should the provider collect before escalating an issue to the migration partner? Customer communication after cutover also affects retention. Our guide on how to reduce churn during a telecom migration covers what customers should hear and when. Post-cutover support should also be part of the conversation when choosing a NetSapiens migration partner, before the project begins. How Should Post-Migration Exceptions Be Managed? Even a well-planned migration can produce issues that need attention after cutover. A device configuration might need adjustment. A customer-specific routing rule may not behave as expected in the target environment. A feature that passed initial testing could need further investigation under normal use. The coordination effort increases when a provider is migrating large subscriber groups with varied configurations. A practical approach to exception management involves four activities: Identify the issue. Determine which accounts, services, or configurations are affected. Assess the impact. Prioritize issues based on their effect on customers and business operations. Assign responsibility. Establish who will investigate and resolve the problem. Verify and document the outcome. Confirm that the issue has been resolved or assigned an agreed next step, and record the result. Not every issue needs the same response. A failed inbound call requires different attention than a minor configuration difference. In multi-tenant environments, grouping exceptions by domain or reseller helps show whether an issue is isolated or part of a wider pattern. It also helps to separate migration-related exceptions from unrelated problems that happen to appear after cutover. Strong preparation makes this work easier. The NetSapiens migration data validation checklist covers the checks that help identify configuration and data issues before customers go live. What Should Post-Cutover Reporting Cover? Service providers need a clear picture of what is happening after migration, especially when large customer groups or multiple environments are involved. Useful reporting helps teams assess service stability and identify what still requires attention. It may include: Migration status: Which customer groups have completed cutover and verification. Outstanding issues: Open exceptions, their impact, and current status. Resolution progress: Which problems have been addressed and which still need investigation. Escalations: Issues requiring additional engineering or vendor support. Next steps: Remaining work before the migration can be formally closed. For executives, this shows whether the project is progressing toward completion. For operations teams, it gives visibility into the issues that still need attention. The reporting format and frequency should reflect the size and complexity of the migration rather than follow an arbitrary standard. When Is Post-Migration Support Complete? There is no universal support period that applies to every telecom migration. A smaller environment with straightforward configurations may stabilize relatively quickly. A larger migration involving multiple source platforms, custom features, and complex integrations may require additional verification and troubleshooting. Before closing the migration, the responsible parties should review the agreed acceptance requirements, confirm issue ownership, and document any remaining follow-up activities. Depending on the project, these may include: Services identified in the agreed acceptance criteria are operating as expected. Migration-related issues have been resolved or documented with clear next steps. Outstanding support responsibilities have been assigned. The provider's operations team is prepared to manage the new environment. Any remaining verification or follow-up activities are understood. Once those requirements are met, the project can move into normal operations. This also matters for legacy platform retirement. Successful customer and service verification is one of the requirements providers should consider before determining when legacy infrastructure can be retired. How Automation Helps Reduce Post-Cutover Work Some avoidable post-migration issues result from configuration discrepancies or manual provisioning errors. Across a large subscriber base, rebuilding user settings, devices, and call flows by hand creates considerable work and more opportunities for inconsistency. Otto™, Vox Matic’s proprietary automated telecom migration framework, automates repeatable extraction, transformation, provisioning, and validation activities across the migration workflow. By applying automated validation checks to source and target data, Otto can identify discrepancies before cutover and reduce the likelihood that avoidable configuration issues reach customers. The provider’s engineers manage the migration workflow and can engage Vox Matic specialists when assistance is required with exceptions, testing, complex configurations, validation issues, or cutover planning. For a side-by-side view, see manual vs. automated telecom migration. The platform changes. The customer experience should remain consistent. Planning a Migration? Discuss Support Before Go-Live. When evaluating a telecom migration partner, ask what happens after cutover. Who handles migration-related issues? How are exceptions managed? What support will be available, and how will the project transition into normal operations? Vox Matic has completed automated migrations of thousands of subscribers from Metaswitch and BroadWorks environments to NetSapiens. As a NetSapiens Ecosystem Partner, Vox Matic can help define how migration-related support, escalation, and handover could be structured for your environment. Request a Migration Assessment Discuss post-cutover support before customers go live. Vox Matic can help you: Review your legacy platform, migration objectives, and proposed timeline. Identify automation opportunities, migration risks, and post-cutover support requirements. Request your Migration Assessment. It's that simple! Frequently Asked Questions What happens after a telecom migration goes live? After go-live, the focus moves to verifying live services, investigating migration-related issues, and helping the provider transition into normal operations. Depending on the project, this may involve additional testing, troubleshooting, escalation coordination, and post-cutover support. What is hypercare in a telecom migration? Hypercare is a period of additional support immediately after go-live. It may involve closer monitoring, faster issue escalation, and additional engineering attention while the new environment stabilizes. The scope and duration should be agreed before cutover. How long does post-migration support last? There is no standard duration. Support requirements depend on subscriber volume, configuration complexity, outstanding issues, and the agreed project scope. The move to normal operations should be based on defined acceptance requirements rather than an arbitrary timeframe. Who is responsible for resolving issues after cutover? Responsibility depends on the issue and the support agreement. The service provider typically manages routine support and initial investigation. The migration partner may assist when an issue is connected to migrated data, transformation rules, provisioning, or other work within the agreed migration scope. Platform vendors may also be involved when additional support is required. Clear ownership should be established before go-live. Can automation reduce post-migration support issues? Automation can reduce repetitive manual work and improve configuration consistency during migration, which may help keep some avoidable provisioning and configuration problems from reaching customers. Testing, verification, troubleshooting, and access to experienced engineering support remain important parts of the migration process.
- Unlocking Expert Voice and UC Engineering Support On Demand with Vox Matic
In the telecom industry, finding senior-level voice and unified communications (UC) engineers quickly can be a challenge. Hiring full-time staff often involves long delays, high costs, and uncertainty about the right fit. Vox Matic offers a solution by giving service providers and enterprises direct access to experts across Metaswitch, Ribbon, BroadSoft, NetSapiens, and other platforms. This approach delivers flexible, project-based, or on-demand engineering support without the burden of permanent hires. Senior engineer working on voice network configuration Flexible Support for Critical Voice Infrastructure Vox Matic specializes in providing engineering services tailored to the needs of service providers and enterprises running critical voice infrastructure. Whether you need help with a specific project or ongoing operational support, Vox Matic connects you with senior engineers who have deep experience across multiple platforms. This flexibility means you can: Get expert help exactly when you need it Avoid the cost and delay of recruiting full-time engineers Scale your engineering resources up or down based on project demands By giving service providers and enterprises direct access to experts across Metaswitch, Ribbon, BroadSoft, NetSapiens, Vox Matic ensures your voice and UC systems stay reliable and efficient. Network Operations and Platform Support Maintaining day-to-day operations and platform stability requires engineers who understand the complexities of voice networks. Vox Matic engineers assist with: Configuration and setup of voice platforms Troubleshooting and resolving escalations quickly Optimizing network performance to reduce downtime These services can be delivered as part of defined engagements or ongoing operational support. For example, a carrier experiencing intermittent call quality issues might engage Vox Matic engineers to analyze the network, identify bottlenecks, and implement fixes without disrupting existing operations. Professional Services and Platform Engineering When your team faces major initiatives like migrations, platform upgrades, or compliance-driven changes, Vox Matic provides the technical leadership to execute these projects smoothly. Their senior engineers bring hands-on experience with Metaswitch, Ribbon, BroadSoft, and NetSapiens platforms, ensuring: Minimal disruption to your internal teams Efficient project execution with clear milestones Risk reduction through expert planning and testing For instance, a service provider upgrading from BroadSoft to Ribbon can rely on Vox Matic engineers to manage the migration, handle integrations, and ensure compliance with industry standards. Staff Augmentation with Senior Engineers Sometimes, your team needs immediate access to experienced engineers without the long-term commitment of hiring. Vox Matic offers staff augmentation services designed to fill this gap. You can bring in senior voice and UC engineers on a short- or long-term basis to: Supplement your existing team during peak workloads Provide expertise for complex projects Accelerate delivery timelines This approach is ideal for organizations that require experience now, not months from now, and want to avoid adding permanent headcount. Targeted IT Consulting and Voice Engineering For focused, high-impact work, Vox Matic delivers consulting and hands-on engineering support. Their services include: Architecture reviews to assess current voice infrastructure Migration planning to ensure smooth transitions Platform assessments to identify improvement areas Execution oversight to keep projects on track By giving service providers and enterprises direct access to experts across Metaswitch, Ribbon, BroadSoft, NetSapiens, Vox Matic helps organizations make informed decisions and implement changes confidently. Network operations center monitoring voice communication systems Why Choose Vox Matic for Voice and UC Engineering? Choosing Vox Matic means gaining access to senior engineers who understand the nuances of voice and UC platforms. Their experience spans multiple vendors and technologies, providing a broad perspective that benefits your projects and operations. Key advantages include: Speed: Immediate access to experts reduces project delays. Cost-effectiveness: Pay for the support you need without full-time salaries. Expertise: Deep knowledge of Metaswitch, Ribbon, BroadSoft, and NetSapiens platforms. Flexibility: Support available on demand or for defined projects. Reliability: Proven track record in maintaining and upgrading critical voice infrastructure. Moving Forward with Expert Voice Engineering Support For telecom organizations facing tight deadlines, complex projects, or gaps in senior engineering resources, Vox Matic offers a practical solution. By giving service providers and enterprises direct access to experts across Telecom platforms Vox Matic removes the barriers of hiring delays and high costs.
- Who Owns What During a NetSapiens Migration? A Responsibility Guide for Service Providers
In a NetSapiens migration, the service provider typically leads source access, customer communications, business decisions, and cutover approval. The migration partner performs the technical activities defined in the agreed scope and provides migration-specific assistance where required. Responsibilities should be documented during scoping because the exact division varies by engagement. A NetSapiens migration involves more than moving subscriber data between platforms. Service providers and migration partners need to coordinate access, discovery, provisioning, validation, customer communications, and cutover decisions. When responsibilities are unclear, even straightforward migration tasks can be delayed. This guide gives you a practical way to frame that conversation before the project starts. Key Takeaways Responsibilities vary by engagement and should be agreed during scoping, not after work begins. Service providers usually handle the areas tied to their business: source access, customer communications, segmentation, and cutover approval. Migration partners perform the technical migration activities included in their scope, with automation supporting repeatable extraction, transformation, provisioning, and validation processes. Exception resolutions, acceptance criteria, and cutover readiness require clearly assigned technical and business decisions. Unclear responsibilities can create delays, duplicate work, and unnecessary confusion during migration. What Does a NetSapiens Migration Responsibility Matrix Look Like? Responsibilities vary by engagement, but the following table provides an example of how work may be divided between a service provider and its migration partner. The exact ownership should be agreed during scoping. Activity Primary Responsibility Migration-Partner Role Decision or Approval Source access Service provider Defines required access and verifies connectivity Access method, security requirements, and timing Discovery Service provider and migration partner Assesses data, configurations, integrations, and tech requirements Scope, assumptions, dependencies, and exclusions Customer segmentation Service provider Advises on technical complexity and migration readiness Service provider approves migration groups and sequence Data transformation and provisioning Migration partner Performs or supports automated transformation and provisioning activities included in the engagement Provider approves applicable configuration standards and profiles Exception handling Assigned according to exception type Identifies migration-related exceptions and presents available technical options Provider approves resolutions affecting customers, services, or business requirements Validation Assigned according to the validation plan Performs automated and technical checks included in the migration scope Provider confirms business acceptance and authorizes progression Customer communications Service provider Migration partner (timing and technical detail) Messaging around cutover dates Carrier and number routing Service provider or its carrier Coordinates migration dependencies within the agreed scope Provider authorizes routing changes and timing Cutover approval Service provider Reports on the readiness of migration activities within its scope Provider makes the final go/no-go decision Post-cutover verification Provider engineering and support Assists with migrated data, configurations, transformation rules, or provisioning issues within the agreed scope Provider confirms acceptance or identifies required follow-up This matrix is illustrative. Actual ownership depends on the provider’s operating model, internal resources, technical environment, and the agreed migration and support scope. Responsibilities, decision rights, escalation paths, and acceptance requirements should be documented before work begins. What Does the Service Provider Usually Handle? Source access. The migration partner requires the agreed level of source access before extraction, detailed technical assessment, or other access-dependent activities can begin. Credentials, permissions, API access, and data exports usually come from your team, and timely access helps downstream work proceed as planned. Our guide to telecom migration prep covers what to line up early. Customer segmentation. Grouping customers into migration stages, identifying high-touch accounts, and flagging contractual sensitivities requires business knowledge your team holds. In multi-tenant environments, migration groups may be organized by domain, reseller, customer type, configuration, technical complexity, or operational priority. Customer communications. Your customers have a relationship with your brand. Communicating what is changing, when, and what they need to do usually stays with you, with your migration partner advising on timing and technical detail. Our guide on how to reduce churn during a telecom migration covers what customers should hear and when. Carrier routing and cutover approval. Carrier routing, number-porting, and SBC changes may require coordination among the provider, its carriers, platform administrators, and migration partner, depending on the engagement. The decision to proceed with cutover usually rests with you, once technical readiness has been confirmed. What Does the Migration Partner Usually Handle? The migration partner performs the migration activities included in the agreed scope and provides technical assistance for migration-specific issues where required. Otto™, Vox Matic's proprietary automated telecom migration framework, automates repeatable extraction, transformation, provisioning, and validation activities across the migration workflow. By applying automated validation checks to source and target data, Otto can identify discrepancies before cutover. Depending on the engagement, the provider's engineers can manage the migration workflow and engage Vox Matic specialists when assistance is required with exceptions, testing, complex configurations, validation issues, or cutover planning. Migrated configurations can be built and tested in a sandbox environment, a non-production NetSapiens setup, and validation can include client-side checks in end-user apps such as SNAPmobile. The NetSapiens migration data validation checklist shows what that review covers. After cutover, the partner typically leads the agreed technical verification activities. The Post-Migration Verification Playbook covers what gets checked once customers are live. Which Decisions Require Coordination? Shared activities need the clearest agreements, because each side can assume the other is handling them. Discovery scope: The partner leads the technical inventory, but you know which accounts have custom or grandfathered arrangements. Exception decisions: When a subscriber or configuration does not migrate cleanly, the partner presents the options and technical implications. You decide based on business context and customer relationships. Validation sign-off: The partner runs the technical checks. You confirm that what has been validated reflects what your customers need. Cutover go/no-go: The partner confirms technical readiness, and you confirm business readiness. Both are required before cutover. A regular check-in rhythm between both teams helps keep these decisions moving. When Should Responsibilities Be Agreed? Before the project starts, ideally during scoping. A clear ownership model can help decisions move on time, reduce duplicated work, and keep customer communications planned rather than reactive. If a prospective partner has not raised the topic, it is worth raising it yourself. Our list of questions to ask a NetSapiens migration partner includes this and other topics to cover before you sign. For platform-specific detail, see our Metaswitch to NetSapiens migration page and our BroadWorks to NetSapiens migration guide. Planning a NetSapiens Migration? Vox Matic has completed automated migrations of thousands of subscribers from Metaswitch and BroadWorks environments to NetSapiens. As a NetSapiens Ecosystem Partner, Vox Matic can help define how migration responsibilities could be structured for your environment. Request a Migration Assessment: Discuss your current platform, timeline, and migration objectives. Identify automation opportunities, project risks, responsibilities, and the most effective migration approach. Request your Migration Assessment. It's that simple! Frequently Asked Questions Who is responsible if something goes wrong during cutover? Responsibility depends on the issue and the agreed project scope. Technical problems may involve the migration partner, the provider's engineering team, or the platform vendor. Defining ownership and escalation procedures before cutover helps issues reach the appropriate team quickly. Can the migration partner handle customer communications on our behalf? It depends on the engagement. Providers often keep customer communications in-house because the relationship is with their brand, while the migration partner advises on timing and technical detail. Whatever the arrangement, it should be agreed before customers are notified. What happens when the migration process surfaces an exception? Exceptions may be identified during discovery, transformation, provisioning, or validation. The migration partner can explain technical options for migration-related exceptions, while the provider approves decisions affecting customers, services, business rules, or operational policy. How much of my team's time does a NetSapiens migration require? It varies by engagement. Provider time is often concentrated at key decision points, such as source access setup, segmentation review, exception approvals, and cutover authorization. Automation can reduce repetitive manual work, but the provider still needs to supply technical information and make informed business, acceptance, and cutover decisions. When should we discuss responsibilities with our migration partner? During scoping, before work begins. Agreeing the responsibility model early gives both teams a shared reference point when decisions come up mid-project. If your migration partner has not raised it, it is worth starting the conversation yourself.












