# Migrating from PrestaShop to WooCommerce

> PrestaShop is a dedicated e-commerce architecture by design. WooCommerce is a plugin that extends WordPress, a general-purpose CMS. That structural difference changes what a migration transfers cleanly and what it forces you to rebuild.

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

## Direct answer

> Export the catalogue and the customers from PrestaShop first, via Catalog then Products and via Customers, using the Export button: that gives you a frozen data set independent of any migration tool. Then freeze the redirect map before the switch: PrestaShop serves addresses containing the product ID and ending in .html, WooCommerce serves /product/ addresses. Without that table, every indexed listing returns a 404.

## A dedicated architecture versus an extended CMS

PrestaShop was designed from the outset for e-commerce, with dedicated tables for products, variations and orders. WooCommerce, by contrast, is a plugin that adds selling features to WordPress: the shop shares its database and application core with the rest of the site, content pages and theme included. This has a direct consequence on data structure: WooCommerce products are themselves a WordPress content type, stored in wp_posts like blog posts, with their specific information (price, stock, variations) attached as metadata.

The catalogue transfers via a CSV import: WooCommerce offers native CSV import and export, found under Tools > Import. Customers and basic orders also transfer, but the mapping between PrestaShop variations and WooCommerce product variations needs checking, since the two systems don’t combine attributes the same way.

Customer accounts need particular attention on one point: passwords are hashed differently between platforms, and an import can’t carry over a password that WooCommerce can actually use as-is. In practice, every customer has to reset their password on first login to the new shop, which needs planning for in how the switch is communicated.

## What doesn’t transfer as-is

- The mapping between PrestaShop variations and WooCommerce product variations: attribute combination logic differs between platforms
- PrestaShop payment or shipping modules, which have no automatically installed WooCommerce equivalent
- Pricing rules and promotions specific to a particular PrestaShop module
- Product URLs, whose structure changes and which must be redirected to the new WooCommerce addresses

## How I run this migration

1. **PrestaShop catalogue audit** — I measure the number of SKUs, presence of variations and specific pricing rules or promotions to reproduce on WooCommerce.
2. **CSV export then import on a test environment** — The catalogue is exported from PrestaShop, adapted to the format WooCommerce expects, then imported via Tools > Import on a test WordPress install.
3. **Manual check of variations** — I check a sample of product sheets with variations to make sure the mapping to the original attributes is correct.
4. **Choosing payment and shipping modules** — Equivalent payment gateways and carriers are found in the WooCommerce ecosystem and tested in test mode before going live.
5. **Setting up redirects** — Old PrestaShop product URLs are 301-redirected to their new WooCommerce addresses before the switch.
6. **Final switch** — The domain only points to the WooCommerce shop once the catalogue is checked, payments tested and redirects live.

## Back up before starting

> A full backup of the PrestaShop database (products, orders, customers) is essential before any export, so you can roll back if the CSV import 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 WooCommerce checkout works under real conditions, and that each variation shows the correct price and stock.

## Related reading

- **WordPress and WooCommerce hub** — Other WooCommerce work I handle. ([/wordpress-woocommerce](/wordpress-woocommerce))
- **Migrating from WooCommerce to PrestaShop** — The reverse direction of this migration, with its own structural gaps. ([/wordpress-woocommerce/migration/woocommerce-vers-prestashop](/wordpress-woocommerce/migration/woocommerce-vers-prestashop))
- **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

### Is WooCommerce’s native CSV import enough for the whole catalogue?

It’s enough for standard fields (name, price, description, categories), but PrestaShop variations need the file adapted before import, since variation logic differs between the two platforms.

### Do my PrestaShop payment modules work under WooCommerce?

No, no PrestaShop module installs automatically on WooCommerce. I look for the equivalent payment gateway in the WooCommerce ecosystem and test it in test mode before the switch.

### Why do my WooCommerce products appear in the same database as my blog posts?

Because WooCommerce is a plugin that extends WordPress: products are a WordPress content type like posts, stored in wp_posts. That’s a structural difference from PrestaShop, not a fault.

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

Product URLs change structure between PrestaShop and WooCommerce. 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 modules are involved. A simple catalogue migrates in a few days, one with many variations needs more manual checking.