How do we migrate active subscription contracts (Recharge, Skio, or native Shopify Subscriptions) from one Shopify store to another during consolidation?
Store-to-store subscription moves are decided by the payment vault, not the contract data. Methods vaulted in Shopify Payments need Shopify Payments approval to move between stores, Shop Pay methods cannot be migrated store to store, and methods held by Stripe, Braintree or Authorize.net transfer only if the destination store connects that processor as a secondary gateway (per Skio, September 2026).
Why Shopify-to-Shopify is harder than it sounds
Merchants assume a consolidation is the easy case: same platform, same data model, same APIs. The contract data is indeed the easy part. The mandate is not, because two Shopify stores are two merchant accounts, and a vaulted payment credential is scoped to a merchant account.
The three vault situations
| Where the payment method lives | What happens store A → store B |
|---|---|
| Shopify Payments vault | Requires Shopify Payments team approval to transfer |
| Shop Pay | Cannot be migrated between stores |
| Stripe / Braintree / Authorize.net (e.g. legacy Recharge) | Transfers if store B connects the same processor as a secondary gateway |
Per Skio's store-A-to-store-B migration guidance, verified September 2026.
Add the PayPal case from Shopify's own documentation: billing agreements "belong to the account that created them", and if the new account cannot use them, "existing renewals can fail" (per Shopify's Help Center, September 2026).
The operational constraints nobody schedules for
- The source store has to keep its subscription app installed for the export to run, even if the store is otherwise dormant (per Skio, September 2026).
- Customer accounts are exported and imported manually between the two stores.
- One to three weeks of vendor queue time, which "cannot be expedited", and no accommodation for multiple migration rounds (per Skio, September 2026). Plan one clean pass; there is no second bite.
- On the Shopify side,
subscriptionContractAtomicCreatestill needs apaymentMethodIdon the destination store, or you setpaymentProcessingPolicytoSKIP_PAYMENT_AND_CREATE_UNPAID_ORDERand reconcile by hand (per Shopify's docs, September 2026).
So what do you actually do?
Answer the vault question in week one, before the consolidation business case is signed. If a material share of subscribers sit in Shop Pay, that share is a re-collection campaign, and its expected loss belongs in the consolidation model rather than in a status update three months later. If the vault is Stripe or Authorize.net and the destination store can attach it, the move is genuinely mechanical.
When not to consolidate. A brand running two stores for two genuinely separate customer bases, with most subscribers paying through Shop Pay, is being asked to trade a real revenue risk for an operational tidiness gain. Expansion stores on Shopify Plus exist so that multiple storefronts do not have to mean multiple platform contracts: a main store plus nine expansion stores is included in the Plus platform fee, with additional stores at $300 USD per month (per Shopify's Plus pricing page, September 2026). Structure is often the cheaper answer than consolidation.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Consolidation decisions should be made on the vault mix, not the org chart. We have yet to see a store-merge business case that priced the Shop Pay cohort correctly at the outset, and that cohort is the one that cannot be moved at all.
- What we’ve seen: The source store staying alive and licensed through the migration window surprises finance every time. It reads as paying twice for a store you are shutting down; it is actually the export dependency, and it belongs in the budget from day one.
- Where we disagree: "Same platform, so the data just moves" is the standard framing for a Shopify-to-Shopify merge. Same platform, different merchant account. And the merchant account is the boundary that matters for anything with a stored payment credential behind it.
- What this page adds: that the Shopify-to-Shopify case has a worse payment story than a legacy-platform migration in one specific way: Shop Pay, which has no secondary-gateway equivalent to fall back on.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.