Moving from WooCommerce to Shopify without losing your SEO
Which columns to export from Woo, how variants and categories map onto Shopify products and collections, and the redirects to set up before you switch DNS.
Migration
Moving from WooCommerce to Shopify without losing your SEO
Which columns to export from WooCommerce, how variable products map
onto Shopify variants, and the redirect work that decides whether your
traffic survives the switch.

What actually breaks in a migration
Almost nobody loses their products in a platform migration. What they
lose is the accumulated search equity attached to those products – the
rankings, the backlinks and the indexed URLs built up over years of
trading. WooCommerce and Shopify structure URLs differently, so unless
you plan for it, every product page on your store changes address on
launch day and every link pointing at the old address returns a 404.
The second thing that breaks is variant structure. WooCommerce calls
them variable products with attributes; Shopify calls them variants
with up to three options. The two models overlap but they are not
identical, and a careless export produces either duplicate products or
products with no variants at all.
products can move in an afternoon. What takes time is the redirect
map, the image audit and the post-launch checks – budget for those
separately from the import itself.
Getting the right file out of WooCommerce
WooCommerce ships with a built-in exporter at
Products → All Products → Export. Two settings matter
more than the rest:
-
Export all columns, even the ones you think you do
not need. It is far easier to delete a column in Excel than to run
the export again after you discover the SKU field is missing. -
Include both product types. The default export
includes variations, but confirm it – a file with parent products
only will import as a catalogue of single-variant products.
Also export your categories and tags separately. WooCommerce
categories become Shopify collections, and getting them in first means
your products land in the right place instead of needing a second
pass.
Open the resulting CSV before you do anything else and check three
things: that prices are plain numbers with dot decimals, that image
URLs are absolute and publicly reachable, and that every row has a
SKU. Fix those in the spreadsheet, not later.
Mapping WooCommerce columns to Shopify
Most of the mapping is mechanical. These are the pairs that account
for the majority of a catalogue:
| WooCommerce column | Shopify field | Watch out for |
|---|---|---|
Name |
Title |
Straight copy |
SKU |
Variant SKU |
Must be unique per variant |
Regular price |
Variant Price |
Strip currency symbols |
Sale price |
Variant Compare At Price |
Reversed logic – see below |
Description |
Body (HTML) |
Shortcodes will not render in Shopify |
Categories |
Collections | Import collections first |
Images |
Image Src |
Comma-separated in Woo, one URL per cell or semicolon-separated in Shopify |
Attribute 1 name / value(s) |
Option1 Name / Option1 Value |
Maximum of three options in Shopify |
what the customer pays. In Shopify,
Variant Price iswhat the customer pays and
Compare At Price is thestruck-through “was” figure. Copy a Woo sale price straight into
Variant Price and move the regular price intoCompare At Price – the other way round and everyproduct on your store looks like it just went up in price.
Shortcodes deserve a special mention. If your descriptions contain
[su_tabs], [woocommerce_...] or any
page-builder markup, that text will publish literally on Shopify.
Search your description column for [ before importing and
clean what you find.
Migrato runs this job from a spreadsheet, with a full preview
before anything is written. Free plan, no card, uninstall anytime.
Variable products become variants
A WooCommerce export gives you a parent row for each variable product
followed by a child row per variation. Shopify has no parent concept –
it has one product with several variant rows, all sharing the same
Handle.
Practically, that means: delete the parent rows once you have copied
their title, description and images onto the first variation row, then
give every variation of the same product an identical handle. The
first row carries the product-level data; the rest carry only
variant-level columns.
-
Every row for one product shares the same
Handle -
Only the first row of each product needs
Title,
Body (HTML),Vendorand
Type -
Every row needs its own
Variant SKU,
Variant Priceand option values -
No two rows in the same product may repeat the same option
combination
If a product has more than three attributes in WooCommerce, Shopify
cannot represent it as-is. Decide which three become options and move
the rest into metafields or the description before you import.
Redirects: the part everyone skips
This is the step that decides whether your organic traffic survives.
WooCommerce product URLs typically look like
/product/blue-cotton-tshirt/; Shopify uses
/products/blue-cotton-tshirt. Category pages move from
/product-category/shirts/ to
/collections/shirts.
Build the redirect map in a spreadsheet while you still have the old
site running:
- Crawl the live WooCommerce store and export every indexed URL.
- Put the old path in one column and the new Shopify path in the next.
-
Sort by traffic. If the list is long, get the top 200 pages exactly
right and pattern-match the tail. -
Import the file into Shopify’s URL redirects – this is one of the
data types a bulk tool handles, so you are not pasting 2,000 rows by
hand.
Do not forget non-product URLs: blog posts, the cart and account
pages, and any landing pages you built for campaigns. Those often
carry the backlinks.
Import in this order
Sequence matters, because later records reference earlier ones:
- Collections – so products have somewhere to land
- Products and variants – the bulk of the work
-
Customers – before orders, so orders attach to the
right person -
Historical orders – if you need them for reporting
or warranty lookups -
Redirects and content pages – last, once the
destinations exist
finished file and run that. Check the result in the Shopify admin
with your own eyes – images attached, variants grouped, prices right
– then run the rest. Ten minutes here saves a full re-import.
What to check in week one
Once the store is live, the migration is not finished – it is being
measured. Watch these:
-
Search Console coverage. A rise in 404s means your
redirect map has gaps. Export the list and fill them. -
Indexed pages. Expect a dip and a recovery over
four to eight weeks. A dip that does not recover means redirects are
missing or pointing at the wrong pages. -
Product images. Spot-check fifty products. Broken
images almost always trace back to URLs that were only reachable
from inside the old host. -
Inventory counts. Compare a sample against your
last stocktake before you trust the numbers in fulfilment. -
Old sitemap. Keep it submitted for a few weeks so
search engines can find the redirects rather than discovering dead
ends.
Handled properly, a migration is a week of preparation and an
afternoon of importing. Handled as an afternoon of importing, it is a
quarter of lost traffic.