STAY. MIGRATE. CONSOLIDATE?

Metaswitch: A practical cost comparison.

Which path makes the most financial sense over the next 24 to 36 months? That is the decision facing every provider still using Metaswitch.

Microsoft ended Metaswitch development on June 3, 2024, laying off the majority of its sales, engineering, and professional services workforce. Alianza acquired the platform on March 4, 2025. Two ownership changes in five years does not provide the stability needed for long-term platform planning.

Staying has a price: licensing, engineering overhead, dual-platform support, and churn exposure. None of those appear as a single line item, which is why they accumulate undetected.

This post gives you a framework to model that decision across three subscriber tiers: 500, 2,000, and 10,000.

Key Takeaways

• Legacy platform costs are not just licensing fees. Engineering overhead, dual-platform support, and churn risk are often the larger line items.

• Manual migrations carry significant hidden labor costs that scale with subscriber volume.

• Automated migration with Otto reduces engineering hours, compresses timelines, and accelerates ROI.

• Automation can accelerate break-even by reducing engineering costs and retiring the legacy platform sooner.

• Consolidating onto NetSapiens via automation is the highest-ROI path for providers managing more than one legacy platform simultaneously.

  
  

The Real Cost of Staying on Metaswitch

Most providers spread Metaswitch costs across multiple budget lines. No single one triggers a review, which is how the total stays invisible.

Six cost categories belong in any honest analysis:

• Legacy platform licensing and support fees: Maintenance contracts rarely decrease as the platform ages. In many cases, they increase as the vendor shifts investment elsewhere.

• Engineering overhead: CSPs spend over 60% of their budgets maintaining legacy infrastructure (Alianza white paper). Engineers working on a platform with no development roadmap are not working on growth. That cost does not show up as a line item.

• Dual-platform support: Providers already running a partial NetSapiens deployment are paying to maintain two environments simultaneously, and that overhead grows with each passing month.

• Integration debt: Legacy platforms require increasing customization to connect with modern UCaaS and analytics tools. That work is billed once but maintained indefinitely.

• Churn risk from feature gaps: Subscribers on legacy platforms do not have access to the same feature set as those on modern platforms, which creates competitive vulnerability over time.

• Deferred migration cost: Delaying does not eliminate migration expense. It defers it, and delayed migrations are almost always more complex and more expensive.

  
  

These costs do not appear together on a P&L, which is why most providers only see the full number after the fact.

Modeling Your Metaswitch Migration: Three Subscriber Tiers

These are directional models. Apply your actual contract values and engineering rates to see where your numbers land.

Five variables drive the model:

• Legacy platform annual support cost

• Engineering hourly rate (fully loaded)

• Hours per subscriber for manual vs. automated provisioning

• Duration of dual-platform parallel operation

• Churn risk premium from feature gaps

  
  

Break-even formula: Total transition investment ÷ Monthly savings after legacy retirement = Months to ROI

Tier Analysis: Where the Numbers Move

	500 Subscribers	2,000 Subscribers	10,000 Subscribers
Stay	Support contract + 1–2 engineers + churn risk	Growing integration debt, rising churn, meaningful support spend	Substantial overhead on a legacy platform with an uncertain development path
Manual move	20–40 hrs per 100 subscribers; dual-platform carry costs	Parallel operation extends 6–12 months; disruption risk rises	Engineering hours become the single largest project line item
Otto-led transition	Automates provisioning and cutover; shorter project duration	Shortens parallel operation window; reduces per-subscriber effort	Strongest ROI case: lower cost, faster retirement, earlier break-even

Engineering labor and dual-platform carry costs are the two largest variables in any budget. Automation addresses both directly.

Why Automation Changes the Economics

Engineering labor and parallel platform duration are the two costs that determine whether a Metaswitch migration pays off quickly or drags.

Vox Matic's Otto automated migration framework handles provisioning, data migration, and cutover work that consumes most engineering hours in a manual project. It reduces per-account effort from hours to seconds, which changes the economics in two key ways:

• Fewer hours billed reduces gross project spend.

• A shorter project cuts the months you run two platforms in parallel, which stops legacy fees from stacking.

  
  

For most providers, that produces a lower total project cost and an earlier break-even.

Explore the full scope of consolidation services at the Vox Matic network solutions page, or connect with our team to start building your own model.

Frequently Asked Questions

What is the biggest hidden cost of staying on Metaswitch?

Dual-platform support. Providers running a partial NetSapiens deployment alongside Metaswitch pay to maintain two platforms, two engineering skill sets, and two support structures simultaneously. That overhead compounds every month the move is deferred.

At what subscriber volume does automation make the most economic sense?

Automation improves the economics at every tier, but the ROI case is strongest at 2,000 subscribers and above. For providers managing multiple legacy platforms simultaneously, the consolidation case is compelling at any scale.

How long does a Metaswitch to NetSapiens migration typically take?

It depends on subscriber volume, platform complexity, and whether the project is manual or automated. Manual projects at larger tiers can extend 6 to 12 months or more. Automated projects are designed to reduce that timeline by handling the repeatable work that drives most of the engineering hours. See our full Metaswitch to NetSapiens migration guide for a detailed breakdown.

Build Your Own Model

Apply your actual contract values, engineering rates, and subscriber volumes to the framework above. The numbers will point you in a direction.

When you are ready to model the automated path, the Vox Matic team can work through it with you. Start at our network solutions page or review the Otto automated migration framework to see what the timeline and cost structure look like for your environment.

It's that simple!