Migrating subscriptions from another provider
If your subscription book lives on another payment platform, Payments AI supports migrating it. The migration is a coordinated process with your Integration Consultant — it covers importing customers, re-tokenizing stored payment instruments, and preserving the active subscriptions' billing schedules so the first renewal on Payments AI happens on the date the customer was expecting.
How to start
Raise the migration with your Integration Consultant during onboarding. They will:
- Confirm what data is needed from your current provider (customer list, active subscriptions, stored payment instruments).
- Coordinate the secure transfer of stored card tokens — raw card data does not move between providers; payment instrument tokens are re-tokenized into Payments AI through the appropriate network rails.
- Agree a cut-over date so charges are not duplicated across the old and new providers during the transition.
The exact data export format, the timing of the cut-over, and the recovery path if anything looks off are all defined together with your Integration Consultant — there is no self-service migration endpoint to call.
What to validate after migration
Run all of these on stage first, before the production cut-over:
- Customer count matches between the source export and the Payments AI import.
- Active subscriptions are present with the correct status and the correct next renewal date.
- Trial subscriptions and paused subscriptions retain their state.
- Payment instruments are attached to the right customers and can be used for the next renewal.
If anything mismatches, your Integration Consultant runs the correction before the production cut-over.