In order to migrate your customers seamlessly, you need to determine what date your migration will take place. There should be no charge dates in your migration file that fall before your migration date, as those will be processed by your old system.

To be safe, move charge dates at least three days out from your migration date. This ensures you have enough time to complete the post-migration checklist and work with Recharge to remove the hold from your account. Taking consideration in these dates helps avoid missing any billing dates and prevents customers from being charged twice.

For example, you plan to launch Recharge on January 1st. Consider the following in this situation:

• The recommended date would be on or after January 3rd to export the data from the old system, which gives a few days to ensure new subscribers are flowing through Recharge correctly.
• Your official migration date is January 8th, giving you a few days from the 3rd to the 8th to validate your data and ensure the file is set up correctly.
• Since you will be migrating on January 8th, the absolute earliest you should set your next charge dates in the migration file is January 11th.

In this example, if you have a customer whose next charge date is January 5th this charge falls before the migration date. In this case you would update the next_charge_date line in your file to February 5th. Your old subscription platform handles the January 5th charge, and the customer processes through Recharge on the February 5th renewal.