The short version

Source: PrestaShop 1.7.8.9. Target: Shopify. Migrated with MigrationPro: 384 products, 41 categories, 2,129 of 2,144 customers, 2,634 of 2,644 orders. 15 customers and their 10 orders did not migrate. Cause: invalid email addresses in the source data. 12 discounts and 5 CMS pages were skipped on purpose. The PrestaShop store kept selling the whole time. Recent Data Migration kept the Shopify store in sync, and Smart Update handled bulk fixes.

2,634 of 2,644 orders came across. The ten that didn’t are the most useful part of this story, and I’ll get to them.

Highly Preppy is a Spanish fashion brand based in Galicia, Spain, selling women’s ready-to-wear at highlypreppy.es: coats, blazers, knitwear, dresses and accessories. After a quiet spell the brand is back and relaunching, and this time it wants to reach customers beyond Spain, which is exactly what an older PrestaShop setup was holding back. The move to Shopify is step one of that relaunch. STRAT handles the storefront redesign and the marketing rebuild next, and that part of the story doesn’t exist yet because the work isn’t done. So this is part one: the migration, including the numbers that didn’t come out round.

What moved from PrestaShop to Shopify

Entity	PrestaShop	Shopify
Products	384	384
Categories	41	41
Customers	2,144	2,129
Orders	2,644	2,634
Discounts	12	0 (skipped by choice)
CMS pages	5	0 (skipped by choice)

Shopify has no category entity, so the 41 PrestaShop categories now live as Shopify collections.

Why 15 customers and 10 orders didn’t migrate

Every missing record traces back to one cause: invalid email addresses. Shopify rejects a customer record whose email is malformed. An order can’t be migrated without its linked customer, so a bad email blocks the order too. MigrationPro documents both cases in its help center: why some customers don’t migrate and why orders need their customers.

This is what real customer data looks like once someone actually checks it. The difference now is that the 15 records are on a list we can fix instead of sitting in a database unnoticed.

What we chose to leave behind

The 12 discounts and 5 CMS pages stayed on the old store. MigrationPro could have moved them. We decided not to. We rebuild both natively in Shopify instead, because PrestaShop discount rules and CMS pages don’t map cleanly onto Shopify’s discount engine and page structure, so bringing them over one to one would import promo logic and markup built for a different platform. Rebuilding them in Shopify keeps the promotions and the content clean from day one.

The detail that saves product pages

PrestaShop has two description fields per product. The full description maps to Shopify’s product description as expected. The short description has no native home in Shopify, and the lazy option is to flatten it into plain text.

MigrationPro mapped it to a product metafield, custom.description, typed as rich text rather than a plain string. So the bold text, line breaks and links in those short descriptions arrived intact instead of collapsing into one block.

Small thing. But it is the kind of detail that either gets caught before launch or degrades every product page for months without anyone noticing.

Keeping both stores in sync until launch

As of September 2026, highlypreppy.es still runs on PrestaShop. The Shopify store is built and waiting. The old store keeps taking real orders and signups the whole time.

That gap between “migrated” and “launched” is where Recent Data Migration earns its keep. It moves products, customers and orders that appeared in the source store after the full migration, so the Shopify store stays current right up to cutover. No re-migration, no manual CSV exports.

Bulk fixes without a second migration

The initial migration was not the last time we touched the data. We use Smart Update to push changes to already-migrated products, fields like title, price and quantity, without running the migration again.

A real example: we ran the migration between collections, so while we were building the new store, the old one dropped its prices for the sales season. Instead of re-migrating by hand, Smart Update pushed those price changes straight to the products already on Shopify, keeping both stores aligned with no manual work.

What’s next (part two, once it’s real)

The migration gets a brand ready to sell on Shopify. It doesn’t make a regional Spanish fashion label look and feel like a brand ready for international customers, and that’s the actual work STRAT is doing now: a storefront redesign built for conversion, a rebuilt acquisition engine across paid media, a retention program on Omnisend, and international selling through Shopify Markets. Part two of this series covers that once there’s something finished enough to show rather than plan.

“We had wanted to move to Shopify for a long time, but we were worried about losing all the data in our PrestaShop store. Thanks to STRAT, who recommended MigrationPro, the migration was fast and secure, and we kept our full customer and product history intact, ready to take on this new phase of growth.” Cesar – CEO of Highly Preppy