Data migration involves importing data from your previous platform into Chargebee. This includes information associated with customers, subscriptions, credit notes, and historical invoices. For more information about data eligibility for migration, contact the Chargebee Migration Team.
If you have moved to a new gateway and want to map the new card tokens to your customers, refer to the document on migrating cards.
This help document outlines the steps involved in data migration when you have submitted a request to our Migration Team. If you want to self-migrate data, see our documentation on Self Migration.
To prevent errors on the Live site during migration, the process is first carried out on the Test site. Once successful, it is repeated for the Live site.
Steps Involved
Complete your Chargebee site setup. Try a few mock transactions to ensure the flow works as expected.
Raise a migration request in your Chargebee app. Click Settings > Import and Export Data > Bring Data into Chargebee.
Our migration team will reach out to understand your requirements and share the migration sheet via Google Drive, which you must complete.
We recommend onboarding all new customers to your Chargebee site during the migration period. Any additions to the original import data may cause delays.
Coordinate with the migration team to determine the best window for migration.
Upon successful migration, Chargebee will handle all billing activities for imported subscriptions.
After migration, Chargebee will manage all further billing for your imported subscriptions.
Note: Cancel all subscriptions in your existing billing system only after the Live site import. This ensures your customers are not billed twice.
Note
Review the data thoroughly in the Test site before importing to the Live site. Changes made to your Live site are irreversible.
For migration-ready subscriptions renewing on the date of migration, the renewal date can be moved forward by about two or three days, based on your preference. This gives you time to review the imported subscriptions before they renew. Alternatively, you can allow these subscriptions to renew in the existing system and migrate them later into Chargebee.
By default, Chargebee will not trigger any webhooks or send email notifications to customers during import. However, this can be enabled if required.
All required fields must be updated in the migration sheet in CSV format to avoid unexpected delays.
For additional safety, we recommend using Google Sheets or Docs when sharing data with us.