What happens in ChartMogul when I switch billing systems?

Switching billing systems is a common business practice. Many of our customers have done it, and we've even done it ourselves. In this article, we outline what happens during a billing system switch, how it impacts your data, and the steps to correct your metrics.

Here's what we cover in this article: 

What happens in ChartMogul during a billing system switch

The exact configuration of settings in your billing system or data settings may impact your data and metrics differently.

When you add your new billing system as a data source and import subscription data, you'll notice the following changes in ChartMogul: 

  • Duplicate customer profiles — Your customers will exist in two billing systems and two data sources. ChartMogul creates duplicate customer profiles even when customers have the same email address or external ID.
  • Multiple data sources — It's recommend to keep your old billing system as a data source to retain customer invoice history. ChartMogul uses invoice data to generate subscriptions, so retaining a customer's invoice history retains their subscription history. For example, let's say you have a customer who started a subscription in September 2019 in Stripe and your business migrates to Chargebee in June 2022. The customer will be reported as New Business from Chargebee in June 2022 and if the Stripe data source is deleted, their subscription history will be lost.
  • Inflated MRR and subscriber metrics — Adding a new data source initially creates a large number of New Business and Churn movements.

Understanding the data

To visualize how a billing system switch impacts your metrics in ChartMogul, let's look at the MRR chart and customer list. 

MRR Chart

  1. Navigate to Monthly Recurring Revenue.
  2. Click ADD FILTER.
  3. Select Data source > is one of > select your old billing system > click ADD.
  4. Click NEW SEGMENT and repeat step 3, selecting your new billing system.

Your chart will show a decrease in MRR from your old billing system, and an increase in MRR from your new billing system.
datasourcecompare.png

Customer List

  1. Navigate to Customers.
  2. Click the Customer column header to sort the list by name to easily view duplicate customer profiles.
    customer.png
  3. Click EDIT COLUMNS and select Data Source Name:
    customer2.png
  4. Now, you can clearly see which data source each customer is from and their current subscription status.
    customer3.png

Correcting your metrics

To have your customer and subscription metrics reported accurately in ChartMogul, merge duplicate customers and connect their subscriptions.

Merge duplicate customers

Merging customers is permanent and cannot be undone.

First, merge duplicate customers so all of their subscriptions, attributes, and transactions are in the same profile.

Let’s look at Cindy as an example. Cindy now has a profile from the original data source and the new data source. She also contributes to churn events and new business events on the charts.

The following happens when merging customer records:

  • The merged customer will have the UUID, email address, and location of the customer that they are being merged into.
  • Both customers’ external IDs, tags, custom attributes, and notes will be preserved.
  • Subscriptions, MRR movements, and transactions will be collated and ordered by date.
  • If the same custom field exists on the customer record that you are merging into, the field value of the target customer will be preserved, and the one from the source customer will be lost.

This is Cindy’s original profile:

cuspro1.jpg

This is Cindy's new profile:

cus_pro_2.jpg

Cindy has more data in the second profile, so we’ll merge the first profile into the second profile.

  1. Navigate to the profile with less data or older data that should be updated.
  2. Click Merge.
  3. Choose the customer you want to merge into. ChartMogul provides suggestions based on email or external ID. If you don't find a match, you can also search.
  4. Select the customer and click Next.
  5. Check the details and then click Confirm and Merge.

We now have one profile for Cindy, will all of her details including:

  • The external IDs from the old and new data sources.
  • A merged-customer tag.
  • The Subscriber since date from her first subscription.
  • A record of her net payments.

The profile contains her entire subscription and transaction history from both profiles:

mergedprofile.jpg

mergedprofile2.jpg

Merging customers can be done manually through the ChartMogul interface or programmatically with the API. Learn more about merging customers programmatically.

Connecting Subscriptions

When the old and new customer profiles have been merged, the customer will still have two subscriptions, one churn movement, and one reactivation movement.

With everything in one profile, use the data editing tools to connect the two subscriptions and remove the false churn and reactivation movements.

You can only connect a canceled subscription to an active subscription and subscriptions paid for in the same currency. Make sure that all of the subscriptions are canceled in the old data source to proceed.

  1. In the customer profile, scroll down to Monthly Recurring Revenue and click CONNECT SUBSCRIPTIONS.
    connect1.jpg
  2. Click both subscription lines.
    connect2.jpg
  3. Click CONNECT.
    connect3.jpg

With the subscriptions connected, the false churn and reactivation events have been removed.

Before connecting subscriptions, Cindy has two subscriptions: one Active and one Cancelled. Her MRR movements are reported as a New Business movement from the original billing system, an Expansion movement from the new billing system, and a Churn movement from the original billing system.

connect4.jpg

After connecting subscriptions, Ciny has one subscription and one MRR movement.

connect5.jpg

Connecting subscriptions can be done in-app or programmatically with the API. Learn more about connecting subscriptions programmatically.

Please contact support if you need further assistance.

Was this article helpful?