What's the actual subscriber-loss risk migrating from a legacy subscription platform onto Skio mid-replatform?
Subscription platform migrations lose 2 to 5% of active subscribers and run 60 to 90 days, per the July 2026 research behind Deploi's migration decision page. The loss concentrates in the payment method: cards vaulted with Shopify require a Shopify Payments data transfer request, and Shop Pay payment methods cannot move to a new store at all (per Skio's migration docs, September 2026).
The loss is not spread evenly, so stop budgeting it that way
"Mid-replatform" usually means store A on the old platform, store B on the new one, and a subscriber base that has to arrive at store B still billable. That is a different project from swapping apps inside one store, and the difference is entirely about where the card lives.
| Where the loss comes from | Why it happens | What you control |
|---|---|---|
| Payment tokens that cannot be ported | Most modern setups vault the card in Shopify's vault, so the merchant has to ask the Shopify Payments team for a payment method data transfer (per Skio's migration documentation, September 2026) | The lead time. Open the request before you set a cutover date |
| Shop Pay payment methods | Skio states plainly that its team is unable to migrate Shop Pay payment methods from store A to store B (per Skio, September 2026) | Nothing. These subscribers re-authorize or churn |
| A gap in the PDP purchase-option experience | New signups stall while the selector, plan copy and discount display are rebuilt on the new theme | Everything. This is theme work |
| Contract state that imports do not carry | Vendor imports move contracts, not dunning state, portal customizations or churn-save rules (Deploi Build vs. Buy analysis, September 2026) | Scope it as agency time, not as a vendor deliverable |
| Billing anchors set wrong on import | A double charge or a skipped cycle reads as a cancellation to the subscriber | Everything. Dry-run it |
Note which rows are the platform's fault. One. The rest are yours, which is the good news, because the ones you control are the ones you can shrink.
The migration sequence that keeps the number near 2% instead of near 5%
- Find out where the cards are actually vaulted, before anything else. If the source store ran legacy Recharge on Stripe, Braintree or Authorize.net, the card data sits in that processor's vault and can be reached by connecting the same processor as a secondary gateway (per Skio, September 2026). If it sits in Shopify's vault, go to step 2.
- Open the Shopify Payments data transfer request first, not last. Plan gating applies: credit card data migration requires the Shopify Plus or Enterprise plan (per Shopify's Help Center, September 2026). On any lower plan this path does not exist and the answer is the slow drip described in step 3.
- Price the slow drip honestly if you are on it. Shopify's own guidance for a deactivated secondary gateway is that payment methods migrate gradually as customers update their billing details, and that it can take months or even years to fully migrate all payment methods (per Shopify's Help Center, September 2026). That is not a failure mode, it is the documented path.
- Do the variant mapping yourself, in a CSV, twice. Skio puts variant mapping on the merchant and warns that errors in mapping or in the migration preview create subscription discrepancies (per Skio, September 2026). Freeze the catalog while you do it.
- Rebuild the PDP purchase option before cutover, not after. New subscriber acquisition stops while the selector is missing, and a two-week acquisition gap costs more than the churn you are worrying about.
- Run the billing validation before the first charge. Anchors, prices and cycle indexes, on a sample first. The two follow-ups below cover the exact checks.
- Sequence the subscriber emails against the first post-migration charge date, not against your go-live date. Those are different days and subscribers only notice one of them.
- Name the date the old platform stops billing, in writing, and have someone confirm it stopped.
Honest boundaries
Skio's own timeline for a store-to-store migration is 1 to 3 weeks minimum and cannot be expedited (per Skio, September 2026). Prepaid gift subscriptions are not supported for that migration at all. And Skio is a Recharge company as of the acquisition that closed 30 April 2026, so a Skio decision today is a decision about Recharge's roadmap.
When NOT to do this mid-replatform
When the replatform itself is the risky part. Moving the storefront and the recurring revenue in the same window means one cutover with two failure modes and one weekend to diagnose them. If the subscriber base is the more valuable asset, launch the storefront first, keep the legacy platform billing through its own rails for a cycle, and move subscriptions as a second project. Our migration verdict is CUSTOMIZE for a reason: the destination is a purchase, the glue is a build, and the glue does not have to ship on launch day.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Subscriber loss in a mid-replatform migration comes from the payment-token re-authorization path and from any gap in the PDP purchase-option experience. It does not come from the platform you picked. We scored subscription platform migration CUSTOMIZE because the destination is a commodity and the glue is not.
- What we’ve seen: The number that moves is not the import success rate, it is the acquisition gap. Teams protect the existing subscribers with a comms plan and then run three weeks with a broken or missing purchase option on the product page, which quietly costs more than the churn they spent the budget preventing. The other recurring surprise is dunning: imports carry the contract, not the retry schedule, so week one after cutover looks like a payment-failure spike that is really a configuration gap.
- What it takes: roughly 46 hours of scoped work for native subscription purchase options on the product page, which is the piece of this you actually control (directional Deploi estimate from a small sample of engagements, not a measured average).
- Where we disagree: Every vendor sells migration as included and frames it as a data-movement problem. The data moves fine. What does not move is the payment token, the dunning state and the merchandising on the product page, and those three are where the 2 to 5% actually lives. Judge a destination platform on its exit terms and its vault story, not on the smoothness of its import.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.
Where we worked this out
Follow-up questions
How do I bulk-export Skio subscriber and consent data before switching to a different subscription app?
Skio exports subscriber data three ways: self-serve CSV files for subscriptions, orders and audit logs; a GraphQL API capped at 2,000 requests per minute per token; and a REST bulk export interface added 27 January 2026 (all verified September 2026). Those exports document no consent fields. Marketing consent lives on the Shopify customer record, which you already own.
How do we communicate a subscription-platform migration to active subscribers so they don't think their subscription was cancelled or their payment failed?
A subscription migration needs four subscriber messages to avoid reading as a cancellation: a notice 14 days before cutover, a portal-change note on cutover day, a payment-update prompt wherever a card did not transfer, and a confirmation on the first charge day (Deploi practice, not a Shopify requirement). Shopify's customerPaymentMethodSendUpdateEmail mutation sends the secure update link (per shopify.dev, September 2026).
What's the real implementation timeline for Skio on a $10M-$30M GMV Shopify Plus brand with an existing subscriber base to migrate?
A Skio implementation on a $10 million to $30 million GMV Shopify Plus brand with subscribers to migrate runs 60 to 90 days end to end, the community-reported envelope behind Deploi's migration decision page (July 2026 research). Skio's own store-to-store migration window is 1 to 3 weeks minimum and cannot be expedited (per Skio, September 2026). The rest is theme, data and billing work.