To get started, submit a migration request here . Once we receive your request, we will reach out to you with additional questions and details of charges, if any. We will also share a Migration Checklist with you.
You should set up your Chargebee test site with the required product configuration (plans, addons, and coupons), email notifications, etc.
We will also need the Subscription data from you in a CSV file. Instructions on sending the data and the format will be sent to you once we receive the migration request.
In the CSV file containing the Subscription data, you should use the exact ids that are in Chargebee for the plans, addons, and coupons.
In Chargebee, you will find the ids under Product Catalog > Plans as shown below:
The Subscription data that you provide will be cleansed and reviewed by us and then by you. Once the data is ready, we will import all the subscriptions into your Chargebee test site for your verification.
In parallel, you need to setup your live site and start signing up new Customers through Chargebee. This is to ensure that you completely tryout the signup flow and to check whether there are new additions to the migration data.
After the you review the data give us the go-ahead, you should cancel all the Subscriptions in your existing system to ensure that the customers are not billed twice.
We will then import the Subscriptions into your live site and Chargebee will take over the billing.
Migrations usually take 5 to 7 business days to complete. This depends primarily on the available migration slots, number of records, data cleansing required, and verification/review iterations.
The migration process ensures that there will be no double billing. First, 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.
Next, before the import begins in Chargebee, all the subscriptions in your existing system should be canceled.
As an additional precaution, if there are any subscriptions that have been scheduled to renew 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. Say, 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.