In short
- The new app creates fresh Shopify subscription contracts, so the old app's contracts must be cancelled, never left billing alongside them.
- Where payment methods are stored decides the risk: cards saved in Shopify carry over, outside gateways need importing, and some PayPal and wallet methods can't move.
- Pick one cutover moment, switch off old billing first, and keep the old app installed until two billing cycles check out.
- Test with test subscriptions, update every portal link and tell subscribers plainly what will and won't change.
A Shopify subscription migration means moving every active subscriber, with their saved payment method, plan, price and next charge date, from one subscription app to another without anyone being charged twice or missing a renewal. In practice, the new app recreates each subscription as a fresh contract in Shopify, the old app stops billing at an agreed moment, and customers are pointed to a new portal. Get that order right and most subscribers never notice, which is why careful migrations sit at the heart of good Shopify subscription management.
Why brands switch subscription apps
Most switches aren't about one missing feature. The reasons build up over time:
- The portal holds retention back. Subscribers want to skip, swap, reschedule and add one-off items without emailing support, and when that's awkward, more of them cancel.
- Cost and plan fit change. What suited you at launch may not suit you once subscriptions are a large share of revenue.
- Retention tools differ. Cancellation flows, win-back offers, bundles, build-a-box and loyalty integrations vary a lot between Recharge, Loop, Skio, Appstle, Seal and Bold.
- Support and direction matter. Response times, account management and ownership changes all prompt a review. Skio, for example, has announced it is joining Recharge.
Whatever the reason, the switch is the risky part. The new app is only better if every subscriber arrives intact.
Why subscription migrations go wrong
On paper, every Shopify subscription migration is an export and an import. The headaches come from the parts a spreadsheet doesn't show.
Each app owns its own subscriptions
Subscriptions on Shopify live as subscription contracts, and each contract belongs to the app that created it. That app schedules every renewal and triggers every charge. Your new app doesn't take over the old app's contracts; it creates new ones, and the old ones have to be cancelled. Until then, two apps can believe they own the same subscriber.
Uninstalling too early cancels contracts
Shopify's developer documentation states that 48 hours after a subscription app is uninstalled, any contracts it owns that haven't been terminated are cancelled. Remove the old app before the new contracts exist and you've cancelled your own subscriber base.
Payment methods don't always travel
Where a card is stored decides how easy the move is. Cards saved in Shopify are usually straightforward. Cards held with an outside gateway need importing, and some payment types can't move at all.
Small mismatches multiply, and customers notice
A wrong interval, a lost loyalty discount or a charge date that shifts by a day looks minor on one record. Across a whole subscriber base it becomes a wave of tickets and refunds. And even when billing moves quietly, the portal, sign-in and emails look different. A subscriber who clicks an old "manage subscription" link and hits an error page is a cancellation waiting to happen.
Pre-migration audit checklist
Do this before you agree dates with the new app's migration team.
- Subscribers by status: active, paused, in payment retry and cancelled. Agree which statuses move. Skio, for instance, says it can't migrate cancelled subscriptions.
- Payment gateways: every gateway holding a subscriber's payment method, including leftovers from older set-ups, and how many subscribers sit on each.
- Payment types: cards, Shop Pay, PayPal, Apple Pay, Google Pay and local methods. They don't all move the same way.
- Plans and intervals: every selling plan, billing and delivery frequency, minimum commitment and prepaid option, including retired plans you still bill.
- Pricing and discounts: subscribe-and-save rates, first-order offers, discounts that change after a set number of orders, grandfathered prices and one-off codes from support.
- Products: every variant on an active subscription, including discontinued ones and bundles. Check each still exists in Shopify.
- Shipping and currencies: renewal shipping charges, free-shipping rules, and who pays in USD, GBP, CAD, INR or anything else.
- Integrations and custom work: email and SMS flows, helpdesk, loyalty, 3PL or ERP feeds, theme widgets and account page links.
- A baseline: renewal volume and failed payments for recent cycles, so you can compare afterwards.
Data mapping: old app to new app
Every app names things differently, but the concepts underneath are the same because they map onto Shopify's subscription contract. Use a table like this as a working document with your migration team.
| In your old app | Concept in the new app | What to check |
|---|---|---|
| Customer record | Shopify customer linked to the contract | Duplicates, changed emails, missing names |
| Subscription or charge ID | Subscription contract | A one-to-one mapping report |
| Product and variant | Contract line with a variant ID | Discontinued or renamed variants, bundles |
| Charge and order interval | Billing policy and delivery policy | Interval unit and count; whether billing and delivery differ |
| Prepaid subscription | Billing interval longer than the delivery interval | Deliveries remaining and the next real charge |
| Price and discount | Line price, pricing policy and contract discounts | Discounts that change after set orders, grandfathered prices |
| Next charge date | Next billing date | Time zones and charges already queued |
| Status (active, paused, skipped) | Contract status | Pause end dates and skipped orders |
| Payment method reference | Customer payment method in Shopify | Every active contract has a valid one |
| Shipping address and rate | Delivery method and delivery price | Late address changes, renewal shipping |
| Notes, tags and attributes | Contract attributes and customer tags | Anything fulfilment or support relies on |
Two things catch people out. First, counts rarely match. Loop explains that Recharge counts each product as its own subscription while Loop groups them by Recharge's charge ID, so a Recharge to Loop migration shows fewer subscriptions with nothing lost. Loop also asks for custom requirements, such as price updates, variant swaps, bundles or prepaid subscriptions, at least a week in advance. Reconcile by customer and line item, not the headline number.
Second, Shopify's contract documentation notes that a line item's price doesn't update automatically. A discount meant to change after a number of orders depends on the new app handling it, so test it before cutover.
Payment tokens and gateways
This is where most of the risk sits. Neither you nor the app sees full card numbers. What moves is a reference, or token, pointing to a payment method stored securely by Shopify or a gateway.
Payment methods already saved in Shopify
If your current app runs on Shopify Checkout and subscribers paid through Shopify Payments, their payment methods sit against the Shopify customer, not inside the old app. The new app can bill them once it has created its own contracts. Skio says Shopify Payments needs no action in its migrations, and Loop says moving from Bold needs no payment migration because Bold is built on Shopify's native subscription APIs.
Cards held with an outside gateway
Older set-ups, such as Recharge's legacy checkout or Bold v1, often kept cards with Stripe, Braintree or Authorize.net. Those references can be imported into Shopify within limits. According to Shopify's migration documentation:
- Stripe: credit cards only.
- Braintree: credit cards and Apple Pay only. PayPal methods held in Braintree follow the PayPal Express route, and the legacy Braintree integration doesn't support multi-currency subscription contracts.
- PayPal Express: imported as billing agreements, and the merchant must be approved by PayPal for reference transactions.
- Authorize.net: imported using both the customer profile ID and the customer payment profile ID.
The old gateway is connected to Shopify as a secondary gateway so renewals keep charging the same stored payment methods. Don't disconnect it while any subscriber depends on it. Shopify's help centre explains that payment methods move to Shopify Payments only as customers update their details, and that this "slow drip" can take months or even years.
What can't move, or needs extra work
- Shopify's help centre lists PayPal billing agreements, wallets such as Venmo, Apple Pay and Google Pay, and bank account details among the things its payment data migration service can't move. Ask your new app how it handles PayPal before setting a date.
- Moving raw card numbers into Shopify Payments is a paid Shopify Professional Services job and needs Shopify Plus or Enterprise. Token migration through your app developer is available on all plans.
- Loop's documentation says Adyen is supported for new subscriptions but not for token migration, and that other providers aren't supported for token import.
- Shopify's list of gateways that work with subscription apps is short: Shopify Payments, PayPal Express, Authorize.net, Adyen and Stripe (for select merchants only), and availability depends on region. Brands selling in India or relying on local payment methods should check subscription gateway support first.
Any subscriber left without a valid payment method will fail at their next renewal. Shopify warns that repeated failed renewals can pause, skip or cancel a subscription depending on your app's retry settings, and that updating a payment method can't restore a cancelled contract. Find these subscribers early and contact them before their charge date. And never send card data by email or spreadsheet: Shopify says cardholder data should only travel encrypted, through a PCI-approved import flow.
Billing dates and preventing double charges
A double charge happens when both apps think they own a renewal. A missed renewal happens when neither does. The fix for both is one agreed moment when billing passes from the old app to the new one.
- Switch off old billing first. Shopify's developer guide makes pausing billing in your current app a prerequisite for migrating, specifically to avoid double billing, and Recharge's guidance on leaving says the same.
- Have the old contracts cancelled. Loop's Recharge process bulk-cancels subscriptions in Recharge through the API after import. Skio says it won't enable billing for migrated subscriptions until it's certain the old platform has stopped charging them.
- Pick a quiet billing day. Skio typically schedules migrations early in the week and checks the old app's billing for the day has finished. Avoid big renewal batches, sales and launches.
- Freeze edits. Changes made in the old app after the export won't reach the new one, so agree a short freeze and log anything urgent.
- Carry next charge dates over exactly. Compare a sample before and after import, watching time zones and anything due on cutover day.
- Check prepaid subscribers' next actual charge, not just their next shipment.
Keep the old app installed, with billing off, until you trust the new set-up. Uninstalling cancels any contracts it still owns, which is only what you want once every subscriber has a live contract in the new app.
Customer portal, sign-in and emails
Billing can switch silently. Everything a customer touches can't.
- Point every link to the new portal. Loop asks for its widget to be live and the account page pointed at its portal before a Recharge migration, and Skio's post-migration steps include updating login links and redirecting the old portal.
- Expect people to sign in again. With Shopify's newer customer accounts, subscribers use their email and a one-time code rather than a password, so tell them what the new screen looks like.
- Catch old links. Past order confirmations, texts and bookmarks still point to the old portal. Redirect what you can and give support a ready-made reply.
- Silence the old app. Loop's process disables portal permissions, notifications and the subscription widget on the old platform first.
- Rebuild email and SMS flows. Upcoming charge, failed payment and win-back flows in Klaviyo or similar usually run on the old app's events. Map them to the new app and test each one.
What to tell subscribers
Loop describes its migration as a silent switch with no customer notifications. That's right for billing, but we'd still send a short, plain message close to cutover:
- Their plan, price and delivery schedule aren't changing.
- Their saved payment method stays the same, or, for the few who need it, a clear request to update it.
- Where to manage their subscription now, and how sign-in works.
- Who to contact if anything looks wrong.
Brief your support team first, with these answers and access to the new app's admin.
A step-by-step cutover plan
The order matters more than the speed. This is the sequence we follow.
Before cutover
- Audit and agree scope. Work through the checklist, decide which statuses and plans move, and tidy up retired plans and discontinued variants now.
- Set up the new app: selling plans, discounts, portal, notifications and integrations. Loop recommends going live before migrating, so new subscribers start in the new app while existing ones stay put.
- Connect any legacy gateway to Shopify as a secondary gateway and confirm it works.
- Share data securely through API access or the exports the new team asks for. For stores on Recharge's Shopify Checkout integration, Recharge points to a "Customer – Payment Tokens" export in its Export Builder.
- Run a test migration with test subscriptions, as described below.
- Book a quiet billing day and write down who switches off what, and when.
Cutover day
- Confirm the old app's billing for the day has finished.
- Switch off the old app's billing, notifications, portal and widget.
- Run the import and have the old contracts cancelled.
- Reconcile the mapping report on a sample, compare totals by customer and line item, and fix exceptions the same day.
- Update account links, redirects, email templates and help pages, then send the customer message.
Testing with test subscriptions
Create test subscriptions in the old app covering each plan type, a prepaid plan, a discounted plan and a paused one. Include them in a trial import, then check that:
- A renewal bills the right amount, discount and shipping on the right date.
- Skip, pause, resume, swap, change frequency and cancel all work in the new portal, including any cancellation flow.
- Renewal orders reach your fulfilment partner with the right tags.
- A declined card triggers the right retry and email.
- Notifications come only from the new app.
Post-migration checks for the first two billing cycles
Most problems show up at the first renewal. The rest appear at the second, when discounts step down, prepaid terms roll over and payment retries finish.
First billing cycle
- Compare renewal orders against subscribers due. A gap is a missed renewal; two orders for one customer is a double charge to refund straight away.
- Check failed payments by gateway. A cluster on one gateway usually means a connection or token problem.
- Spot-check prices, discounts and shipping on renewal orders against the old app's records.
- Confirm the old app created no orders and sent no emails.
- Tag every ticket about billing, sign-in or the portal so patterns show quickly.
Second billing cycle
- Check that discounts meant to change after a set number of orders have changed.
- Check prepaid subscriptions that started a new term.
- Review retries from cycle one: recovered, still retrying or cancelled.
- Compare renewals and failed payments against your baseline, and make sure reporting ties up.
- Only then take a final export from the old app and uninstall it.
Planning a subscription migration?
The Night Marketer is a Shopify Select Partner agency in New Delhi working with brands in the US, UK, Canada and India. We manage subscriptions on Recharge and Loop for brands including Fuel Your Body in Canada, and Nutriseed and Herbal Dog Co. in the UK. If you'd like a second pair of eyes on your audit, data mapping or cutover day, see how we run subscriptions for UK brands, Canadian brands and US brands.
Frequently asked questions
Usually not, if their payment methods are saved in Shopify or held on a gateway Shopify supports for import. Methods saved through Shopify Payments can be reused by the new app, and Stripe, Braintree, PayPal Express and Authorize.net references can be imported within set limits. Subscribers on unsupported gateways or payment types may need to add a new payment method before their next renewal.
Make sure only one app can bill each subscriber at any moment. Switch off billing in the old app before the new contracts go live, have the old contracts cancelled once the import is confirmed, and cut over after that day's renewals have run. Then compare first-cycle renewal orders against the subscribers due and refund any duplicates straight away.
No. Keep it installed with billing switched off until the first two billing cycles look right. Shopify cancels any subscription contracts still owned by an app shortly after it is uninstalled, which is only safe once every subscriber has a live contract in the new app. Take a final export of customers and subscriptions for your records before you remove it.
Often, yes, because they will manage their subscription in the new app's portal rather than the old one. Depending on your set-up, they may sign in through their Shopify customer account using their email and a one-time code. Update every manage subscription link, redirect the old portal where you can, and tell subscribers what the new sign-in looks like.
Loop's migration team usually handles the import once you have done the groundwork. You connect any legacy gateway in Shopify, share API access to your current app and agree a date. For Recharge, Loop imports the subscriptions as new contracts, bulk-cancels them in Recharge and provides a one-to-one mapping report to check. You own the audit, testing, customer messages and post-migration checks.