# Migrating from WooCommerce to PrestaShop

> Catalogue, customers and orders aren’t modelled the same way on both platforms. Migrating from WooCommerce to PrestaShop means telling apart what a migration tool transfers cleanly and what you have to rebuild or check yourself.

- Source canonique : [https://allaux.fr/en/wordpress-woocommerce/migration/woocommerce-vers-prestashop](https://allaux.fr/en/wordpress-woocommerce/migration/woocommerce-vers-prestashop)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> Export the catalogue through Products, All Products, Export in the WooCommerce admin, and the customers with an export plugin that reads wp_users and wp_usermeta: that frozen set is your reference for checking the import. On the PrestaShop side the entry point is Advanced Parameters, CSV Import, categories before products. Freeze the redirect map before the switch, since the two platforms build addresses differently.

## What changes structurally between the two platforms

WooCommerce is a plugin that extends WordPress, a general-purpose CMS: products are just another WordPress content type, stored in wp_posts like posts. PrestaShop, by contrast, was designed from the ground up as a dedicated e-commerce architecture, with its own tables for products, variations and orders. This structural difference has a direct impact on migration: what WooCommerce models with attributes and variations doesn’t map term for term onto PrestaShop’s variation system, even if the end result looks similar to the customer.

With a suitable migration tool, such as an official PrestaShop module or a custom script, the product catalogue, categories, customers and basic order history transfer correctly. Everything else doesn’t.

Product images deserve a separate check: WooCommerce handles them as WordPress media library attachments linked to the product by its ID, whereas PrestaShop indexes them in its own structure and automatically regenerates its display formats (thumbnail, zoom, large image) on import. Each image’s alt text, useful for accessibility and search rankings, isn’t always carried over as-is by a generic migration tool — I check it on the sample I review.

## What doesn’t transfer automatically

- Product variation structure: WooCommerce attributes and variations don’t map identically onto PrestaShop, so each product sheet needs a manual check
- Specific pricing rules and promotions, rarely carried over as-is by a generic migration tool
- Extensions and their own business logic: no WooCommerce extension has an automatically installable PrestaShop equivalent
- Product URLs, which change structure and must be 301-redirected to their new PrestaShop addresses to avoid losing existing rankings

## How I run this migration

1. **Catalogue audit** — I measure the real complexity: number of SKUs, presence of variations, specific pricing rules or promotions to reproduce.
2. **Migration on a test environment** — Catalogue and customers are migrated to a test PrestaShop environment, never directly to production.
3. **Manual check of a sample** — I check a sample of product sheets, particularly those with variations, to spot discrepancies before rolling out fully.
4. **Rebuilding extensions and promotions** — Specific business logic (pricing rules, third-party modules) is either found on PrestaShop or rebuilt one by one.
5. **Setting up redirects** — 301 redirects from old product URLs to new ones are put in place before the switch, not after.
6. **Final switch** — The domain only points to the new PrestaShop shop once the catalogue is checked and redirects are live.

## Back up before starting

> A full backup of the WooCommerce database (products, orders, customers) and site files is essential before any export, so you can roll back if the migration tool misbehaves on a specific case in the catalogue.

## Checking after the switch

> I check that 301 redirects work on a sample of old URLs, that the PrestaShop checkout works under real conditions, and that variations show the correct price and stock.

## Related reading

- **PrestaShop hub** — Other PrestaShop work I handle. ([/prestashop](/prestashop))
- **PrestaShop migration** — Switching host or version on an existing PrestaShop shop. ([/prestashop/migration](/prestashop/migration))
- **Migrating without losing your rankings** — The detail on redirects and preserving existing SEO. ([/guides/migrer-sans-perdre-referencement](/guides/migrer-sans-perdre-referencement))
- **Backing up your shop before any work** — What to back up before starting a catalogue migration. ([/guides/sauvegarder-boutique-avant-intervention](/guides/sauvegarder-boutique-avant-intervention))

## FAQ

### Will my product variations end up identical on PrestaShop?

Not automatically. WooCommerce attributes and variations don’t map term for term onto PrestaShop’s variation system. I manually check a sample of sheets to fix discrepancies before rolling out fully.

### Do my WooCommerce extensions have a PrestaShop equivalent?

No WooCommerce extension installs automatically on PrestaShop. I look for an equivalent module in the PrestaShop ecosystem, or rebuild the specific business logic if needed.

### Will I lose my rankings when switching platforms?

Product URLs change structure between WooCommerce and PrestaShop. I set up 301 redirects to the new addresses before the switch to preserve existing rankings.

### How long does a catalogue migration take?

It depends on the number of SKUs and whether variations or specific pricing rules are involved. A simple catalogue migrates in a few days, one with many variations needs more manual checking.

### Will my orders in progress be carried over?

Basic order history transfers with a suitable migration tool. Orders placed between the initial copy and the final switch are carried over separately so nothing is lost.