Blog — Insight 29 November 19, 2026 · 2 min read

PrestaShop to Shopify: preserving combinations, prices and languages

PrestaShop: the official website, captured on 19 November 2026.
PrestaShop: the official website, captured on 19 November 2026.

Product count tells you little about the complexity of a PrestaShop migration. Combinations, translations and pricing rules matter more. Start with a product that contains those details. It will show whether your proposed import preserves the behaviour customers need.

Keep products and combinations connected

PrestaShop exposes products, combinations, available stock and specific prices as separate resources in its webservice reference. Exporting basic product records alone is therefore not a complete migration plan.

Map each combination to its future Shopify variant. Check reference numbers, barcodes, option values and the correct image. A price adjustment needs to produce the correct final price in the destination. Matching total product counts will not catch that mistake.

Separate shop and language differences

Record which content and prices differ by shop or language. Decide whether those differences belong in Markets, translations, catalogues or separate stores. Each choice should solve a specific operational need.

Include a translated product page in acceptance testing. Check its title, description, media, availability and old URL. Otherwise the main language receives careful testing while another market is only checked after launch.

Review the work behind each module

A quantity discount, configurator and shipping extension need different replacements. Ask the team to demonstrate the process behind each important module. Include any extra data it stores, which may be missing from the standard export.

  • Which system owns prices and stock?
  • Which customer groups receive different terms?
  • What vouchers or outstanding credit must be considered?
  • Where are reviews, attachments and custom product fields stored?

Turn the answers into field mappings and acceptance cases. If an API export is used, give it only the access it needs. PrestaShop's webservice setup documents permissions by resource.

Before switching the domain

Reconcile a sample of customers and orders against the source. Define the new login journey and document where historical records remain available. Test a purchase, stock change and refund through the connected systems.

Build the URL inventory while the old store is available. After the switch, recheck redirects, important organic landing pages and incoming orders. Our migration checklist supports preparation, and the migration service page explains how we help with delivery.

All articles