NetSapiens Billing and CDR Migration: How to Protect Revenue During Platform Consolidation
Protecting revenue during a NetSapiens migration means keeping billing records, usage data, and invoices aligned as each customer moves. Confirm what each customer is billed for before cutover, plan how call detail records (CDRs) from both platforms will be collected and reconciled, and review charges before the first invoices go out.
Platform migrations are usually planned around users, devices, and call flows. Billing often sits outside the voice platform, in a separate system fed by service records and CDRs, so it can be treated as someone else’s problem until the first invoice goes out.
That is when gaps show up: a number that was migrated but never billed, usage that was rated twice, or a tax line calculated from an outdated address. For providers consolidating from Metaswitch or BroadWorks into NetSapiens, billing deserves its own place in the migration plan.
Key Takeaways
Billing systems depend on service and usage data from the voice platform and other systems, so a platform change affects billing even when the billing system itself does not change.
Recurring services, numbers, usage, taxes, and reseller billing should each be checked against the NetSapiens environment before cutover.
During a phased migration, billing may need to process CDRs from both platforms, with clear rules for attribution and reconciliation.
Historical CDR retention should be settled before the legacy platform is retired.
Charges for migrated customers should be reviewed before the first invoices are issued, while differences are still easy to trace.
Why Is Billing a Migration Risk?
Billing systems often rely on service records, usage data, and integrations with the voice platform. Seat counts, feature assignments, phone numbers, and call usage may flow into billing through an integration, regular exports, or connected systems such as CRMs and provisioning tools. When the platform changes, those connections need to be reviewed.
Customers move from the legacy platform into NetSapiens in stages, so for a period the billing system may be receiving data from both. Without a plan, a few common problems can appear:
Missed revenue: Services or numbers are active in NetSapiens but never added to billing.
Duplicate charges: Usage from the cutover period is rated from both platforms.
Incorrect taxes and fees: Charges are calculated from outdated or missing address information.
Mismatched products: Feature bundles in NetSapiens no longer line up with the products being invoiced.
An incorrect invoice is something customers notice quickly, which makes billing accuracy part of protecting the customer experience during migration.
What Billing Data Needs to Be Checked Before Cutover?
Billing Readiness at a Glance
Billing Item | What Can Go Wrong | What to Confirm Before Cutover |
Recurring services | Seats or features billed that no longer exist, or new ones not billed | Provisioned users and features in NetSapiens match each customer’s contracted billing arrangement |
Phone numbers | Numbers active but unbilled, or billed after release | Number inventory in NetSapiens matches billed numbers per customer |
Usage (CDRs) | Gaps or double counting around cutover | How CDRs from each platform are collected and attributed for each customer |
Taxes and regulatory fees | Charges calculated from incorrect information | Billing addresses, applicable tax information, and any separately required E911 location records |
Reseller and wholesale billing | Usage assigned to the wrong account | Reseller and domain structures match billing accounts |
One-time charges and credits | Credits lost or applied twice | Open credits and adjustments stay with the billing system |
Many of these checks overlap with broader migration data validation. The difference is that billing checks compare the platform against what customers are actually paying for.
How Should CDRs Be Handled During Migration?
Call detail records drive usage billing. Three questions matter during a migration.
Collection Across the Cutover Period
During a phased migration, billing systems may need to process usage records from both the legacy platform and NetSapiens. Establish how CDRs will be collected, attributed, and reconciled across the cutover period to avoid missing usage or duplicate charges.
Format Differences
CDR fields, call types, and identifiers differ between platforms. Rating rules in the billing system may need adjusting so that NetSapiens CDRs are classified and priced according to the intended billing arrangement.
Historical Records
Older CDRs are often needed for billing disputes, customer inquiries, and record-keeping requirements. Decide where historical usage will be retained and how it can be accessed before the legacy platform is retired. Whether history is kept in the billing system, archived separately, or imported depends on your requirements.
How Do You Keep Billing in Step With Cutover?
Billing works best as a checkpoint in the migration workflow rather than a separate project that runs alongside it.
Billing dependencies should be discussed during migration planning. Depending on the environment and agreed scope, billing-related checks or updates may be incorporated into the migration workflow.
A Practical Sequence Per Customer or Migration Stage
Before cutover: Confirm billed services, numbers, and address information against the provisioned NetSapiens configuration.
At cutover: Update billing references and confirm how CDRs for the customers moving in that stage will be collected and attributed.
Before invoicing: Review billing records and, where available, draft invoices for migrated customers, investigate unexpected differences, and resolve issues before invoices are sent.
In multi-tenant environments, running these checks by domain or reseller keeps billing aligned with how customers are grouped for migration.
How Do You Reconcile Billing After Migration?
The first billing cycle after cutover is an important opportunity to reconcile charges before customer invoices are issued. Useful comparisons include:
Seat and number counts per customer, before and after
Recurring charges per customer, before and after
Usage volumes for the first period compared with recent averages
Tax and fee lines for customers whose address information was updated
Variances are not always errors. A customer may have dropped unused numbers or changed features during migration. The goal is to explain each difference before the invoice goes out, rather than after a customer calls. Our post-migration verification playbook covers the wider set of checks after go-live.
Where Does Automation Help?
Billing problems during a migration often start with a mismatch: a number or service that exists on one side but not the other. Otto™, Vox Matic’s proprietary automated telecom migration framework, applies automated validation checks throughout data extraction, transformation, and provisioning, helping identify discrepancies in services and numbers before cutover, when they are also easier to address in billing.
Where additional integration is required, Forge™, Vox Matic’s custom automation and workflow development service, can help connect compatible systems and automate repeatable processes. Available functionality depends on the systems, integration options, and agreed project scope.
Retiring a legacy platform can eliminate its related ongoing costs once the platform has been fully decommissioned and the associated obligations have ended.Read abou a business case for retiring legacy telecom platforms. Accurate billing through the transition helps ensure those savings are not offset by lost revenue.
Planning a Migration? Bring Billing Into the Plan.
Vox Matic has completed automated migrations of thousands of subscribers from Metaswitch and BroadWorks environments to NetSapiens. As a NetSapiens Ecosystem Partner, Vox Matic can review the systems around your platform, including billing, during migration planning.
Request a Migration Assessment:
Discuss your current platform, timeline, and migration objectives.
Identify automation opportunities, billing dependencies, project risks, and the most effective migration approach.
It’s that simple!
Frequently Asked Questions
Does migrating to NetSapiens require changing billing systems?
Not necessarily. Providers often keep their existing billing system and change the source of service and usage data from the legacy platform to NetSapiens. The integration, data formats, and rating rules may need updating as part of the migration.
How do we avoid double billing during cutover?
Agree how usage from each platform will be attributed during the cutover period, and establish clear procedures for CDR collection and recurring charges. Reviewing billing records and draft invoices, where available, helps identify overlap before invoices reach customers.
What happens to historical CDRs after migration?
That depends on your requirements. Historical records are often kept in the billing system or archived separately so they remain available for disputes and record-keeping. Retention should be decided before the legacy platform is retired.
Can billing updates be included in the migration workflow?
Depending on your environment and the agreed scope, yes. Billing-related checks or updates can be incorporated into the migration workflow, and billing dependencies should be reviewed during migration planning.
Why do taxes and fees need checking during a migration?
Taxes and regulatory fees are often calculated from the address and account information held in the billing and tax systems. If that information is outdated or changes during migration, charges can be calculated incorrectly. Confirming the information your tax and billing systems actually use before cutover helps keep those lines accurate.
Comments