Migration
Switch from Recharge in a day.
A migration importer that preserves payment tokens, cadences, and subscriber data. No re-authentication. No broken billing. Most stores cut over inside an afternoon.
- 01
Install Reapita on your dev or live store
Two-minute install from the Shopify App Store. Pick the plan you want; the 14-day trial means no charge until you've cut over.
- 02
Export your Recharge subscription CSV
Recharge's admin → Tools → Export → Subscriptions. Pull customers, plans, addresses, and payment-method tokens. The Recharge dashboard generates the file in about a minute.
- 03
Run the migration importer
Drop the CSV into Settings → Migration. Reapita preserves Shopify Vault payment tokens — the customer's card stays on file, no re-authentication, no broken billing. Each row maps to a Shopify SubscriptionContract one-to-one.
- 04
Verify on a test product
Pick one subscription and run a dry-run billing cycle. Confirm the charge processes, the order lands in Shopify, and the customer portal at /account/subscriptions shows the right plan. Takes ~5 minutes.
- 05
Cut over — uninstall Recharge
Once verified, the importer flips the active flag on Reapita and pauses Recharge's billing webhook. Subscribers don't notice — same cards, same cadence, same plans, just a new engine underneath.
Why the payment tokens transfer cleanly
Shopify owns the vault — not your subscriptions app.
When a customer first subscribes on your store, Shopify stores their card in its own vault and hands the subscriptions app a reference ID. So when you switch from Recharge to Reapita, the card itself never moves — we just start referencing the same Shopify vault entry. No PCI re-tokenization, no customer prompted to re-enter a card, no subscription paused mid-cycle. This is the trick that makes migration take hours instead of weeks.
Migration questions
What happens to the payment tokens?
Reapita reads the Shopify Vault payment-method ID, not Recharge's internal token. Because the source of truth is Shopify, not the previous app, the migration is non-destructive — your subscribers' cards remain on file with Shopify and we just point new charges through Reapita.
Do my subscribers get a notification email?
Not unless you send one. Migration is invisible by default. We recommend a short heads-up email letting subscribers know the customer portal URL is changing — we ship a template you can edit.
What about Recharge's bundles and prepaid?
Imported as Reapita bundles and prepaid plans automatically. Build-a-box configurations map one-to-one. Subscriber selections are preserved.
What if a subscription is mid-cycle?
Reapita reads the next-charge date from the CSV. If a charge is due before you cut over, Recharge runs it; if it's due after, Reapita does. No duplicate billing.
What about Loop, Appstle, Skio, or Seal?
Same flow — those apps each support a subscription CSV export. We've documented per-app mappings in the in-app migration tool, and Scale plan customers get white-glove migration where we run it for you.
How long does it actually take?
Most stores migrate in 2-4 hours including verification. Our largest migration to date — 18,400 active subscriptions — took six hours including a 90-minute verification window.
Ready to migrate?
Install Reapita free, run the importer against a test CSV first, then cut over for real when you're comfortable. We're here on chat the whole way.