Drupal Migration: Why It’s Time to Upgrade to Drupal 11
Drupal 11 is the current supported major version, and it is the required next step for any site on Drupal 10. Drupal does not support skipping major versions, so waiting for Drupal 12 does not shorten the work. It removes the runway. Drupal 10 reaches end of life on 9 December 2026, the same week Drupal 12 and Drupal 11.5 ship. Here is what Drupal 11 gives you, how the Drupal 12 release affects the decision, and how to run the migration properly.
Key Takeaways
- Drupal does not support skipping majors, so waiting for Drupal 12 removes runway rather than saving work.
- Drupal 12.0.0 and 11.5.0 both ship the week of 7 December 2026, two days before Drupal 10 reaches end of life.
- Drupal 11 requires PHP 8.3 plus MySQL 8.0, MariaDB 10.6, or PostgreSQL 16, which is an infrastructure ticket with its own lead time.
- The deprecated-code scan in Step 3 is the best early predictor of the timeline, and the item that most often doubles an estimate.
If you are running Drupal 7, 9, or 10, you are on a version that has either passed end of life or has a date on it. That is a planning problem rather than an emergency, and the planning gets harder the longer it waits.
Drupal 10 support ends on 9 December 2026, and Drupal 11 is now powering enterprise platforms worldwide. The cost of migrating rises the closer you get to that date, which is exactly why Q4 2026 is the most expensive time to migrate.
What's New in Drupal 11?
Drupal 11 moved the platform onto Symfony 7 and PHP 8.3, and the features built on top of that foundation have matured considerably since the 11.0 release. Four are worth knowing before you scope a migration.
Recipes
Recipes apply predefined configuration in a single step, so a site builder can add a complete capability without assembling it module by module. They are no longer experimental. Recipes are the packaging mechanism behind Drupal CMS, which is how the distribution installs functionality as one-step integrations.
Single-Directory Components (SDC)
SDCs centralize all of a component's code, markup, styles, and behavior in one directory. This makes front-end development more efficient and promotes reuse. Adopting SDC during a migration is the cheapest time to do it, because you are already touching the theme layer.
Project Browser
Project Browser lets you find and install modules from inside the admin UI, with curated recommendations and security flags, rather than through the command line. It ships in Drupal CMS.
Drupal Canvas and Drupal CMS 2.0
Drupal CMS 2.0, released 28 January 2026 and built on Drupal core 11.3, ships Drupal Canvas as the default visual page builder. Canvas reached 1.0 in December 2025 and was developed under the working name Experience Builder. If your migration business case includes giving marketers direct page-building control, this is the capability that carries it.
Drupal 10 vs Drupal 11: What Actually Changes?
The differences fall into two groups: platform requirements you have to satisfy before you can upgrade, and capabilities you get once you have.
| Drupal 10 | Drupal 11 | |
|---|---|---|
| Support status | End of life 9 December 2026 | Current supported major |
| Symfony | Symfony 6 | Symfony 7 |
| Minimum PHP | PHP 8.1 | PHP 8.3 |
| Database minimums | MySQL 5.7.8+, MariaDB 10.3.7+ | MySQL 8.0+, MariaDB 10.6+, PostgreSQL 16+ |
| Recipes | Introduced late in the cycle | Stable, and the basis of Drupal CMS packaging |
| Visual page building | Layout Builder | Drupal Canvas, default in Drupal CMS 2.0 |
| AI module ecosystem | Available, but on a branch heading to EOL | Actively developed against the supported branch |
The database row is the one that most often surprises teams. A hosting environment that was fine for Drupal 10 may need a database upgrade before Drupal 11 will install, and that is an infrastructure ticket rather than a code change.
Why Should You Migrate to Drupal 11?
Four reasons, in the order they usually matter to a technical buyer.
1. A Supported Framework
Drupal 11 is built on Symfony 7 with modern developer tooling, and it is the branch receiving active development. Sites on Drupal 8 or 9 are already past end of life and receive no security coverage. Sites on Drupal 10 lose coverage on 9 December 2026. Adopting PHP 8.3 also brings compatibility with current server environments and better memory behavior.
2. Improved Performance
Dynamic Page Cache optimizations and more efficient asset loading deliver faster response times and better scaling behavior under high traffic. The gain is most visible on sites with many authenticated users, where caching is hardest.
3. Security Posture
Drupal 11 applies stricter deprecation handling and more secure coding practices, which reduces the surface area for vulnerabilities in custom code and third-party integrations. The larger security benefit is simply being on a branch that still receives advisories.
4. Content Authoring Experience
A refined CKEditor 5 interface, drag-and-drop media management, and better content workflows improve the day-to-day experience for non-technical editors. Combined with Drupal Canvas in Drupal CMS 2.0, this is the part of the upgrade your content team will actually notice.
Should You Wait for Drupal 12?
No. Drupal does not support skipping major versions, so a Drupal 10 site cannot upgrade directly to Drupal 12. Drupal 11 is the required step either way, and waiting does not shorten the work.
Drupal 12.0.0 and Drupal 11.5.0 are both scheduled for the week of 7 December 2026, two days before Drupal 10 reaches end of life. Three implications follow from that:
- If you are on Drupal 10, migrate to Drupal 11 now. Waiting until December means doing the same work with no runway and against peak agency demand.
- If you reach Drupal 11 before December, your next step is the 11.5 minor rather than the Drupal 12 major. That is a routine update, not a project.
- If you are on Drupal 7, 8, or 9, this is a rebuild rather than an upgrade and should be scoped separately. Our Drupal 7 migration readiness checklist covers that assessment.
How Do You Migrate to Drupal 11? A Step-by-Step Guide
Seven steps, in order. Steps 1 through 5 are preparation and are where the timeline is actually decided; deprecation debt found in Step 3 is the variable that most often doubles an estimate.
Step 1: Assess Your Current Site
Audit your existing site to inventory installed modules, themes, and custom code, and establish which of those have Drupal 11 support. This assessment determines the scope of everything that follows. If you are starting from Drupal 7, the Drupal 7 migration readiness checklist walks through the evaluation step by step.
Step 2: Update to the Latest Drupal 10 Minor
Drupal 11 requires that you upgrade from a recent Drupal 10 release, so bring the site to the current 10.x minor first. Drupal 10.6.0 is the final minor in the series. Sites sitting on an older 10.x minor are also already outside security coverage for that minor, which makes this step urgent independently of the migration.
Step 3: Check for Deprecated Code
Use the Upgrade Status module to scan custom modules and themes for deprecated API usage. Resolving these before the upgrade is what separates a smooth migration from a long one, and the size of this list is the best early predictor of the overall timeline.
Step 4: Update Contributed Modules and Themes
Bring all contributed projects to Drupal 11-compatible releases. Where a module has no Drupal 11 support and no maintained fork, decide early between a contributed alternative, a custom replacement, or dropping the functionality. Leaving this decision until after the core upgrade is a common cause of slipped timelines.
Step 5: Review Platform Requirements
Drupal 11 requires PHP 8.3 or later and updated database versions: MySQL 8.0+, MariaDB 10.6+, or PostgreSQL 16+. Confirm your hosting environment meets these before scheduling anything. A database version upgrade is an infrastructure change with its own lead time.
Step 6: Perform the Upgrade
With preparation complete, run the upgrade against a staging environment first and follow the official Drupal upgrade documentation. For a distribution-led approach, see our six steps to a Drupal 11 migration with Varbase.
Step 7: Test Thoroughly
Test against real traffic patterns rather than a happy path, paying closest attention to custom functionality and external integrations. Integrations are where post-migration incidents concentrate, because each connected system has its own compatibility assumptions.
How Does Vardot Approach a Drupal 11 Migration?
We start with the assessment in Step 1 rather than with the upgrade, because the audit is what makes the estimate meaningful. Migrations run on the Vardot Delivery System, which begins with Align and Blueprint: scope, dependency health, and measurement agreed before any code moves.
Vardot is a Drupal Diamond Certified Partner with 200+ platforms launched, a 4.9/5 Clutch rating across 58+ verified reviews, standing among the top 20 Drupal contributors worldwide, and Gold Sponsorship of the Drupal AI Initiative. Our Drupal migration practice is built around reducing the number of surprises between Step 1 and Step 7.
Choosing the right team matters as much as the timing. Before you sign with anyone, it is worth working through 10 questions to evaluate a Drupal migration partner.
Find out what your migration actually involves before you scope the budget.
FAQs
Duration depends on the site size and the complexity of the migration; it varies from a few weeks to a few months.
No security patches since January 2025 EOL, vulnerable to attacks. Compliance risks, rising costs, harder to hire developers. Delay increases cost and risk.
Faster performance (Symfony 7, PHP 8.3+), enhanced security with regular patches, and AI-powered content tools. Modern headless capabilities, improved CKEditor 5 editorial experience, and lower long-term maintenance costs.
No. Migrate API preserves all content, users, and configurations. Best practice: full backups, staging tests, and data validation. Experienced consultants ensure zero data loss and minimal downtime.