What's the actual subscriber-loss risk migrating from a legacy subscription platform onto Skio mid-replatform?

Where does subscriber loss come from when you move onto Skio mid-replatform?

Subscriber loss on a move onto Skio mid-replatform comes from six places, and only Shop Pay and Shopify-vaulted cards below Plus sit outside your control. Mid-replatform, every subscriber has to reach the new store still billable, so the deciding question is where each card lives.

Size those two cohorts first, because neither has a documented route. Where each saved payment method sits in a store-to-store move has its own answer.

How do you get your own loss number before cutover?

Your own loss number comes from Skio before cutover, not from an industry range. For a move from outside Shopify, Skio runs a required test before front-end integration starts. The test shows what percentage of subscriptions can migrate and what percentage cannot, for missing payment method data (Skio Help Center, October 2026). For every migration, Skio's data preview gives the total to be migrated and lists each subscription it cannot migrate, and why (Skio Help Center, October 2026).

Read those counts against the right baseline. Recharge counts every product as its own subscription, while one Skio subscription can hold several products, so the two totals differ by design (Skio Help Center, October 2026). The community-reported 2 to 5% loss is merchants' own accounts of past migrations, not a forecast for your base (Deploi Build vs. Buy, July 2026 research). So the term to write into the agency's scope is a card-retention rate you can hold it to, measured against Skio's preview.

What has to be settled before the migration date?

Four things have to be settled before Skio sets a migration date, and the card vault comes first because every later step depends on it.

1. Find where every card is vaulted. Skio says Shopify requires primary processors to vault cards in the Shopify Payments vault. The one exception is legacy Recharge, whose cards may sit in Stripe, Braintree or Authorize.net. They can move if the new store connects the same account as a secondary gateway (Skio Help Center, October 2026).
2. Ask Shopify for the payment method migration early. Shopify's migration service moves card numbers only for stores on Plus or Enterprise (Shopify Help Center, October 2026). On other plans, an old Stripe, Braintree, PayPal Express or Authorize.net gateway stays connected until the last card moves. Shopify says that slow drip "can take months or even years" (Shopify Help Center, October 2026). Cards already in Shopify's own vault have no such fallback.
3. Fill in Skio's variant-mapping file yourself, and check it twice. Skio treats that file, and any data preview you approve, as your verification, and says errors in either "may cause discrepancies" (Skio Help Center, October 2026). Freeze the catalog while you map.
4. Put the product-page purchase option live first. Skio migrates no existing subscriber until the store is live and selling Skio subscriptions: at least 24 to 36 hours by its migrations guide (Skio Help Center), about 24 by its overview (Skio Help Center, October 2026).

What has to happen on and after migration day?

Migration day moves the billing, so four things have to happen on that day and in the first cycle after it.

1. Stop the old platform's billing on migration day, in writing. Skio tells merchants to cancel or disable billing in the former platform that day. Skio holds billing for migrated subscriptions until it is sure the old platform has stopped charging (Skio Help Center, October 2026).
2. Watch the subscriptions that arrived without a card. Skio routes a migrated subscription with no valid payment method into its Payment Recovery at the next billing attempt (Skio Help Center, October 2026). So the first cycle can look like a failed-payment spike.
3. Time the subscriber emails to each first charge date, not to go-live, with the four-message migration sequence.
4. Check billing dates, prices and cycle counts on a sample before the first charges run. A double charge or a skipped cycle reads as a cancellation to the subscriber, which is why the sample comes before the full run.

What does Recharge's ownership of Skio add to the risk?

Recharge's ownership adds an open roadmap question to any move onto Skio. Recharge announced in April 2026 that "Skio is joining the Recharge team", and the post's AI summary says Recharge "has acquired Skio" (Recharge, October 2026). The post also says "nothing is changing today" for merchants on either platform, and that details of the combined roadmap are "coming in the months ahead". Skio's App Store listing now reads "Skio, a Recharge Company" (Skio on the Shopify App Store, October 2026), and neither page gives a closing date. Our Skio record treats choosing Skio as choosing Recharge's roadmap (Deploi Build vs. Buy, October 2026), so test Skio's exports before you need an exit. How the move fits a quarter is in the week-by-week calendar for a $10 million to $30 million brand.

When should the subscription move wait until after the replatform?

The subscription move should wait whenever the replatform itself is the risky part. One cutover with two failure modes leaves one weekend to tell a theme fault from a billing fault, so the safer plan is two cutovers.

Our migration verdict is CUSTOMIZE for that reason: the destination is a purchase, the migration work around it is a build, and that work does not have to ship on launch day (Deploi Build vs. Buy, October 2026).