Should we switch subscription apps? What breaks when you leave Recharge

Why are you thinking about switching?

It usually starts with a symptom. Renewal revenue went flat. Cancels climbed. The inbox fills with "how do I skip my order" emails. Or a vendor demoed a cleaner portal and a lower fee, or someone proposed a checkout funnel that "handles subscriptions natively".

All real. But the expensive part of a switch is rarely the new contract. It is the renewals that fail, the cards customers re-enter and the history left behind. So split the question: is the problem the platform or how it is set up? And if it is the platform, what moves and what breaks? Every rule below was checked against Shopify's and the vendors' documentation on October 4, 2026.

What actually moves when you change subscription apps?

On Shopify, a subscription is three things kept in different places: the contract (what, how often, at what price, on what date), the payment method (card, Shop Pay or PayPal agreement), and the app's own memory (portal, flows, retry state, cancel reasons, discount logic).

Contracts do not move. "Shopify subscription contracts created by one app are not able to be "taken over" by a different app," so the new app makes copies and your old program "will still exist until the legacy app is deleted" (Skio Help Center). Shopify's contract import takes a next billing date, and a contract needs a valid payment method before it can be billed (Shopify Dev Docs).

Skio's required migration fields are email, shipping address, status, next billing date, line items and frequency. The price it carries "is the actual price charged", "not the pre-discount price", and "canceled subscriptions are not able to be migrated". It also lists redirects "from the old subscription platform's Customer Portal" as a post-migration step (Skio Help Center). Hence three risks below: flattened discounts, lost cancel history and dead portal links.

Where do your subscribers' cards actually live?

This question decides whether a migration is a back-office job or something every subscriber feels.

Cards and Shop Pay vaulted in Shopify

If you sell subscriptions through Shopify's checkout, payment methods are vaulted in Shopify, not in the app. "Saved payment methods are stored with the Shopify Payments account that processed them" (Shopify Help Center). For an app-to-app move, Skio says: "For Shopify Payments, no action is required, as all data is accessible via Shopify's API" (Skio Help Center). Shop Pay is one of those methods; Shopify's API calls it "a Shop Pay card instrument for customer payment method" (Shopify Dev Docs).

The catch is the store, not the app. Skio is "unable to migrate ShopPay payment methods from store A to store B" (Skio Help Center).

Tokens still held at Stripe, Braintree or Authorize.net

Older Recharge stores often carry subscribers from before Recharge moved onto Shopify's checkout. On the Migrated Shopify Checkout Integration, "All pre-existing subscriptions on Recharge will continue to be processed by Recharge via the payment gateway configured in Recharge until the customer updates their payment methods or billing information" (Recharge Help Center). To move those, the new app needs the processor's tokens and the processor connected to Shopify as a legacy subscription gateway (Shopify Dev Docs; Loop Help Center).

Two details bite. If a token is missing, "Shopify doesn't fall back to the customer's default payment method" (Shopify Dev Docs). And moving those cards into Shopify is either a slow drip, one customer at a time as they update details, or a paid Shopify Professional Services migration that requires Shopify Plus or Enterprise and excludes Apple Pay, Google Pay and PayPal billing agreements (Shopify Help Center).

Shopify-native subscription app or an external checkout like Checkout Champ?

• Shopify-native apps (Recharge, Skio, Loop, Stay AI, Shopify Subscriptions) sell through Shopify's checkout using its selling plan and subscription contract APIs. The App Store does not permit purchase option apps that misuse those APIs (Shopify App Store requirements).
• External checkout funnels replace the checkout. Checkout Champ calls itself "an alternative checkout platform, not just another Shopify app" (Checkout Champ). Customers pay on its pages and orders are sent over to Shopify (Checkout Champ Help).

Before modeling an external checkout, read three Shopify documents current on October 4, 2026:

• Terms of Service, last updated August 1, 2026: "You agree to use Shopify Checkout for any sales associated with your online store," and not to work around the Services' limits, "including to process orders outside Shopify's Checkout" (Shopify Terms of Service).
• API Terms, last updated February 27, 2026: developers may not, "except with Shopify's express written authorization", "use an alternative to Shopify Checkout for checkout or payment processing for Shopify Merchants" (Shopify API Terms).
• App Store requirements: "Apps that bypass checkout or payment processing, or register any transactions through the Shopify API in connection with such activity, are prohibited" (Shopify App Store requirements).

This is not legal advice, and Shopify can grant written exceptions. The practical rule: if a vendor proposes moving store sales off Shopify Checkout, get Shopify's written authorization for your store before you sign.

Then the payments. Checkout Champ's help center says "Shop Pay does not support rebills" (Checkout Champ Help). And per Recharge's offboarding guide, a merchant leaving Shopify must ask Shopify Support for Shopify Payments tokens, and "this one-off service may come with a charge" (Recharge Help Center).

So "Recharge vs Checkout Champ" is a checkout migration with a subscription migration attached, not an app swap. Every Shop Pay subscriber, and possibly every vaulted card, has to enter payment details again. If the real complaint is checkout conversion, start with why shoppers add to cart and do not buy.

How do Recharge, Skio, Loop, Stay AI and Shopify Subscriptions compare?

Only on facts each vendor publishes. List prices change and large brands negotiate, so read this as a snapshot.

Two facts change how to read it. Recharge announced on April 30, 2026 that Skio is joining the company (PR Newswire), and Skio's listing now reads "Skio, a Recharge Company" (Shopify App Store). "Recharge vs Skio" is now a choice between two products of one company. And fee bases differ: Recharge charges "transaction fees for both one-time and recurring subscription orders" (Recharge Help Center), while Skio's fee covers "orders involving a subscription". Compare on your own order mix.

All four paid apps list a portal, cancel flows and failed payment recovery. The differences sit in the detail (who sees cancel reasons, how retries are timed, what a customer can change from a phone), so test those in a demo with your own edge cases.

What does switching cost at your volume?

Cost is the reason founders give most often for leaving, so do the math both ways.

Here the gap between Recharge Plus and Loop Pro is about $4,400 a month, a little over $52,000 a year at list price. Now the other side, same illustrative brand:

• If the cutover makes an extra 2% of first renewals fail and half of those subscribers never return, that is 100 lost subscribers. At $40 an order and five more orders each, about $20,000 of future revenue is gone from one bad cutover.
• If old portal links break and some would-be skippers cancel instead, the loss grows, and no migration report shows it.
• If the fix-first work below recovers even a small share of the renewals that fail every month, that gain repeats monthly.

Switching can pay. But the saving is easy to count and the loss is not, so put both in one table, and take the competing quote to your current vendor before assuming the gap is real. Our guide on LTV to CAC for subscription supplement brands shows how to value a lost subscriber.

What should you fix before you migrate? The 90-day test

Most complaints that start a migration talk are configuration problems that follow you to the next app. Fix them where you are and measure for 90 days. Either the problem goes away, or you arrive at the migration with clean data and a clear reason.

1. The cancel flow

Who processes cancels today? If most go through the inbox, chat or chargebacks, the app's save offers never run. Put the same save offer in every cancel channel, require a reason on every cancel, and keep the exit easy to find. Recharge tells merchants to check cancel flows against regional consumer protection laws (Recharge Help Center), and on March 11, 2026, opening new negative option rulemaking, the FTC's consumer protection director said these subscriptions "continue to be plagued by difficult cancellation processes, unlawful retention tactics" (FTC). More in how to cut supplement subscription churn.

2. Dunning and hard declines

Recharge's Failed Payment Recovery retries failed payments and cancels the subscriptions if every retry fails (Recharge Help Center). Hard declines "don't enter your Failed Payment Recovery strategy," and the Card Declined email that asks those customers for a new card is "disabled by default" (Recharge Help Center). Check yours. Then find active subscriptions with no next charge date or a charge stuck in error: subscribers you are neither billing nor saving.

3. The portal

Can a subscriber log in, skip, swap and update a card from a phone in under a minute? Recharge offers passwordless login with a four-digit code by email or SMS (Recharge Help Center). A portal that demands a password or hides the skip button is a fix, not a migration.

4. Renewal price clarity

A renewal amount nobody expected is an easy cancel to prevent. Send an upcoming order notice with the exact amount and a one-click delay; Recharge's Upcoming order email does this without a portal login (Recharge Help Center). And make sure the subscribe-and-save price on the product page is the price that renews. See how much subscribe-and-save discount to offer.

Which four triggers justify moving anyway?

Fix first does not mean stay forever. Four situations justify a migration, each with a test:

1. A feature you need that the current app cannot do. Not a nicer demo: a capability tied to revenue (a bundle model, a prepaid structure, a portal action, an integration) that your vendor confirms in writing it does not support and will not ship in time.
2. Cost at your volume, after negotiation. Run the table above on your real order mix, take the best competing quote to your current vendor, and count only the gap that remains.
3. Platform reliability. Renewal runs that stall, late notifications, an admin you cannot get into. Recharge publishes its incident history on a public status page; line up 12 months of incidents that touched charge processing against your renewal calendar.
4. Contract and support. A renewal clause, price increase or support level you cannot accept, with no movement after you ask. Read your term and notice period now; they set your migration date more than any feature does.

If none applies after 90 days, the right answer is usually to stay and keep fixing.

What breaks during a migration, and how do you prevent it?

Failed first renewals

The first renewal on a new system is the riskiest charge. For imported cards, Stripe warns that if cards on file are labeled wrongly, "Issuers who can't confirm a cardholder's consent to future or recurring payments might decline them," and that retrying many cards after a migration "can appear suspicious to issuers" (Stripe Docs). Shopify says customized charge flows are not supported when migrating Stripe payment methods and "might result in an elevated rate of authorization failures" (Shopify Dev Docs). Watch the first full cycle daily, by payment type.

Customers re-entering cards

Inside one store, vaulted cards and Shop Pay stay put. Re-entry happens when you change stores, leave legacy tokens behind, move to an external checkout, or replace your Shopify Payments account, where "Your customers need to add their payment methods again" (Shopify Help Center). Do the outreach before renewal day, with one link and one action.

Double charges

Because contracts are copied, both apps can bill the same subscriber. Shopify strongly recommends pausing billing in the current app to "avoid double-billing a contract" (Shopify Dev Docs). Recharge says to cancel "before subscriptions become enabled on the new provider" (Recharge Help Center), and Skio waits until it is certain the legacy platform has stopped (Skio Help Center). Pick a cutover with no renewals in the gap.

Lost reason data, retry state and dead links

Export cancelled subscriptions before you cancel the old account; Recharge's cancelled subscriptions export carries the reason and the customer's comments (Recharge Help Center). Tag everyone mid-retry, since failed renewals can pause, skip or cancel a subscription and a new card "can't restore a cancelled subscription contract" (Shopify Help Center). Recharge also "does not have a built-in notification to alert customers that subscriptions will be ending", and customers inside its flows "will continue receiving emails until they complete the flow" (Recharge Help Center). Its portal uses paths on your domain such as /tools/recurring/login (Recharge Help Center): redirect them, and update every email and SMS flow, the FAQ and support macros.

Migration day, in order

1. Export active and cancelled subscriptions, queued charges, errors, payment methods and discounts.
2. Unpublish the old widget and switch off portal rescheduling, as Recharge's offboarding guide recommends.
3. Stop billing in the old app and confirm it stopped.
4. Import, then spot-check subscribers across every payment type, plan and discount.
5. Enable billing in the new app, redirect portal paths, update flows.
6. Watch the first full renewal cycle daily.

How we audit a subscription program before a migration at Succession

We do not start with vendor demos. We start with the program as it runs today, because that is what a new app inherits.

1. One market first. US subscribers only before reading any rate, so international payment quirks do not blur the picture.
2. Who processes cancels. Support, portal, chat, chargebacks. Then whether a save offer appears in every channel, and whether a reason is logged on every cancel.
3. Failed payments by type. Soft declines in retry, hard declines that never enter it, and whether anyone asks hard-declined subscribers for a new card.
4. Subscriptions with no next charge date. Active on paper, not billing in practice.
5. Checkout and offer before platform. The subscribe-and-save offer, renewal price and checkout get fixed before anyone redesigns pages or replaces the app.
6. A leak map. Each leak gets a ceiling in orders per day, so fixes, and the migration itself, are ranked by what they are worth.
7. Cohort payback. By acquisition month, on net revenue and real gross margin, with Shopify orders as the scoreboard, so a lost subscriber has a value.

The audit often answers the migration question by itself. When it does not, it gives the new vendor a clean list of what must survive the move.

What should you do this week?

1. Count active subscribers by where the payment method lives: Shopify vault, Shop Pay, PayPal or a legacy processor.
2. Find your subscription contract's term, renewal date and notice period.
3. Check that your hard-decline email is on, and count active subscriptions with no next charge date.
4. List every channel where customers cancel, and whether each shows a save offer and logs a reason.
5. Write down which of the four triggers you think applies, and your evidence.
6. If an external checkout is on the table, ask the vendor for Shopify's written authorization for your store before the next call.
7. If you want a second pair of eyes, book a free growth audit and we will go through the subscription program, checkout and offer with you.

FAQ