PrestaShop · upgrades, migration, bug fixes, integrations and care
Is your store stuck on an old version, did a module break after an update, or does an integration lose orders? I review the store, fix what blocks sales and upgrade it on a copy, so orders keep coming in the whole time.
Individual quote
Free first call. I usually reply within 2 hours.
Many PrestaShop stores still run on 1.7 and PHP 7.4, which has had no security fixes since 2022. Every change becomes a risk: a new module will not install, the host forces a newer PHP, and nobody knows what will break. I start with a review of modules, overrides and integrations. Then I upgrade or migrate on a copy of the store, test orders and switch over once everything works.
This decides whether an upgrade is enough or a migration is needed.
| Part | Now | Target |
|---|---|---|
| PrestaShop | 1.7.8 | 8.2 or 9 |
| PHP | 7.4, no security fixes | 8.1 or newer |
| Theme | bought in 2019, with custom changes | updated or replaced |
| Core overrides | 2 | moved into a module |
These are what usually break after an upgrade.
After the upgrade, marketplace orders would stop reaching the store.
What to do: A newer module version or an integration through an order hub, tested before the switch-over.
They slow down the back office and add security risk.
What to do: Disabled and removed once it is clear nothing depends on them.
An order of work that keeps the store selling throughout.
We agree the scope, price and timeline in writing before I start. Paid modules and hosting are billed separately.
Individual quote
from 1 working day
When something stopped working or you want to know what state the store is in.
Individual quote
from 1 week
Moving from 1.7 to PrestaShop 8 or 9, or moving the store to another platform.
Individual quote
monthly
For stores that want one PrestaShop person on call.
„We worked with Vlad on a Next.js project. He knew what he was doing from day one, didn't overcomplicate things and came up with better approaches on his own. I especially value his work on the site's performance. Everything was delivered as agreed.”
George B. CEO, finance company
„We needed to build an MVP fast to test our idea in practice. Vlad helped us choose sensible solutions and focus on what we really needed for launch. We didn't try to build everything at once, yet he made sure the project could grow later without starting from scratch.”
Alex N. Product Manager at StartupX
„Vlad got up to speed with our project quickly and pointed out several problems we hadn't treated as priorities. He sorted out our database and security issues. I liked that he didn't just complete tasks but clearly explained why something was worth changing and what the consequences could be.”
Michał R. CTO at TechCorp
„We had an app where every bigger change was becoming a problem. Vlad helped us clean up the code, rebuild some of the older parts and introduce automated tests. Working on new features is much easier now. I also appreciate his patience in explaining technical topics to people outside the development team.”
Sara K. Product Owner at WebSolutions
The store address and two sentences are enough: the PrestaShop version and what does not work or what you want to change. I usually reply within 2 hours.
Yes, if it is done on a copy of the store. I first check modules, the theme and overrides, because those break most often. I upgrade the copy, test orders, payments and integrations, and switch the live store only when everything works.
PrestaShop 9 came out in June 2025 and needs PHP 8.1 or newer. If your key modules already have a version for 9, going straight to 9 makes sense. If not, PrestaShop 8 is a safe intermediate step. We decide after the module review.
No. I work on a copy and switch over at a quiet hour. Orders placed in the meantime are moved to the new version.
PrestaShop is actively developed: version 9 came out in 2025, and in February 2026 the platform was bought by the Polish group cyber_Folks together with Sylius. For many stores an upgrade costs less than a move. A migration makes sense when the store needs rebuilding anyway or another platform fits the way you sell better. After the review I tell you plainly which is cheaper.
You do not have to. I carry over product and category addresses, set up 301 redirects from the old ones and check in Google Search Console after the switch-over that the pages stay visible.
Yes, that is common. I start with a review of code, modules and access, so I quickly see what the previous developer did. Afterwards I leave documentation, so the store does not depend on one person.
It depends on the store version, the number of modules and integrations. After the review you get the scope, price and timeline in writing before we start. Paid modules and hosting are billed separately.
Furniture store (NDA)
Ekspres Parking