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?
Short answer
Pausing new subscription sign-ups for a whole platform migration is the wrong default, so take the subscribe option down only for the hours around the billing cutover. Recharge's guide puts new subscribers on Recharge before the old data is exported (Recharge Help Center). Skio wants the store selling Skio subscriptions first: at least 24 to 36 hours by its migrations guide (Skio Help Center), about 24 by its overview (Skio Help Center, October 2026).
- Recharge's migration order
- Launch, export from day 3, migrate on day 8Recharge's example launches Recharge on 1 January, exports from the old system on or after 3 January once new subscribers flow through Recharge, and migrates on 8 January (October 2026).Source: Recharge Help Center (Migrating to Recharge)
- Skio's clean break
- 24 to 36 hours, or about 24, live on Skio firstSkio's migrations guide says at least 24 to 36 hours live on Skio before it checks new subscriptions; its data migration overview says typically 24. Skio can run a top-up migration for holdouts (October 2026).Sources: Skio Help Center (Data Migration: An Overview, Skio Migrations Guide)
- What Shopify asks you to pause
- Billing in the old app, not sign-upsShopify strongly recommends pausing billing in the current app while payment methods and contracts migrate, to avoid double-billing a contract (October 2026).Source: Shopify developer docs (Migrate customer information to Shopify)
- Skio moves from outside Shopify
- One round, 1 to 3 weeks, no expeditingSkio can't run multiple migration rounds from outside Shopify, and the merchant must stop new subscriptions on the old platform once the migration completes (October 2026).Source: Skio Help Center (Migrating subscriptions from outside of Shopify (Woocommerce, BigCommerce, Magento, Custom solutions))
Deploi’s call
Pause new sign-ups for the cutover hour, not the migration quarter. A multi-week sign-up pause is a scoping failure disguised as caution.
CustomizeKeep sign-ups open and sync the late contracts when
- The destination can sell to new subscribers before the old base moves, so sign-ups keep flowing; Recharge's and Skio's own guides use that order (Recharge Help Center, Skio Help Center, October 2026).
- Someone owns the delta step: a scripted re-export, or Skio's top-up migration for subscribers who slip into the old app (Skio Help Center, October 2026).
- A promotion, a paid-acquisition flight or peak season falls inside the migration window.
- The program needs scripted glue, the profile of 10,000 to 50,000 subscribers that our subscription migration record scores CUSTOMIZE (October 2026).
WaitTake the subscribe option down, for hours only, while
- The product page's subscribe option is switching from the old app to the new one.
- Billing state is in flight at cutover, the hour the old app's billing pauses, as Shopify recommends while contracts and payment methods move (Shopify developer docs, October 2026).
- A one-round migration from outside Shopify is pulling data while the old storefront could still take sign-ups (Skio Help Center, October 2026).
Basis: Recharge Alternatives: Build or Buy the Subscription Migration?, our Build vs. Buy decision record, scored CUSTOMIZE.
Why is a multi-week sign-up pause the wrong default?
A multi-week sign-up pause is the wrong default because a subscription program compounds, so a cohort you skip is lost for its whole lifetime. A cohort you do not acquire in October is not one month of revenue; it is every renewal that cohort would have paid. The migration risk a pause avoids is bounded by comparison: the contracts created during the window, which a delta step can map. Community-reported subscription migrations run 60 to 90 days, per July 2026 research in our subscription migration record (October 2026). So a pause across the whole window gives up two or three monthly cohorts (Deploi arithmetic). That trade only arises once you have decided to migrate, which is the cost-benefit case for leaving Recharge or Skio.
How do Recharge and Skio keep sign-ups open during a migration?
Recharge and Skio keep sign-ups open by moving new subscribers to the destination first and the existing base second. Recharge's migration guide has you export from the old platform after launching on Recharge, so "you can ensure all existing data is captured for migration" (Recharge Help Center, October 2026). Its worked example launches Recharge on 1 January and exports on or after 3 January, "to ensure new subscribers are flowing through Recharge correctly", before an 8 January migration. Skio requires the store to be "live with Skio & selling Skio subscriptions" before its team migrates, so that "no new subscribers are missed": typically 24 hours by its data migration overview (Skio Help Center, October 2026), at least 24 to 36 hours by its migrations guide (Skio's migrations guide, October 2026). Shopify asks for a pause too, but of billing, not sign-ups: "We strongly recommend that you pause any billing in your current application while migrating customer payment methods and contracts" (Shopify developer docs, October 2026).
When is a sign-up freeze the right call?
A sign-up freeze is the right call only when two or more of these are true:
- The destination platform has no supported path for contracts created after the export snapshot, and your agency has not written a delta-sync script.
- The cutover window exceeds 72 hours, so "just re-run the export" is not available.
- Sign-up volume during the window is small enough that the lost cohort is immaterial, which at $20M to $500M a year it usually is not.
- The vendor migrates in one round from a fixed snapshot. Skio can't run a move from outside Shopify in "multiple" rounds, and says its 1 to 3 week queue "cannot be expedited" (Skio Help Center, October 2026).
Even then, close sign-ups on the old platform only once the new storefront can take them. Skio leaves the merchant "ensuring that no new subscriptions can be created in the previous platform" once the data migration is complete (Skio Help Center, October 2026), so the old platform stays open until the new one holds the base.
What replaces a long freeze?
A delta step replaces a long freeze: export the base, migrate it, then re-export and map only the contracts created between the snapshot and cutover. Skio's own version is a "top-up" migration that gathers holdouts from the legacy platform, and its team scans for apps such as Tapcart and Rebuy that could still create subscriptions in the old app (Skio Help Center, October 2026). Without a vendor top-up, the delta step is a scripted job beside the contract mapping that our subscription migration record counts as glue to build (October 2026). Either way, a multi-week commercial freeze becomes a few hours of technical freeze, because only the late contracts wait. Ask any agency what it does about contracts created after the snapshot; an answer of "we paused sign-ups" tells you its default.
A short freeze at the moment of cutover is a different decision, and it is usually correct. Taking the subscribe option off the product page for the hour that billing state is in flight avoids a class of bug that is unpleasant to unwind. Say hours, write hours into the plan, and hold the agency to hours.
When is pausing sign-ups the wrong move?
Pausing sign-ups is the wrong move across a promotion, a paid-acquisition flight already in market or a seasonal peak, because the cost is the spend you already committed, not only the revenue in the window.
Deploi’s point of view
Our own position, from building on Shopify. Kept apart from the sourced facts above.
- Where we disagree
- Some migration plans still present a sign-up freeze as best practice. In our judgment it is best practice for the migrator, not for the merchant, and the two are not the same interest. Recharge's and Skio's own guides don't ask for one: both send new subscribers to the destination before the old base moves.
- What we ask for first
- The delta-sync script. In our judgment, a freeze proposed in a kickoff deck usually stands in for a script nobody has written yet; ask for the script and the freeze request tends to disappear.
- What this page adds
- The parent decides whether to leave Recharge or Skio at all. Inside a migration, Recharge's and Skio's own sequences move new sign-ups to the destination before the old base, and a delta step catches the stragglers, so the sign-up freeze shrinks to hours.
Decision records behind this answer
When this answer changes
- Recharge or Skio changes its migration order, for example by asking merchants to pause sign-ups.
- Skio starts running migrations from outside Shopify in more than one round, or changes its 1 to 3 week queue.
- Shopify changes its recommendation to pause billing in the current app during a migration.
- A promotion, a paid-acquisition flight or peak season moves into the migration window.
- Shopify or a subscription vendor ships a supported import for contracts created after the export snapshot.
Related questions
This follows from 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?
- What questions should we ask a migration agency specifically about their subscription-migration track record before trusting them with an active subscriber base?
Test a migration agency's track record with 3 questions about its last 3 subscription migrations: how many subscribers moved to which platforms, what payment-method transfer rate it achieved, and where the cards were vaulted.
- 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 migrating everyone at once above roughly 2,000 subscribers (Deploi practice); start with newest subscribers on cards your current processor holds.
Sources
Every figure on this page traces to one of these. Official and vendor pages are checked on the date shown; Deploi records are our own published decisions.
- Recharge Help Center, Migrating to Recharge
- Skio Help Center, Data Migration: An Overview
- Shopify developer docs, Migrate customer information to Shopify
- Skio Help Center, Migrating subscriptions from outside of Shopify (Woocommerce, BigCommerce, Magento, Custom solutions)
- Skio Help Center, Skio Migrations Guide
- Deploi Build vs. Buy, Recharge Alternatives: Build or Buy the Subscription Migration?