Shopify migration services: moving to or from Shopify

Most Shopify migrations are moves to Shopify, typically from a self-hosted WooCommerce, Magento or PrestaShop store whose team is tired of hosting, patches, plugin conflicts and developer dependency. Shopify is a reasonable answer when the catalog fits its product-and-variant model and the business can live with its checkout and URL conventions.

The other direction exists too. Stores leave Shopify when app subscriptions pile up, when they need a checkout or catalog logic Shopify will not allow, when a deep category tree or complex B2B pricing keeps fighting the collection model, or when they want full control of hosting and code (often moving to WooCommerce). Neither direction is automatically right. If the reason for moving is a theme that looks dated or a single missing feature, a redesign or one app may be cheaper than a platform change; the assessment should say so.

Shopify's own guidance is to import products first, then customers, then historical orders, so orders can link to the products and customers they belong to. The methods range from manual entry and CSV imports through migration apps from the Shopify App Store to custom scripts against the Admin API. For an established store we normally combine them: CSV or an import app for the bulk of the catalog, and scripted API work for what a CSV cannot express cleanly, such as metafields, metaobjects, order history with the right statuses, and redirects.

The constraints of the model decide most of the mapping work. A product has up to three option dimensions (for example size, colour, material), and every sellable combination is a variant with its own SKU, price and inventory. Extra product data lives in metafields or metaobjects that have to be defined before import. Categories become collections, manual or automated by rules, and a collection is not a tree. Customers arrive without passwords and must be invited to activate their accounts. Imported historical orders are records for reference and customer history, not live orders to be re-fulfilled, and Shopify notes that importing them can trigger new-order notifications to staff unless those are switched off first.

Shopify admin exports CSVs for products, customers and orders, which is enough for a first inventory but rarely for the migration itself. Metafields, metaobjects, collection rules, redirects, blog comments and multi-language content are more reliably pulled through the Admin API, and data held by apps (reviews, subscriptions, loyalty points, wishlists, bundles) lives with each app vendor and needs that vendor's export or API.

Two things cannot come out at all: customer password hashes and stored payment methods. Customers will set a new password on the target platform, and saved cards or subscription payment tokens depend on the payment gateway and its PCI process, never on a data export.

Moving to Shopify, the heavy lifting is almost always the catalog. Products with more than three option dimensions, or with options that change price like add-ons or engraving, must be split into separate products, remodelled with bundles, or handled by an app. Custom attributes and specification tables are mapped to typed metafields so they can be filtered and displayed. A multi-level category tree is rebuilt as collections plus navigation menus, and the filters customers used before are rebuilt on metafields or tags. Customer groups often become customer tags or, on Shopify Plus, B2B companies and catalogs, which we check against your plan.

Moving from Shopify, the transformation runs the other way: collections have to become categories, tags that carried business meaning have to become attributes, and metafields have to land in the target platform's custom-field system. In both directions we transform order statuses, tax and shipping lines, and product descriptions that contain theme-specific markup or app shortcodes.

Apps from the Shopify App Store replace most plugins or modules from self-hosted platforms, but they are replacements, not ports. Moving in, we list every plugin that does something customers or staff rely on, find the app or native feature that covers it, and flag what needs custom work. Moving out, we list every installed app, what data it holds and whether that data can be exported.

Themes do not transfer between platforms. Shopify themes are built with Liquid, so moving in means adapting a theme from the Shopify Theme Store or building a custom one, and moving out means rebuilding the storefront on the new platform. Checkout customization is limited on standard plans; on Shopify Plus it runs through Checkout Extensibility and Shopify Functions, not edited checkout templates. Payment gateways, shipping rates, tax settings, ERP, PIM, feeds and email marketing connections are configured or reconnected on the target, then tested with real orders before launch.

Shopify uses fixed URL paths: /products/{handle}, /collections/{handle}, /pages/{handle} and /blogs/{blog}/{handle}. The prefixes cannot be removed, so a store moving to Shopify almost never keeps its old URLs. Every indexed URL that matters, including products, categories, CMS pages, blog posts, and old URLs that already redirect, needs a mapped destination, uploaded as URL redirects in Shopify admin (Online Store > Navigation > URL redirects). Shopify applies a redirect only when the old path no longer resolves to a live page, so we test the map after import, not just before.

Leaving Shopify, the fixed paths are predictable, which makes the redirect map simpler, but the target platform must be able to serve 301s for the old /products/ and /collections/ paths. Either way we crawl the old site before migration, carry over titles, meta descriptions, alt text and canonical intent, crawl the new store on staging, and watch Search Console after launch. Nobody can guarantee rankings through a platform change; we can make sure no important URL is lost without a destination.

Customer passwords cannot be imported into Shopify, and Shopify does not export password hashes, so every Shopify migration involves an account activation or reset step. Shopify Markets covers multiple countries, currencies and languages in one store, but a source with several separate stores or store views may still be better as several Shopify stores; that is a business decision we make with you, not a default. Subscriptions depend on the subscription app and the payment gateway, and moving active subscribers without asking them to re-enter payment details is only possible where the gateway supports a token transfer.

Large catalogs, many variants per product, heavy B2B logic or long order histories change the effort and the method, so we check your real data against current Shopify limits and your plan during the audit.

A named lead owns the project from the first audit to post-launch QA. We audit the source store (catalog structure, custom data, customers, orders, apps or plugins, integrations, indexed URLs), agree a written mapping, and run a trial migration into a development store or staging target that you check record by record. Only after sign-off do we plan the launch: a content freeze, the full migration, a delta migration of orders and customers created since the trial, redirects, DNS and payment checks.

Import apps, scripts and automated comparisons help where they save time; a person approves every production decision. After launch we check orders, emails, feeds, redirects and Search Console, and fix what the first days of real traffic reveal.