Moving from 3CX, Metaswitch, BroadWorks, FreePBX or Switchvox? NCS runs beside it while you move. See how

Moving from 3CX?

We help you move to NCS one module at a time, with your 3CX setup carrying calls until you switch it off.

Plan your move with us Moving from something else

How we help you move

Plan the move with our team

We map your tenants, numbers and call flows with you, and choose the first module and the customers to pilot it with.

Start beside 3CX

The first NCS module goes live alongside your 3CX setup. Nothing is switched off, and your customers keep calling as they do today.

Move tenants when you are ready

Tenant by tenant, on your schedule, timed to your own contract renewal if you like.

Switch 3CX off last

Only when nobody depends on it anymore.

What stays the same

Your SIP carrier and your numbers. NCS works with any SIP server, so nothing is ported on day one.

Are you ready to move from 3CX?

Tick what you already have. Nothing has to be complete before we talk; the list simply becomes the brief for your scoping call.

When your current 3CX agreement renewsA list of your tenants, and roughly how many users each hasYour numbers, and which carrier holds themYour SIP trunk detailsThe desk phone models your customers useYour IVR menus, ring groups and office hoursAny contact center queues you runThe customers who would pilot the first module

0 of 8 ready. Nothing here has to be complete before we talk.

Send my checklist with a request

No cutover weekend. Three steps.

1
One module goes live beside it
Your current platform keeps carrying every call.
2
Customers move when it has earned them
Tenant by tenant, on your schedule.
3
The old platform is switched off last
When nobody depends on it anymore.

How adoption works, in full →

Questions about moving across.

The first NCS module goes live beside your current platform, which keeps carrying calls exactly as it does today. NCS works over SIP with what you already run, so the two systems coexist: same numbers, same carrier, same customers. Customers move to the new module when it has proven itself with real calls, at the pace you set. Nothing is switched off until nobody depends on it. That is why there is never a cutover weekend.

You start with one module, most often the softphone your customers see, because it changes their experience without touching what carries the call. Every provider in production today started this way. Each next module is adopted the same way: switched on beside what exists, proven with real traffic, then relied on. The spend follows the rollout, and the risk never piles up into one migration.

Yes. NCS works with any SIP server and is compatible with Asterisk and FreePBX. Bring your own carrier and keep your numbers. Nothing has to be ripped out before the first module goes live.

No. You keep your carrier and your numbers. The first module runs beside your current platform, so nothing is ported on day one.

The timing of a port is set by the carrier releasing the numbers. We plan each move around it, and calls keep flowing on your current platform until the port completes.

Setup takes from a few hours to a couple of days. After that the pace is yours: a pilot with customers you choose, then tenants move, then the old platform is switched off, timed to its renewal if you like.

Their numbers stay the same. If you start with the app, the new app is the change they see.

Yes. We plan the first module, the pilot customers and the order of the rest with your team before anything goes live.

More on moving across →Did not find your question? Ask us →

Moving from something else?

Moving from

Metaswitch

Start with one module beside the platform you run today.

Moving from

BroadWorks

Move tenants on your own timeline, one module at a time.

Moving from

FreePBX

NCS is compatible with FreePBX and Asterisk.

Moving from

Switchvox

Plan your move with our team, one module at a time.

3CX, Metaswitch, BroadWorks, FreePBX, Switchvox and Asterisk are trademarks of their respective owners. Netstratum and NCS are not affiliated with, endorsed by or sponsored by them. These names are used only to identify the platforms providers move from and to describe compatibility; nothing on this site describes or assesses those products.