Migration
Moving from another app
The whole risk of a subscription migration is in one question: who holds the payment method?
- AuditExport every active subscription
- Confirm the modelNative contracts? Who holds the card?
- Pause signupsNever migrate a moving target
- Test batchTen subscribers — let one renew
- ReconcileCounts, charge dates, discounts
- Migrate the restKeep the old app for one cycle
- Watch two weeksFailures surface at renewal
If your contracts are native
If your current app creates native Shopify subscription contracts, the contracts and payment methods already live in your store. Migration is configuration — plans, discounts and schedules — and your subscribers generally do not notice.
If they are not
If your app holds payment methods in its own vault, those credentials are not transferable. You are asking every subscriber to re-authorise, which is a churn event rather than a migration. We will tell you honestly if that is your situation rather than discovering it mid-move.
What we do
- Establish the contract model of your current app before anything moves
- Rebuild plans, discounts, tenure tiers and build-a-box rules
- Migrate a test batch first, and let one subscription actually renew
- Reconcile active counts, next charge dates, discount amounts and cycle counts
- Keep the old app installed for a full billing cycle so rollback stays available
The thing we check hardest
Next charge date, on every contract. Not a sample. Dates moving is the failure customers notice immediately — a subscriber billed early may not have the funds, and at scale that is a support crisis and a payment failure spike in the same week.