Migrations & Replatforming
Powered by Deploi
Common Questions
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 run Lightspeed and Shopify POS side by side while building out the new ecommerce store, or migrate everything in one cutover?
A parallel run works for catalog and inventory and fails for the register. Lightspeed's own Shopify integration requires Retail POS to be the system of record and warns that updates made in Shopify may be overwritten or cause syncing issues (Lightspeed, September 2026). Two live registers against one stock pool produce two counts.
Does customer purchase history and loyalty-points balance transfer from Lightspeed Retail to Shopify, or does that data get lost?
Purchase history does not transfer. Shopify's customer CSV carries Total Spent and Total Orders columns, and the field reference says of each that the column "isn't imported with customer details" (Shopify Help Center, September 2026). Lightspeed X-Series exports a loyalty_balance column, but no Shopify field receives it. Order history needs a separate third-party import.
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).
Do SuiteCommerce's bulk-pricing tables (common in B2B/wholesale setups) migrate to Shopify B2B's volume-pricing rules, or do they need rebuilding?
SuiteCommerce bulk-pricing tables need rebuilding, though not for the reason most teams expect. Shopify allows up to 10 price breaks per product, while a NetSuite quantity pricing schedule allows only 4 non-zero quantity levels (Shopify Help Center and Oracle NetSuite docs, September 2026). The break count fits. The calculation basis does not.