Is PrestaShop reaching end of life? What merchants need to know

PrestaShop is not officially end-of-life. The company still releases updates, still employs a core team, and the platform still powers a significant number of stores across Europe. But "not dead" is not the same as "healthy." Merchants who have been running PrestaShop stores for five or more years are noticing real changes — and some of those changes have direct consequences for their security, their operating costs, and their ability to grow.

This article is not a scare piece. It is an honest assessment of where PrestaShop stands in 2026 and what you should factor into your roadmap.

The numbers behind the narrative

Let's start with what is measurable. The PrestaShop GitHub repository (PrestaShop/PrestaShop) tells a revealing story. In 2020 and 2021, the project was averaging 2,000 to 3,000 merged pull requests per year, with dozens of active external contributors each month. By 2024, those numbers had dropped significantly. Contributor activity from outside the core team became sparse. Many of the names that had been regular contributors — individual developers, agency engineers, module authors — stopped appearing in commit history.

The official marketplace (addons.prestashop.com) has also shifted. Several module categories that used to have 30 or 40 competing options now have far fewer. Some vendors who built their business around PrestaShop addons have quietly migrated their own offerings to Shopify App Store equivalents. This is not anecdotal: look at the payment, loyalty, or email marketing categories and compare today's offering to what existed in 2020.

Forum activity on the official community forums and on Stack Overflow has decreased as well. Threads that would have attracted five or six responses in 48 hours now sit unanswered for days or weeks. The community's collective knowledge is still there in archived posts, but active troubleshooting support is thinner than it was.

Security patching has slowed

This is the most consequential issue for production stores. PrestaShop has had a history of serious vulnerabilities — SQL injection chains, file upload exploits, object injection via Smarty. In 2022, a critical RCE vulnerability affected tens of thousands of stores and went unpatched long enough that active exploitation campaigns were documented in the wild.

The pattern since then has been inconsistent. Some patches arrive quickly; others take weeks. The version cycle from 1.7 to 8.x introduced meaningful improvements, but the upgrade path from 1.6 or older 1.7 installs is still painful enough that a large portion of stores have simply not upgraded. Estimates from security researchers suggest that a substantial minority of live PrestaShop stores are still running versions that are no longer receiving patches.

If your store is on PrestaShop 1.6 or an early 1.7 release, you are almost certainly running unpatched vulnerabilities today. The upstream project has explicitly de-prioritized those branches.

The agency exodus is real

One signal that matters more than GitHub stars or forum posts is where agencies are sending their new clients. In France, Spain, and Belgium — historically the three strongest PrestaShop markets — the direction of new e-commerce projects has shifted noticeably toward Shopify. Several agencies that built their entire practice on PrestaShop development have either added a Shopify track or pivoted entirely.

This matters for merchants because your access to skilled PrestaShop developers shrinks over time. As fewer junior developers learn PrestaShop, the pool of available talent ages, and rates for experienced PrestaShop specialists increase relative to the market. Finding someone who genuinely knows the module override system, the hook architecture, or the Smarty templating engine in 2026 is harder and more expensive than it was in 2018.

Some agencies have stopped quoting new custom PrestaShop module development altogether. The economics stopped working: building something bespoke on a platform with a shrinking addressable market means less chance to amortize the development investment across future clients.

What this means if you are still on PrestaShop

Staying on PrestaShop is a legitimate choice if your situation fits. If your catalog is stable, your hosting is managed, your modules are up to date, and your business does not require integrations that depend on a thriving ecosystem, you can extend your runway. Businesses with highly customized PrestaShop setups — unusual pricing logic, complex B2B rules, deep ERP integrations — often find that the cost of migration exceeds the cost of maintenance for a 12-to-18 month window.

However, there are four situations where continuing on PrestaShop carries concrete risk:

Your store is on 1.6 or early 1.7. You are running known, unpatched vulnerabilities. The question is not whether an exploit attempt will happen, but whether your hosting layer will catch it. Moving to a current version or migrating to a different platform is not optional — it is a security necessity.

Your business is growing and needs new integrations. The best loyalty platforms, headless CMS solutions, subscription billing tools, and personalization engines prioritize their Shopify integrations. If a tool you need does not offer a PrestaShop module, you are building a custom connector that you will need to maintain indefinitely.

Your agency is deprioritizing PrestaShop. If your primary technical partner has started steering you toward other platforms, take that signal seriously. It usually means their team's skill base is shifting and your next project will have longer timelines and higher costs.

You are planning to raise investment or sell. Many acquirers and investors have developed a negative view of PrestaShop as a platform choice. It does not disqualify a business, but it adds friction to due diligence and can affect valuation conversations.

The migration window to consider

The practical question is not "is PrestaShop dying?" but "at what point does migration become more attractive than continued maintenance?" That window is narrowing for most merchants. Migration costs have come down significantly as tooling has improved. A 10,000-SKU catalog with 50,000 customer records that would have taken three months of custom development a few years ago can now be migrated in a fraction of that time.

If you are at the point of evaluating migration, the honest calculus involves comparing your next 24 months of PrestaShop operating costs — including developer time, module licenses, hosting, and the opportunity cost of features you cannot build — against a migration investment that positions you on a platform with an active ecosystem.

WarpForge was built specifically for this migration path. It connects directly to your PrestaShop database, reads your catalog, customers, and order history, and imports everything into Shopify through the GraphQL Admin API. No CSV exports, no manual mapping for standard fields, no risk of encoding corruption on your product descriptions. If you want to understand what a migration would actually look like for your specific store — catalog size, attribute structure, customer count — it takes less than an hour to get a clear picture.

Conclusion

PrestaShop is not end-of-life in a binary sense. But the ecosystem around it is contracting at a rate that creates real operational risk for merchants over a two-to-three year horizon. Security patching is inconsistent, available talent is shrinking, and the tooling ecosystem is no longer keeping pace with what merchants need. None of that means you must migrate today — but it does mean that staying on PrestaShop requires an active decision with open eyes, not a passive default.

The merchants who will have the smoothest transitions are the ones who start planning now, before they are forced to move in response to a security incident or a critical module that stops being maintained.