Luca Cavallini

PrestaShop migration & upgrade

PrestaShop migration & upgrade

Move from PrestaShop 1.6 or 1.7 to 8 or 9 without losing data, SEO or sleep. Planned, staged and reversible — handled by the developer who’ll keep running it afterwards.

Work with me → See the work →

Upgrading PrestaShop is where shops break: data that doesn’t map, modules that don’t exist anymore, URLs that change and tank your SEO, a theme that won’t come along. Done in a hurry on the live site, it’s a disaster waiting to happen.

I treat a migration as a project, not a button. We map what you have, build the new version on staging, migrate and validate data, preserve URLs and rankings, and switch over only when it’s proven. And because I run servers too, the infrastructure move is part of the plan, not an afterthought.

Scope

What’s included

  • Pre-migration auditInventory of modules, overrides, theme and data — and an honest map of what survives the jump.
  • Staged rebuildThe target version built and tested on staging, so the live shop is never the experiment.
  • Data migrationProducts, customers, orders and SEO data migrated and validated — not just dumped across.
  • SEO preserved301 redirects, URL mapping and structured data kept intact so you don’t lose rankings.
  • Infrastructure moveNew PHP/MySQL versions and server config handled together with the code — one coherent plan.
  • Reversible cutoverA switch-over with a rollback path, scheduled to minimize downtime.
Proof

Related work

Development PrestaShop development Custom shops, themes and modules on 1.6 → 9 — clean, upgrade-safe code. Performance PrestaShop performance Slow shops made fast — measured, not guessed. Big catalogues a specialty.
FAQ

Questions, answered

Will I lose my SEO rankings?
Not if it’s done properly. URL preservation and 301 redirects are part of the plan from day one — protecting rankings is exactly why migrations need a developer, not a one-click tool.
Can you migrate a heavily customized shop?
Yes. Customization is the normal case, not the exception. The audit identifies what to port, what to rebuild cleaner, and what to drop.
How much downtime?
Minimal and planned. The new version is fully built and validated on staging first; the live cutover is a short, scheduled, reversible step.

Tell me what’s not working — or not talking to what.

New build, a system that needs rescuing, an integration, the June 2026 deadline. One developer who builds it and stays to run it. Reply usually within 1–2 business days.