WooCommerce to Shopify Migration

Why merchants leave WooCommerce for Shopify

WooCommerce is powerful and open, but it puts the whole stack on your shoulders. You own the hosting, the WordPress and PHP updates, the plugin compatibility, the security patches, the backups, and the performance tuning. For a small catalog that runs fine. As traffic and product count grow, the maintenance load grows with it, and a single mismatched plugin update can take checkout down at the worst possible moment.

Shopify trades that flexibility for an operated platform. The most common reasons merchants make the move are concrete:

• Managed hosting. Shopify runs the servers, the CDN, and the scaling. There is no host to size, no PHP version to babysit, and no traffic spike that requires you to provision capacity in advance.
• A checkout that is maintained for you. Shopify's checkout is PCI-compliant out of the box, supports Shop Pay and the major wallets, and is tuned for conversion. On WooCommerce the checkout is yours to harden, extend, and keep secure.
• Less maintenance, fewer moving parts. Updates, security, and uptime are handled by the platform. The time you used to spend keeping WordPress healthy goes back into selling.
• A predictable app ecosystem. Shopify apps are reviewed and run on Shopify's infrastructure, which reduces the conflict-and-breakage cycle that comes from stacking many independent WordPress plugins.

None of this makes WooCommerce a bad choice. It makes Shopify a different trade: less control over the stack in exchange for far less operational burden. The single biggest blocker to acting on that trade is moving the catalog, and that is exactly what the rest of this guide solves. If you would rather skip the reading and start exporting now, the no-code scraper captures your store in a few clicks.

What transfers in the migration

A clean migration is mostly about the product data, because that is what would take weeks to rebuild by hand. The export captures every field that Shopify's import format has a column for, so the data is ready to map rather than retype. Specifically:

• Product titles. Decoded, clean text that maps directly to Shopify's Title column.
• Descriptions. The full product body, including HTML formatting, ready for Shopify's Body (HTML) column.
• Prices. Regular and sale prices, mapped to Variant Price and Variant Compare At Price.
• Variations. Every size, color, or material combination expanded into its own row, the way Shopify expects variants to be listed.
• Images. Direct image URLs so your photos come across intact instead of broken placeholders.
• Categories. The WooCommerce taxonomy, which you map to Shopify collections during or after import.
• SKUs. Stock-keeping references preserved per variant so your inventory and fulfillment references stay aligned.

It is worth being precise about what a catalog export does not carry, so there are no surprises on the other side. Customer accounts, historical orders, and gift card balances are account-level data that lives behind WooCommerce's login, not on the public product pages, so they are not part of a catalog export. Most stores recreate those separately or start fresh on Shopify; the catalog is the part that is painful to rebuild manually, and the part this workflow handles.

The migration step by step

The whole migration is four steps. The first produces a clean spreadsheet; the rest move that spreadsheet into Shopify and confirm it landed correctly.

Step 1: Export the WooCommerce catalog to CSV

Start by capturing the source catalog. Enter your store URL in the scraper and let it read the full product list, variations and images included, then download a structured CSV with every field organized into columns. This works even on stores where the WordPress REST API is locked down, because the extraction falls back across multiple strategies. The dedicated walkthrough on how to export WooCommerce products to CSV covers the export in detail; that CSV is the file every following step depends on.

Step 2: Map the columns to the Shopify product import template

Shopify imports products from a CSV with a specific, fixed set of column headers. Download Shopify's sample product CSV from the admin so you have the exact template, then line your exported columns up against it. The core mappings are straightforward:

• Product name maps to Title.
• Description maps to Body (HTML).
• Regular price maps to Variant Price, and the original price of a discounted item maps to Variant Compare At Price.
• Image URL maps to Image Src.
• SKU maps to Variant SKU.
• Stock reference maps to Variant Inventory Qty.
• Category becomes a Shopify collection, mapped through Type or Tags and then organized into collections after import.

The one rule that matters most: a Shopify CSV needs a Handle column, and every row that belongs to the same product must share the same handle. That handle is how Shopify groups a product with its variants and its extra images. Get the handle right and the rest of the import behaves predictably.

Step 3: Import in the Shopify admin

In your Shopify admin, open Products, click Import, and upload the mapped CSV. Shopify shows a preview of the first few products so you can sanity-check that titles, prices, and images line up before you commit. Run the import, and Shopify creates the products, variants, and image references from your file. Large catalogs are processed in the background, and Shopify emails you when the import finishes.

Step 4: Verify the result

Do not assume the import was perfect. Spot-check a representative sample: open a simple single-variant product, a product with many variants, and a product with several images, and confirm each one looks right in the admin and on the storefront. Compare the product count in Shopify against your source store. Confirm prices and compare-at prices display correctly, and that images loaded rather than failing to fetch. Verification is the step that catches a column that drifted by one position during mapping, and it takes minutes compared to discovering the problem from a customer.

Handling variants and images

Variants and images are where most migrations go wrong, because Shopify models them differently from WooCommerce. Understanding the model before you import saves a re-import later.

Variants are extra rows, not extra columns

In a Shopify CSV, a product with three sizes is three rows that all share the same Handle. The first row carries the shared product fields (title, description, vendor); the additional rows leave those blank and only fill in the variant-specific columns: Option1 Name and Option1 Value (for example "Size" and "Large"), Variant Price, Variant SKU, and inventory. Shopify supports up to three option dimensions through Option2 and Option3, which covers combinations like size plus color. Because the export already expands every WooCommerce variation into its own line, the rows are there; your job in mapping is to point each option onto the right Shopify option column.

Images attach through the handle

The main product image goes in Image Src on the product's first row. Additional images for the same product go on their own extra rows that repeat the Handle and fill only Image Src (and optionally Image Position), leaving the other columns empty. Shopify fetches each image URL during import and rehosts the file on its own CDN, so the photos end up living on Shopify rather than pointing back at your old WooCommerce server. That means you can decommission the old store afterward without breaking images, but it also means the source URLs must be publicly reachable at import time. If a URL is behind a login or already offline, Shopify cannot fetch it. If you want a local copy of every product photo as a safety net before you import, the guide on how to download product images covers pulling them down in bulk.

Post-migration checklist

Importing the catalog is the hard part, but a launch needs a few more steps so you keep the SEO equity and the merchandising you built on WooCommerce. Work through this list before you point your domain at Shopify:

• Set up URL redirects. WooCommerce and Shopify use different URL structures, so your old product and category links will not exist on Shopify. Create 301 redirects (Shopify supports them under Online Store > Navigation > URL Redirects) so old links, bookmarks, and search results land on the right new page instead of a 404. This is the single most important step for protecting your search rankings.
• Check SEO basics. Confirm page titles and meta descriptions carried over or were re-entered, that each product has a sensible URL handle, and submit a fresh sitemap to Google Search Console so the new structure gets crawled.
• Organize collections. Map your imported categories and tags into Shopify collections, and decide which are manual and which are automated by rule. This is what rebuilds your store navigation and category pages.
• Re-create app functionality. Any feature that came from a WooCommerce plugin (reviews, upsells, subscriptions, currency switching) needs a Shopify equivalent installed from the App Store. Make a list of your active plugins and find the matching app before launch.
• Configure shipping, taxes, and payments. These are store settings, not catalog data, so they do not come across in the import. Set up your shipping zones, tax regions, and a payment provider before you open for orders.
• Test a real order. Place a test purchase end to end, from product page through checkout to order confirmation, so you catch anything broken before a customer does.

Keeping catalogs in sync

Some merchants do not switch overnight. They run WooCommerce and Shopify in parallel for a while, or they keep WooCommerce as a secondary channel after Shopify becomes the main store. In that situation a one-time CSV export is not enough, because prices and stock on the WooCommerce side keep changing and the Shopify copy drifts out of date.

For an ongoing sync, move from the manual export to the API. Instead of clicking through an export whenever something changes, you schedule a job that pulls the current WooCommerce catalog as structured JSON and pushes the updates into Shopify on a cadence you choose. The same extraction engine behind the no-code tool is available programmatically, with async export jobs and webhook callbacks so a hands-off, scheduled sync is straightforward to build. The guide to automating exports walks through scheduling and webhook handling, and the full Scraper API guide covers authentication, endpoints, and rate limits.

Whether you migrate once or sync continuously, the principle is the same: capture the WooCommerce catalog as clean structured data, then load it into Shopify. The CSV path is right for a one-time move; the API path is right when the two stores need to stay aligned over time.

Frequently asked questions

Do I need a plugin or a developer to migrate from WooCommerce to Shopify?

No. The workflow in this guide is entirely no-code: you export your WooCommerce catalog to a CSV with the scraper, map the columns to Shopify's product import template, and upload the file in the Shopify admin. There is no plugin to install on either store and no custom code to write.

Will my product variations and images come across?

Yes. The export expands every WooCommerce variation into its own CSV row, which is exactly how Shopify expects variants to be listed, and it captures direct image URLs. As long as the rows for one product share the same Handle and the image URLs are publicly reachable, Shopify recreates the variants and fetches the images during import.

Does the migration move my customers and past orders?

No. A catalog export covers products, variants, prices, images, categories, and SKUs. Customer accounts, historical orders, and gift card balances are account-level data that does not live on public product pages, so they are handled separately. The catalog is the part that is impractical to rebuild by hand, and that is what this workflow migrates.

Will I lose my Google rankings after switching to Shopify?

Not if you set up redirects. WooCommerce and Shopify use different URL structures, so you should create 301 redirects from your old product and category URLs to the new Shopify pages, then submit a fresh sitemap to Google Search Console. Redirects pass your existing ranking signals to the new URLs and keep old links from hitting a 404.

How do I keep WooCommerce and Shopify in sync after migrating?

For an ongoing sync, use the API rather than repeating the manual export. You can schedule jobs that pull the current WooCommerce catalog as JSON and push updates into Shopify on a regular cadence, with webhooks so the process runs hands-off. See the guides on automating exports and the Scraper API for the setup.