Hi. I don't have anything directly on-topic to contribute here, but I
was hoping that some of the other providers here who've migrated to
Netsapiens and other similar Meta/Broadsoft/Ribbon/DMS/5E replacement
products might be willing to share why they made the move, and what were
the most important features in their chosen product. I'm currently
working on developing a similar SaaS/Hosted (or optionally on prem)
voice switching system, and I'm really interested in what the most
important factors were when you made the move.
Thank you,
Enzo Damato
On 2/16/26 1:05 PM, Mark R Lindsey via VoiceOps wrote:
Voxmatic definitely has a lead in migrations into NetSapiens! They've
got a lot of logic built for pulling in subscribers and moving them
over to NetSapiens.
So, assuming you're using them and have that settled, and focusing
just on the parts that are generally your responsibility even when the
database is loaded:
SIP Devices are typically the biggest labor part of any of these
projects. For Cellular clients (SIMs, not apps), e.g., using Tango,
you can reconfigure it in the core without having to create a new SIM.
For desk phones (Yealinks, etc.) you really want to have your
endpoints managed by the NetSapiens Endpoint Device Provisioning
Server at the end of the process. Sending an update to each device to
get it under NetSapiens management is key part of the work.
For SIP trunks currently talking to Metaswitch or 3CX, a lot depends
on how they were built. If you desire to keep your SBC, e.g.,
Perimeta, then you could retarget the SIP adjacency for each customer
separately and minimize it. But usually we see people migrating over
one SIP trunk at a time, after giving the customer notice of the
change with all the new settings.
During the migration you'll be rerouting calls from the PSTN to the
proper system; e.g., customers that were homed on Metaswitch will then
be on NetSapiens. You'll need to decide if that can be done in the
Metaswitch or in the PSTN carrier. Sometimes it's just easier and
cleaner to establish a new SIP trunk from your provider (Sinch,
Bandwidth, CarrierX, etc.) and "port" the number to your other SIP
trunk rather than setting up internal routing in your own network.
Then you get CDRs/stats from your PSTN carriers telling you which
numbers are on which platform.
But...assuming you're not doing a flash cutover, and so you'll have
Metaswitch and 3CX running at the same time, you certainly can route
calls between the different platforms. We're doing that with a client
that's maintaining another platform while also adding NetSapiens to
the mix.
The NetSapiens core architecture is really interesting - allowing you
to home groups of customers on a particular core server, wtih
synchronization and failover between them. It gives you an entirely
new capability that wasn't available on Metaswitch or 3CX (or
BroadWorks, or Ribbon...but I'm not sure how PortaOne handles it). If
you have customers in different regions or different networks, the
ability to make them "primary" one core server is really useful.
Very likely Voxmatic can help in the management of some of these
elements. And for anybody who sells these softswitch platforms - ECG
is not particularly for or against any softswitch/application server
that works. Almost everything I mentioned above would be the same if
you were moving between any two platforms.
*Mark R Lindsey| +1-229-316-0013 | [email protected] | LinkedIn
<https://www.linkedin.com/in/markrlindsey/>*
On Feb 16, 2026, at 13:08, Shripal Daphtary via VoiceOps
<[email protected]> wrote:
Mike,
I can recommend JJ and Voxmatic. I have worked with his team for
years on different projects.
On Thu, Jan 15, 2026 at 1:34 PM Mike Hammett via VoiceOps
<[email protected]> wrote:
We're about to embark on a migration from Metaswitch and 3CX to
Netsapiens. Have any of you looked at tools or companies like
this to manage the migration?
https://www.linkedin.com/events/7396241683555946496/
-----
Mike Hammett
Intelligent Computing Solutions
Midwest Internet Exchange
DNA Communications
_______________________________________________
VoiceOps mailing list -- [email protected]
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email to [email protected]
_______________________________________________
VoiceOps mailing list -- [email protected]
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email to [email protected]
_______________________________________________
VoiceOps mailing list [email protected]
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email [email protected]
_______________________________________________
VoiceOps mailing list -- [email protected]
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email to [email protected]
