Migrating from ReCharge to Skio: A Practical Guide (and When Not To)
On 30 April 2026, ReCharge bought Skio for $105M in cash. If you are reading a "migrate from ReCharge to Skio" guide two months after that announcement, the first thing you need to know is that you are no longer being pointed at a competitor. You are being pointed at a sibling product owned by the same vendor. That single fact changes almost every calculation in this post, so we are not going to bury it in paragraph six the way most of the internet's migration content still does.
This guide covers what actually moves in a ReCharge → Skio migration, the payment-token problem that catches almost everyone out, a cutover sequence that doesn't drop a single charge, and — updated for the acquisition — a much sharper answer to the question of whether you should still bother at all. If you haven't made that decision yet, start with our rewritten ReCharge vs Skio comparison, which is now built specifically around the post-acquisition landscape. This post assumes you've made the call and need to execute it well.
The acquisition you need to know about first
ReCharge's acquisition of Skio was, by the numbers reported at the time, the largest private acquisition in subscription commerce. Skio was a Y Combinator alum that had raised roughly $8M — a fraction of the sum it sold for. Together the two platforms now power more than 20,000 merchants and upwards of $20B in annual GMV. That is not a rounding error in the subscription-tooling market; it is close to a consolidation event.
ReCharge's own public statement on the deal is carefully worded: "for merchants on both platforms, nothing is changing today," with details of a combined offering promised for later. Read that literally. It does not say the products will merge. It does not say they will stay separate forever either. As of this post going live, ReCharge and Skio continue to run as two distinct products, with two distinct codebases, two distinct support teams and — as far as we can establish — two distinct roadmaps. Whether that persists is genuinely unknown, and we are not going to pretend otherwise by inventing a roadmap ReCharge hasn't published.
What we can say with confidence: the reason most brands historically wanted to leave ReCharge for Skio was some mix of "escape ReCharge's per-transaction pricing," "escape ReCharge generally," and "get Skio's native Shopify checkout." The acquisition doesn't touch the third reason. It substantially weakens the first two.
- Whether Skio and ReCharge merge into one product, stay as a two-tier line-up, or run as fully independent brands long-term
- Whether Skio's pricing model moves toward ReCharge's transaction-fee structure, or ReCharge's moves toward Skio's
- Long-term investment in Skio-specific features like its cancel-flow A/B testing and passwordless portal
- Skio and ReCharge run as two separate products with separate logins, dashboards and support queues
- Existing contracts on either platform are unaffected — ReCharge has said explicitly that nothing changes for current merchants today
- Skio's technical capabilities — Shopify-native checkout, passwordless portal, cancel-flow experimentation — still work exactly as they did before the deal
Separate what has actually changed since 30 April from what merchants are anxious might change. The two lists are not the same size.
Does this migration still make sense?
This is the section that has changed most since we first wrote this guide. Before the acquisition, "should I move" was a straightforward cost-benefit call. Now it has an extra dimension: are you solving the problem you think you're solving, or has the acquisition quietly solved — or un-solved — it for you?
Be honest with yourself about which row you're actually in. Most brands are a blend, and the blend now needs re-weighing.
That last row is worth dwelling on, because it's the one the acquisition genuinely creates rather than merely complicates. If part of your motivation for leaving ReCharge was never wanting to have all your subscription billing infrastructure sitting inside one company's risk profile — one outage surface, one pricing decision, one support org, one company's fortunes — moving to Skio does not achieve that any more. You would be swapping a ReCharge-branded single point of failure for a ReCharge-owned single point of failure with different branding. If vendor concentration is genuinely your concern, look at the platforms that are still independently owned: Loop, Smartrr, Stay AI, Ordergroove, Bold and Appstle all remain outside the ReCharge group, and Loop in particular has publicly claimed more than 400 brands have migrated to it from ReCharge. We are not saying any of those is automatically the right answer for you — that evaluation belongs in a proper platform review — but they are the honest answer to "how do I actually reduce vendor concentration," and Skio no longer is one.
For everyone else — brands moving for a specific, still-real Skio capability, not for the vendor relationship — the rest of this guide is unchanged from what we'd have told you in March. A working subscription stack is worth a lot, and migration carries real risk regardless of who owns the destination. Migrate when the ongoing pain clearly exceeds the one-off risk. Not before.
The part everyone underestimates: payment tokens
Exporting subscription data — products, frequencies, next-charge dates, customer mappings — is the easy half of this migration. The hard half is the payment methods, and it is the single most misunderstood part of any subscription platform move, acquisition or no acquisition — the same problem we flag as the hardest part of a full platform migration to Shopify, just scoped to one app instead of the whole store. You cannot simply export and re-import card numbers. Nobody outside a PCI-compliant vault is allowed to touch them, including you, and including the platform you're migrating to.
What actually exists on each side is a token — an opaque reference the processor generates and hands back to the merchant platform, which stores the token, not the card. Whether that token can move with the customer depends entirely on what sits underneath it. Here is the shape of the problem.
The token, not the card, is what moves — and only some routes let it move at all.
If both platforms sit on the same underlying vault — typically Shopify Payments, since both ReCharge and Skio can run on Shopify's native checkout — the tokens can often be carried across without re-collecting a single card. This is the good path, and it's the one most Shopify-native ReCharge-to-Skio migrations should expect to be on.
If ReCharge is running on its own processor and Skio will use a different one, you need a genuine processor-to-processor token migration. That only works with the direct cooperation of both gateways, a signed data-sharing agreement, and a clear audit trail — and it is not something either platform will do for you automatically just because they happen to share a parent company now. The acquisition changes the corporate ownership chart. It does not change what the underlying payment processor's compliance team will and won't agree to move.
Scope this first, before you touch anything else. It is the single factor that decides whether your migration is a weekend project or a quarter-long one, and it is the thing every ReCharge-to-Skio migration horror story we've heard about traces back to.
4–8w
is a realistic lead time for a processor-to-processor token migration once both gateways are engaged. Start this conversation in week one of the project, not week six — it is invariably the longest lead-time item on the plan, and everything else can be sequenced around it.
A cutover sequence that doesn't drop charges
The governing principle is simple: never let both systems believe they own the same charge at the same time. Here is the order of operations we run, with the point in the timeline where a dropped or duplicated charge actually becomes possible marked clearly — because that's the bit that matters, not the neat five-step list.
Migration sequence and charge-risk window
Snapshot and reconcile
Export every active subscription with its next-charge date and freeze the dataset. Reconcile counts and recurring revenue totals against ReCharge's dashboard so you know exactly what "correct" looks like on the other side.
Migrate payment tokens
Run the token migration from the section above. Verify a sample with zero-value authorisations before trusting it at volume.
Load subscriptions into Skio, paused
Recreate every subscription with its real next-charge date — not "today" — so nobody gets double-charged or charged early once billing is switched on.
Cut over in one clean switch risk window opens here
Pause billing in ReCharge, activate it in Skio, in a tight window on a low-charge day — never the 1st of the month, when a disproportionate share of subscription bases bill.
Watch the first billing cycle like a hawk
The real test is the first set of live charges on Skio. Monitor success rates against your step-1 snapshot, and have a rollback note ready for anything that fails.
Steps 1–3 and 5 are low-risk if done carefully. Step 4 is the only point where a genuine double-charge or dropped charge becomes possible — keep the window as short as the token migration allows.
What moves, and what has to be rebuilt
Beyond billing itself, a subscription migration touches more surface area than most teams expect going in. Some of it transfers cleanly. Some of it has to be rebuilt from scratch, and rebuilding it is where projects quietly blow past their estimate.
-
Subscription product mappings, frequencies and next-charge dates, via CSV or API import
-
Payment tokens, where both platforms sit on the same Shopify Payments vault
-
Customer-to-subscription mapping, since both sit on top of the same Shopify customer record
-
Historical order data, since it lives in Shopify rather than in ReCharge itself
-
Every "manage subscription" link in account pages, transactional emails and Klaviyo flows
-
ReCharge-specific dunning rules, skip/pause logic and cancelation-flow offers
-
Any custom scripts, checkout customisations or Liquid built against ReCharge's API surface
-
Webhook consumers — analytics, fulfillment, loyalty — that key off ReCharge's event payloads
In the audits we've run this year, the right-hand column is consistently where estimates go wrong, not the left.
The customer portal and every touchpoint that points at it
Subscriptions aren't just billing — customers manage them. The "manage subscription" links in your account area, transactional emails and lifecycle flows all point at ReCharge's portal today; every one of those needs to move to Skio's. Miss a link and you get confused customers and a support inbox that fills up with "how do I skip my next box" tickets. Audit every touchpoint — account page, transactional emails, Klaviyo flows, help docs — and update them as part of the cutover, not after. This is exactly the kind of self-serve gap we cover in our custom member portal guide, and it's worth deciding upfront whether Skio's default portal is enough or whether you want more control over it.
Tell customers — but carefully
A short, calm heads-up — "we're upgrading how subscriptions work; your plan and next delivery are unchanged" — prevents the panic-cancel reflex that a surprise charge from an unfamiliar billing descriptor can trigger. Make sure the payment descriptor and sender identity are sorted before that email goes out. A charge from a name a customer doesn't recognize is the fastest way to manufacture chargebacks and involuntary churn, and it's a completely avoidable one — see our note on reducing involuntary churn for the wider pattern.
There's a temptation, given the acquisition, to skip this communication because "it's basically the same company now." Resist it. Your customers don't know or care who owns Skio's cap table. From where they sit, their card is about to be charged by a system they've never seen, and that alone is enough to trigger the anxious cancellations you're trying to avoid. The acquisition changes your risk calculus, not theirs.
Audit for leaks while you're in there
A platform migration is, inconveniently, also the best moment to catch the quiet revenue leaks that build up in any subscription program over time — orphaned discounts still applying at renewal, failed-payment retries that silently stop retrying, skipped orders that never get re-scheduled. We go through the common patterns in subscription revenue leaks. Reconciling your full subscriber base against Skio's import is the natural checkpoint to run that audit — you're already comparing every row for accuracy, so extend the comparison a little further while you have the two datasets open side by side.
If de-risking is the actual goal
We said above that migrating to Skio no longer reduces vendor concentration, and we want to be specific about who the genuinely independent alternatives are, because "look at other platforms" is a useless sentence without names. As of this post, the following subscription platforms are not part of the ReCharge group and remain plausible ReCharge alternatives depending on your stack and Shopify tier:
Loop has publicly stated that more than 400 brands have migrated to it from ReCharge — the clearest sign there's an established, well-trodden path away from the ReCharge group specifically, not just away from ReCharge the product.
We're not going to run a full feature comparison of six platforms in a post about ReCharge-to-Skio migration mechanics — that's a separate piece of work, and the right answer depends on your order volume, your churn drivers and which capabilities actually move revenue for your brand. But if vendor concentration is the concern that brought you to this page, it deserves its own proper evaluation before you commit engineering time to any migration, Skio included.
Timing: don't migrate onto an unsettled roadmap during peak
Beyond the usual advice to avoid your peak trading season — never November through January for most DTC brands — there's a new timing consideration specific to this moment. ReCharge has said a combined offering is coming, without saying when or what it looks like. If you migrate onto Skio now and a genuinely merged product or a repriced tier arrives in the next twelve months, you may find yourself migrating again, or absorbing a pricing or feature change you didn't plan for.
That's not a reason to freeze indefinitely — "wait and see" can become its own form of paralysis, and if you need Skio's capabilities today, the acquisition uncertainty alone shouldn't stop a well-planned move. It is a reason to build your migration plan with the token architecture we described above documented clearly, your export scripts kept, and your integration inventory written down somewhere durable. If the combined offering does eventually require a second move, you want that second move to be a formality, not a repeat of this entire project from scratch.
If you're weighing a ReCharge → Skio move against staying put, or against one of the independent platforms, and want a second pair of eyes that isn't selling you either outcome, take a look at our subscription migration work, or get in touch. We've moved subscription stacks in both directions, plan every one of them to be boring on purpose, and if the honest answer for you is "stay on ReCharge for now," we'll tell you that too.