What's the honest cost-benefit case for migrating from Recharge/Skio to Shopify's native Subscriptions APIs, given the 2026 Recharge-Skio acquisition uncertainty?
Migrating from Recharge or Skio to Shopify's native Subscriptions app trades a per-order fee for a worse subscriber portal. Shopify Subscriptions is free and bills weekly, monthly or yearly, but it does not work with bundles, draft orders or local payment methods (verified September 2026). Deploi scores the move CUSTOMIZE: rebuild the product-page purchase-option layer now, and move billing only when the portal gap closes.
What you actually stop paying, and what you start owning
| Line | Today, on a paid app | On Shopify Subscriptions |
|---|---|---|
| Platform fee | Recharge $25 / $99 / $499 per month by tier; Skio $599 per month (verified Sep 2026) | $0 |
| Per-transaction | Recharge 1.49% + $0.19 (Plus tier), 1.34% + $0.19 (Premium); Skio 1% + $0.20 (verified Sep 2026) | $0 |
| Subscriber portal | Vendor-hosted, vendor-themed | Shopify customer accounts, thinner |
| Dunning and card updater | Vendor's retry logic, tuned across thousands of stores | Shopify Payments card updater, broadly available in the US (per Shopify's docs, Sep 2026) |
| Churn-save flows | Product feature | Build it or go without |
| Cohort and churn reporting | Product feature | Build it or go without |
The gaps that are hard stops, not settings. Shopify Subscriptions is not compatible with bundles, cannot be used with draft orders, does not support local payment methods, and is not supported by the order edits API (per Shopify's docs, September 2026). Gift cards and Shopify Scripts discounts apply to the first payment only. Supported gateways are Shopify Payments, PayPal Express, Authorize.net, Adyen and Stripe for select merchants. If any one of those lines describes how your program runs today, the migration is off the table until that changes.
What the acquisition actually changed. Recharge closed its acquisition of Skio on 2026-04-30 (per Recharge, April 2026). The App Store listing now reads "Skio, a Recharge Company" (verified September 2026). Two of the three obvious destinations share one owner, which narrows the market more than it raises the risk of any individual platform disappearing. Loop Subscriptions is the independent alternative at free to $399 per month (verified September 2026).
The thresholds we use
- Under ~2,000 active subscribers: the vendor's own migration service is usually the right buy. The glue is not worth building at that volume.
- 10,000–50,000 active subscribers: CUSTOMIZE. Buy the destination platform, build the glue the vendor import skips: contract mapping, payment-method transfer checks, parallel billing reconciliation. Deploi scopes that at $15,000–$40,000 (Deploi estimate, illustrative).
- Above ~50,000, or on a second migration: a first-party subscription data layer starts to pay, at $25,000–$75,000 on top (Deploi estimate, illustrative).
When NOT to migrate
Do not migrate on vendor-uncertainty grounds alone. Uncertainty is a reason to shorten the contract term and keep the exit cheap, not a reason to spend 60–90 days and 2–5% of your subscribers (July 2026 research) on a move whose benefit is a fee line. Do not migrate mid-peak. Do not migrate while a replatform is in flight; that is a separate page and a separate answer. And do not migrate to Recharge from Skio expecting to escape Recharge's roadmap; since 2026-04-30 that is the same roadmap.
The interim step that is defensible regardless. Rebuild the product-page purchase-option layer in your own theme, against Shopify's Subscription APIs, so the selector your customers see is no longer vendor-rendered. The front end stops depending on the vendor. The billing engine can be argued about later, on its own timetable.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: The subscription app you pay for is the portal, the dunning and the cohort reporting. It is not the product-page selector, and it is not the billing cadence. Migrate for a portal you have outgrown, not for a fee you resent.
- What we’ve seen: Vendor imports move contracts. They do not move dunning state, portal customizations or churn-save rules, and the rebuild of those is agency time nobody quoted at kickoff. Payment-method transfer is the single variable that decides whether the migration is boring or expensive.
- Times we’ve shipped this: 5 builds delivered.
- What it takes: roughly 46 hours scoped for the product-page purchase-option layer (directional Deploi estimate from a small sample of engagements, not a measured average).
- Where we disagree: The category frames native subscriptions as "good enough now." Native is good enough for fixed-cadence replenishment on standard products and nothing more: the bundles, draft-orders and local-payment-methods gaps are documented and unresolved (verified September 2026). We would rather say that plainly than sell a migration into a wall.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.
Where we worked this out
Follow-up questions
What's the honest churn-risk estimate for a subscription-program migration, and what benchmark should we hold the migration agency to?
Subscriber churn from a subscription-platform migration runs 2 to 5% by the community-reported envelope (July 2026 research), and payment-method transfer is where that loss concentrates. Hold the agency to a card-retention rate, not a churn rate: the number to write into scope is the percentage of active payment methods that transfer without re-collection. Churn follows from it.
How much should we budget specifically for subscription-migration risk mitigation (QA, parallel-run, customer support surge) as its own line item separate from the core platform migration budget?
Subscription-migration risk mitigation deserves a separate budget line at roughly 25 to 40% of the scripted migration cost. Deploi scopes a scripted subscription migration at $15,000 to $40,000 (Deploi estimate, illustrative), which puts the mitigation line near $5,000 to $15,000. That money buys a 2 to 4 week parallel billing run, a reconciliation pass, and support capacity through the first two billing cycles.
Do subscription-migration best practices differ meaningfully for consumer (DTC) subscriptions versus B2B recurring/replenishment orders?
B2B replenishment and DTC subscriptions diverge at the payment mechanism, not the cadence. Shopify Subscriptions cannot be used with draft orders (verified September 2026), and draft orders plus payment terms are how most B2B reorder flows actually run. DTC migrations are a billing-token problem; B2B replenishment migrations are usually a purchase-order and approvals problem wearing a subscription label.
How do we communicate a subscription-platform migration to high-LTV, long-tenured subscribers specifically, versus the general subscriber base?
High-LTV subscribers need a named-sender email before the migration, not a system notice after it. Send a personal note from a real person 10 to 14 days ahead, name the change, confirm the price and cadence are unchanged, and give a direct reply address. Reserve the generic transactional notice for the rest of the base; tenure-weighted revenue justifies the extra handling.
How do we decide whether to migrate ALL subscribers at once versus staggering the cutover by cohort (e.g., newest subscribers first, as a lower-risk test group)?
Cohort-staggered cutover beats a big-bang migration above roughly 2,000 active subscribers, and the right first cohort is newest subscribers on cards held by your current processor. Newest subscribers carry the freshest payment credentials and the lowest tenure-weighted LTV, so a failed transfer costs least there. Below about 2,000 contracts, a single-window migration with a parallel billing run is simpler and cheaper.
Is it ever the right call to pause new subscription sign-ups during a platform migration, or does that hurt growth more than the migration risk justifies?
Pausing new subscription sign-ups during a platform migration is the wrong default for almost every mid-market merchant. Freeze the sign-up surface only for the hours around the actual billing cutover, not for the whole 60 to 90 day migration window (July 2026 research). A multi-week freeze costs compounding cohort growth to avoid a risk that rehearsal removes.
Should we migrate to a Shopify-native subscription setup, or keep our subscription app (Recharge/Skio) completely separate from the core platform migration timeline?
Subscription migration and platform migration belong on separate timelines. Deploi keeps the subscription app live through the replatform and rebuilds only the product-page purchase-option layer on the new theme, roughly 46 hours of scoped work. Coupling the two puts payment tokens, billing state and theme cutover in the same release window, which is where the 2 to 5% subscriber loss reported for migrations concentrates (July 2026 research).
Should we use the subscription-platform migration as an opportunity to renegotiate our subscription app's pricing tier, given our subscriber count has likely changed since we first signed up?
Renegotiate the subscription app contract before the migration starts, because leverage evaporates once the destination platform is chosen. Recharge lists $25, $99 and $499 monthly tiers plus 1.34 to 1.49% and $0.19 per transaction; Loop runs free to $399 monthly at 0.75 to 1.0%; Skio is a single $599 monthly tier at 1% plus $0.20 (all verified September 2026).
What questions should we ask a migration agency specifically about their subscription-migration track record before trusting them with an active subscriber base?
Ask a migration agency 3 questions: the subscriber count of their last three subscription migrations, the payment-method transfer rate achieved on each, and the name of the destination platform. Vague answers to those three are disqualifying. Agencies that have really done this will also volunteer the parallel-run length and who handled the support surge, because both are where the work actually lives.