Upgrading from Drupal 9: a practical checklist for getting to 10 or 11
By Kawal Kohli · · 6 min read
Good news first. If you're on Drupal 9, you're in a much better spot than anyone still on Drupal 7. Drupal 9 to 10 is an upgrade, not a rebuild. Your content stays where it is. Most of the work is in modules, themes, and custom code.
The less good news: Drupal 9 reached end of life in November 2023. So if you're still on it, you've been running without security fixes for a while. Here's how I approach it.
1. Get Drupal 9 fully up to date first
Before going anywhere, update to the last Drupal 9 release and run all the database updates. Upgrading from an old point release just adds problems you don't need. Same for contributed modules: get each one to its latest Drupal 9 compatible version.
2. Run Upgrade Status
The Upgrade Status module is the best place to start. It scans your site and tells you which modules and themes aren't ready for the next major version, and why. It's not perfect, but it turns a vague worry into a list.
3. Check your PHP version
Drupal 10 needs PHP 8.1 or newer. Drupal 11 needs PHP 8.3 or newer. Check what your host runs, and check whether you can change it. On some older hosting plans this ends up being the slowest part of the whole project, so ask early.
4. Sort out contributed modules
For each contributed module, you'll land in one of three places:
- It has a Drupal 10 compatible release. Update it and move on.
- It's abandoned or replaced. Find what replaced it, or decide you don't need it anymore. You'd be surprised how often that's the answer.
- It was in core and got moved out. Drupal 10 removed a few things from core, including CKEditor 4, Quick Edit, Color, and the Bartik and Seven themes. Those now live in contrib, or have replacements.
CKEditor deserves its own mention. Drupal 10 uses CKEditor 5, and moving from 4 to 5 can change how your editors' content looks, especially if they relied on custom styles or plugins. Test this with real content, not just the homepage.
5. Fix custom code
Custom modules and themes usually need some changes for deprecated APIs. Drupal Rector can fix a good chunk of these automatically. The rest is reading the Upgrade Status report and fixing things by hand. This is where a site with lots of custom code costs more than one built mostly from contrib.
6. Upgrade, test, launch
Do the actual upgrade on a copy of the site, never on production. Update core with Composer, run the database updates, and then test the things that matter: forms, logins, search, anything that takes payments, and every page type editors use. When it's solid, plan a short, quiet launch window.
Can I go straight to Drupal 11?
Not in one jump. You need to be on Drupal 10 first, and on a recent enough 10 release, before Drupal 11 will take the update. But you can plan it as one project. Get to 10, make sure everything is clean, then go to 11 while all the context is still fresh. Drupal 11 also moved more modules out of core, like Forum, Book, and Statistics, so check for those too.
If you're not sure how much work your site needs, that's what the discovery call is for. Thirty minutes, and you'll know roughly where you stand.
