top of page

Telecom Migration in 2027: Five Shifts Service Providers Should Plan For

3 days ago
10 min read

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.


Timeline of key dates for 2027 planning: FCC copper retirement order (March 26, 2026), BroadWorks Release 24 end of maintenance (end of July 2026), BroadWorks Release 27 general availability (August 2026, planned) and UK PSTN switch-off (January 31, 2027)

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.


Formula: monthly cost of the legacy platform multiplied by months until its last customer moves equals the cost of the dual-platform period, with maintenance, hosting, specialist staff time, duplicate integrations and training in the monthly figure

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.


Chart of NetSapiens users as reported by Crexendo, rising from about 1.7 million in June 2021 to more than 8 million in August 2026

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.


Vox Matic white paper model for 15,000 lines: about 23 months for a manual migration compared with about 8 months automated

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.


From signed order to first invoice: four manual handoffs between CRM, ticketing, voice platform, carrier order and billing, compared with a coordinated workflow where information is captured once

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



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.

Comments


Vox Matic and NetSapiens together for the win

Planning a Migration?

Share your platform and timeline, and our migration team will follow up with next steps for moving from BroadWorks, Metaswitch or Ribbon to NetSapiens.

It's that simple!

Planning a Migration?

Vox Matic has completed automated migration of thousands of subscribers from BroadWorks and Metaswitch to NetSapiens. Save time and reduce migration costs through automation, experienced engineering, and a proven migration process.

​

Share a few details and our team will:

• Discuss your current platform, timeline, and migration objectives.

• Identify automation opportunities, risks, and the most effective migration approach.

How did you hear about us?
Google Search
AI Search (ChatGPT, Perplexity, Claude, Gemini, etc.)
LinkedIn
Referral
Event or Conference
NetSapiens
Other
Vox Matic  It's that simple!

Automated telecom migration powered by Otto.

Company

Solutions

Legal/Contact

3379 Peachtree Rd NE

Suite 700
Atlanta, GA 30326

Phone:

470-284-6303

© 2025 by Nobel Design Group LLC. 

bottom of page