URLs are part of the job
Redirects and canonicals belong in the plan, not as a post-launch panic.
Freelance · Madrid and worldwide
Migration to PrestaShop 9
Catalogue, customers, orders and SEO moved with a plan — not a CSV dump and hope.
Redirects plannedCheckout retestedGo-live window
Why a plan
Migration is not an export button
URLs, modules and payment gateways fail if you only copy files.
Modules and overrides
I inventory what survives 9 and what must be rebuilt.
Payments and carriers
A migrated catalogue that cannot charge is not a migration.
Staging first
We prove orders on a copy before touching the live domain.
One owner
You speak with the person doing the mapping and the cutover.
A real go-live window
Cutover is scheduled. Rollback is discussed before we start.
Scope
What a migration has to cover
From PrestaShop 1.7/8 to 9, or from WooCommerce/Shopify when PrestaShop is the right home.
Catalogue and combinations
Products, images, stock and attributes mapped without silent loss.
View more →Customers and orders
History moved when the business needs it — not always, not never.
SEO and redirects
Old URLs pointed at the new ones. Search Console checked after cutover.
View more →Theme and modules
What can be upgraded, what must be replaced, what I rebuild.
View more →Payments and shipping
Gateways and carriers retested on the new version.
View more →PrestaShop 9 specifics
Symfony stack, module compatibility and a store that can keep updating.
View more →
How I work
A clear sequence before production
Inventory
Version, modules, overrides, traffic URLs and payment stack.
Mapping
What moves, what is rebuilt, what is left behind on purpose.
Staging
A working copy with test orders before DNS or domain cutover.
Redirects
SEO mappings prepared, not guessed on launch morning.
Cutover
Agreed window, checks, and a way back if a blocker appears.
Stabilise
Logs, checkout and Search Console in the days after go-live.
Live stores
Work you can open in a browser
-
reparacionmovil.es
PrestaShop catalogue, search and checkout for a live repair-parts store.
-
gsmsofia.com
B2B PrestaShop catalogue with account pricing in production.
-
comastrial.com/shop
Industrial ecommerce storefront built to take real orders.
-
irepairphone.es
Service-led storefront with a catalogue the owner can keep updating.
Investment
Quoted after I see the live site
Hourly work is €30 + VAT where applicable. Maintenance starts from €150/month. Larger builds are scoped after review — I do not invent package prices.
-
Live site and version
I quote after seeing the URL, platform version and how customised production is.
-
Scope, not a package sticker
Catalogue size, languages, payments and integrations change the work. There is no honest one-price store.
-
Hourly vs closed quote
Diagnosis is €30/h + VAT where applicable. Builds and migrations are scoped when the outcome is clear.
-
What you send
Public URL, the fault or goal, and screenshots if there is an error. No passwords in the first message.
Questions
PrestaShop migration FAQs
Can you upgrade a PrestaShop 1.7 store?
Yes, after reviewing version, theme, modules, overrides, PHP and data quality.
Will my SEO URLs be kept?
Preservation and redirects are planned. The final mapping depends on old and new catalogue structure.
Can the store stay open during migration?
Preparation usually happens while the current store remains live. A controlled final sync may still be needed.
How is a migration quoted?
After an audit. Uncertain stores start with a discovery phase.
Next step
Request a PrestaShop 9 migration review
A migration is more than copying products. I assess data, URLs, modules, theme behaviour and operational risk before choosing an upgrade path to PrestaShop 8 or 9.