Akeneo v7 end of support on September 30, 2026: migrating to cocoPIM without breaking your budget or your schedule

What really stops with the September 30, 2026 end of support (and what doesn’t)

Enterprise editions, on-premise and PaaS (Flexibility). Version 7, released in March 2023, is the last release of these offerings: Akeneo announced it as early as March 2024, and its support ends on September 30, 2026. From that date, no more technical support, no more fixes, no more security patches. The path Akeneo offers is its Serenity SaaS platform, updated automatically, which does not accept custom code: in-house bundles must be removed before the migration.

Community Edition. CE v7 has the same end-of-support date: September 30, 2026. The Community Edition is not going away, though: in early 2026 Akeneo released versions “2026-2” and then “2026.3” (PHP 8.3, MySQL 8, Elasticsearch 8.17), now versioned independently of the Enterprise edition. But they come with no SLA and no contractual vendor support: help comes from the community and partners. Upgrades, security and operations remain your responsibility, or your integrator’s.

In practice, a vulnerability discovered in your v7 after September 30 will stay open until you have migrated or patched it yourself. For your CISO, your cyber insurer and your DPO, an unmaintained component at the heart of your information system, the one that holds your prices, your descriptions and your media, is no minor detail.

Your three options, without the spin

The first option is legitimate and Akeneo supports it seriously. The second is an engineering choice, not a product choice. The third is the one cocoPIM was designed to make smooth.

Why the Akeneo → cocoPIM migration is smoother than you think

You already speak the same language

Families, attributes, channels, languages, variants: this vocabulary belongs to no one. It is the grammar shared by every PIM on the market, just as rows and formulas are the grammar of spreadsheets. cocoPIM is designed and developed in France on this same business standard. The practical consequence: what your teams have learned remains valid, concept for concept.

Your product leads find their bearings on day one. So does your integrator.

Your Akeneo exports are cocoPIM’s input format

Akeneo exports its catalogs as CSV and XLSX: one row per product, one column per attribute, broken down by language and by channel, with the media in an archive. That is exactly what cocoPIM’s import wizards expect. No converter, no script.

The import happens in two stages. Structure first: attribute groups, option lists, attributes, families, channels, categories, imported as CSV, XLSX or JSON. One case was handled specifically for Akeneo: importing options per attribute, the way Akeneo exports them, with multilingual labels, order and color. Products next: the wizard shows a preview of the file, suggests column mappings when the names look alike, lets you skip what you are not bringing over, and saves the whole setup as a template for the following batches. If your export says “TERRA” where your list says “Terracotta”, value mapping makes the link once and for all.

Each import runs in the background and produces a line-by-line report: unknown family, unmapped value, duplicate SKU. You fix, you rerun, and only the corrected lines change. An explicit setting decides what happens to SKUs that already exist (skip, update, flag), which prevents accidental overwrites, the classic migration nightmare.

Media follow the same path. The media library is loaded in bulk, from a ZIP archive or a list of URLs, and the file names in your product export are automatically matched to the imported media: your photos find their way back to their product records with no re-keying.

For screen-by-screen details, the Importing your data (in French) module of the documentation walks through the wizard step by step.

What the migration does not carry over: your rules and approval workflows

This is the point that derails schedules when it is discovered too late, so let’s say it right away. The migration carries over the structure and the product data. It carries over neither enrichment rules, nor approval workflows, nor custom code. A rules engine that copies one attribute into another, a multi-level approval workflow, a bundle developed by your integrator: these are behaviors, not data, and they are specific to the platform that runs them.

In cocoPIM, some of these needs are covered differently: calculated fields and AI fields from the Pro plan up, completeness requirements per channel, product statuses and publication status per channel, roles and fine-grained permissions. Others are rebuilt more simply, or turn out to be unnecessary: in a PIM installed several years ago, some of the legacy rules no longer have an identifiable user.

After the import: reconnect, don’t redevelop

cocoPIM plugs back into your ecosystem with standard building blocks: a native Shopify connector to publish, an Odoo connector to import items from the ERP, CSV and Excel exports targeted per channel, a public REST API (GraphQL from the Growth plan up) for the ERP and the e-commerce site, and webhooks to notify your systems of every change. Whatever your integrator had connected to Akeneo’s API reconnects to a documented API, with limited-scope keys and quotas.

A five-step migration plan

Orders of magnitude for a catalog of a few thousand SKUs, one to three languages, two or three channels, in days of effort, not calendar days.

1. Scope (1 to 2 days). Inventory of families, attributes, channels, languages, categories. An explicit decision on what you will not carry over. Inventory of rules and approval workflows in three columns.
2. Export from Akeneo (half a day). CSV or XLSX exports of the structure and the products through the standard export profiles, plus the media archive.
3. Import the structure (half a day to 1 day). Option lists, groups, attributes, families, channels, categories. Column mapping, saving the template, checks on a few families.
4. Import the media, then the products (1 to 3 days depending on volume). The media archive first, so that product records find their photos. Then twenty representative products, reading the report, adjustments, and import in batches.
5. Reconnect and switch over (2 to 5 days). Connectors and API, rebuilding the essential rules, acceptance testing with the business teams, freezing data entry in the old tool, switchover.

That comes to one to three weeks of effort, spread over whatever schedule suits you, with no development, no servers to order, no intermediate upgrade. And if the end of support has already passed, or falls before the end of the project: what counts for your risk exposure is having a switchover date and a dated plan, not having finished everything the day before September 30.

Time and money: what you stop paying for

A self-hosted PIM rarely costs what its license says. It costs servers, a MySQL database and an Elasticsearch cluster to run, backups to test, PHP upgrades to plan, integrator days to maintain bundles that nobody reads anymore, and an on-call rotation for when the search engine goes down on a Sunday in the middle of the sales season.

With cocoPIM, all of that becomes a monthly subscription, excl. VAT, with no surprises: Discovery at €0 to test with your own data, Essential at €99, Pro at €249 (calculated fields and AI fields), Growth at €549 (GraphQL API), Enterprise on quote with SSO and custom quotas. And above all, what you don’t pay for: unlimited users on every plan, no setup fees, continuous updates, daily database backups, 15% off with an annual commitment. The details are on the Pricing page.

Changing PIM doesn’t mean changing continents: hosting in France with OVHcloud, GDPR built into the data model, AI powered by Mistral. And because a successful migration is a reversible one, you can export your entire catalog, structure and media included, at any time, in standard formats. You arrive with your Akeneo exports; you leave, if you ever want to, with exports that are just as readable.

We won’t put a figure here on what your current setup costs you: you know that better than we do. But put your annual operating budget side by side with 12 times the plan that fits you: the conversation with the finance department is usually rather short.

Who cocoPIM is not the right fit for

We would rather say it here than in the middle of your project. If you run multi-level approval workflows with dozens of contributors, complex entity reference data, structured supplier data collection at scale, or catalogs of several hundred thousand SKUs, an Enterprise offering (Serenity first among them) will remain a better fit. cocoPIM is built for French micro, small and mid-sized businesses that want a PIM that does its job, fast, in French, at the price of a tool.

If you are unsure which category you fall into, that is exactly what the migration assessment is for.

Where to start this week

• Export twenty products from Akeneo with their families and attributes.
• Create a Discovery space on cocoPIM, free, no credit card required.
• Import your structure, then your twenty products, and read the report.
• List your rules and approval workflows in three columns. Set a target switchover date.

Twenty minutes of testing saves weeks of doubt.

Frequently asked questions

Is it too late to migrate after September 30, 2026?

No. Your v7 keeps running after the end of support, but without support or security fixes. What matters is having a dated plan and limiting how long an unmaintained component stays at the heart of your information system. A migration to cocoPIM takes one to three weeks of effort.

Is our Akeneo data compatible with cocoPIM?

Yes, through Akeneo’s standard CSV and XLSX exports and the media archive. The structure (families, attributes, options, channels, categories) is imported first, then the media, then the products. The import wizard suggests column mappings and remembers them.

What happens to our enrichment rules and approval workflows?

They are not migrated: they are behaviors tied to the platform, not data. Some can be recreated with calculated fields, AI fields and completeness requirements; some can be simplified; the rest, often, no longer has a user.

What about our existing integrations (ERP, e-commerce site)?

They reconnect to cocoPIM’s public API (REST, GraphQL from Growth up) and webhooks, or through the native Shopify connector. The work happens on the connector side, not on the data side.

Akeneo is a registered trademark of Akeneo SAS. cocoPIM is published by T2ND SAAS and is neither affiliated with nor a partner of Akeneo. Information on Akeneo’s offerings comes from the public sources cited, as of the date of publication and of the last update.