PrestaShop: upgrade to 9 or a new platform
PrestaShop 1.7 no longer receives patches, and an upgrade to 8.2 or 9 is often more expensive than the word “upgrade” suggests. Before you commission either road, we cost both: the price, the risk and what the store cannot do today but will have to do tomorrow.
An upgrade is a legitimate outcome of this conversation. We propose a migration only when the numbers justify it.
What is happening to your version
The decision starts with the version number, because it determines whether the store receives security fixes and whether modules still get updates. Status according to the PrestaShop project announcements, checked in October 2026.
| Version | Status | What it means for the store |
|---|---|---|
| 1.6 and older | Unsupported for years | No security fixes, old PHP, modules without updates. A store holding customer data should not run on it. |
| 1.7.8 | Unsupported since the 9.0 release in June 2025 | From version 8.0 it received security fixes only. Now it receives none. |
| 8.2 | Extended support until the 10.0 release | Critical bugs and security only. A safe harbour for a few quarters, not a plan for years. |
| 9.x | Actively developed | PHP 8.1 to 8.4, Symfony 6.4. Modules and themes from 1.7 often need a rewrite. |
When an upgrade is enough
If the sentences below describe your store, you do not need us. Commission the upgrade from a proven PrestaShop vendor and come back when the store starts blocking sales.
- The store sells in a standard way: catalogue, cart, payments, shipping, without per-customer prices and without company accounts.
- Your key modules have versions for PrestaShop 8.2 or 9, and their authors still develop them.
- The theme is standard or small, so moving it to the new branch is cheaper than a new storefront.
- The integration with the ERP, order management tools and carriers works and has a connector for the new version.
- You have someone who will upgrade a copy first, test customer logins and only then touch production.
When an upgrade will not solve the problem
If you recognise two or more of these points, an upgrade buys time but does not solve the problem. Then we cost the second road.
- Per-customer discounts. Customer groups give one percentage per group, and with several groups the default group wins. A discount tied to last year’s turnover needs a module you rewrite with every major upgrade anyway.
- Company accounts. B2B mode adds company fields and a credit limit, but no roles: who orders, who approves, who sees invoices.
- ERP integration. If the connector to your ERP decides which PrestaShop version you run, the connector rules the store, not the other way round.
- Passwords and customer data. With a clean install of the new version and a data import, passwords work only if the installation key is carried over. It can be done, but it has to be planned, not discovered on launch day.
- Two stores. A separate B2B and B2C store on two PrestaShop installations means two catalogues, two sets of modules and double work with every change.
How we cost both roads
In the conversation we collect five things: the PrestaShop and PHP versions, the list of modules with their status on the new branch, the integrations (ERP, payments, carriers, marketplaces), the number of products and customers, and one change the store cannot make today.
We cost the upgrade as: vendor work, new versions of paid modules, moving the theme and testing on a copy. We cost the migration as: a new store on our Medusa foundation, moving data and URLs, integrations and 24 months of operation. You get both figures in the same layout.
The outcome is one of three: upgrade, migrate, or stay on 8.2 and revisit in a year. Each of them is fine.
What a move from PrestaShop to Medusa looks like
If the numbers point to a migration, we run it by these rules.
- Products, combinations, categories, images, customers, addresses and order history come from the PrestaShop database through a trial migration on a copy. Differences show up before launch, not after.
- We map URLs one to one, with 301 redirects for categories, products and CMS pages. After launch we compare indexing with the state before the migration.
- We carry customer passwords over when it can be done safely. If not, we design a convenient new-password step at first login.
- We rebuild discounts and specific prices as per-customer or per-group price lists in Medusa, and simplify the rules that were workarounds.
- We run the ERP integration alongside the old store and test it on real orders before switching the domain.
Questions about PrestaShop
Is PrestaShop 1.7 still safe?
The 1.7.8 branch received security fixes only after version 8.0 shipped in 2022, and since the PrestaShop 9.0 release in June 2025 it is no longer maintained. A 1.7 store holding customer data runs without security patches, so leaving it as it is is not a neutral decision.
How much does a PrestaShop upgrade to 9 cost?
It depends on the number and state of modules, the theme and the PHP version on the server. A small store with a standard theme and a few modules upgrades for little, a store with a custom theme, paid modules and an ERP integration needs part of them rewritten. We do not publish ranges, because without the module list any figure would be a guess. We help you calculate it in the conversation.
Can we go from 1.7 straight to 9?
Technically yes, through the Update Assistant or a clean install with a data import. In practice, jumping two major versions means a change of PHP (minimum 8.1) and Symfony (6.4), so the modules and the theme from 1.7 have to be checked one by one. Always on a copy first.
Do we have to move the whole store at once?
No. A common scenario is keeping the B2C store on PrestaShop 8.2 and building the B2B platform on Medusa next to it, with a shared ERP integration. The B2C migration comes later or not at all.
What about the modules we use?
We list them and split them into three groups: those with a version for the new branch, those that must be replaced, and those nobody uses any more. The third group is usually larger than it seems.
Before you commission the upgrade, let’s cost both roads.
Prepare your PrestaShop version, the list of key modules and one change the store cannot make today. In 20 minutes we will tell you whether an upgrade is enough.