You can choose to migrate the customer data yourself by making use of the Bulk Operations feature. In case you are worried about dealing with overwhelming data, we have an in-house migration team to migrate your customer data for free the first time around. However, there will be a charge levied for subsequent migration requests to our migration team.
In Chargebee terminology, 'Data Migration' is the process of moving all subscription and payment information from your existing service provider to Chargebee so we can take over the billing of your subscribers.
Data pertaining to Subscriptions including Customer details (name, email address, billing address etc), Subscription status (Trial, Active, Canceled, etc.) and Shipping address, invoices, if present, can be imported into Chargebee.
Equipping Chargebee with your latest invoice data will ensure that any prorated charges on active subscriptions are handled seamlessly during the shift.
We do not take card details directly. We will only need the tokens that represent the card. These tokens are issued by the vault where the cards are stored (Spreedly, Stripe, or Braintree) depending on the payment gateway you're currently using and intend to use with Chargebee. For more information on payment details migration, contact [email protected] .
The migration process ensures that there will be no double billing.
However, you will need to stop taking new sign ups through your existing billing platform. This task will be a part of the migration checklist that we will share with you; we cannot proceed with the migration unless this is done.
As a precaution, if there are any subscriptions that have been scheduled for renewal on the day of migration, the renewal will be postponed by a few days (usually 2 or 3 days, based on your preference). This gives you sufficient time to review all the data in the live site and make changes if needed before renewals start happening in Chargebee. For example, if the migration is scheduled for the 1st of June and a few subscriptions are also scheduled to renew on that date, and you'd like the renewals to be postponed by 2 days, the renewal will happen on the 3rd of June.
While migrating cards, contact your payment gateway and clarify whether 3DS authentication is required for the cards after migration.
Cards already present in your Gateway's vault are considered to be verified, but this might change when the cards are moved to a different vault or when billed using a different billing system.
Contact [email protected] if you need further guidance regarding SCA compliant migration.
To learn more on SCA and 3DS authentication, take a look at our doc on PSD2 regulation and SCA.