What changes when moving from PrestaShop 1.7 or 8 to 9

The scale of the change depends on your starting version. Moving from PrestaShop 1.7 is a bigger technological step: version 8 introduced, among other things, support for PHP 8.1 and Symfony 4.4, while PrestaShop 9 is built on Symfony 6.4 LTS and offers a new Admin API for integrations. Overview of version 8, overview of PrestaShop 9

The move from PrestaShop 8 is shorter, but it is still an upgrade to a new major version. Release 9.2 supports PHP up to version 8.5 and adds a native one-page checkout and Extra Properties, which provide custom fields for products, customers and orders. PrestaShop 9.2 release highlights

In either case, check the compatibility of your modules, theme and external integrations in advance. The newer version provides a more modern technical foundation, but it does not by itself guarantee a faster store or better search rankings.

Why clicking “Update” is not enough

Moving from 1.7 to 9 is a major-version migration. The official documentation warns that modules may be incompatible and need to be configured again after the migration; an older theme may need changes or replacement. Start by listing your modules, checking which versions they support, and deciding what to replace, adapt or remove. Pay particular attention to custom core changes and modules whose authors no longer maintain them.

An outdated module can cause an error on a product page, in the cart or in the back office after a PHP or internal interface change. It may also contain a security vulnerability. In 2026, for example, PrestaShop issued a critical security notice for the ps_facetedsearch module; the fix is available in version 4.0.4. Not every old module is vulnerable, but its origin and update history should be checked. Migration documentation and ps_facetedsearch security advisory

Community reports show why a migration should first be tried outside the live store. One merchant described repeated failed upgrades from 8.2.1, a 500 error and back-office issues. After 9.2 was released, another user reported a backup failure while upgrading a larger store. These reports do not mean that upgrades generally fail; they are good reasons to make a backup, prepare a test copy and have a rollback plan. Forum discussion about an upgrade and report of an upgrade backup failure

What One Page Checkout changes

PrestaShop 9.2 includes the native One Page Checkout; the back office lets you choose between the one-page and original four-step flow. Address, delivery and payment appear on one page, guests can place orders, and some details update without a full page reload. The aim is to remove unnecessary steps, but the feature alone does not guarantee a higher conversion rate. The checkout must work properly with the payment provider, carriers, legal modules and theme. For example, after 9.2 was released, a conflict with the ps_legalcompliance module was reported that could break the checkout. Test the full purchase flow, including discounts, VAT, delivery, confirmation emails and the mobile layout. PrestaShop 9.2 release and checkout issue report

Your theme affects speed and SEO

A new version or One Page Checkout cannot make up for a poor theme. The theme determines how many scripts and styles load, how images are prepared and whether page content shifts while loading. A slow or overloaded theme can make a site harder to use on mobile and lead to more abandoned orders. Google includes Core Web Vitals among its page experience signals, but a high PageSpeed score alone does not guarantee good rankings. What matters is the visitor’s actual experience: how quickly the main content appears, how fast the page responds to input and whether the layout stays stable. Measure specific pages before and after migration instead of relying on a single overall score. Google’s Page Experience documentation

Why work with an experienced developer

An experienced developer does more than install the new version. Before the migration, they review modules, custom changes, hosting, the database and integrations with accounting or warehouse systems. They prepare a test copy, backup and rollback plan. After the migration, they check orders, payments, emails, permissions, redirects from old URLs and theme performance. This is where the difference between a basic upgrade and a managed migration matters most.

You can recognize an experienced developer by verifiable work, a clear process and a willingness to explain risks before touching the live store. If you are looking for a developer with that approach, I can help audit your shop and plan a safe migration. The goal is not simply to launch PrestaShop 9, but to keep your data, orders, search visibility and customer trust intact.