Migrations & Replatforming
Powered by Deploi
Common Questions
How do I migrate an active subscription program (Recharge, Skio, or a legacy platform's native subscriptions) during a full platform replatform?
An active subscription program moves as its own project, sequenced after the storefront cutover rather than inside it. Shopify imports contracts through the subscriptionContractAtomicCreate mutation, but payment methods follow only when the same processor (Stripe, Braintree, PayPal Express or Authorize.net) connects as a secondary gateway, and migrating card numbers requires Shopify Plus or Enterprise (per Shopify's docs, September 2026).
How do multiple simultaneous B2B catalogs (one per customer segment) migrate to Shopify's 3-catalog limit on non-Plus plans, if we exceed that number?
Shopify caps Basic, Grow and Advanced at 3 active catalogs across all B2B markets, with unlimited catalogs on Plus (Shopify Help Center, September 2026). The count is rarely the binding constraint. On non-Plus plans catalogs attach to B2B markets rather than directly to company locations, so a per-segment model has to be rebuilt around pricing rules, not segments.
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?
Migrating from Recharge or Skio to Shopify's native Subscriptions app trades a per-order fee for a worse subscriber portal. Shopify Subscriptions is free and bills weekly, monthly or yearly, but it does not work with bundles, draft orders or local payment methods (verified September 2026). Deploi scores the move CUSTOMIZE: rebuild the product-page purchase-option layer now, and move billing only when the portal gap closes.
How do wholesale/B2B customer net-terms payment history and credit-limit data migrate as customer metadata during a platform switch?
Shopify B2B has no native credit-limit field, so credit limits and payment history migrate as metafields on the company or company location (per Shopify's Admin API docs, September 2026). CompanyLocation exposes billing address, catalogs, payment terms and tax settings, but nothing that stores a limit or an aging balance. Enforcement is custom work or an app.
What happens to active subscription contracts' billing cycles and payment tokens when migrating subscribers between any platform and Shopify's subscription data model?
Two contract-level fields decide whether a subscriber migration succeeds: nextBillingDate and the payment method reference. Shopify requires nextBillingDate on every imported contract and treats it as "independent of billing cycles", and payment methods import through customerPaymentMethodRemoteCreate only from Stripe, Braintree, PayPal Express or Authorize.net connected as a secondary gateway (per Shopify's docs, September 2026).
Should we migrate to a Shopify-native subscription setup, or keep our subscription app (Recharge/Skio) completely separate from the core platform migration timeline?
Subscription migration and platform migration belong on separate timelines. Deploi keeps the subscription app live through the replatform and rebuilds only the product-page purchase-option layer on the new theme, roughly 46 hours of scoped work. Coupling the two puts payment tokens, billing state and theme cutover in the same release window, which is where the 2 to 5% subscriber loss reported for migrations concentrates (July 2026 research).