Pimcore Upgrade
We help you plan and execute a Pimcore version upgrade safely and without budget surprises. Upgrade Pimcore to a newer version with a clear scope, realistic estimates, and controlled delivery.
Recognised by Pimcore for advanced expertise and proven delivery experience.
Hands-on Pimcore experience across implementations that support daily business operations.
Proven experience upgrading Pimcore systems from version 4.6 onward.
REDUCE COMPLIANCE EXPOSURE & IMPROVE SECURITY
Older Pimcore versions eventually stop receiving security fixes and support. Running unsupported versions increases operational and security risk.
AVOID ACCUMULATING TECHNICAL DEBT
Skipping upgrades for years turns the next upgrade into a large, expensive project. Regular upgrades keep changes smaller and more predictable.
BENEFIT FROM BUG FIXES
Many issues reported by teams are already fixed in newer Pimcore versions. Staying on old versions often means living with known problems.
IMPROVE PIMCORE PERFORMANCE
Performance issues often appear gradually as Pimcore versions fall behind. Keeping versions up to date helps prevent slowdowns caused by outdated components and accumulated changes.
UPGRADE SCOPE: WHAT'S INCLUDED AND WHAT'S NOT
A Pimcore upgrade focuses on moving Pimcore to a newer, supported version and handling the technical work required to make that possible. Included:
- Aligning the technical stack required by the target Pimcore version
- Identifying bundle compatibility with the target Pimcore version
- Flagging risks related to unsupported bundles or dependencies
- Upgrading Pimcore to a newer, supported version, including step-by-step version transitions when older releases are involved
- Updating the technical stack required by the target Pimcore version (OS, PHP, and required libraries)
- Reviewing and updating project's custom code affected by deprecated or removed functionality
- Testing critical Pimcore behavior, including background processes
- Deploying the upgraded Pimcore version following an agreed rollout plan
Some work may be related to a Pimcore upgrade, but is not part of the upgrade scope unless agreed separately. Not included by default:
- Upgrading or changing external systems connected via API (ERP, CRM, external portals)
- Fixing or upgrading third-party bundles that are not supported by their vendors
- Refactoring or replacing third-party libraries
- Infrastructure redesign, scaling, or hosting changes
- Functional improvements unrelated to the Pimcore version upgrade
Plan Your Pimcore Upgrade
Most Pimcore upgrade issues happen because systems are upgraded without proper analysis or planning. A structured process keeps the upgrade predictable, controlled, and aligned with business expectations.
When Pimcore upgrades involve end-of-life functionality
As Pimcore evolves, some older functionalities reach end of life and are no longer supported, such as the transition from Classic Admin UI to Pimcore Studio. During the upgrade, we assess how these changes affect your system and recommend a clear migration approach to ensure existing content and business-critical processes remain stable.
COMMON QUESTIONS ABOUT PIMCORE UPGRADE
What is a Pimcore upgrade?
A Pimcore upgrade means upgrading Pimcore itself to a newer, official version.
In practice, this often includes aligning the underlying technical stack and adapting custom code so the system continues to work on the new version. It is not a feature project, but technical maintenance required to keep Pimcore secure, supported, and viable.
When should Pimcore be upgraded?
Pimcore should be upgraded when:
- the current version is outdated or approaching end of support
- security patches are no longer available
- performance degrades due to outdated underlying components
- bugs exist that are already fixed in newer Pimcore versions
- preparation is needed for upcoming changes such as the transition to Studio UI
Do we need to upgrade every Pimcore release?
No. Many teams upgrade based on Long-Term Support (LTS) releases. This approach allows teams to stay supported and secure without upgrading every minor version.
Is a Pimcore upgrade a one-click process?
No. Pimcore upgrades usually involve multiple components and dependencies. The more custom code and skipped versions there are, the more planning and work is required.
What makes Pimcore upgrades complex?
The main complexity comes from:
- custom code written outside the Pimcore core
- dependencies on older PHP or Symfony versions
- third-party bundles that may not support newer Pimcore versions
- background processes that are not visible in the UI
These areas must be reviewed before upgrading to avoid breaking the system.
What is the biggest cost driver in a Pimcore upgrade?
Custom code. The more custom code exists, especially code written years ago or not regularly maintained, the more effort is required during an upgrade. Regular upgrades usually reduce long-term cost.
What happens if we skip Pimcore upgrades for several years?
Skipping upgrades often leads to:
- large version jumps
- step-by-step upgrades across multiple major versions
- significantly higher effort and longer testing cycles
In such cases, upgrades can take hundreds of hours and require careful planning.
How do you handle very old Pimcore versions?
Very old versions usually cannot be upgraded directly to the latest version. Instead, upgrades are done step by step across major versions, updating required components along the way to ensure stability and correctness.
What happens with third-party bundles?
Third-party bundles are maintained by their vendors.
During an upgrade, we:
- identify which bundles are in use
- check whether they support the target Pimcore version
- flag bundles that are incompatible or risky
If a bundle does not support the target version, we cannot upgrade or fix it by default. The next steps must be decided together with the client.
Do you upgrade or fix third-party libraries?
No, not by default. Third-party libraries that are treated as “black boxes” are not refactored or rewritten during a Pimcore upgrade. If such a library becomes a bottleneck or incompatible, we highlight the risk and recommend separate action.
Are external systems like ERP or CRM included?
No. External systems connected to Pimcore via API are out of scope for a Pimcore upgrade. The goal is to preserve Pimcore-side behavior. Changes to external systems must be handled separately.
Are infrastructure or server upgrades included?
No, not by default. Infrastructure changes may sometimes be required to support newer Pimcore versions, but they are not part of the Pimcore upgrade unless agreed separately.
How do you handle testing during an upgrade?
Testing is critical because many failures are not visible in the UI. During an upgrade, testing focuses on:
- critical Pimcore functionality
- background processes such as imports, exports, and scheduled jobs
- Pimcore-side behavior of integrations
If automated tests do not exist, we recommend creating them to reduce risk.
How does the upgraded system go live?
The upgraded Pimcore version is deployed according to an agreed rollout plan. The goal is a controlled release, not an unplanned production change.
How long does a Pimcore upgrade take?
There is no fixed duration. Effort depends on:
- the current Pimcore version
- how many versions are skipped
- the amount and quality of custom code
Regular upgrades typically take significantly less effort than large, delayed upgrades.
What is the first step if we’re unsure whether an upgrade is needed?
The first step is an upgrade assessment. It helps determine:
- whether an upgrade is required
- which version makes sense
- where the main risks are
- what realistic effort looks like