Investigate a churn spike after a SaaS billing migration

Start with the accounts moved between billing systems and the dates their old and new subscriptions changed. Match those accounts to the reported churn and new-business movements. A simultaneous surge in both categories can indicate administrative replacement, but it is only a lead to investigate. Some customers may genuinely cancel or change scope during the same period.

ChartMogul's migration documentation describes how old-system cancellations and new-system subscriptions can inflate churn and new-business reporting. It also explains that preserving continuity can require both merging duplicate customer records and connecting their subscriptions. The exact repair depends on the reporting platform and the underlying customer facts.

Use the migration map, contracts, service periods and invoices to establish continuity. Record the source and destination customer IDs, subscription IDs, final old service date and first new service date. Note any actual gap, price change or product change. A shared name is not enough to conclude that two records are the same continuing relationship.

Separate cases where the customer truly left and later returned from cases where only the billing identifier changed. Preserve genuine losses even if removing them would make the migration report easier to reconcile. Have the commercial owner confirm unusual cases and retain the evidence supporting each classification.

Compare the recurring value immediately before and after migration using the same definition. Identify differences caused by discounts, currency, quantity, billing interval or missing invoice data. The correct reporting repair should preserve a real increase or decrease rather than force every migrated customer to show zero movement.

For illustration, a continuing customer may move from $900 to $960 of monthly recurring value because an approved price change coincides with migration. The administrative cancellation and new subscription should not imply a complete customer loss and acquisition, but the $60 commercial increase still needs an explanation. Keep that distinction in the reconciliation.

Provide the analytics administrator with approved record pairs and expected outcomes. Use the platform's supported merge or continuity mechanism after checking its effects on history and identifiers. Retain a before-and-after export so finance can verify the result and investigate unintended changes. Avoid a broad deletion of all migration-month churn events.

Test a representative group first, including an unchanged customer, a real scope change and a genuine cancellation. Then reconcile the full population. A repair that fixes the headline total while merging unrelated customers can damage retention and acquisition reports for later periods, so identity and history checks matter as much as the total.

Quantify how the repair changed churn, new business, reactivation and customer counts, and whether closing recurring value changed. Keep an explanation with any management report that used the earlier data. Distinguish an analytical correction from a change in the actual commercial results.

Leave the migration map and review evidence with the ongoing reporting owner. Recheck the next period for delayed invoices or imports that recreate duplicate records. The completed deliverable is a reconciled customer history with genuine movements intact, plus a documented reason for the temporary reporting spike.