Drupal Upgrade Services: Drupal 8, 9, or 10 to Drupal 11
Drupal upgrade services move your site from Drupal 8, 9, or 10 to Drupal 11 without rebuilding it. Metadrop preserves your content, users, configuration, integrations, and SEO while updating core, contributed modules, custom code, and the underlying PHP and database stack. Delivered by an EU-based, Drupal Silver Certified team with ENS, GDPR, and NIS2 compliance experience.
Book a free Drupal upgrade assessment
EU-based Drupal upgrade experts review your current version, modules, and integrations and return a written upgrade plan within 5 business days.
Why upgrade to Drupal 11: security, compliance, and EOL risk
Drupal 9 and 10 are running out of runway. Drupal 9 reached end of life on November 1, 2023, every site still on it accumulates unpatched CVEs each release cycle. Drupal 10.3 ended support in June 2025; Drupal 10.4 and Drupal 11.1 ends in December 2025. Only Drupal 11.2 (until June 2026) remain under active security coverage, making the Drupal 11 branch the only sustainable path forward.
Corporate Compliance Risk
An unpatched Drupal core is a direct compliance liability under three regulatory regimes:
- GDPR (Art. 32): Classifies unpatched software as a failure to maintain "appropriate technical measures" for data safety.
- NIS2: Mandates that essential and important entities keep all software actively patched and supported.
- ENS (Spanish Esquema Nacional de Seguridad): Requires regulated suppliers to run exclusively hardened, vendor-supported CMS versions.
Drupal 11 is a genuine platform leap, not just a version bump
It ships with Symfony 7, PHP 8.3, CKEditor 5, Single Directory Components (SDC), Recipes, Workspaces, and the Project Browser. Modernizing editorial workflows, simplifying theme architecture, and unlocking the AI-assisted content tooling now mainstream in enterprise CMS deployments.
Performance gains are measurable
A lighter front end, Big Pipe enabled by default, and PHP 8.3 translate into improved TTFB and Core Web Vitals on every production site we have migrated to date.
The compatibility window is closing fast
Contributed modules are rapidly dropping Drupal 9 and 10.3 support — staying on an EOL version means inheriting orphaned modules within months, not years.
The risk of delaying your Drupal upgrade
- No security patches. Every new CVE in core or in a contributed module remains exploitable on your site indefinitely once you fall off supported releases.
- Compliance audit failure. GDPR DPO reviews, NIS2 reporting, ENS recertification, and enterprise procurement questionnaires increasingly flag unsupported CMS versions as a critical finding that blocks renewal or onboarding.
- Module abandonment. Maintainers cut Drupal 9 and early Drupal 10 support as the community moves forward. Your CRM, SSO, search, or commerce integrations may silently break on the next contrib release.
- Hosting incompatibility. PHP 7.x and MySQL 5.7 are end-of-life. Managed hosts including Acquia, Pantheon, and Platform.sh are deprecating the PHP versions that older Drupal cores depend on.
- Rising remediation cost. Each missed minor release adds deprecated APIs and database schema changes. Drupal 9 to Drupal 11 is harder than Drupal 10 to Drupal 11, and the gap widens every month you wait.
- Reputational and operational risk. A publicized breach on an end-of-life platform is hard to defend in front of your board, your customers, and your regulator, especially after the EOL date is a matter of public record.
The Drupal upgrade path: no rebuild, content preserved
Drupal 8, 9, and 10 sites move to Drupal 11 in place. There is no re-platforming, no re-keying of content, and no loss of historic URLs, user accounts, or media library entries. The upgrade is an evolution of the existing site, not a fresh build.
Configuration is preserved across the move. Content types, fields, views, blocks, taxonomies, menus, roles, permissions, and language settings all carry over without manual recreation.
SEO equity is protected throughout the project. URLs, metatags, redirects, canonical settings, hreflang, and XML sitemaps are audited before and after the upgrade, and URL aliases and 301 redirect maps are validated to avoid any loss of organic ranking.
Integrations stay connected. SSO (SAML, OAuth, OpenID), Salesforce, HubSpot, SAP, ERP middleware, payment gateways, Solr and Elasticsearch, and analytics tags are all tested end-to-end on a pre-production environment before release.
The further back your starting point (Drupal 8 compared to Drupal 10.4), the more deprecated APIs and contributed-module replacements are required. Our analysis phase quantifies this work explicitly before any code is written, so the scope and effort are known up front.
Drupal 8 to Drupal 11 upgrade
Drupal 8 reached end of life on November 2, 2021. Sites still on Drupal 8 need a two-step path: first to Drupal 9 (a Composer dependency rebuild plus deprecated API replacement using Drupal Rector), then onward to Drupal 11.
We use Upgrade Status and Drupal Rector to scan custom and contributed code, then patch or rewrite deprecated calls so the codebase becomes compatible with the modern Drupal API surface.
Database schema, files, users, and configuration are migrated in place, there is no data export and re-import cycle, and editors continue working with the same content model they already know.
Drupal 9 to Drupal 11 upgrade
Drupal 9 sites are the most common starting point we see in 2026. The path is Drupal 9 → Drupal 10 → Drupal 11, delivered as two compatible Composer transitions rather than a single jump.
Required updates include the CKEditor 4 → CKEditor 5 migration, the move from Symfony 4 to Symfony 7, jQuery UI removal, and the replacement of deprecated contributed modules, typical examples are major version bumps for Address, Webform, and Paragraphs.
Typical Drupal 9 to Drupal 11 timelines run between 4 and 10 weeks, depending on custom module footprint and integration complexity.
Drupal 10 to Drupal 11 upgrade
Drupal 10 to Drupal 11 is the smoothest path. Most contributed modules are already Drupal 11 compatible, and the deprecation surface is narrow compared to the earlier jumps.
Key technical checks cover PHP 8.3, MySQL 8.0 or MariaDB 10.6, Drush 13, Composer 2.7, and the removal of deprecated APIs flagged by Upgrade Status.
Typical Drupal 10 to Drupal 11 timelines run between 2 and 5 weeks for sites without heavy custom code.
Drupal Core Release Cycle
Drupal 11 ships a new minor release every 6 months, and each minor receives 12 months of security coverage. We recommend planning your upgrade to land at least 3 months before the EOL date of your current minor, so the site never runs uncovered in production.
| Drupal version | Status | Support ends |
|---|---|---|
| Drupal 11.2 | Current recommended | June 2026 |
| Drupal 11.1 | Supported | December 2025 |
| Drupal 10.5 | Supported | June 2026 |
| Drupal 10.4 | Supported | December 2025 |
| Drupal 11.0 | Ended | June 2025 |
| Drupal 10.3 | Ended | June 2025 |
| Drupal 10 (overall) | Ends | December 9, 2026 |
| Drupal 9 | Ended | November 1, 2023 |
| Drupal 8 | Ended | November 2, 2021 |
| Drupal 7 | Ended (see Drupal 7 support page) | January 5, 2025 |
Drupal core release schedule
Our Drupal 11 upgrade roadmap (4-step process)
1. Analysis
The analysis phase delivers a full site audit covering content architecture, custom code, contributed modules, core deprecations, vendor dependencies, and frontend libraries. Nothing is changed in this phase, we only measure.
Automated scanning with Upgrade Status and Drupal Rector quantifies deprecated API usage across the codebase, so the engineering effort is grounded in real numbers rather than estimates.
A module compatibility report follows. It lists which contributed modules are Drupal 11 ready, which need patches, which need replacement, and which can be retired entirely.
We also produce an integration inventory, SSO, CRM, ERP, search, payment, analytics, marketing automation, and DAM. So every external system the site depends on is accounted for before implementation begins.
The phase closes with a written upgrade plan that includes an effort estimate, a risk register, a rollback strategy, and a proposed timeline you can take to your steering committee or budget owner.
2. Implementation
Code actions. We manage core dependencies via Composer, adapt custom modules and themes, patch or fork contributed modules where needed, review vendor dependencies, and remove jQuery UI along with other dropped libraries.
Database and content. Schema updates are run with drush updb, data integrity is verified, and any config splits and language overrides are migrated cleanly.
Server actions. PHP is updated to 8.3, MySQL or MariaDB is brought to the required version, Drush is upgraded to 13 and Composer to 2.7, and web server configuration, opcache, and Redis or Memcache settings are reviewed and tuned.
Editorial. The CKEditor 4 → CKEditor 5 content migration runs as part of implementation, and Single Directory Components are introduced where the theme architecture benefits from them.
3. Testing
Automated testing. Behat covers behavioural tests, BackstopJS handles visual regression, Postman exercises the API surface, and PHPUnit covers custom module logic.
Manual testing. Editors and QA walk through content workflows, multilingual routing, SSO login paths, payment and form submissions, accessibility against WCAG 2.1 AA, and a full SEO check on URL alias maps, metatags, sitemap, and structured data.
Performance baseline. Lighthouse, WebPageTest, and synthetic monitoring run before and after the upgrade to evidence the performance improvements rather than just claim them.
Issue loop. Issues found in testing are fixed, redeployed to staging, and re-tested until the regression list is clean and signed off.
4. Release
The release phase opens with a pre-production deployment dry run using a full data sync from production, so the deployment script is rehearsed against realistic data before it ever runs against the live site.
Pre-production smoke and regression testing then runs on production-equivalent infrastructure to catch any environment-specific issues.
Production deployment happens inside a maintenance window, typically under 30 minutes for sites with a tested deployment pipeline. High-availability sites can be cut over with zero downtime where the architecture supports it.
After go-live we run post-release production testing, real-user monitoring, and error log review, and the upgrade team stays on-call through a 7-day hypercare window.
The project closes with a final compliance, security, and SEO report you can share internally and with auditors.
Talk to a Drupal upgrade expert
Share your current Drupal version, module list, and integrations, you get a written upgrade plan and effort estimate, no commitment required.
Drupal upgrade vs. Drupal migration: what's the difference
A Drupal upgrade moves a site from one Drupal major version to a newer Drupal major version (for example, Drupal 9 to Drupal 11). Content, users, configuration, and integrations are preserved in place, and the existing site continues to operate.
A Drupal migration moves content from a non-Drupal CMS, WordPress, Sitecore, AEM, Joomla, or from Drupal 6 or 7, into a fresh Drupal 10 or 11 instance. It requires schema mapping and the Migrate API. See Migration to Drupal for the dedicated service.
Drupal 7 to Drupal 11 is technically a migration, not an upgrade, because the data model and the upgrade path are different. It uses the Migrate Drupal module and is handled on our Drupal 7 support service page.
Upgrades are typically faster, lower risk, and lower cost than migrations because the data and configuration carry over without re-mapping.
Drupal upgrade + revamp option
A standard upgrade keeps your existing design, information architecture, and editorial model intact. It is the right choice when the version is the only thing that needs to change.
An "upgrade + revamp" pairs the version upgrade with a parallel design refresh, accessibility uplift, SEO restructure, or new feature build. This is the right choice when the editorial or visual layer is also overdue.
We deliver upgrade + revamp as a single project plan rather than two consecutive engagements. The aim is to avoid two separate change windows and reduce total disruption to editors, users, and stakeholders.
Common revamp triggers we see include an outdated visual identity, accessibility gaps against WCAG 2.1 AA, a legacy information architecture that no longer serves the audience, or the chance to introduce SDC and Recipes for faster future iteration.
Why choose Metadrop as your Drupal upgrade partner
- 15+ years of Drupal-only expertise. We are not a generalist agency. Our team has shipped upgrades on every Drupal major release since Drupal 6.
- Drupal Silver Certified Partner with 100+ contributed modules, 500+ open-source contributions on drupal.org, and 50+ talks at DrupalCon and regional Drupal events.
- EU-based delivery, 100% in Spain. GDPR-aligned by default, NIS2-aware, and ENS certified for Spanish public-sector and regulated supplier work.
- Compliance track record across ENS, GDPR, WCAG 2.1 AA, NIS2, and ISO 27001/27002 alignment the credentials required for EU public-sector contracts and enterprise procurement.
- Enterprise client base across regulated and high-traffic sectors: Saint-Gobain, UNICEF, Solvay, Syensqo, Telefónica, Schär, Lyreco, Technip Energies, and World Archery.
- Multilingual and multi-site experience: 30+ languages across 50+ countries. The same governance model scales from single sites to multi-site networks. See Drupal Multisite.
- Independent technical governance. We represent your interests as a strategic partner, not as a vendor selling licences or hosting.
- Transparent reporting. Monthly written reports, a fixed-fee analysis phase, SLAs on response and resolution time, and no surprise change orders.
Client outcomes and proof
Drupal upgrade: frequently asked questions
- How long does a Drupal upgrade take?
Typical Drupal 10 to Drupal 11 upgrades take 2–5 weeks; Drupal 9 to Drupal 11 takes 4–10 weeks; Drupal 8 to Drupal 11 takes 8–16 weeks. Custom module count, integration complexity, and multilingual or multi-site scope are the main drivers. - How much does a Drupal upgrade cost?
Cost depends on starting version, custom code volume, contributed modules in use, integrations, and whether you choose an upgrade-only or upgrade + revamp engagement. We provide a fixed-fee analysis phase first; the implementation quote is firm once the analysis is signed off, with no hidden change orders. - Will my content, users, and SEO be preserved? Yes. The Drupal upgrade path preserves content, users, configuration, URL aliases, metatags, redirects, hreflang, sitemaps, and structured data. We run a full SEO audit before and after release to evidence ranking continuity.
- Will my contributed modules and custom code work on Drupal 11? We scan the codebase with Upgrade Status and Drupal Rector to identify deprecated APIs and module incompatibilities. Where a contributed module is not Drupal 11 ready, we patch it, replace it with a supported alternative, or fold the functionality into a custom module.
- What is the difference between a Drupal upgrade and a Drupal migration? An upgrade moves you between Drupal major versions (Drupal 8, 9, or 10 to Drupal 11) and preserves the existing site. A migration moves content from a different CMS or from Drupal 7 into a fresh Drupal 10 or 11 instance and uses the Migrate API.
- What is the difference between a Drupal upgrade and a Drupal migration? An upgrade moves you between Drupal major versions (Drupal 8, 9, or 10 to Drupal 11) and preserves the existing site. A migration moves content from a different CMS or from Drupal 7 into a fresh Drupal 10 or 11 instance and uses the Migrate API.
- When does Drupal 10 reach end of life? Drupal 10 overall support ends December 9, 2026. Specific minors end earlier 10.3 ended June 2025, 10.4 ends December 2025, and 10.5 ends June 2026.
- Will my site experience downtime during the upgrade? Most upgrades land inside a maintenance window of under 30 minutes using a tested deployment pipeline. High-availability sites can be cut over with zero downtime using blue/green or rolling deployment strategies.
- Can we cancel or pause the project mid-way? Yes. The analysis phase is a fixed-fee deliverable on its own — you keep the upgrade plan even if you do not proceed with implementation. Implementation is broken into milestones, and you can pause at any milestone boundary.
- Do you offer post-upgrade support and maintenance? Yes. Our Drupal maintenance and support service covers proactive monitoring, security patching, contributed-module updates, and evolutive maintenance. A 7-day hypercare window is included with every upgrade.
- Are you Drupal certified? Metadrop is a Drupal Silver Certified Partner with 100+ contributed modules and 500+ open-source contributions on drupal.org.
- Do you handle multilingual and multi-site Drupal upgrades? Yes. We have shipped upgrades for sites in 30+ languages across 50+ countries, including multi-site networks for industrial and NGO clients. See Drupal Multisite.
Get a free Drupal 11 upgrade assessment
Tell us your current Drupal version, hosting, and key integrations. You will receive a written upgrade plan, effort estimate, and risk register within 5 business days. EU-based team, response within 1 business day.