Back to Insights

Akeneo 7 End of Support: Your Options for On-Premise

Tech & Development · · 4 min read
Julia, Content Marketing Manager
Author Julia Content Marketing Manager

An outdated on-premise server labelled 7.0 with a warning sign and an arrow leading to a secure cloud, with 2026.x as an alternative route AI generated

Akeneo 7 end of support on 30 September 2026: what applies to Enterprise and Community Editions, your options and how to plan the move to SaaS.

Support for Akeneo PIM 7.0 ended on 30 September 2026. For many companies that have run Akeneo on their own servers or as PaaS for years, that's a turning point. According to Akeneo, Enterprise Edition customers now only get bug fixes by moving to the SaaS version.

But Akeneo 7 end of support doesn't affect everyone in the same way. Different rules apply to the Community Edition and the Enterprise Edition. That's why it pays to look closely before you choose a route.

At a glance:

  • What Akeneo 7 end of support means

  • What applies to the Enterprise and Community Editions

  • Which options you have now

  • How to plan the move

What Akeneo 7 end of support means

According to Akeneo, version 7.0 was supported until 30 September 2026. After that, there are no more regular bug fixes for 7.0.

For Enterprise Edition customers, this means: if you want to keep receiving bug fixes and SLA-backed support, Akeneo says you have to move to the SaaS version. Akeneo calls its cloud version "Serenity", and it's available to customers on the Enterprise and Growth packages.

And the Community Edition?

The Community Edition is explicitly not affected by the end of support. According to Akeneo, it continues to be maintained, remains free and open source, and no end of life has been announced. According to Akeneo, the current version is 2026.5 from 30 October 2026.

To keep receiving security and bug fixes, Akeneo recommends Community users update to the latest 2026 release. If you're still on 6.0, update to 7.0 first; if you're on 7.0, apply all 7.0 migrations first.

The catch: the Community Edition has no commercial support and doesn't include all the features of the commercial packages. For companies with many users, workflows and channels, it's often not enough.

Your options at a glance

  • Move to the Akeneo Product Cloud (SaaS): Akeneo runs and updates the PIM, and you get new features such as AI agents. Custom extensions in the core need to be replaced with APIs and external extensions.

  • Update the Community Edition to 2026.x: you stay responsible for operations and updates yourself, without commercial support.

  • Switch PIM: if a major rebuild is due anyway, comparing alternatives such as Pimcore can make sense.

In practice: for most Enterprise customers, moving to the SaaS version is the obvious route. Whether it also pays off functionally depends on how heavily your Akeneo is customised.

What the move means for your team

Moving from on-premise to SaaS is more than a relocation. Custom bundles and core customisations that were possible in the self-hosted version can't be carried over directly to SaaS. They become API integrations, apps, or are dropped.

At the same time, a lot of operational effort disappears: servers, updates and security patches are handled by Akeneo. Your team can focus on the data model, data quality and channels.

Our recommendation: use the move to clean up your data model and interfaces. A 1:1 transfer of old custom solutions costs more than it brings.

How to plan the move

  1. Take stock. Document version, edition, hosting and all your own customisations.

  2. Assess customisations. For each extension, decide: replace via API, cover with standard features, or drop.

  3. Check interfaces. Align ERP, shop, DAM and marketplaces with the SaaS APIs.

  4. Test the migration. Transfer data in a test environment and check workflows.

  5. Train your team. Introduce the new interfaces and features before go-live.

Conclusion: Akeneo 7 end of support is a chance to clean up

Akeneo 7 end of support forces Enterprise customers to make a decision. For most, the route leads to the SaaS version; for Community users, to the 2026.x update.

If you see the move only as an obligation, you miss its potential. A clean migration is the opportunity to modernise your data model, interfaces and processes.

As an Akeneo agency, we support the move from Akeneo 7 on-premise or PaaS to the SaaS version, from analysis to go-live.

Frequently asked questions

When does support for Akeneo 7 end?

According to Akeneo, version 7.0 was supported until 30 September 2026. After that, Enterprise Edition customers only get bug fixes by moving to the SaaS version.

Is the Akeneo Community Edition being discontinued?

No. According to Akeneo, the Community Edition continues to be maintained and remains free and open source. No end of life has been announced. To get fixes, update to the latest 2026 release.

What is Akeneo Serenity?

Serenity is the cloud version of Akeneo PIM. Akeneo runs and updates it. According to Akeneo, it's available to customers on the Enterprise and Growth packages.

Can I carry my customisations over to Akeneo SaaS?

Not directly. Extensions in the core of the self-hosted version have to be implemented in SaaS via APIs, apps or external integrations. Review each customisation before migrating.

Sources

Still running Akeneo 7?

We'll review your version, customisations and interfaces and plan the move to the Akeneo Product Cloud or the right update with you.