Foundation · 2 min
What you need to know
Can ecommerce subscriptions be migrated?
Subscriptions can move only when the platform, contract, payment authority and token support permit it. The plan must preserve customer price, cadence, consented terms and next billing date.
How should active subscriptions be migrated?
Export each active agreement with customer, plan, status, quantity, price, cadence, next bill date and payment authority. Import through supported processes and prevent the old and new systems from billing simultaneously.
Can recurring payment tokens be transferred?
Recurring tokens transfer only through provider-supported portability or an approved vault transition. Otherwise, obtain new customer authorization without exposing card data.
How should subscription billing dates be preserved?
Store the original next billing timestamp with its time zone and map cadence rules explicitly. Test end-of-month, paused, trial and prepaid cases, so the migration does not bill early or twice.
How should failed subscription migrations be handled?
Keep failed subscriptions inactive in a visible exception queue and preserve the old agreement. Resolve token, customer, plan or date errors individually and communicate only when customer action is truly required.
A quick store check
Trace a subscription through migration and its next renewal, checking for early, missed or duplicate billing.
Foundation · 2 min
Frequently asked questions
Can subscriptions be copied like ordinary orders?
No. They are continuing agreements with billing authority, schedule and payment credentials that require supported migration.
What if a customer must reauthorize payment?
Explain the action clearly, keep the subscription inactive until authorization succeeds, and avoid unexpected charges.