Akeneo support
Akeneo v7 support ends on 30 September 2026. What are your options?
Three realistic paths, described without a sales pitch, and what we can do on each of them. We run production PIM systems for a living and have no stake in which one you choose.
The facts
What is changing
Support for v7 ends
Akeneo PIM v7, the last PaaS and on-premise version, reaches end of support on 30 September 2026. After that date Akeneo provides no technical support and no bug or security patches for it. Source: Akeneo PIM product support dates.
No new self-hosted versions
Akeneo stopped releasing new PaaS and on-premise versions to focus on its SaaS product, Serenity. Source: Akeneo on the move to Serenity.
The Event API retires too
The Akeneo Event API will be retired on 31 December 2026. Integrations built on it, typically the ones pushing product changes to a shop, an ERP or a DAM, need to move to the new Event Platform. Source: Event API deprecation FAQ.
Your options
Three realistic paths
None of these is always the right one. Which fits depends on how customised your instance is, what runs on the Event API, and what else is changing in your systems over the next two years.
Keep running v7 self-hosted
You stay on the version you have, with your own maintenance and security measures in place of vendor patches. This makes sense when the instance is stable, the integrations around it are mature, and a migration would cost more than it returns in the next one or two years. It needs someone who watches the dependencies, keeps the platform underneath current, and knows the codebase well enough to patch it.
Move to Akeneo Serenity
Akeneo's SaaS product is where new features go. This is the natural path when you want to stay in the Akeneo ecosystem and your customisations are light enough to rebuild on the SaaS APIs. Custom bundles and anything built on the retiring Event API need to be rewritten, so the work is in the integrations, not the catalogue.
Migrate to another PIM, such as Pimcore
Worth considering when you want to keep the system on your own infrastructure, when the data model has outgrown what Akeneo does well, or when the PIM should merge with DAM or master data needs. It is the largest of the three moves and pays off over years, not months, so it fits companies that are already planning a wider change.
Why us
What we bring to the decision
Four years running production PIM systems, including Akeneo and Pimcore integrations with DAM, CRM and translation systems at a medical device manufacturer. We have done the version upgrades, the failed syncs at three in the morning, and the data model corrections that a migration exposes. That experience is what makes an honest assessment possible: we can tell you which of the three paths your instance is actually ready for.
Whichever way you go, the first step is the same: a written look at the instance you have, its customisations, and the integrations that hang off the Event API.
Next step
Talk through your instance before September
Thirty minutes on what runs on your Akeneo today, what is customised, and which of the three paths is realistic for you. If the answer is to leave it alone, we say so.
Related pages