Drupal 11 was released in August 2024, and moving from Drupal 10 is an upgrade, not a rebuild. Drupal's continuous-upgrade model means the work is mostly about removing deprecated code and meeting new platform requirements. Done in the right order, it is predictable.
Step 1: Meet the platform requirements
| Component | Drupal 11 minimum |
|---|---|
| PHP | 8.3 |
| MySQL / MariaDB | 8.0 / 10.6 |
| PostgreSQL | 16 |
| SQLite | 3.45 |
| Drush | 13 |
Upgrade PHP and the database on Drupal 10 first, deploy, and let it run in production. Changing one thing at a time makes problems easy to isolate.
Step 2: Get to the latest Drupal 10 minor
You must be on Drupal 10.3 or later before moving to 11, and it is best to be on the newest 10.x release with all database updates applied.
Step 3: Scan with Upgrade Status
composer require --dev drupal/upgrade_status
drush en upgrade_status -y
drush upgrade_status:analyze --all
Upgrade Status reports deprecated API use in custom code, contrib projects without a Drupal 11 release, and environment issues, all in one place.
Step 4: Fix custom code (let Rector do the boring part)
Drupal Rector automatically rewrites many deprecated calls:
composer require --dev palantirnet/drupal-rector
cp vendor/palantirnet/drupal-rector/rector.php .
vendor/bin/rector process web/modules/custom --dry-run
vendor/bin/rector process web/modules/custom
Then update each custom module and theme's .info.yml:
core_version_requirement: ^10.3 || ^11
Step 5: Handle modules removed from core
Several rarely used modules were deprecated during Drupal 10 and removed from core in Drupal 11, including Actions UI, Activity Tracker, Book, Forum, Statistics and Tour. If you use any of them, install the contributed project version while still on Drupal 10, then upgrade core.
Step 6: Check contributed projects
For each contrib module, update to a release that supports both 10 and 11. If one is not ready, check its issue queue for a compatibility patch, consider an alternative, or contribute the fix. Remove modules you no longer use; every one removed is one less to upgrade.
Step 7: Upgrade core with Composer
composer require 'drupal/core-recommended:^11' \
'drupal/core-composer-scaffold:^11' \
'drupal/core-project-message:^11' --no-update
composer update --with-all-dependencies
drush updatedb -y
drush cache:rebuild
If you use drupal/core-dev, require ^11 for it as well.
Step 8: Verify before go-live
- Run automated tests and a visual regression pass on key templates.
- Check the status report and recent log messages for warnings.
- Test editorial workflows, forms, search and integrations end to end.
- Compare performance (TTFB, Core Web Vitals) before and after.
Typical effort
A well-maintained site with modest custom code is often a matter of days. Sites with heavy custom modules, unmaintained contrib or outdated hosting take longer, and the code scan in Step 3 is where you find out. Next, read our guide to preparing for Drupal 12 so the next upgrade is even easier, or ask our team to run the assessment for you.