Scope

How do I remap customers in Salesforce version (1.46+)?

Summary

The Chargebee-Salesforce integration supports 1:1 mapping between customers (Chargebee) and Accounts (Salesforce). If a customer record is already synced to Salesforce but was not mapped to the preferred Account due to any reason, you can make a correction from your end by resyncing the record to the right account. If the currently mapped account should not be deleted, you can unlink the Chargebee mapping by navigating to the Account page and removing all values from the following fields:
1. ‘Chargebee ID'
2. Is Synced’ [uncheck the box]
3. ‘Chargebee Site’

Step 2: Once the above step is completed, navigate to Chargebee Settings in Salesforce → Advanced Actions → ‘Retrieve Past Data’ → Fill in the details along with the Chargebee ID and hit 'Retrieve’ as highlighted below:

If the sync rules point the customer record to an already synced Account in Salesforce, it would appear as a duplicate error, as detailed here.

Solution
Step 1: If the currently mapped account is not of any significance, you can go ahead and delete the account in Salesforce.
(OR)
If the currently mapped account should not be deleted, you can unlink the Chargebee mapping by navigating to the Account page and removing all values from the following fields:
1. ‘Chargebee ID'
2. Is Synced’ [uncheck the box]
3. ‘Chargebee Site’

Step 2: Once the above step is completed, navigate to Chargebee Settings in Salesforce → Advanced Actions → ‘Retrieve Past Data’ → Fill in the details along with the Chargebee ID and hit 'Retrieve’ as highlighted below.

Now, once this is performed, the individual Chargebee record referenced will be resynced according to the sync rules in Salesforce at the time, and you can track the status in the sync health section to see if it succeeded or failed. This type of sync will be named as ‘Targeted' as opposed to 'Schedule’ which is for regular auto-sync.

This feature allows syncing of only the referenced Chargebee object based on the ID provided, so if there are invoices and subscriptions already synced under the previous mapping, they will not be corrected retrospectively.