Drupal maintenance since 2015
Evolve your platform without compromising continuity
PartITech has been developing and maintaining Drupal projects since 2015. An update is not just about changing a version number: it must preserve business paths, content, integrations, performance and the ability of teams to continue to evolve the application.
We work on the applications that we have built as on existing Drupal platforms. Our goal is to put each project back on a maintainable trajectory, with a version of Drupal, PHP and dependencies that still benefit from security patches.
- Since 2015
- Drupal development and maintenance
- Code, data, infrastructure
- A complete migration scope
- Acceptance testing before cutover
- Changes verified outside of production
Security and sustainability
Why keep Drupal up to date?
Keeping the Drupal core, modules, themes, Composer and PHP environment up to date is an integral part of a platform's security.
Fix vulnerabilities
Maintained versions receive security advisories and core fixes. Contrib extensions and Composer dependencies should be followed with equal care.
Preserve stability
Patched releases resolve anomalies, strengthen compatibility and reduce unpredictable behavior in editorial and business journeys.
Improve performance
Drupal 11.4 greatly reduces entity loading queries and improves compression, translations, and several critical core paths.
Stay compatible
Drupal scales with PHP, Symfony, Twig, CKEditor, database engines and Composer. A platform that is too old ends up blocking its entire environment.
Limit technical debt
Frequent updates isolate changes. Waiting for several generations accumulates deleted APIs, abandoned modules and data migrations.
Retain the ability to evolve
A maintained base makes it possible to deliver new functions without starting each project with an urgent upgrade of the entire base.
2026 Calendar
Which version of Drupal to favor?
Drupal 11 is the reference generation. For a new project or a migration compatible with its prerequisites, the current target is the branch Drupal 11.4.x.
Recommended branch
Drupal 11.4
Published on 1er July 2026, Drupal 11.4 is ready for production and benefits from security support announced until June 2027.
View Drupal 11.4 release notes- Faster loading of entities and lists, with significantly fewer database queries.
- Brotli compression possible for aggregated CSS and JavaScript files.
- Application of Recipes and import of translations accelerated.
- New native command line interface, still experimental.
- Easier security updates to key dependencies with
core-recommended.
Drupal 11.4.x
Preferred
Current branch for new developments and migrations. Security support announced until June 2027.
Drupal 11.3.x
To be upgraded
Still covered by security patches until December 2026. Upgrade to 11.4 should be planned.
Drupal 10.6.x
Transition branch
Latest Drupal 10 branch, maintained until December 2026. Drupal 10 will reach end of life on December 9, 2026.
Drupal 10.5 and earlier
Not maintained
Drupal 10.5, Drupal 11.2, and all earlier branches no longer have standard security support.
Modern base
What Drupal 11 changes for maintenance
Drupal 11 continues the modernization started with Drupal 8, 9 and 10. These developments improve the construction of platforms, but require obsolete APIs and dependencies to be addressed before migration.
Single Directory Components
Twig templates, styles, scripts and metadata of a component can be grouped into a coherent structure, easier to test and reuse.
Recipes
Sets of modules and configurations can be applied in a repeatable manner to accelerate the installation or evolution of features.
Workspaces
Teams can prepare coherent sets of content changes before publishing, subject to checking the uses and extensions of the project.
Decoupled architectures
JSON:API and the core APIs allow Drupal to be used as an editorial base for React, Vue.js, mobile or multi-media interfaces.
Modernized front-end
The core gradually reduces its dependence on legacy libraries and improves Twig tooling, components and web standards.
Obsolete code removed
Removing deprecated APIs keeps the core modern. Specific modules must therefore be analyzed and corrected before a major climb.
PHP and infrastructure
Technical compatibility is not enough
The PHP version must be both accepted by Drupal, compatible with the project's modules and dependencies, and still maintained by PHP.
Drupal 11.4 supports PHP 8.3, 8.4 and 8.5
For a new target, we favor a version with sufficient support duration, after validation of PHP extensions, contrib modules, specific code and hosting.
Drupal 10.6 still accepts older PHP versions, but keeping an end-of-life runtime negates some of the benefit of migration.
- Required PHP version and extensions
- Composer version and dependencies locked
- MySQL, MariaDB or PostgreSQL
- Web server, cache, filesystems and scheduled tasks
- Monitoring, backups and rollback procedure
Compatibilities are detailed in the Drupal PHP prerequisites. The runtime status must be checked separately in the official PHP calendar.
Choose the right trajectory
What to do according to your current version?
You are already on Drupal 11
We apply the latest patch version of the target branch, check for extensions and deprecations, and then test critical paths. A recent major version does not exempt you from monitoring minor versions.
Objective: join 11.4.x and maintain a regular cadence.
You are on Drupal 10
The first step consists of joining Drupal 10.6, the last branch of this generation, then removing the deprecations and blockages identified before migrating to Drupal 11.4.
Objective: migrate before end of life on December 9, 2026.
You are on Drupal 8 or 9
These builds no longer receive patches. The project must address compatible tiers, historical versions of PHP and Symfony, abandoned modules and specific code before reaching the current target.
Objective: secure the existing then organize an increase in controlled stages.
You are on Drupal 7 or earlier
Drupal 7 has been at the end of its life since January 5, 2025. The transition to Drupal 11 is generally a migration project: new architecture, resumption of content, users, taxonomies, files, redirections and rewriting of part of the specific.
Objective: build a new database and migrate the data with completeness checks.
A verifiable migration
The essential steps of a Drupal version upgrade
Every project is different, but a reliable migration should make dependencies, decisions, tests, and rollback conditions visible.
Audit of the existing
Drupal and PHP versions, modules, theme, specific code, Composer, database, volumes, interfaces and infrastructure.
Target definition
Drupal version, PHP runtime, database, hosting and transition strategy compatible with the expected support duration.
Gap mapping
Incompatible modules, deprecated APIs, abandoned libraries, configuration changes and developments to adapt or replace.
Migration environment
Isolated copy, reproducible dependencies, controlled backups and documented procedure to avoid working directly in production.
Updating code and data
Composer setup, specific adaptations, configuration, content migrations and corrections of incompatibilities.
Testing and acceptance
Business journeys, administration, rights, search, forms, media, SEO, external interfaces, performance and security.
Toggle repeat
Timing, final data synchronization, intervention window, responsibilities, decision criteria and rollback.
Production and monitoring
Deployment, post-failover checks, logs, message queues, scheduled tasks, cache, metrics and anomaly tracking.
Proof, not just a version
What the migration should produce
- Inventory of modules, themes, dependencies and specific developments
- Compatibility report and decision register
- Reproducible Composer repository and updated dependencies
- Data migration plan and completeness checks
- Test plan and acceptance report
- Restoreable backups and rollback procedure
- Production plan and post-deployment controls
- Operational documentation and maintenance schedule
PartITech Experience
From regular updates to complex migrations
Since 2015, we have updated dozens of Drupal applications. We can also upgrade the servers when their outsourcing is entrusted to us and take over platforms that we have not developed.
This experience allows us to intervene on both a minor version upgrade and the complete modernization of an old application, taking into account business and operating constraints.