Upgrading PrestaShop 8 to 9: Case Study on Upgrade & Migration
The upgrade from PrestaShop 8 to 9 not only delivered a modern system, it also massively improved the server response time: the Time to First Byte dropped from over 6,000 ms to around 200–250 ms. In this case study we share our experience from a real PrestaShop migration: the upgrade of a high-traffic shop from PrestaShop 8 to 9. Even though PrestaShop offers an update tool, in practice a major upgrade is often more of a small migration than a “one-click update”. That is exactly why we document our experience here and give concrete instructions on how to prepare a PrestaShop upgrade from 8 to 9 cleanly and take it live reliably while avoiding typical sources of error.
Why a PrestaShop upgrade from 8 to 9 is more of a migration
Many shops are still running on older PrestaShop versions. This is risky in the long term. The main reasons for an upgrade are:
- security updates
- better PHP compatibility
- Performance improvements
- long-term maintainability of the shop system
- better module compatibility
For heavily trafficked shops in particular, it is important to keep the platform technically up to date without jeopardising day-to-day operations.
Fischkaufhaus.de is an established online shop with thousands of daily visitors, which we have now been looking after for ten years. The shop has already won several awards and was most recently named best online shop in the fish trade in 2026.
An update therefore must not cause any downtime during peak traffic hours.
Updating a high-traffic shop: planning is everything
The update was deliberately scheduled for a low-traffic time: 3:00 am. The real key to success, however, lay in the preparation. Before the update was started on the live server, we simulated the entire process several times:
- locally in a Docker environment
- on a separate development server
In total, three full days were set aside in the preparation phase exclusively for testing and troubleshooting.
In doing so, we were already able to:
- identify module conflicts
- optimise server configurations
- document update issues
- prepare concrete fixes
By the time the actual update process started on the live system, most problems were already known, documented and resolved.
Technical process of the update from PrestaShop 8 to 9
Technically speaking, a PrestaShop upgrade from version 8 to 9 is often more of a migration than a classic update. We followed a clear upgrade procedure: local first, then development, and only after that production. This turns a potentially risky update into a controlled migration in which risks become visible early and fixes are prepared in advance. The update process began locally.
- full backup of the shop
- setting up a local Docker environment
- carrying out the update step by step
- documenting all changes
The actual update was then carried out with the PrestaShop module “Update Assistant” (formerly “1-Click Update”). Before the update, all non-core modules were deactivated to avoid conflicts.
For comparable e-commerce requirements, our WooCommerce agency develops robust processes instead of short-term plug-in solutions.
Nevertheless, a classic problem of large shops became apparent: some modules reach deeper into the system than expected. One example was the Trusted Shops Easy Integration module, which still affected the update process even when deactivated.
Thanks to the previously documented tests, however, this problem could be fixed quickly.
Challenges during the live update
Despite the intensive preparation, additional problems arose during the live update. The reason: the production server did not exactly match the test environment. Differences in the server structure in particular led to additional adjustments. For troubleshooting, we analysed:
- Apache logs
- MySQL logs
- PHP error logs
Based on this data, targeted adjustments could be made to the server configuration. A PrestaShop update checklist provides good information on the typical challenges.
Go-live: the shop was back online the same morning
After the update was completed, the following critical functions were tested manually:
- Shopping basket
- Login
- Checkout
- Shipping (shipping label creation)
- Payment
- SEO structures
Once these tests had been passed, the shop was released again.
The first order in the new system came in shortly after 8 am.
Stabilisation after the update
A major update of a shop system does not end with the go-live. Over the following days, further optimisations were carried out:
Backend work:
- analysing server errors
- fine-tuning configurations
- fixing module issues
Frontend work:
- fixing missing images
- adjusting module layouts
- fixing minor UI errors
In total, full stabilisation took about five days, because some issues only became apparent in real-world use that had not been picked up by automated crawler tests and log data.
An important point from our experience: after a PrestaShop migration, tracking and consent should always be part of the instructions, not just a “nice-to-have”. Otherwise Google Ads, affiliate campaigns and conversion tracking run into thin air during or after the upgrade and burn ad spend.
Today the shop runs stably, and minor optimisations are made as needed.
Scaling e-commerce successfully
Further practical examples show how technology, user guidance and visibility turn complex shops into reliable sales platforms with measurable growth.
Performance: why PrestaShop 9 is significantly faster
Another important effect of the update was the massive improvement in server response time. Before the upgrade, the Time to First Byte (TTFB) was at times a staggering 6,000 milliseconds or more. The causes lay not only in the server environment but also in the PrestaShop system itself. In combination with the server configuration at the time, the older PrestaShop version caused additional delays in the backend.
Our web design agency combines clear user guidance with a technically clean, responsive implementation.
In the course of the update, several measures were implemented:
- upgrade to PHP 8.4
- full update of all server packages
- optimisation of the Apache and PHP configuration
- adjustment of the server parameters to the load of a heavily trafficked shop
20 times faster: TTFB from 6,000 ms to 200 ms
The result was clearly measurable: TTFB after the update: 200–250 ms … and therefore in the green zone.
This means the shop’s backend now responds around 20 times faster than before. In e-commerce in particular, a fast server response is crucial for:
- loading times
- conversion rate
- SEO signals
- crawling efficiency of search engines
Working in the backend on product maintenance and order processing is now also much faster, thanks to the significantly improved server response time.
Lessons from the project: PrestaShop update from 8 to 9 for Fischkaufhaus.de
Besides the technical challenges, a shop update also involves organisational aspects that are often underestimated.
- Always carry out the update outside shipping hours: for shops with daily dispatch, it is essential to bear in mind that parcels have to be prepared and sent out on the shipping day. All the people involved in the company should therefore be informed of maintenance windows in good time, so that day-to-day operations are not disrupted.
- Tracking systems can fail during and immediately after the update: during the update, some tracking systems temporarily did not work correctly. These included Google Ads tracking, consent management and affiliate campaign tracking. All stakeholders must therefore be informed in good time, and ad spend should be paused for the upgrade phase. These systems had to be checked again after the update and in some cases reconfigured. For shops with active marketing campaigns in particular, it is important to plan for this.
- Modules reach deeper into the system than expected: even deactivated modules can still affect the system. In our case, the Trusted Shops Easy Integration module showed exactly this behaviour.
- Production servers and development environments often differ: even with good preparation, differences between the development and live systems can lead to additional adjustments.
- Plan for stabilisation after the update: a major update does not end with the go-live. In our case, we planned for – and needed – about five days of stabilisation, fine-tuning and bug fixing.
Over the past few years, we have been able to steadily improve rankings – despite AI answers in Google. We are now keen to see how the updated system and the noticeable PageSpeed improvement will pay off in terms of future visibility.
Conclusion: is a PrestaShop upgrade from version 8 to 9 worth it?
An upgrade from PrestaShop 8 to 9 is particularly worthwhile for shops with many modules, high load or older server configurations. In addition to security updates, the new version often brings noticeable performance improvements, better PHP compatibility and long-term maintainability. The key, however, is thorough preparation: if you test the upgrade locally and in a development environment first, you can minimise risks and update the live shop without major downtime.
Frequently asked questions about PrestaShop upgrades & migrations
In theory, the “Update Assistant” helps; in practice, an upgrade from PrestaShop 8 to 9 is often a small migration for customised shops. Themes, overrides, modules and the server environment need to be checked beforehand – otherwise errors occur in live operation that interrupt it for longer than shop operators (and customers) would like.
With clear instructions: test locally or in staging first, then run through it on development, document module conflicts and server requirements, and only then start the live upgrade. This makes the upgrade controllable and low-risk.
That depends heavily on custom developments and modules. In our case, the live upgrade was possible within a few hours because several days of preparation had been done beforehand. Stabilisation afterwards can still take a few days.
Common issues are incompatible modules, differences between test and production, and server-side matters (PHP, Apache, MySQL). Even deactivated modules can still interfere and must be taken into account during the upgrade.
Very often: tracking and consent. Google Ads tracking, consent management and affiliate tracking must be actively checked after the upgrade and in some cases set up again – otherwise conversion data is missing and campaigns run “blind”.
Ideally during minimal traffic hours (e.g. at night) and coordinated with operational processes. For shops with shipping logic: take shipping days into account and inform everyone involved in advance so that day-to-day business is not disrupted.
Planning a PrestaShop upgrade or migration?
Updating a shop system is not a routine click but a technical project in which experience makes the difference.
We have been supporting PrestaShop shops since version 1.6 and have carried out numerous upgrades and migrations in recent years – from 1.6 to 1.7 and 1.7 to 8 through to the current upgrade to PrestaShop 9. Here we report on the PrestaShop upgrade from 1.6 to 8, which skipped an entire version.
We know the typical challenges from practice: modules, overrides, server configurations, performance problems or tracking issues after go-live.
If you are unsure whether your shop is ready for a PrestaShop upgrade or migration, we will analyse your installation and show you the safest route to the update.
👉 Get in touch now and have your PrestaShop upgrade assessed