The PrestaShop to Shopify migration checklist

Updated 12 November 2026 · Grumspot

1. 01Back up the database and the filesTake a full backup before anyone touches anything, and keep it off the server. It is your record of the shop as it was.
2. 02Count every recordNote the number of products, combinations, customers, orders and CMS pages in the back office, per shop if you run multistore.
3. 03List every module and overrideWrite what each module and each class in /override/ does at checkout, in pricing and in the catalogue. Years of them add behaviour nobody has written down, and each one needs a Shopify app, a Function or a decision to drop it.
4. 04Export your URLs, per languageDownload the pages that get clicks from Search Console and the sitemap for each language. PrestaShop URLs carry IDs, like /12-product-name.html, and every language has its own set.
5. 05Write out the price rulesList customer groups, specific prices, quantity discounts, cart rules and which groups see prices with or without tax. This is the part that breaks quietly if it is rebuilt from memory.
6. 06Decide the plan: standard or PlusCustomer groups with their own prices map to B2B companies and catalogues on Shopify Plus. On a standard plan, customer tags with Shopify Functions handle group discounts. Settle this before the build starts.

1. 07Resolve every combination before importA combination can override the parent’s price, weight and reference, or inherit them, and the export does not always say which. Work out each value so every Shopify variant carries its own price, weight and SKU.
2. 08Split products with more than three attributesShopify allows three options per product. A product with four or more attributes is split into linked products.
3. 09Turn features and attachments into metafieldsProduct features become metafields that feed the storefront filters. PDF attachments become file metafields shown on the product page.
4. 10Map categories, manufacturers and suppliersThe category tree becomes collections with the hierarchy in the menus. Manufacturers become the vendor field and a collection each. Suppliers become metafields.
5. 11Import customers, groups and order historyAccounts, addresses, newsletter consent and group membership come across, with past orders, carriers, order states and invoice numbers attached.
6. 12Import each languageProduct names, descriptions and URLs per language go into Translate & Adapt, under one Shopify Market per language or country. Nothing is retyped.
7. 13Rebuild prices and vouchersSpecific prices and catalogue price rules become Shopify discounts or B2B catalogue prices. Vouchers become discount codes.
8. 14Build the redirect map, per languageEvery /12-product-name.html and /3-category URL in every language gets a 301 to its new /products/ or /collections/ address.

1. 15Compare the countsCheck products, variants, customers and orders on Shopify against the numbers you wrote down on day one.
2. 16Check prices as three different buyersOpen the same products as a guest, a retail customer and a trade customer. The price and the tax display have to match what each saw on PrestaShop.
3. 17Place a real orderBuy a product with each payment method and each carrier, check the confirmation email and the invoice, then refund it.
4. 18Test the top URLs by hand, in each languageOpen the old address of each page that brings search traffic and confirm it lands on the right new page in the right language.
5. 19Run the final importRight before the switch, import the orders and customers that arrived on PrestaShop since the first import.
6. 20Point the domain at Shopify and send the invitationsChange the DNS on a quiet day and hour for your shop. Passwords cannot move, so each customer gets an invitation to set a new one, timed with your launch announcement.

1. 21Submit the new sitemapAdd the Shopify sitemap in Search Console so Google finds the new addresses in every language.
2. 22Watch for 404s and order errorsCheck Search Console, the order list and the error logs every day for the first weeks, and add a redirect for every missed URL.
3. 23Keep the old server until everything is verifiedLeave the PrestaShop server running in maintenance mode, off the public domain, until every count matches. Then archive the backup and close the hosting.