Migrations
Bring your customers onto one platform.
Whether you’re a carrier moving off an end-of-life platform or an MSP running a fleet of single-tenant systems, the destination is the same: one multi-tenant platform you control — not a per-customer-instance product, not a single-tenant PBX, not a SaaS that competes with you for the end customer.
BroadWorks reached end of sale and Metaswitch is consolidating inside Microsoft, so carriers need a modern home for thousands of seats. At the same time, MSPs on 3CX or Yeastar are tired of adding a new system for every customer they win.
Thirdlane is a true multi-tenant platform built for the channel. These pages cover what a migration actually looks like — from the business case down to how we cut each customer over without disruption.
Bottom line
Thirdlane migrates operators and MSPs from BroadWorks, Metaswitch, 3CX, Yeastar, FreePBX, and other systems onto one multi-tenant platform they control. Every migration follows the same shape — inventory, run in parallel, cut over per customer without downtime, then archive the legacy platform.
When to start planning
If three or more of these are true, you’re past the point where waiting is the cheap option. The cheaper move is to put a plan on a slide before the next renewal cycle locks you in.
- You’re operating a fleet of single-tenant PBX installs (one per customer) and ops cost is rising faster than revenue.
- Your platform vendor’s end-of-sale or roadmap schedule is forcing the conversation, not your strategy.
- Your platform vendor competes with you for end-customer revenue, or has signaled they will.
- You’re stitching UC, contact center, recording, AI, CRM, and messaging together from separate procurements.
- Your reseller channel is asking about your migration plan and you don’t have a public answer.
- The last major version of your platform forced license re-purchase or material restructuring — and the next one will too.
- Per-seat licensing is squeezing margin on the enterprise tenants you most want to keep.
- You can’t credibly serve a multi-site enterprise customer without spinning up a PBX per site.
From BroadWorks
End-of-life consolidation, with the operator workflows your team already knows.
For service providers planning their post-Cisco-EoL move. Thirdlane preserves the multi-tenant, channel-friendly economics of a BroadWorks footprint without inheriting the licensing model or the carrier-grade procurement floor.
Read the playbook →From Metaswitch
A modern multi-tenant platform for the post-Microsoft-acquisition reality.
For operators who built UCaaS on Metaswitch and need a path forward as the product roadmap consolidates inside Microsoft. True multi-tenant, MSP-friendly licensing, and modern admin tooling — without abandoning the multi-tenant operating model.
Read the playbook →From 3CX
One platform instead of a separate 3CX system for every customer.
For MSPs running a fleet of single-tenant 3CX installs. Consolidate onto one platform you control — lower cost to run, better margins, your brand on the apps, and a move that doesn’t disrupt your customers.
Read the playbook →From Yeastar
One platform with no size ceiling for your Yeastar customers.
For MSPs managing per-customer Yeastar P-Series systems. Bring every customer — of any size — onto one platform, with better economics, your own branding, and no appliance swap when a customer grows.
Read the playbook →Migrations — frequently asked questions
Which platforms can I migrate to Thirdlane from?
Thirdlane publishes migration playbooks for BroadWorks, Metaswitch, 3CX, and Yeastar, and also handles FreePBX/FusionPBX consolidations, custom Asterisk builds, Kazoo deployments, and a long tail of older proprietary systems. The destination is the same: one multi-tenant platform you control.
How does a migration to Thirdlane work?
Migrations run in phases: inventory and shape, a parallel Thirdlane platform stood up alongside the existing system, per-customer or per-tenant cutover on a schedule you control, and archival of the legacy platform. Extensions, numbers, auto-attendants, queues, and voicemail carry over.
Will migrating disrupt end customers?
No. Phones keep working through the switch and people keep dialing the way they always have. Cutover happens one customer or tenant at a time, and the old system stays available until everyone is settled.
Why consolidate onto a multi-tenant platform?
Running one platform instead of a fleet of single-tenant systems lowers cost to run, improves margins, and removes the need to stand up a new system for every customer you win — with white-label apps under your brand and contact center, CRM, messaging, and AI included.
Coming from another platform?
We also work with operators migrating from FreePBX/FusionPBX consolidations, custom Asterisk builds, Kazoo deployments, and a long tail of older proprietary systems. The pattern is the same: true multi-tenancy on one platform, white-label apps under your brand, and a per-tenant cutover that doesn’t disrupt end customers.
- FreePBX / FusionPBX shops consolidating fleets of single-tenant installs onto one multi-tenant platform.
- Asterisk-based custom builds where the operator wants the platform but not the maintenance burden.
- Kazoo deployments looking for a more conventional admin and a deeper out-of-the-box feature set.
If you’re comparing platforms before committing to a migration, the comparison hub covers Thirdlane vs 3CX, Yeastar, Bicom Systems, and NetSapiens.