Long-term support for Pimcore Platform 2024.4 ends in December 2026, and after that Pimcore ships no security patches or critical bug fixes for this version.
On this page 6 sections
The nearest safe landing point is Pimcore 2025.4 LTS, supported until December 2028 and the last release that runs Classic UI and Studio side by side.
Status as of 2026-11-11, based on Pimcore documentation and announcements (sources at the end). That leaves about seven weeks, and fewer in practice: many companies freeze production changes in the second half of December.
What exactly ends in December 2026?
Pimcore released 2024.4 on 2024-12-11 as an LTS version with two years of support. The release documentation is explicit: LTS covers security and critical bug fixes until December 2026 and is included in the Enterprise editions.
The scope is narrow. According to the Platform Versions page, LTS means fixes for critical CVEs plus bug fixes limited to issues that can cause data loss or destroy infrastructure. No features, no routine fixes. After December, not even that.
A second rule gets overlooked. Outside LTS, community support for a platform version ends when the next version ships. For 2024.4 that happened with the release of 2025.1.
Who is affected?
One question decides it: does the company have LTS today? Pimcore documentation grants LTS to the Enterprise and Enterprise PaaS editions only.
Edition on 2024.4 | LTS for 2024.4 | After December 2026 | What it means |
|---|---|---|---|
Enterprise, Enterprise PaaS | yes, until December 2026 | no security patches | a real deadline, plan the upgrade now |
Professional | no | no change: no fixes for 2024.4 since 2025.1 shipped | already running without patches |
Community (GPLv3) | no | as above | moving to 2025.x also changes the licence (see below) |
For Professional and Community users the honest reading is less comfortable than the December headline. Their deadline passed earlier. December 2026 is a good moment to name that and close it.
What changes between 2024.4 and 2025.4?
The upgrade crosses a major version boundary. The core moves from Pimcore 11.5 (in 2024.4) to Pimcore 12.3 (in 2025.4), and Pimcore covers this in a separate "V11 to V12" guide. The changes that matter most:
Area | Pimcore 2024.4 | Pimcore 2025.4 | Source |
|---|---|---|---|
Core | Pimcore 11.5 | Pimcore 12.3 | 2024.4 docs, pimcore/platform-version package metadata |
Community Edition licence | GPLv3 (last version under it) | Pimcore Open Core License (POCL): free for companies under EUR 5M annual revenue | Pimcore announcement 2025-04-29 |
Product key | not applicable | without a valid key the container build fails | V11 to V12 guide |
Admin interface | Classic UI | Classic UI and Studio in parallel; Studio only from 2026.1 | Pimcore announcements 2025-12-09 and 2026-04-14 |
Classic UI in Community Edition | included | separate perpetual licence, EUR 1,480 (ExtJS licensing) | V11 to V12 guide |
WYSIWYG editor | TinyMCE in core | TinyMCE moved to a separate bundle, no further security updates | V11 to V12 guide |
LTS | until December 2026 | until December 2028 (3 years from release) | Platform Versions, announcement 2025-12-09 |
The core itself updates with Composer and migrations. The time goes into everything around it: custom bundles, admin extensions written for Classic UI, third-party bundles that must support the target version, and the integrations with ERP, e-commerce and partner exports.
Which upgrade path makes sense?
Pimcore documentation requires a system to be on the latest release of the previous major version before it moves to the next one. A jump from 2024.4 to 2026.x therefore goes through 2025.4 anyway. The only question is where to stop.
Path | Fits when | Risk | Our view |
|---|---|---|---|
2024.4 to 2025.4 LTS now, Studio as a separate 2027 project | many Classic UI extensions, critical integrations, little time before December | lowest: Classic UI stays, LTS until 2028 | the default choice for this December |
2024.4 to 2025.4 and straight on to 2026.x | few admin customisations, a need for 2026 features | higher: two major versions, Studio and Symfony 7 in one window | only for a well-tested system |
Stay on 2024.4 | nobody who processes customer or partner data | a system without security patches | not recommended |
The criteria behind the table are three: the number of custom Classic UI extensions, the edition and licence, and how much time is really left before the change freeze. In our view 2025.4 is not a half-measure. It is the only version that combines LTS until 2028 with Classic UI, which buys time for a calm move to Studio without a calendar gun to your head.
How to plan the upgrade in seven weeks
- Inventory in week one. Platform version, edition and licence, the list of bundles (own and third-party), admin extensions, integrations and background jobs.
- Bundle compatibility. Every third-party bundle must support the target version. If one does not, decide: replace it, patch it or drop it.
- Deprecations. The Symfony deprecation log,
@deprecatedusages in code and warnings in the admin interface, as Pimcore's upgrade guide describes. - Full backup of database and files before each step.
- Upgrade a test environment to 2025.4, run migrations, clear caches.
- Regression tests on production data: imports, exports, Datahub, workflows, ERP and shop integrations.
- A production window before the December freeze, with a rollback plan.
- A Studio plan as a separate 2027 project, starting from an inventory of Classic UI extensions to rewrite.
If it is unclear where to start, start with an audit: version, code, bundles and integrations, ending in a list of work and risks. That is what our Pimcore audit delivers. For the interface switch itself, see our Classic UI to Studio migration guide; for the edition question, the Professional vs Enterprise licence comparison.
Who we are and why we write about it
LemonMind, a Pimcore Platinum Partner and Ergonode partner based in Gdańsk, Poland, implements Pimcore, Akeneo and Ergonode. According to our partner profile on pimcore.com, we have 48 Pimcore customers and 31 Pimcore certifications in the team. Version upgrades and data migration and integrations are a standing part of our work on the Pimcore platform.
Sources
- Pimcore Docs: Platform Versions · accessed 2026-11-11
- Pimcore Docs: Platform Version 2024.4 · accessed 2026-11-11
- Pimcore: Platform Version 2024.4 · 2024-12-11
- Pimcore: Platform Release 2025.4 · 2025-12-09
- Pimcore: Platform Version 2026.1 · 2026-04-14
- Pimcore Docs: Updating Pimcore V11 to V12 · accessed 2026-11-11
- Pimcore Docs: Major Version Upgrades · accessed 2026-11-11
- Pimcore Docs: Pimcore Editions · accessed 2026-11-11
- Pimcore: moving from GPL to POCL · 2025-04-29
- Packagist: pimcore/platform-version · accessed 2026-11-13
