01What moves from WordPress to Shopify, and what does not fit as it is

A WooCommerce store is a WordPress install with a commerce plugin and, almost always, many other plugins around it. Moving to Shopify brings the data —products, variants, images, customers, orders, pages and posts— but not the code: not the theme, not the plugins, not the PHP customisations. Each of those pieces is reviewed and either replaced, rebuilt or left out.

The general method is in the e-commerce migration SEO checklist. If the source store were PrestaShop, the differences are in the PrestaShop to Shopify migration guide. The usual project scope is described in the website and e-commerce migrations service.

Fig. 1 · Slugs, parameters and the 301 redirect table

02Slugs, parameters and the 301 redirect table

WordPress lets you customise permalinks: products under /product/ or /shop/, categories under /product-category/, posts with the date in the path. Shopify uses /products/, /collections/, /pages/ and /blogs/. The mapping table lists every URL with value —by traffic, external links or rankings— and its destination. The example below is fictional:

WooCommerce URL (example)Shopify destinationType
/product/ceramic-mug//products/ceramic-mugProduct
/product-category/kitchen//collections/kitchenCategory
/shipping-and-returns//pages/shipping-and-returnsPage
/2025/03/caring-for-ceramics//blogs/news/caring-for-ceramicsArticle

Filters and parameter-based searches rarely need a redirect per URL; they are reviewed in Search Console to decide which deserve a destination. Google explains how to handle a site move with URL changes at https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes

03Products, variants, images and stock: the pilot import

WooCommerce variable products become products with options and variants in Shopify. Global and custom attributes, SKUs, stock per variant, variant images and fields added by plugins all need checking. Before importing everything, a pilot import with a representative sample is compared with the original store, product by product.

04Customers and orders: history and accounts

Order history and customer data can be imported so customer service and reporting do not start from zero. At the end there is a count: how many products, customers and orders were in the source and how many are in the destination. Passwords do not move between platforms, so a message is prepared for customers to activate their account in the new store.

Fig. 2 · The blog and content pages

05The blog and content pages

Many WooCommerce stores have a blog with posts that rank. There are three routes: migrate it to the Shopify blog with redirects, keep it on WordPress for a while, or redirect what no longer adds value. What matters is deciding in writing and checking the internal links, images and metadata of every post that moves.

06Plugins, payments, shipping and cutover day

Every active plugin is reviewed with the same question: what does it do for the business today? Payment gateways, shipping rules, tax, transactional emails and ERP or invoicing integrations are reconnected or replaced. The cutover is rehearsed with test orders first. On the day, the domain is switched, the redirects go live and the new sitemap is submitted; Search Console is then monitored until the change has been recognised.

If the platform change comes with a new design, read the guide on whether to redesign a website or build a new one before closing the scope.