Loading...
Drupal 7, 8 or 9 upgrade to Drupal 10 / 11: audit of custom and contrib modules, optional theme rebuild for Olivero or Claro, data and configuration migration, SEO and performance preserved.
Automatic legacy-code conversion tools produce code that compiles but stays unreadable and unmaintainable: original patterns are copied as-is, without idiomatization, with dependencies on a proprietary runtime. Pushed to production without full re-characterization, this code is neither reliable nor scalable. End-to-end automatic translation isn't a modernization method — it's a debt transfer.
Our approach is the opposite. ATLAS relies on multiple readings of the legacy code, from several angles: data flows, business rules, dependencies, edge cases. AI comes in as a comprehension accelerator — to decipher decades of accumulated business logic, reverse-document uncommented branches, surface the intent behind the code. It doesn't decide and it doesn't translate: it informs the architect's work, who then designs the target architecture (cloud, database, services) and drives the migration pattern by pattern, under parity audit.
This understanding still requires humans who know legacy languages. That's our edge: where Europe and North America face a retirement wave among mainframe and legacy developers, Tunisia retains a pool of experienced developers (COBOL, Delphi, PowerBuilder, RPG…). Paired with modern architects and developers trained in the ATLAS method, they ensure continuity between the original business intent and the target system.
Drupal 7 is officially end-of-support since January 2025 (extended support possible but expensive). Drupal 8 is end-of-life since November 2021. Drupal 9 requires an upgrade to 10 or 11 to benefit from latest features and security patches. Organizations staying on these versions inherit security risks (unpatched CVEs), technical debt (contrib modules stopping), and progressive incompatibility with modern hosting (recent PHP, recent MariaDB/MySQL). Urgency depends on site criticality and sector.
Drupal 10 (released December 2022) brings: Symfony 6, PHP 8.1+, Olivero (modern default theme), Claro (modern admin), CKEditor 5, removal of deprecated jQuery UI. Drupal 11 (2024) consolidates with Symfony 7, PHP 8.3+, Recipes (preconfigured installation), stable Workspaces. For institutional, media, e-commerce sites with structured content, the upgrade releases technical debt, reduces security risk, and opens access to modern contrib modules (Layout Builder, Paragraphs, Single Directory Components).
Three questions to ask before the upgrade. Does the current editorial site meet business needs? If yes, Drupal 10/11 upgrade = good choice (preserves investment). Has the functional scope changed? If yes (added multilingual, headless target, UX redesign needed), a deeper migration may be relevant: see WordPress to Drupal migration, CMS to headless migration, or Multilingual site redesign. Are there many custom modules? If yes, upgrade effort is greater — compare with the cost of a redesign with modern stack.
Healthy Drupal 7/8/9 site with standard contrib modules. Default recommendation. Migration via Drupal Migrate API or Upgrade Status module.
If current theme is outdated, take the upgrade opportunity to switch to Olivero (front) and Claro (admin). Modernized UX without functional redesign.
If editorial benefits from being more structured (reusable components, typed paragraphs). Increases work but durably improves editorial experience.
If needs evolve radically (edge performance, modern custom front, multi-channel). Greater effort. See CMS to headless migration.
A Drupal upgrade is typically structured over 2 to 6 months depending on complexity. For a Drupal site with a few custom and standard contrib modules, plan 2 to 3 months with a 3-person cell: senior Drupal developer, theme integrator, QA. For a complex site with 20+ custom modules, multi-site, or theme redesign, plan 4 to 6 months and 4-6 people. The marginal cost of a Drupal 9 → 10 → 11 upgrade is lower than a Drupal 7 → 10 upgrade (which goes through Drupal 8 or uses migration).
Underestimating custom modules. A Drupal site typically has 20-50 custom modules written over several years, some by departed developers. Their compatibility with Drupal 10/11 must be validated one by one.
Module audit from Intake with Upgrade Status module Drupal native: generates an automatic compatibility report. Each incompatible module is qualified: to update, to replace with equivalent contrib, or to remove if unused. Dormant module inventory often reduces upgrade scope by 20-30%.
Neglecting Drupal 7 migration specifically. Drupal 7 → 10 requires a complete migration (data + structure), not a simple upgrade. Many Drupal 7 contrib modules have no Drupal 10 equivalent.
Drupal Migrate API with custom scripts per content type, conversion of Drupal 7 structures (Drupal 7 nodes, fields, taxonomies) to Drupal 10. Or switch via Drupal 9 as intermediate step if many contrib modules. Sample validation phase before mass migration.
Forgetting PHP/MySQL/PostgreSQL dependencies. Drupal 10 requires PHP 8.1+, Drupal 11 requires PHP 8.3+. Old hosting may not support.
Infrastructure audit from Intake: PHP version, MySQL/PostgreSQL, server configuration. If current hosting doesn't support, plan a hosting migration (Plesk, Pantheon, Acquia, Cloudways) in parallel with the Drupal upgrade. Additional cost to anticipate.
Mishandling the theme during upgrade. If the custom theme is old, it can break on Drupal 10/11 (modern Twig, jQuery UI removal).
Theme audit: if compatible with light adaptations (jQuery UI → vanilla JS, Twig 2 → Twig 3), keep. Otherwise, migrate to Olivero (Drupal 10 default theme) or modern custom theme redesign. Decision argued by ROI: an old theme reworked can modernize the site without major extra cost.
Digital redesign of a Middle Eastern public university on Drupal CMS, with horizontal → vertical shift, native Arabic/English bilingual handling with RTL, RESTful API integration. Mastery of the complete Drupal chain for a demanding public institution.
Drupal heritage management CMS for a ministry of culture, XR platform on 14 historic sites (Vision 2030). Multi-language Arabic/English Drupal architecture with integrated 3D and VR/AR content.
Drupal 11 released in 2024. For new sites, start in 11 directly. For an upgrade from Drupal 9, go through stable Drupal 10 then Drupal 11 when critical contrib modules are up to date. The 9 → 10 transition is the main effort; 10 → 11 is generally marginal on common contrib modules.
Drupal 9 → 10/11 standard site: 30 to 80 k€ depending on number of custom modules (3 to 8 weeks, 3-person cell). Drupal 7 → 10/11: 80 to 200 k€ because of structure migration (8-16 weeks, 3-5 people). Complex multi-site: 150-400 k€.
Drupal 7 and 8 are end-of-support: no security patches, unfixed CVE vulnerabilities expose the site to compromises. For institutional sites (government, public services, regulated sector), it's a regulatory risk (security duty). For e-commerce sites, it's a GDPR/PCI-DSS risk. For media, it's a reputational risk.
Standard Drupal 9 → 10/11 upgrade: 2 to 3 months in 3-person cell. Drupal 7 → 10/11 upgrade (full migration): 4 to 6 months in 4-6 person cell. Complex sites (multi-site, 50+ custom modules): 6-9 months.
We frame the trajectory, the budget, and the deliverables in a first thirty-minute conversation. A short POC can be proposed before committing to the full program.
Start this path →