Upgrade PrestaShop
Running an older version? It's a sign that it's time to move
-
Version 1.6 / 1.7
Is your shop on PrestaShop 1.6 or 1.7?
Plan your upgrade before compatibility issues with modules, payments or the server start to appear. -
Modules and integrations
Using many modules and integrations (payments, delivery, ERP/WMS/CRM)?
Take care of compatibility, versions, dependencies and testing of critical paths (basket, payments, shipping, registration). -
SEO
Want to keep your SEO?
Keep the URL structure, redirects and structured data, and after implementation we will verify performance.
PrestaShop upgrade : a safe process
Backup and recovery plan
Test environment
SEO and integrations
Performance and security
Post-launch monitoring
What to avoid
A safe upgrade step by step
Compatibility audit
We take stock of the theme, modules and integrations, check the PHP version and dependencies and identify the elements that need work. This stage eliminates most risks before we touch production.
Backup and restore plan
We make a full copy of the files and database and prepare a rollback scenario with a defined recovery time, so that you can return to a stable version at any moment.
Upgrade and tests on a copy
We raise the version in the development and staging environments, adapt the modules and theme, and then test the critical paths: cart, payments, delivery and login.
Maintenance window and switchover
We roll out the actual upgrade in a short off-peak window, in maintenance mode, keeping the URL structure and 301 redirects so as not to lose positions in Google.
Post-launch monitoring
After the switchover we monitor errors, performance, indexing and conversion, rolling out fixes before they affect customers. You can cover the store with ongoing post-implementation support.
Version comparison PrestaShop 1.7, 8 and 9
| PrestaShop 1.7 | PrestaShop 8 | Recommended PrestaShop 9 | |
|---|---|---|---|
| Support and security updates |
Ended
|
Limited, a transitional version
|
Full, the current version
|
| Supported PHP |
Up to PHP 7.4
|
Up to PHP 8.1
|
PHP 8.1 and later
|
| Symfony framework |
Symfony 2.8 / 3.4
|
Symfony 4.4 LTS
|
Symfony 6.x
|
| Native WebP and SVG formats |
None
|
Yes
|
Yes
|
| Native SEO features |
Require modules
|
Partly native
|
Extended natively
|
| Future readiness |
End of development
|
A transitional step
|
Recommended target version
|
| Product data and API |
ean13, older API
|
ean13, current API
|
gtin instead of ean13, newer API
|
PrestaShop upgrade : frequently asked questions
Will a PrestaShop upgrade interrupt sales? +
It’s worth planning the upgrade in a short off-peak maintenance window, for example at night or at the weekend, to limit the impact on customers. Maintenance mode is best switched on only for the moment of the actual switchover, because most of the work can be done earlier on a copy of the store. Before going back online, it’s a good idea to run a quick test of the critical paths: adding to cart, payments, delivery and login.
How do I protect SEO during a PrestaShop upgrade? +
The safest approach is to keep the existing URL structure and, where changes are necessary, prepare complete 301 redirects. It’s worth carrying over meta data and structured data, and after implementation checking 404 errors, indexing and the performance of key pages. An updated sitemap and a correct robots file will help maintain visibility and stable rankings.
Can I go straight to PrestaShop 9? +
Yes, provided the theme, modules and environment are compatible with the new version. For extensive stores, it’s safer to run the process in stages: start with an audit, then upgrade and test the solution on a copy, and only then roll it out to production. You can read more about the version itself on the PrestaShop 9 page. The checklist should include critical modules such as payments, shipping and ERP/WMS/CRM integrations.
How long does a PrestaShop upgrade take? +
The time depends on the starting version, the number and quality of modules, the state of the theme and the scope of integrations. The best results come from a staged approach: a compatibility audit, upgrade and tests on a copy, a short maintenance window for the switchover and monitoring after launch. A contingency plan prepared in advance (a full backup and a rollback procedure) minimises the risk.
What is the difference between a PrestaShop upgrade and a migration? +
An upgrade means raising the version within PrestaShop (e.g. 1.7 → 8 → 9) while keeping data and configuration. Migration is a broader term: moving a store from another platform (e.g. WooCommerce, Shopify, Magento) to PrestaShop or between environments. If you are staying on PrestaShop and only raising the version, we call it an upgrade.
Upgrading PrestaShop 1.7 to 8 +
Moving to version 8 gives you ongoing security fixes, a more modern environment and a more stable foundation for integrations. Before the upgrade, it’s worth checking the compatibility of the 1.7 theme, module versions and the required PHP version, and after raising the version clearing the cache, verifying payments and delivery and reviewing logs and alerts. Tests on a copy make it possible to plan a short maintenance window precisely and return quickly to normal sales.
Upgrading to PrestaShop 9 +
A good start is an audit of the theme (interface and assets), a list of requirements for modules and integrations, and a plan of environment changes, including the PHP version, database and server configuration. The implementation is best carried out in turn in the development, staging and production environments, with full tests of the key paths. Before the switchover, it’s worth confirming that redirects work and that there are no 404 errors, and after launch monitoring indexing, performance and any errors, so that deviations are caught quickly.
Read the case study PrestaShop upgrades
Client clients
Get in touch to discuss your PrestaShop upgrade
Quick form
We reply within 24 working hours







