Migrations & Replatforming
Powered by Deploi
Common Questions
How do I migrate loyalty program points/tiers/history to Shopify during a full replatform?
Loyalty point balances and current tier migrate by CSV import; earn and redemption history does not. Smile.io requires a brand-new account on the destination platform and moves only current balances and current tier, and LoyaltyLion imports email plus points but "can't import customers' historic orders" (per both vendors' help centers, September 2026). Keep the program disabled until cutover finishes.
How do customer tags and segments built up over years on the old platform migrate to Shopify's customer tagging and segmentation system?
Customer tags migrate through Shopify's customer CSV import as a comma-separated Tags column. Saved segments do not migrate. Shopify segments are rebuilt as ShopifyQL queries, and metafield-based filters work only for four data types: date and time, number, text, and true or false (per Shopify Help Center, September 2026).
How do multi-location company hierarchies (headquarters plus regional branches, each with different pricing) migrate to Shopify B2B's company/location model?
Shopify B2B has exactly two levels: a company and its company locations. The Company object in the Admin API carries no parent or child company field, so a three-level headquarters-to-region-to-branch tree flattens on import (Shopify developer docs, September 2026). Per-branch pricing survives, because catalogs and payment terms both attach at the location.
What's the honest churn-risk estimate for a subscription-program migration, and what benchmark should we hold the migration agency to?
Subscriber churn from a subscription-platform migration runs 2 to 5% by the community-reported envelope (July 2026 research), and payment-method transfer is where that loss concentrates. Hold the agency to a card-retention rate, not a churn rate: the number to write into scope is the percentage of active payment methods that transfer without re-collection. Churn follows from it.
How do subscription discount/pricing-lock contracts (grandfathered pricing) get preserved when migrating the underlying subscription data to Shopify?
Grandfathered subscription pricing survives a migration only when it is written onto each contract line at import. Shopify's SubscriptionLineInput carries a required currentPrice field, set independently of the selling plan, plus an optional pricingPolicy that "describes expected price changes of the subscription line over time" (per Shopify's docs, September 2026). Selling-plan pricing otherwise applies.
Do subscription-migration best practices differ meaningfully for consumer (DTC) subscriptions versus B2B recurring/replenishment orders?
B2B replenishment and DTC subscriptions diverge at the payment mechanism, not the cadence. Shopify Subscriptions cannot be used with draft orders (verified September 2026), and draft orders plus payment terms are how most B2B reorder flows actually run. DTC migrations are a billing-token problem; B2B replenishment migrations are usually a purchase-order and approvals problem wearing a subscription label.