Drupal 10 ends December 9, 2026. After that date: no official security patches.
This is not Drupal 7. Same architecture. Same theme. Same content. A typical site takes a week. A site with old contrib or custom code takes two.
You need a senior who has done the jump. Not a six-month project.
⚠ The date is set. Not by us.
Hosts, auditors, and attackers treat unsupported Drupal the same way they treated Drupal 7 after January 2025. Upgrade while you still have runway.
What changes on December 9
The site still loads. The safety net does not.
- No core fixes. New holes get patched in Drupal 11 only.
- Contrib walks. Maintainers follow the supported line. Your lock file ages out.
- Hosts and auditors flag you. An emergency upgrade under a compliance deadline is the expensive version of this work.
How to upgrade
Five steps. Skip one and you pay for it later.
1. Clone production. Run Upgrade Status.
Install Upgrade Status on a clone with real data. That report is the backlog. Do not bump drupal/core until you can sort every error: update, patch, replace, or ignore with a reason.
2. Unblock contrib first.
This is the critical path. Update what has a Drupal 11 release. Patch what is close. If a module is dead: drop the feature, swap the module, or write a thin replacement. Decide now. Not during the freeze.
3. Fix your code on Drupal 10. Then bump core.
Drupal 11 removes APIs that were already deprecated. Clear those on 10 first. The upgrade diff stays small and reviewable.
4. Dry-run twice on staging that matches production.
Same PHP. Same database. Same cache. Composer, database updates, caches. Then smoke-test editors, forms, search, login, and anything that takes money or talks to a CRM. First runs hide one-time surprises. The second run from a fresh dump is the one that counts.
5. Cut over. Watch it for 48 hours.
A short window or a blue/green flip. Warm the cache. Keep the previous build ready so rollback is a deploy, not a rebuild.
How long
| Site | Time | Why |
|---|---|---|
| Current contrib, light custom | About a week | Upgrade Status is clean |
| Old contrib or custom modules | About two weeks | Patches, replacements, editor tests |
| Multi-site, SSO, compliance gates | Longer | Approvals and cutovers, not the core bump |
Still on Drupal 7 or 8? That is a migration, not an upgrade. Read the Drupal 7 end-of-life guide.
What blows a one-week job
- Composer first. Composer tells you what will not install. Upgrade Status tells you what will break after it does.
- Production first. The first run belongs on a clone.
- A generic PHP shop. This is Drupal work: plugins, entities, update paths, config sync. A senior who has shipped 11 finishes in days what a generalist spends weeks rediscovering.
A seat. Not a project.
Most teams do not need an agency contract for this. They need one senior in their repo and their chat for a short window.
SeatADev sells that. US-based Drupal developers, US hours, published day rate from $600. No timesheets. You buy days by the month. Profile and a 30-minute call before you accept. Swap free in month one. Drop the seat when you are on 11.
One date. One job. One seat.
Book one month. The upgrade lands in week one or two. Use the rest for cleanup, or cancel. seatadev.com/drupal-10-end-of-life
Run Upgrade Status on a clone this week. If the report is short, book the window. If it is long, start on contrib — that is the delay, not the version number.
Need a multi-site program or government delivery? Talk to Sympals. We have shipped every Drupal jump since 2011.