Skip to content

Drupal service

Drupal 10 to 11 upgrade and Drupal site takeover

Compatibility audit, upgrade and takeover of your existing Drupal site, before and after Drupal 10 reaches end of life on 9 December 2026.

Drupal 10 reaches end of life on 9 December 2026. After that date, core gets no more security fixes.

Our guide sets out the official Drupal 10 end-of-life timeline. We audit your site, upgrade it to Drupal 11, take over Drupal sites left by another vendor and migrate Drupal 7 or 9 sites. We work with banks and insurers in Morocco and with companies in France, and can support teams elsewhere in Europe, through a nearshore team based in Casablanca.

Drupal 10 ends on 9 December 2026: where does your site stand?

Your site runs a recent Drupal 10

On 10.3 or later, the move to Drupal 11 is an in-place upgrade, not a rebuild. The audit tells you how many modules and how much code need work.

Start with the audit

Your site runs an old or heavily customised Drupal 10

It first needs to reach 10.3 at least, with deprecated code fixed. We quote this batch separately, before the upgrade.

See the upgrade package

Your site runs Drupal 7 or Drupal 9

Drupal 9 takes two steps. Drupal 7 needs a migration, meaning a rebuild of the site on Drupal 11.

See Drupal 7 and 9 migration

Your vendor has gone or the site is unstable

We take over the site: access, backups, security, then the upgrade to Drupal 11.

See site takeover

Our packages

Four packages, from the audit to a full migration. Depending on scope, the upgrade is quoted as a fixed price after the audit or delivered on a time and materials basis: our terms of sale provide for both models.

Drupal 11 compatibility audit

Goal: know exactly what blocks the move to Drupal 11 and what the upgrade will cost.

Deliverables

  • Inventory of contributed and custom modules, with their Drupal 11 status
  • Upgrade Status report with our comments
  • Hosting gaps: PHP, database, web server
  • Firm quote for the upgrade and a switch plan
Duration
[TO PROVIDE: duration of the compatibility audit in working days]
Starting price
[TO PROVIDE: audit price excluding VAT in EUR and MAD, and whether it is deducted from the upgrade]

To measure SEO and performance before and after the switch, our SEO and performance audit (Express Diagnostic, MAD 8,000 excluding VAT, about €730, online price) complements the compatibility audit. It is a web audit, not a review of your Drupal code.

Drupal 10 to 11 upgrade

Goal: move to Drupal 11 in place, without a rebuild, with a controlled switch.

What we do

  • Move to the latest 10.6.x release
  • Fix deprecated code (Drupal Rector, then review) and update contributed modules
  • Upgrade core with Composer and run database updates
  • Acceptance testing in a dedicated environment, then a switch with rollback
  • Warranty: blocking defects fixed free of charge for 30 days after delivery, under article 9.1 of our French terms of sale (in French)
Duration and starting price of the upgrade by site profile
Site profileTypical durationStarting price excl. VAT
Up-to-date corporate site, little custom code[TO PROVIDE: typical duration in weeks for this profile][TO PROVIDE: starting price excluding VAT in EUR and MAD for this profile]
Multilingual or multisite portal[TO PROVIDE: typical duration in weeks for this profile][TO PROVIDE: starting price excluding VAT in EUR and MAD for this profile]
Headless or transactional platform[TO PROVIDE: typical duration in weeks for this profile][TO PROVIDE: starting price excluding VAT in EUR and MAD for this profile]
Plan my upgrade

Takeover of an existing Drupal site

Your vendor has changed, disappeared or stopped answering? We apply our four-step application maintenance takeover process to Drupal.

  1. Audit of the existing site: access, code repository and backups, then a review of code, modules and security.
  2. Knowledge transfer: handover with the outgoing team when possible, documentation, environments.
  3. Stabilisation: immediate security updates, monitoring, priority fixes.
  4. Run: maintenance under an SLA, then the upgrade to Drupal 11.

Duration and price: [TO PROVIDE: duration and starting price excluding VAT of the takeover phase (audit, handover, stabilisation), in EUR and MAD]

Migration from Drupal 7 or Drupal 9

  • Drupal 9: two steps, first Drupal 10.3 at least, then Drupal 11.
  • Drupal 7, end of life since 5 January 2025: a migration to Drupal 11, meaning a rebuild. Migration plan, field mapping and content migration with the Migrate API, 301 redirects, SEO parity and a secure switch.

We target Drupal 11: the Migrate Drupal and Migrate Drupal UI modules, used to bring over a Drupal 7 site, are removed from Drupal 12 core (drupal.org). Price: quoted after the audit, as the scope depends on the content model and the features to rebuild.

How an upgrade runs

Each stage produces a deliverable. Tests run in a dedicated environment on our VOID DevOps Platform before anything reaches production.

Stages, deliverables and typical durations of a Drupal 10 to 11 upgrade
StageWhat happensDeliverableTypical duration
0. ScopingAccess, code repository, environments, contacts, constraints (freeze, change advisory board)Project sheet[TO PROVIDE: scoping duration in working days]
1. AuditInventory, Upgrade Status, hosting gapsReport and firm quote[TO PROVIDE: audit duration in working days]
2. Upgrade in testCode, modules and core, in a dedicated environment (DDEV and Docker)Release candidate[TO PROVIDE: duration of the upgrade in the test environment, in weeks, by site profile]
3. AcceptanceCritical journeys, automated tests (Playwright), code analysis (SonarQube), SEO, accessibilityAcceptance report[TO PROVIDE: acceptance testing duration in working days]
4. SwitchAgreed window, backups, rollback readyGo-live[TO PROVIDE: switch window and any downtime, in hours]
5. Warranty, then maintenanceFixes for blocking defects, then maintenance under an SLAEnd-of-warranty report30-day warranty (article 9.1 of our French terms of sale, in French), then as per contract

What is included and what is not

Included

  • Audit and firm quote
  • Move to 10.6, then to Drupal 11
  • Deprecated code fixes and module updates
  • Acceptance testing and a switch with rollback
  • 30-day warranty on blocking defects

Not included, quoted separately

  • Visual redesign
  • New features
  • Rewriting an abandoned module that has no equivalent
  • Change of hosting provider, unless under our AWS managed services

[TO PROVIDE: sign-off of the included and excluded list by VOID sales management]

Meeting the 9 December 2026 deadline

What is still feasible depends on your site and your internal constraints.

  • Up-to-date site, little custom code: the audit will tell you whether the switch can happen before the deadline.
  • Your organisation freezes releases at year end: the switch has to happen before the freeze.
  • You will not be ready: apply plan B (latest 10.6.x release, hardening, a firm date in the first quarter of 2027), detailed in our Drupal 10 end-of-life guide.

Slots available before 9 December 2026: [TO PROVIDE: number of upgrades VOID can still deliver before the deadline, if management wants to show it]

For companies in Europe: a nearshore team in Casablanca

  • A team on Paris working hours: 0 to 1 hour time difference depending on the season.
  • Working languages: [TO PROVIDE: languages in which the VOID team can run meetings, write deliverables and handle support]
  • A representative office in Paris, delivery from Casablanca.
  • Contract and invoicing in euros: [TO PROVIDE: legal entity that contracts and invoices in euros (VOID France or VOID Maroc) and terms]
  • GDPR: acceptance testing on anonymised data. [TO PROVIDE: contractual framework for data transfers (DPA, standard contractual clauses)]
  • Accessibility: non-regression checked against WCAG 2.2 or your national standard.
  • Reversibility: [TO PROVIDE: reversibility clause of the standard contract (timelines, deliverables, conditions)]

French reference: since 2018 we have supported the multisite Drupal portal of Elsan, which federates 140 healthcare facilities. Learn more about our nearshore team in Morocco.

For banks and insurers in Morocco and the region

Change advisory board, release windows, security-approved images, penetration tests: the upgrade fits into your processes.

  • On premises or OpenShift: we support Drupal portals on Red Hat OpenShift for Al Barid Bank since 2020 and Diriddik since 2021. We prepare the PHP 8.3 image with your teams.
  • Change advisory board: change file, switch plan and rollback plan provided.
  • Personal data: acceptance testing on anonymised data, in line with Moroccan law 09-08.
  • Penetration test after the switch: [TO PROVIDE: what VOID offers (test run by VOID, by a partner or by the client's provider)]
  • Invoicing in Moroccan dirhams.

Published Drupal 10 references: the Attijariwafa bank digital hub, designed and maintained since 2018, and the Wafa Assurance portal on headless Drupal 10 with Next.js.

Drupal references

22 of the 24 projects published on our site use Drupal. VOID's Drupal.org profile lists 6 maintained projects and 19 credits.

Elsan group portal displayed on a smartphone

Elsan (France)

Multisite Drupal portal of a French private hospital group, federating 140 healthcare facilities with more than 6 million monthly visitors. Supported since 2018, including SEO.

Crédit Agricole du Maroc portal displayed on a laptop

Crédit Agricole du Maroc

Corrective and evolutive maintenance of the corporate Drupal portal since 2020.

Al Barid Bank portal displayed on a laptop

Al Barid Bank

Product and corporate portal on Drupal and Red Hat OpenShift, with a DevOps approach, since 2020.

Wafa Assurance portal displayed on a laptop

Wafa Assurance

Product and corporate portal on headless Drupal 10 with Next.js, since 2019.

Completed upgrade

[TO PROVIDE: one completed Drupal upgrade or migration: named or anonymised client, versions, duration, any incident, SEO outcome]

What a client says

[TO PROVIDE: approved client quote about a Drupal upgrade, takeover or maintenance, with name and job title]

After the upgrade: maintenance and Drupal 12 readiness

An upgrade does not settle the matter for years. Each Drupal minor release is supported for only one year (drupal.org), and Drupal 12 will require a site on 11.3 or later and PHP 8.5. Our application maintenance service keeps the site on a supported release.

  • Security and minor-release updates, tested before production.
  • SLA by severity: [TO PROVIDE: response and resolution times for P1, P2 and P3 incidents, business hours or 24/7]
  • Maintenance reports drafted by an AI agent in about 5 minutes instead of 2 to 4 hours, always checked by a person.
  • Drupal 12 preparation in 2027, with no rush.

For an overview of our Drupal work, see our Drupal expertise.

Frequently asked questions

What is the difference between a Drupal 10 to 11 upgrade and a Drupal 7 to 11 migration?

An upgrade keeps the site: same content, same URLs, with the code updated through Composer. A migration from Drupal 7 rebuilds the site on Drupal 11 and moves the content with the Migrate API, with 301 redirects. It is a rebuild project.

Can we still upgrade before 9 December 2026?

It depends on your site profile and internal constraints, such as a year-end release freeze. The compatibility audit will tell you. If the date cannot hold, plan B is to stay on the latest 10.6.x release, harden the site and set a firm date in the first quarter of 2027.

How much does a Drupal 11 upgrade cost?

The price depends on modules without a Drupal 11 release, custom code, the theme, integrations and hosting. Starting prices by site profile: [TO PROVIDE: starting prices excluding VAT, in EUR and MAD, for an up-to-date corporate site, a multilingual or multisite portal, a headless or transactional platform]. The firm quote comes out of the audit.

Can you take over a Drupal site built by another vendor?

Yes. We follow four steps: audit of the existing site, knowledge transfer, stabilisation, then ongoing maintenance. We start by securing access, the code repository and verified backups.

Will the site go down during the switch?

The switch happens in a window agreed with you, with a database and files backup and a rollback ready. Any downtime depends on your hosting and data volume: we measure it during the rehearsal in the test environment.

Who handles hosting and PHP 8.3?

If the site is hosted by you or a hosting provider, we send them the prerequisites (PHP 8.3 or 8.4, database version) and check the environment before the switch. If VOID hosts the site on AWS as a managed service: [TO PROVIDE: whether the PHP 8.3 upgrade is included in the upgrade price].

Do you work with companies in Europe?

Yes. Our team works from Casablanca, on Paris working hours (0 to 1 hour time difference depending on the season). Since 2018 we have supported the multisite Drupal portal of Elsan, a French private hospital group that federates 140 healthcare facilities.

What happens after the upgrade?

A 30-day warranty on blocking defects, under article 9.1 of our French terms of sale (void.ma/cgv/, in French). Then, if you wish, maintenance under an SLA keeps the site on a supported minor release and prepares Drupal 12.

Have your Drupal site audited before the deadline

We reply to every request within 24 business hours.