Migrations & Replatforming
Powered by Deploi
Common Questions
How do I migrate from Lightspeed Retail (POS) to Shopify without disrupting in-store sales during the transition?
A Lightspeed Retail to Shopify migration keeps stores selling when registers move only after catalog and inventory are live, one store at a time, because the risk is two systems counting the same stock. Shopify's Store Migration app imports only products and customers, not gift cards, loyalty balances or orders, and its Lightspeed path is in early access for certain stores (Shopify Help Center, October 2026).
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 we map a legacy platform's subscription-app integration to Recharge, Skio, or Loop Subscriptions, given the 2026 Recharge-Skio acquisition uncertainty?
A legacy subscription integration maps onto Shopify's subscription contract first, not onto a vendor: rebuild the selling plan, the purchase option on the product page, and the billing policy, then choose the portal. Loop Subscriptions wins that portal choice as of September 2026, at $99 to $399 per month, because Recharge is still digesting its $105M Skio acquisition, closed 30 April 2026.
How does Lightspeed's built-in vendor/purchase-order management map onto Shopify's native tools or Stocky-successor inventory apps?
Shopify now has native purchase orders and supplier records in the admin, added in June 2026, and Stocky was retired on 31 August 2026 (Shopify, September 2026). Neither purchase orders nor suppliers appear in the Admin API, so nothing imports, integrates or migrates automatically. Choose the destination system before you export anything from Lightspeed.