# Should we migrate to a Shopify-native subscription setup, or keep our subscription app (Recharge/Skio) completely separate from the core platform migration timeline?

Reviewed by Martin Dejnicki, Director of SEO & AI Search · facts verified October 9, 2026 · canonical: https://deploi.ca/shopify/faq/native-subscriptions-or-keep-recharge-skio

## Short answer

Subscription billing belongs on its own timeline, not inside the core platform migration. Keep Recharge or Skio billing through the replatform; rebuild only the product-page purchase options on the new theme. Shopify recommends pausing billing in the current app while contracts and payment methods move ([Shopify developer docs](https://shopify.dev/docs/apps/build/purchase-options/subscriptions/migrate-to-subscriptions-api/migrate-customer-information), October 2026), so weigh Shopify Subscriptions only after two clean billing cycles.

- **Billing while contracts move:** Paused in the current app. Shopify: "We strongly recommend that you pause any billing in your current application while migrating customer payment methods and contracts" (October 2026) ([Shopify developer docs, Migrate customer information to Shopify](https://shopify.dev/docs/apps/build/purchase-options/subscriptions/migrate-to-subscriptions-api/migrate-customer-information))
- **Theme Shopify Subscriptions needs:** Sections and blocks. Supported free themes: Online Store 2.0 themes built by Shopify, Horizon, Debut 15.0 or later and Brooklyn 17.0 or later (October 2026) ([Shopify Help Center, Shopify Subscriptions app eligibility considerations](https://help.shopify.com/en/manual/products/purchase-options/subscriptions/shopify-subscriptions/considerations))
- **Repeated failed renewals after the move:** Can cancel the contract for good. Shopify: repeated failed renewals can pause, skip or cancel a subscription, and "Updating a payment method can't restore a cancelled subscription contract" (October 2026) ([Shopify Help Center, Migrating payment methods to your Shopify account](https://help.shopify.com/en/manual/products/purchase-options/subscriptions/migrating-payment-methods))
- **Community-reported migration loss:** 2 to 5% of subscribers. Merchants' own accounts of subscription platform migrations, from the July 2026 research behind Deploi's migration record; not a measured average ([Deploi Build vs. Buy, Recharge Alternatives: Build or Buy the Subscription Migration?](https://deploi.ca/shopify/build-vs-buy/subscription-platform-migration))

## Deploi's call

Keep Recharge or Skio completely separate from the core platform migration, and weigh Shopify-native subscriptions only after the new storefront has billed cleanly. Decouple by default. The replatform gets the theme and the purchase-option layer; the billing engine gets its own quarter.

**WAIT: Keep the subscription move out of the replatform when**

- The replatform changes the theme, catalog or checkout in the same window, so a billing fault would hide inside a storefront fault.
- A billing move would need the pause Shopify recommends while contracts and payment methods migrate ([Shopify developer docs](https://shopify.dev/docs/apps/build/purchase-options/subscriptions/migrate-to-subscriptions-api/migrate-customer-information), October 2026).
- You have more than about 2,000 active subscribers, above the band where [Deploi's migration record](https://deploi.ca/shopify/build-vs-buy/subscription-platform-migration) calls the vendor's migration service enough on its own (October 2026).
- Peak season falls within two billing cycles of the storefront launch.

**BUY: Fold a bought migration into the cutover only when**

- The subscription platform is the reason for the replatform, so the two were one project from the start.
- Fewer than about 2,000 subscribers sit on simple plans, where the record calls the destination's migration service the right buy ([Deploi Build vs. Buy](https://deploi.ca/shopify/build-vs-buy/subscription-platform-migration), October 2026).

## Why are a replatform and a subscription migration two projects?

A replatform and a subscription migration are two projects because they fail in different ways. A replatform moves catalog, customers, orders, content and theme, and a bad launch has a rollback. A subscription migration moves billing contracts and payment credentials, and a failed charge has none. Shopify warns that repeated failed renewals can pause, skip or cancel a subscription, and that "Updating a payment method can't restore a cancelled subscription contract" ([Shopify Help Center](https://help.shopify.com/en/manual/products/purchase-options/subscriptions/migrating-payment-methods), October 2026).

Shopify's migration guide adds a second reason: "We strongly recommend that you pause any billing in your current application while migrating customer payment methods and contracts" ([Shopify developer docs](https://shopify.dev/docs/apps/build/purchase-options/subscriptions/migrate-to-subscriptions-api/migrate-customer-information), October 2026). So a billing move needs its own pause, and a launch weekend has no room for one. Whether to leave Recharge or Skio at all is [the cost-benefit case for moving to Shopify Subscriptions](https://deploi.ca/shopify/faq/recharge-skio-to-native-subscriptions-cost-benefit), a separate decision from when the subscription work runs.

## In what order should the replatform and the subscription work run?

The storefront goes first and the billing engine last, so each cutover can fail on its own and be read on its own.

1. Keep the existing subscription platform live and billing throughout the replatform.
1. Rebuild the product-page purchase options natively on the new theme, so new sign-ups land in your own markup rather than a vendor widget.
1. Cut the storefront over.
1. Let two full billing cycles run clean on the new storefront.
1. Then, and only then, open the question of whether the billing platform itself should move, to Shopify Subscriptions or anywhere else.

Keeping the two apart has a real cost: a second change-management cycle and a second round of subscriber emails, and merchants reasonably dislike both. So plan [the message for long-tenured, high-value subscribers](https://deploi.ca/shopify/faq/subscription-migration-messaging-high-ltv-subscribers) as its own piece of work, and use [the order of operations for moving an active program](https://deploi.ca/shopify/faq/migrate-active-subscriptions-during-replatform) once step 5 arrives. We still take two cutovers over one window in which a theme regression and a billing regression are indistinguishable at 2am.

## What does Shopify Subscriptions need from the new theme?

Shopify Subscriptions needs a theme that is "compatible with sections and blocks" before it can display subscription products ([Shopify Help Center](https://help.shopify.com/en/manual/products/purchase-options/subscriptions/shopify-subscriptions/considerations), October 2026). Shopify lists the free themes it supports: any Online Store 2.0 theme built by Shopify, the Horizon family, Debut 15.0 or later, and Brooklyn 17.0 or later. If you're unsure about another theme, Shopify says to contact its developer. A replatform is the natural moment to meet that requirement, which is a real argument for sequencing the theme work first.

The purchase options are theme work whichever app bills. Subscription apps create selling plans, and a theme can render them with Liquid and JavaScript ([Shopify developer docs](https://shopify.dev/docs/storefronts/themes/pricing-payments/subscriptions), October 2026). So a selector built into the new theme during the replatform reads whichever app's selling plans exist (Deploi's reading of that guide). That means it can survive a later billing move, native or paid.

## When is folding the subscription move into the replatform defensible?

Folding the subscription move into the replatform is defensible only when the subscription platform is the reason for the replatform, or when fewer than about 2,000 active subscribers sit on simple plans; outside those two cases, the two stay apart.

> **When not to keep the two timelines apart**
> - **The subscription platform is the reason for the replatform.** You are leaving a platform its vendor no longer supports, so the two were one project from the start.
> - **Fewer than about 2,000 active subscribers on simple plans.** Deploi's subscription migration record calls the destination's migration service the right buy at that size ([Deploi Build vs. Buy](https://deploi.ca/shopify/build-vs-buy/subscription-platform-migration), October 2026), so the added risk is small enough to absorb into a larger cutover.

Between about 2,000 and 10,000, the same record adds your own reconciliation checklist to a vendor-led migration. From about 10,000 it scores the move CUSTOMIZE: buy the destination, then build the glue the import skips, such as contract mapping and payment-method transfer checks. That glue needs the same people as the launch, which is one more reason to give it its own quarter. Hold the agency to [a card-retention benchmark written into its scope](https://deploi.ca/shopify/faq/subscription-migration-churn-risk-benchmark), whichever timeline you choose.

## Deploi's point of view

**What we've seen.** The failure we keep meeting is not a bad migration script; it is a cutover weekend where nobody can tell whether a drop in subscription revenue is the theme, the feed or the billing move, because all three shipped together.

**What this page adds.** The sequencing, and the theme requirement that makes the purchase-option rebuild a natural part of the replatform rather than a separate ask, alongside Shopify's own advice to pause billing while contracts move.

## When this answer changes

- Shopify changes its advice to pause billing in the current app while contracts and payment methods migrate.
- Shopify changes the theme requirement for Shopify Subscriptions or the list of free themes it supports.
- Your storefront launch date moves into peak season or into the same quarter as the billing move.
- Recharge publishes the combined Recharge and Skio roadmap, which could force a billing move on its own schedule.
- Your subscriber count crosses about 2,000, where Deploi's migration record stops calling the vendor's migration service enough on its own.

## Sources

1. [Shopify developer docs, Migrate customer information to Shopify](https://shopify.dev/docs/apps/build/purchase-options/subscriptions/migrate-to-subscriptions-api/migrate-customer-information), checked October 9, 2026
2. [Shopify Help Center, Shopify Subscriptions app eligibility considerations](https://help.shopify.com/en/manual/products/purchase-options/subscriptions/shopify-subscriptions/considerations), checked October 9, 2026
3. [Shopify Help Center, Migrating payment methods to your Shopify account](https://help.shopify.com/en/manual/products/purchase-options/subscriptions/migrating-payment-methods), checked October 9, 2026
4. [Shopify developer docs, Subscriptions](https://shopify.dev/docs/storefronts/themes/pricing-payments/subscriptions), checked October 9, 2026
5. [Deploi Build vs. Buy, Recharge Alternatives: Build or Buy the Subscription Migration?](https://deploi.ca/shopify/build-vs-buy/subscription-platform-migration), checked October 9, 2026, Deploi research