PrestaShop to Shopify for French Merchants: Map Product Combinations Before Migration
A catalogue migration brief for retaining the exact options customers can buy, rather than transferring product titles alone.
In this article
Illustrative workspace. Screens show concepts, not a delivered client system.
A product with several sizes and finishes can contain more migration work than a whole page of simple products. For a French merchant considering PrestaShop to Shopify, review product combinations before accepting a store-transfer estimate. The sample should prove that the destination preserves the sellable item, its identifier and the choices the customer sees.
Inventory the product and its combinations
List the parent product, option groups, combination references and the fields that differ for each. Include images, stock and any approved pricing rules. A total product count does not describe the complexity of that structure.
PrestaShop’s webservice resource documentation lists products, combinations and related resources separately. Assess the merchant’s actual version and supported access before choosing an export or integration route.
- Parent and combination identifiers.
- Attributes and permitted values.
- Images associated with specific options.
- The source of stock and commercial data.
Map combinations to the intended Shopify variant model
Define how each PrestaShop combination becomes a supported Shopify variant or another approved product representation. Preserve meaningful SKUs and check option images, availability and fulfilment references against an actual destination product and order.
Shopify’s product CSV documentation describes its import structure. A PrestaShop export is not automatically a Shopify-ready file. Map fields deliberately and assess current product limits and any app-owned options against the merchant’s actual catalogue.
Special combination behaviour may need supported Shopify configuration, a maintained app or an approved change in the offer. The proposal should identify that decision and its recurring costs before the full migration.
Preserve the receiving team’s item references
The order needs to identify the exact selected combination in terms operations understands. Translated labels help the customer; stable references help the team reconcile stock and fulfilment. Avoid changing identifiers casually just because the new database creates different internal IDs.
If another application owns the catalogue or inventory, define the source of truth and field map. A migration that initially imports correctly can still fail operationally if later updates overwrite the wrong records.
Review addresses, images and historical needs
Map existing product and category destinations to useful new pages. Check images embedded in descriptions and those associated with variations. A correct product title with the wrong option image can mislead a buyer.
Decide separately what happens to customer access and historical orders. Those records have their own migration requirements and information-handling arrangements. Do not assume a catalogue export contains everything the support team needs.
Reconcile a difficult sample before the bulk move
Choose a product with several combinations, an unavailable option, a shared image and a special rule. Compare source records, destination display and an authorised test order. Use approved sample data and keep test actions clearly identified.
| Review area | Acceptance question |
|---|---|
| Combination | Can the customer choose the intended item? |
| Reference | Can operations identify it? |
| Media | Does the image match the selection? |
| Update | Can the merchant maintain it after launch? |
Can the design change during migration? Yes. Agree the new presentation and option behaviour before the final mapping so a design decision does not accidentally remove catalogue meaning.
For the wider implementation decisions, see the Shopify store planning checklist.
Discuss a scoped implementation
Send the PrestaShop version, representative product matrix and the reason for moving. We can assess a Shopify sample and its remaining dependencies before estimating a full migration.
My ecommerce implementation work is Shopify-only. I’m Jagjeet Singh, based in India and working remotely with businesses and agencies. Discuss your store migration sample. Share the current site or workflow and the first outcome you want to review; I can assess the requirements and propose an implementation scope.
Written by
Jagjeet Singh
Full stack development, WordPress engineering and practical web products. I work with businesses, teams and agencies in India and worldwide.
Explore my work
