PrestaShop 1.6 to 9 Upgrade Checklist

These are the things that actually went wrong, or nearly did, when we moved live stores from PrestaShop 1.6 on PHP 5.6 to PrestaShop 9.2 on PHP 8.4. One was a small shop; the other had tens of thousands of orders and customer accounts. Your store may hit different problems, so treat these as things to check rather than fixed rules. If you are planning the same move yourself, check these before you start. If you would rather hand it off, we can do it for you.

1. Plan the upgrade path and PHP versions

  • There is no direct jump from 1.6 to 9. Go 1.6 to 1.7.8, then 8.2, then 9.x, and take a full snapshot (database and files) after each hop.
  • Each hop needs a PHP version both sides support: 1.7.8 and 8.2 run on PHP 7.4; PrestaShop 9 needs PHP 8.1 to 8.4. Running the 8.2 to 9 hop on PHP 8.1 and serving the finished store on 8.4 worked well.
  • 1.6 code on PHP 7.2+ can fail on removed extensions such as mcrypt. On our stores the first hop needed small patches.
  • Give the command-line PHP plenty of memory (1 GB) for the upgrade and for clearing the cache.

2. Work on a copy, never on live

  • Clone files and database to an isolated staging site behind a password. Turn off outgoing mail and blank payment keys in the copy so it can never email customers or charge cards.
  • Clean the copy first: expired cart rules, years of visitor statistics and old mail logs can make the database several times larger than it needs to be and slow every hop.
  • Look for things that should not be public at all: old backup zips, debug scripts, stray PHP files and old admin tools left in the web root.

3. Keep customers able to sign in

  • Stock 1.6 passwords use an old format. PrestaShop 9 can accept them and rehash on login, but if a module changed the password format, customers will not be able to sign in unless you carry that format over with a small compatibility override.
  • Old passwords are verified with the original cookie key from the old store's settings. Carry it over securely, keep it out of tickets and logs, and remove the compatibility override once most customers have signed in again.
  • Test staff (employee) logins separately. They can use a different format from customer accounts and may fail where customers work.

4. Deal with old modules and overrides

  • Leftover 1.6 module folders can break the PrestaShop 9 module manager and console. Move every unused legacy module out of the store, not just disable it.
  • Watch for modules that bundle their own copy of Symfony or other libraries. One did, and it took down the whole admin with a blank error after the move to 9.
  • Audit the override folder. Many old overrides belong to modules you are dropping and should go with them.
  • Check whether each paid add-on is still needed. PrestaShop 9 has built-in product reviews, faceted search and mail alerts, and small features like printing order notes on invoices are quick to rewrite.

5. Check the store in a real browser

  • Simple page checks said everything was fine while shoppers saw an unstyled list of categories with no checkout button. Only a real browser run, with JavaScript and CSS loaded, showed it.
  • The cause was a media server (CDN) setting carried over from 1.6 that pointed at the old site, so none of the new theme's files loaded. Turn media servers off during the upgrade and purge the CDN at switch-over.
  • After the upgrade, module files can end up unreadable by the web server. Check file permissions on the modules folder after every install or file copy.
  • Re-check slider images, favicon and category banners; they live in places the upgrade does not always carry across.
  • Test at phone width as well as desktop, all the way to the payment step.

6. Get payments right

  • PayPal (PrestaShop Checkout) and Stripe both depend on webhooks reaching the store. Allow those specific callback URLs through password protection and firewall rules, and keep the providers' signature checks switched on.
  • Your site's security headers must allow the payment providers' scripts, or checkout hangs on loading payment methods.
  • With multistore off, payment settings must be saved at the global level. A setting saved only for one shop caused PayPal orders to fail.
  • Compare order totals and rounding against the old store, and place a small real order and refund after go-live.

7. Protect your search rankings

  • Crawl your most visited URLs on the old and new store and compare them. Products whose manufacturer had been deleted returned errors on PrestaShop 9 until fixed.
  • Carry over custom redirects from the old .htaccess, above the section PrestaShop manages.
  • Regenerate the sitemap and resubmit it.

8. Plan the switch-over

  • Time a full rehearsal on a fresh copy. On the larger store the upgrade hops alone took about 1.5 hours, and the whole switch-over took longer than first estimated.
  • Write every manual fix you made on staging into a script. If the staging build cannot be repeated from scripts, the live run will miss something.
  • Take a fresh backup with the store in maintenance, run the rehearsed steps, enter live payment keys, test, then reopen. Remember to switch the store back out of maintenance mode.
  • On shared servers, reload PHP services after a config check rather than restarting them, so one site's mistake cannot take others down.
  • Keep the rollback ready until you have seen real orders come through.
New Blog Hosting

Published prices, real support.

Plans from $8/month or $75/year, renewing at the current published price. Cancel within 60 days for a full refund of your first payment.

See plans ↗