NetSapiens Device Migration Guide: Desk Phones, ATAs, Softphones and Provisioning

Device migration is one of the most visible parts of any BroadWorks or Metaswitch to NetSapiens migration. While platforms, databases and configurations run in the background, users immediately notice when a phone, ATA or softphone is not working after cutover. Proper planning, device mapping and automated migration workflows help ensure a smooth transition with minimal disruption.

For many end users, their phone or app is a highly visible part of the service. If an endpoint does not register or work as expected after cutover, users may experience a service issue even when the rest of the migration has gone to plan. That makes endpoint planning an important part of a Metaswitch or BroadWorks to NetSapiens migration.

This guide covers the planning side of device migration: what to inventory, which decisions to make and how desk phones, ATAs and softphones differ.

Key Takeaways

• An accurate device inventory, including models, ownership and customizations, provides the basis for endpoint planning.

• Compatibility decisions help determine which devices are reused, reconfigured or replaced.

• Standard device configurations can make endpoint provisioning more consistent across customers and device types.

• Redirection methods vary by device and environment, and some steps may require provider or on-site involvement.

• Desk phones, ATAs and softphones each need their own testing approach.

  
  

What Should a Device Inventory Include?

Device planning starts with an accurate view of what is in the field. In large BroadWorks and Metaswitch environments, device records are often spread across multiple systems or contain historical inconsistencies.

Device inventory validation before migration helps reduce provisioning issues and cutover delays. A useful inventory captures:

• Make and model of each endpoint

• Ownership: Whether the device is provider-owned, leased or customer-owned

• Device users: Which users and line appearances each device serves

• Customizations: Programmable keys, busy lamp fields, shared lines and other device-specific settings

• Location: Which customer site the device sits in, for redirection and E911 purposes

• Provisioning method: How the device currently receives its configuration

  
  

Depending on the source platform and available data, Vox Matic can extract device records, user associations and supported configuration details for mapping into NetSapiens devices and applicable provisioning configurations. Settings that cannot be extracted or mapped directly may require engineering review. The BroadWorks to NetSapiens migration page shows how devices typically map at a glance.

Which Devices Can Be Reused?

Compatibility decisions can affect both the budget and the cutover plan.

Device Decisions at a Glance

Decision	When It Applies	What to Confirm
Reuse without replacement	The model is compatible and can continue operating after the required provisioning or registration changes	Supported firmware and provisioning method
Reuse with changes	The model is supported but needs updated device configuration settings or a firmware update	Firmware update responsibility and timing
Replace	The model is not supported or is due for replacement	Replacement timing, shipping and on-site support
Retire	The device is no longer in use	Removal from the inventory and billing

Firmware compatibility and updates are typically handled by the provider or its device vendor and should be planned before cutover rather than during it.

How Do Standard Device Configurations Help?

Device configurations define how each device type is set up, including registration settings, line keys, feature buttons and display options. A standard set of device configurations can help keep endpoint provisioning consistent across customers and may make troubleshooting easier after go-live.

A migration can also provide an opportunity to reduce device-by-device customization. Customer-specific settings, such as programmed keys or shared line appearances, should still be preserved where they are part of the agreed customer requirements.

Device standardization also creates opportunities for ongoing operational efficiency. Forge™, Vox Matic's provisioning automation platform, can help service providers maintain consistent device deployment standards after migration while reducing manual provisioning activities.

How Are Devices Redirected to NetSapiens?

Redirection is the step that moves an endpoint from the legacy platform to NetSapiens. For large service providers with thousands of deployed endpoints, coordinating device redirection manually can significantly increase project timelines and operational overhead. Depending on the device type and environment, it may involve:

• Updating provisioning server settings so devices pick up their new configuration

• Using a device vendor's redirection service, where available

• On-site or user-assisted steps for devices that cannot be redirected remotely

  
  

Redirecting IP phones at the customer location can be part of the migration workflow, depending on the environment and agreed scope. After redirection, registration and essential calling functionality should be verified, with a plan for endpoints that do not work as expected.

How Do Desk Phones, ATAs and Softphones Differ?

Desk Phones

Desk phones are often the largest group. Testing should cover registration, inbound and outbound calls, line keys, busy lamp fields, voicemail access and any shared line appearances.

ATAs

Analog telephone adapters often support fax machines, analog lines and other connected devices that customers may still depend on. Fax and analog services should be identified during inventory and tested specifically, since they can behave differently from standard voice calls.

Softphones

Softphones and mobile apps typically depend on user credentials and sign-in rather than physical redirection. Any changes for users should be identified in advance, so they can be guided through them. Where required, the provider or customer may also complete client-side testing in end-user applications to confirm that users can place and receive calls after cutover.

For the wider set of checks after go-live, see our post-migration verification playbook.

Where Does Automation Fit in Device Migration?

Device migration frequently involves thousands of phones, ATAs and softphone users across multiple customers and locations. Manually collecting device information, validating records, mapping users and preparing provisioning data can consume significant engineering resources and increase project risk.

Otto, Vox Matic's proprietary migration automation framework, automates the extraction, transformation and validation of supported device records, user associations and migration data. Automated validation checks help identify exceptions before cutover, improving migration consistency while reducing manual effort during Telecom Migration.

Combined with Forge provisioning automation, service providers can accelerate both migration and post-migration operations while maintaining consistent device deployment standards.

Planning a BroadWorks or Metaswitch Device Migration?

Vox Matic has successfully migrated thousands of subscribers from BroadWorks and Metaswitch platforms as a NetSapiens Ecosystem Partner, using its automated migration framework. Whether you're evaluating endpoint compatibility, provisioning requirements or large-scale device migration strategies, our team can help identify the fastest and lowest-risk path forward.

Request your Migration Assessment:

Discuss your current platform, migration objectives and target timeline. Identify automation opportunities, device compatibility requirements, project risks and the most effective migration approach.

It's that simple!

Metaswitch and BroadWorks are trademarks of their respective owners. NetSapiens is a trademark of Crexendo, Inc. Otto™ and Forge™ are trademarks of Vox Matic.

Frequently Asked Questions

Can we reuse our existing phones when moving to NetSapiens?

Often, yes. Devices that are supported for NetSapiens endpoint provisioning can typically be reused after the required provisioning or registration changes, sometimes with updated device configuration settings or a firmware update. Unsupported or older models may need replacement.

Who handles firmware updates during a device migration?

Firmware updates are typically handled by the provider or its device vendor. Compatibility should be confirmed and updates planned before cutover.

How are phones redirected to NetSapiens?

Depending on the device and environment, redirection may involve updating provisioning server settings, using a vendor redirection service or on-site steps. Registration and essential calling functionality should then be verified for each device.

Do ATAs need special attention during migration?

Yes. ATAs often support fax machines and analog lines, which can behave differently from standard voice calls. These services should be identified during inventory and tested specifically.

What changes for softphone users?

Softphone and mobile app users typically sign in with new credentials or settings rather than having a device redirected. Clear communication about any changes and, where required, client-side testing can help guide users through the transition.

Can Device Migrations be automated?

Many aspects of device migration can be automated, including extraction of supported device records, user associations, validation checks and provisioning preparation. Physical activities such as hardware replacement or certain on-site tasks may still require human involvement.