Migrations & Replatforming
Powered by Deploi
Common Questions
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.
What order-level custom fields (gift messages, engraving instructions, delivery-date selections) need special handling during an order-history migration?
Order-level custom fields migrate as order and line item custom attributes, which Shopify's own documentation describes as holding a gift message, delivery instructions, or internal notes (per shopify.dev, September 2026). Gift messages and engraving text survive as key-value pairs. Delivery-date selections need a metafield with a date type, or they arrive as unvalidated strings.
Do return/RMA records and their approval history migrate cleanly to Shopify's returns model or a returns app like Loop/AfterShip?
Return records do not migrate. Shopify's returnCreate mutation requires at least one fulfilled line item that has not yet been refunded, and the Return object exposes no field for backdating a request or importing prior approval history (per shopify.dev, September 2026). Historical RMAs land as order notes or a read-only archive, not as returns.
How do vendor/supplier records and purchase-order history migrate as data objects during a platform switch, given Shopify has no native supplier-management model?
Historical purchase orders cannot be imported into Shopify, and Shopify says so plainly (Shopify Help Center, September 2026). Supplier records have no documented CSV import and no Admin API object, so they are rekeyed by hand or held in the app or ERP that will own purchasing. Decide that owner before extraction, not after.
What review-and-UGC plugin functionality maps to Yotpo, Okendo, or Judge.me on Shopify, and how do star ratings/photos actually transfer?
Review migrations move text, star ratings and dates through a CSV import wizard; videos are not imported by default, and verified-buyer status is re-earned by matching the reviewer's email to a Shopify order (per Judge.me's docs, September 2026). Shopify retired its own Product Reviews app in May 2024, so a third-party app is the only path.