I migrate online stores and websites between Shopify, WooCommerce, PrestaShop and Magento, protecting catalogue, orders, URLs and SEO.
Scope: In writing, after the audit
What I migrate: platforms and data
I work with stores and sites on PrestaShop, WooCommerce, Shopify, Magento and custom builds, in both directions. The work covers products and variants, customers, orders, images, stock and, when the source system has them, other records that the audit lists in writing.
The aim is that the new store opens with the data it needs to keep selling, not a half-imported catalogue that has to be fixed by hand after launch.
How I protect SEO: URL table, 301s, canonicals, structured data and sitemaps
Before changing anything I inventory current URLs and build a redirect table. Each important address points to its equivalent on the new site with a 301. Titles, descriptions, canonicals, structured data and the sitemap are checked so they match the new addresses.
I do not promise to keep or improve rankings. I do the technical work that avoids losing what the current site already has, and I leave a record of what was redirected.
Integrations: payments, carriers, invoicing, ERP/PIM, newsletter and consent
A store does not work on the catalogue alone. The audit reviews payments, carriers, invoicing, ERP or PIM if you use them, the newsletter and how consent is collected.
What has to be reconnected, replaced or left out is written down before work starts, so there are no surprises at cutover.
The process in six steps
The work follows a path that is agreed after the audit: audit; catalogue and data; SEO and 301s; integrations; tests; then cutover to production.
The old store keeps selling until the new one is ready. The switch happens when tests pass, not on a date set before seeing the work.
- 01Audit: scope and risks in writing
- 02Catalogue and data
- 03SEO and 301s
- 04Integrations
- 05Tests
- 06Cutover to production
From PrestaShop or WooCommerce to Shopify (and equivalents)
Moving from PrestaShop or WooCommerce to Shopify is not a CSV export. You need a URL inventory, a map of products, variants and 301 redirects, a plan for what Shopify cannot reproduce as-is (some paths, modules, tax rules), and a cutover only after a rehearsal. The current store keeps selling until then. Rankings cannot be guaranteed.
What actually changes (URLs, modules, variants, taxes, apps)
The same six-step process applies here: audit, catalogue and data, SEO and 301s, integrations, tests, then cutover. What changes is the detail of each platform, not the method.
On PrestaShop, custom modules, attribute combinations, routes with .html or IDs, and tax rules often do not have a one-to-one equivalent. On WooCommerce, plugins, WordPress slugs, customers and orders in the same database, and the blog — if the blog is in scope — have to be inventoried. Shopify has a URL structure with prefixes that cannot always be cloned; what cannot be reproduced is redirected, not faked.
This service is not only a move to Shopify. The same method holds for Magento and other equivalents, in both directions. This section answers the pairs people ask for most often; it does not close the rest.
URL inventory and the 301 redirect table
Before anything is switched, I inventory the URLs that matter and build a mapping table. Each important address gets a single destination on the new store, implemented as a permanent (301) redirect. Nothing is dumped onto the homepage. The table is part of the audit and stays as a record after launch, so it is clear what was redirected if Search Console later flags a path.
A typical fictional row looks like this: /categoria/producto.html maps to /products/producto. Real tables use the actual catalogue, not this example. URLs without a clear equivalent are decided one by one: the closest collection, a new product page, or a conscious removal.
Catalogue, customers and orders: a pilot import
Products, variants, attributes, images and stock are imported first as a pilot, then counted and checked before the rest follows. Customers and orders can be included; editorial content too, if it is in the scope. What goes into the first cutover and what waits is decided in the diagnosis, not assumed.
Cutover: rehearsal, DNS and rollback
The current store keeps selling until cutover. Before DNS (or the agreed equivalent) is changed, there is a rehearsal: test orders, redirects, payments, shipping and languages. There is also a rollback path. I do not quote a standard downtime, because it depends on the catalogue and the integrations. The switch happens when the rehearsal passes, not on a date set before the work has been seen.
Other routes (Magento or another destination): the same method
If the destination is Magento, a custom build, or a move away from Shopify rather than towards it, the work still follows the same six steps. The platform pair changes the inventory, not the way the project is scoped and signed off.
The full checklist is in the guide on migrating a store without losing SEO. If the look of the store has to change as well, that is the website and store redesign service, and there is a guide on whether to redesign or rebuild. This page also answers common questions. You can book a free 30-minute meeting or write to hello@diegosanjuan.com; the project quote comes in that email, before work starts.
After launch: Search Console and ongoing support
After cutover I watch Search Console for crawl errors, coverage and how the new URLs are being seen. If something is off, I correct it.
If you want ongoing support after the project, there is an optional monthly arrangement. You can stop after any step, including after launch.
What's included
- 01Shopify, WooCommerce, PrestaShop, Magento and equivalents
- 02Products, variants, attributes, images, stock, customers and orders
- 03URL mapping table, 301s, canonicals, metadata, structured data and sitemaps
- 04Payments, carriers, invoicing, ERP or PIM, newsletter and consent
- 05Search Console monitoring after launch
Process
01
Audit
Inventory of platform, modules and integrations, a catalogue sample and a map of indexed URLs. You come away with scope and risks.
02
Catalogue and data
A pilot import and count reconciliation before the full run.
03
SEO and 301 redirects
URL mapping table, 301s, canonicals and sitemaps. Search Console monitoring after launch.
04
Integrations
Each connector is reviewed before it is quoted.
05
Testing
Test orders, payments, coupons, taxes, shipping, search, languages and mobile. A rehearsal of the cutover before the real day.
06
Go-live
Your current store keeps selling until cutover. The last orders move over in the same window, and I stay on once the new store is live.
A real project
A real project will be published here when I can share it. Nothing is invented in the meantime.
How I can help
If you are planning a migration, the first step is a diagnosis: a short review that sets out what would change, the risks and the scope, in writing. You can also book a free 30-minute meeting, or write to hello@diegosanjuan.com; the project quote comes by email, before work starts.
Related guides
Other services
Frequently asked questions
Can a store be migrated without losing SEO?
You can work to protect what you have already earned, but rankings cannot be guaranteed. The method is to inventory the URLs that matter, build a mapping table with 301 redirects, keep metadata and canonicals, and watch Search Console after cutover. I set this out in the guide on migrating a store without losing SEO.
What happens to the URLs and the 301 redirects?
Every important URL on the current store should have a single destination on the new one. That mapping is documented in a table and implemented with permanent (301) redirects. Nothing is dumped onto the homepage. URLs without an equivalent are decided one by one (a redirect to the closest collection, a new product page, or a conscious removal).
What are canonicals and why do they matter in a migration?
The canonical URL tells Google which version to index when there are duplicates or parameters. On the destination store, each product, collection and language should point to the right URL, and 301s and canonicals should not contradict each other. Copying them blindly from the source will carry errors over.
What is cutover like, and what happens to sales that day?
Before cutover there is a rehearsal: test orders, redirects, payments, shipping and languages. The current store keeps selling until the DNS change (or the agreed equivalent). Cutover is planned and has a rollback path. There is no single magic hour that fits every store: it depends on the catalogue and the integrations.
Are customers, orders and the blog migrated too?
The catalogue (products, variants, attributes, images and stock), customers and orders can be migrated, and editorial content too if it is in scope. Each block is checked with a pilot import and a count. What goes into the first cutover and what waits until later is decided in the diagnosis, not assumed.
How is a quote prepared? What are your fees?
No two projects are alike, so each one receives an individual budget once I understand the full scope. You can book a free 30-minute meeting or email hello@diegosanjuan.com with your current platform, the destination and a sense of the catalogue. I reply with a written diagnosis: risks, scope and the project quote, before work starts. Only hour-bank contracts use a rate: €50 per hour or €300 per day, VAT not included.
Tell me where your website, shop or process stands. A few lines are enough, and I'll suggest a first step.