EN ES

Maintenance

Usual PrestaShop upgrade mistakes — and a 1.6 to 9 path that did not skip staging

· 1 min read · Published by Rafa

Upgrading without a plan takes the store down. On gsmsofia.com the path from PrestaShop 1.6.4 toward 9 used staging, B2B data checks and order tests — not a production one-click.

Live store: gsmsofia.com. Moving a B2B PrestaShop 1.6 catalogue toward 9 is not the 1-click updater. Modules, overrides, customer groups and order history have to survive.

Mistakes that kill upgrades

  • Running the updater on production with no verified backup.
  • No inventory of paid modules that have no 8/9 equivalent.
  • Skipping URL redirects, then wondering why rankings dropped.
  • Not placing a test order after cutover.

A safer order

Backup files and database. Staging with the target PHP version. Module replacement list. Data migration. Login, cart and payment tests. Then cutover. Hourly work is €30 + VAT where applicable when the unknown is still the unknown; a closed quote follows a store review.

Migrations · Maintenance · Request a quote.

Need the same kind of diagnosis?

Send the public URL and the symptom. I reply directly with a next step or a scoped quote.

WhatsApp
Next step

If this matches your store, write

A blog post is not a quote. Share the URL and what is failing. I tell you whether it starts hourly or needs a closed estimate.

WhatsApp Request a quote