01How this differs from a theme change

Changing theme inside PrestaShop keeps the URLs, the database and the modules. Moving to Shopify changes everything at once: the URL structure, the product model, how tax and shipping are handled, and the extension ecosystem. That is why this migration is planned as a project, with an inventory, a redirect table, a pilot import and a rehearsed cutover.

The general method —audit, 301 table, catalogue, tests and monitoring— is in the e-commerce migration SEO checklist. This guide focuses on what is specific to PrestaShop. For the full project, the website and e-commerce migrations service describes the usual scope.

Fig. 1 · PrestaShop URLs: what usually breaks and how to inventory them

02PrestaShop URLs: what usually breaks and how to inventory them

Depending on its settings, PrestaShop generates URLs with numeric IDs, a «.html» extension, a language prefix or the category inside the product path. Shopify uses fixed paths instead: /products/ for products, /collections/ for categories, /pages/ for pages and /blogs/ for articles. Almost no PrestaShop URL matches as it is.

The inventory draws on several sources at once: the current sitemap, a full crawl of the store, the pages with traffic in Search Console and analytics, and the URLs with external links. That way, old pages that still get visits are not lost just because they are no longer in the menu.

03Mapping table and 301 redirects

Every important URL gets a destination in Shopify. That mapping is written in a table and loaded as 301 redirects. The example below is fictional and only shows the format:

PrestaShop URL (example)Shopify destinationType
/en/trainers/123-city-trainer.html/products/city-trainerProduct
/en/12-trainers/collections/trainersCategory
/en/content/4-shipping/pages/shippingPage
/en/blog/size-tips/blogs/news/size-tipsArticle

URLs with no equivalent are not all sent to the home page: they go to the closest category or product. Google explains how to handle a site move with URL changes in its official documentation: https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes

04Combinations, attributes and images

In PrestaShop, a product with size and colour is handled with combinations. In Shopify, with options and variants. The translation is usually direct, but references, barcodes, stock per combination and the images linked to each one all need checking. A pilot import with a representative sample of the catalogue comes first, and the result is compared with the original store.

05What does not fit Shopify as it is

Shopify limits the number of options and variants per product. Check the current limits in its documentation before designing the catalogue. Products with many attributes, bundles, personalisation or customer-group pricing may need a different structure, metafields or an app. Those decisions are made in the diagnosis, not on import day.

Fig. 2 · Modules, tax, payments and carriers

06Modules, tax, payments and carriers

Every active PrestaShop module is reviewed with the same question: what does it do for the business today? There are three possible answers: replace it with an app, rebuild it, or leave it out. Tax by country, available payment gateways, carriers and shipping rules are reviewed too. What gets reconnected, replaced or left out is written down before work starts.

07Cutover rehearsal, DNS and Search Console

The cutover is rehearsed first: test orders, payments, transactional emails, redirects and forms. On the day, the domain is switched, the redirects go live and the new sitemap is submitted. Afterwards, Search Console is monitored: crawl errors, coverage, pages affected by redirects and sitemap processing. Any error is fixed. There is no set number of weeks that suits every store.

If the source store runs on WooCommerce, several points change; they are covered in the WooCommerce to Shopify migration guide.