Telecom Migration Cost and Timeline Calculator
How long will your migration take, and what will it cost while it runs?
Enter your line count, engineering capacity and legacy platform cost. You'll get an estimated manual timeline, the engineering effort involved, and the legacy costs you carry until cutover, with an illustrative comparison to an automated migration.
Automation first. Expert engineering where required.
Estimate Your Migration
Start with four numbers. Defaults are based on Vox Matic's published migration model and can be changed under Assumptions.
Want these numbers checked against your real environment?
Example: Migrating 500 Customers from Metaswitch to NetSapiens
A provider with 500 business customers averaging 10 seats has 5,000 lines to move. At 130 engineering hours a month, a manual migration takes about 7.7 months, 1,000 engineering hours and almost $29,000 in legacy platform costs before the old system can be retired. In the illustrative automated scenario, the same migration finishes about five months sooner.
A Real Migration Benchmark
18 → 6
MONTHS: MANUAL ESTIMATE VS. ACTUAL
< 5
MONTHS TO ROI
Fuse.Cloud estimated its BroadWorks-to-NetSapiens migration would take about 18 months manually. With Otto™, Vox Matic's automated migration framework, it was completed in about six months, with full ROI reported in under five months.
How the Calculator Works
The calculator uses five formulas, shown here so you can check them.
01
Engineering hours
Manual engineering hours = lines to migrate ÷ lines per engineer-hour.
02
Manual timeline
Manual timeline (months) = engineering hours ÷ hours available per month.
03
Labor cost
Manual labor cost = engineering hours × hourly cost.
04
Legacy cost avoided
Legacy cost avoided = months saved × monthly legacy platform cost.
05
Revenue realized sooner
Revenue realized sooner = revenue per line × lines × months saved ÷ 2. Revenue is divided by two because lines move gradually, not all on day one.
1/3
Automated scenario
The automated scenario assumes about one third of the manual timeline. Vox Matic's published 15,000-line model estimates 23 months manually against about 8 automated, in line with the benchmark above.
Not included: the cost of customer disruption, extra support tickets and churn during a long migration, or running two platforms' integrations side by side. Each makes a slow migration more expensive than shown.
Where the Time Goes in a Manual Migration
Most of a manual migration is repetitive work done account by account. That is the work automation removes.
TASK
MANUAL
AUTOMATED
Data extraction
Exported and checked by engineers
Pulled directly from the source platform
Configuration rebuild
Often recreated account by account
Converted to the NetSapiens structure
Provisioning
Entered by hand
Built through NetSapiens APIs
Consistency
Varies by engineer and account
Same logic applied to every account
Engineer time spent on
Data entry
Planning, exceptions, testing and cutover
Example task
About 60 minutes
About 15 seconds, plus a few minutes of checks
Legacy platform
Kept until the last account moves
Retired sooner
Example task time is from one Vox Matic migration. Results vary by task and environment.
Every additional month of migration can mean another month of legacy licensing, infrastructure, support and duplicated platform costs.
Learn how NetSapiens and Vox Matic create a faster path to profitability
Frequently Asked Questions
How much faster is an automated telecom migration than a manual one?
On large migrations, automation can reduce timelines by months by removing much of the repetitive extraction, conversion and provisioning work. Engineers still review, test and manage cutover.
What is the cost difference between a manual and an automated migration?
Manual migrations cost more in engineering hours, and they keep the legacy platform running longer. Automation cuts repetitive labor and shortens the time you pay for two platforms. The calculator above shows the difference for your numbers.
How long does a telecom platform migration take?
A manual migration can run from several months to more than a year, depending on line count, data quality and engineering capacity. Automating the repeatable work shortens that significantly.
What is the fastest way to migrate 500 legacy phone system customers?
Automate the repeatable work, then move customers in planned waves. Extraction, configuration rebuild, provisioning and endpoint conversion take the most time by hand. Validating each wave before cutover keeps speed from costing service quality.
What is the typical ROI timeline for an automated migration?
It depends on how much the legacy platform costs each month and how much sooner it can be retired. Savings come from lower migration labor, ending legacy fees earlier and selling new services sooner. The calculator shows how much each month saved is worth for your numbers.
What does a NetSapiens migration cost for 500 customers?
It depends on seats per customer, source platform, data quality and custom configurations. The larger cost is often a slow migration itself: engineering hours plus months of legacy platform fees. Use the calculator for a planning figure, then request an estimate for your environment.
How much does it cost to keep running a legacy voice platform?
Licensing, maintenance, hardware, hosting, support contracts and the engineers who run it. If NetSapiens is also running, integrations and billing are duplicated too. Enter your monthly legacy cost above to see what each extra month adds.
Get an Estimate Based on Your Environment
The calculator uses averages. A Vox Matic migration specialist can review your platform, line count and configurations, and show you what a migration automated with Vox Matic's Otto™ would look like for your customers.