Written by 4SYSTEMPublished on Updated on
7 min read
Plan migration object by object, mapping data and URLs, then checking the results before switching stores.
To prepare a migration from PrestaShop to Shopify, inventory the data, define its destination and build redirects before cutover. Start with a representative sample, then compare results object by object. Changing platform is not a folder transfer: the catalogue, accounts and URLs must make coherent sense in the destination model.
The central document is a migration matrix. Each row identifies the source object, its identifier, transformation rule, destination, transfer method and expected check. Add an owner and exception handling to avoid improvised launch-day decisions.
Scope the migration from PrestaShop to Shopify
Define what will be migrated, archived or recreated. Products, combinations, images, customers, historical orders and editorial pages may need different treatment. Separate data from functionality too: assess a business module, theme or custom journey by its purpose, without assuming copied content recreates its behaviour.
Shopify distinguishes migration methods by object type and recommends importing products, then customers, then historical orders to preserve their relationships.[1] Choose a method for each data family. A catalogue file is not a complete plan for migrating orders, accounts and all their relationships.
Build a mapping matrix
Build the matrix against an export retained as a reference. Keep PrestaShop identifiers in your tracking to match each object to its destination. For free-text fields, specify what remains text, what becomes a structured attribute and what needs editorial cleaning.
| Source object | Transformation decision | Destination check |
|---|---|---|
| Product and combinations | Map options to the intended variants | References, options and prices match. |
| Images and documents | Preserve order, captions and associations | The correct media are accessible. |
| Customers and history | Define relationships and migration method | Data are not assigned to the wrong account. |
| Pages and old URLs | Choose a relevant destination | Content and redirect match. |
CSV updates need particular care. Shopify states that, when overwriting matching products, an included but empty optional column can replace an existing value with a blank.[2] Distinguish omitted fields, deliberate clearing and unknown information. Retain the exact file used for each import attempt.
Prepare imports and cutover
Organise migration as traceable operations with stop criteria. Before the final transfer, decide who may still change the source store and how data created after the first export will be handled.
- Inventory data and URLs, including pages receiving links or traffic. Record languages, references and custom fields in use.
- Prepare mappings and a sample covering variants, multiple media, accented characters and incomplete data. Keep issues visible rather than hiding them.
- Import into a preparation environment and match source and destination identifiers. Check rendered descriptions and the information needed to buy.
- Plan to capture recent changes: new orders, stock and catalogue updates. Define a freeze window and who is authorised to initiate cutover.
- Write a rollback plan covering stop conditions, source retention and orders received during an incident. Avoid uncontrolled ordering on both stores.
The guide to product pages and pre-purchase questions helps check useful content after transfer. An imported description is not necessarily well presented. Check tables, downloads and variant information in the actual journey, not just export columns.
Fictional example: a product with several combinations
Entirely fictional example: a bag has combination references PX-01-M and PX-01-L. The matrix specifies one product with matching variants and preserves image order. The old address /12-sac-atelier.html maps to /products/sac-atelier. Document this mapping before creating the redirect so the expected product can be checked at the destination.
In this scenario, a variant without a reference is flagged for a decision rather than arbitrarily merged. A removed page receives a destination only where genuinely relevant content exists. Tracking distinguishes successful import, completed visual review and verified redirect. These are fictional preparation criteria, not a client migration report or a traffic-retention guarantee.
Check data and old URLs
For redirects, check Shopify's constraints: this mechanism applies to broken URLs; an address still serving a valid page will not redirect. Certain fixed paths are excluded too.[3] Check mappings against the destination configuration before accepting the file.
- Compare products and variants by identifier, then inspect differences in references, options, prices and availability.
- Open media and documents from destination pages, especially products with several variants or translations.
- Follow priority old URLs and check the response, final destination and absence of loops or unnecessary chains.
- Prepare a demonstration order without real payment capture and check basket, delivery, configured taxes and messages within the authorised scope.
Migration does not end with the domain switch. The Shopify SEO guide helps organise visibility checks. Keep a post-cutover issue register and compare data using the same scope. Neither an import tool nor a redirect file alone can guarantee search engine rankings.
Frequently asked questions
Can everything be migrated through one CSV?
Do not assume so. The method depends on object type and relationships to preserve. Document catalogue, customers, orders and content separately. Check the chosen format's limits before concluding that a PrestaShop export can be imported unchanged into Shopify.
Should all old pages redirect to the home page?
No. Look for a destination matching each old page's intent. A replaced product may have a relevant equivalent; a page without one requires an explicit decision. A technically easy blanket redirect is not necessarily useful to visitors.
When can the old store be closed?
After defining cutover checks, required retention and rollback arrangements. Preserve useful evidence without allowing uncontrolled orders in two stores. Timing depends on data and operational constraints, not a universal duration promised in advance.
Base the cutover decision on evidence
A migration from PrestaShop to Shopify should explain where each data item goes, how old URLs are handled and which checks justify cutover. Gather the matrix, sample and unresolved exceptions. To scope the work with 4SYSTEM, present them through the servicespage. They provide a concrete basis for discussing migration and its limits.