Buy the answer before you buy the upgrade
Drupal 10 → 11 Readiness — the first rung
$1,250 flat · 5 business daysDrupal 10 stops getting security fixes on December 9, 2026. If you’re on 10, this tells you what that means for your site specifically: what’s already D11-ready, what needs a patch, what needs replacing, what the whole thing costs, and how long it takes. One costed page you can hand to whoever signs the cheque.
Upgrade Status and Rector are free and you should absolutely run them — go do that first, honestly. What they can’t tell you is what the blockers actually cost and which of your contrib modules are never getting a D11 release because nobody’s maintaining them. That’s this.
Credits in full toward the upgrade if you start within sixty days. And a real limit: I can take four of these through to a finished upgrade before December 9. After that, the honest advice is a paid extended-support subscription and a calmer schedule in the spring, not a rush job in the last week.
- Best when
- You are on Drupal 10 and December 9, 2026 is on your calendar
- What gets opened
- Every contrib module checked for a D11 release, every deprecation flagged with an effort estimate
- What lands
- A go/no-go and a fixed-price upgrade quote good for 60 days — one costed page for whoever signs the cheque
- Credits toward
- The upgrade, 60 days
The full rung sits with the rest of the ladder on the diagnostics page, and the form at the bottom of this page starts one.
How many sites are in this boat
No more coordinated security releases for 10.x. Roughly 157,000 sites still report running it, and the path to 11 is deprecation cleanup rather than a rebuild.
What each rung costs
Which rung you’re on is decided by the version you’re standing on and how many sites you own — not by how big the project looks. Every fee credits toward the work that follows, so the assessment is free in hindsight if we keep going.
| Rung | Who it’s for | Price | Back in |
|---|---|---|---|
| Drupal 10 → 11 Readiness | You are on Drupal 10 and December 9, 2026 is on your calendar | $1,250 flat | 5 business days |
| Upgrade Assessment — one site | You are on Drupal 7, 8 or 9 and need a real number | $3,500 flat | 10 business days |
| Upgrade Assessment — an estate | Up to five sites, sequenced so a budget owner can read the order | $7,500, then $1,200 a site after five | 10 business days |
| The upgrade itself | You have the assessment and you want it done | Fixed price, quoted by the rung above | Scheduled with you, in writing |
Why a quote and not a range
An upgrade number is set by contrib health, custom code, and data volume — three things nobody can see from the outside. A range published before anyone reads your modules is a guess wearing a suit. The assessment is what turns it into a number you can put in a budget.
What the quote is worth
It’s yours. Take it to your board, to your current agency, or to a shop you like better — the roadmap is written to be read by somebody who isn’t me. If it gets you a fair price from somebody else, it still did its job.
Older branch? Different rung, same road
December 9 isn’t your date — yours already passed, and the site is still up, which tells you something about how much panic the situation deserves. What it needs is the Upgrade Assessment rather than the readiness read: more modules to check, more custom code to price, and 10 business days on the clock instead of 5 business days.
Drupal 7
Passed January 5, 2025
No security team, no coordinated releases — every month is borrowed time. Still running on hundreds of thousands of sites whose owners keep getting quoted rebuild prices as ransom. The migration to modern Drupal is real work, but it is a known road.
Drupal 8 & 9
Both past end of life
The awkward middle: modern architecture, dead branches. The good news is the jump to 10 and 11 from here is far gentler than from 7 — often more housekeeping than surgery.
- Millions
- of nodes migrated D7 → D10, every relationship intact
- 5 → 11
- Drupal versions worked across, since 2013
- 2
- contrib modules maintained on drupal.org
If it still works
Start with the Upgrade Assessment — $3,500 flat for a single site, $7,500 for an estate of up to five. Module by module, a costed roadmap to Drupal 11, and the custom-code risk called honestly. You’re not out here alone, either: the live Drupal 7 census counts six figures still on the old boat, updated from drupal.org on every deploy.
If it’s already on fire
Hacked, broken, or the builder is long gone? Don’t start with an upgrade — start with the rescue practice, which stabilizes what you have before anybody talks about moving it. Then the migration runs on your schedule instead of an attacker’s. Read how a millions-of-nodes migration actually ran if you want the long version first.
What everyone asks first
What everyone asks firstthe follow-ups
What happens to Drupal 10 on December 9, 2026?
Your site keeps running — nothing switches off. What stops is the security team: no more coordinated security releases for the 10.x branch. Every vulnerability disclosed after that date stays open on your site unless you pay somebody for extended support, which is a real option with a real invoice attached.
What does the Drupal 10 to 11 upgrade cost?
The Readiness read is $1,250 flat and comes back in 5 business days with the real number: a fixed-price quote for the upgrade itself, based on your contrib modules and your custom code rather than on a guess. The fee credits in full toward the upgrade if you start within sixty days, and the quote is yours to take to any shop, including not this one.
Can I just run Upgrade Status and skip the assessment?
Please do run it — Upgrade Status and Rector are free, they are good, and they will tell you plenty. What they cannot tell you is what a blocker actually costs to clear, or which of your contrib modules is never getting a Drupal 11 release because nobody is maintaining it any more. That judgment is the part you are buying.
How many upgrades can you actually take before December?
Four, start to finish. One person, a fixed date, and an upgrade measured in weeks — that is the honest arithmetic, and I would rather publish the cap than discover it with you in November. If the calendar has run out by the time you call, the right advice is a paid extended-support subscription and a calmer schedule in the spring, not a rushed migration.
Will we lose content?
The standard here is every record, every relationship, verified — a monolithic Drupal 7 application with millions of nodes has made this exact trip with its data relationships intact. Migrations run against copies, verify against counts, and never touch the live site until the numbers match.
How long does a Drupal 7 migration take?
A modest site is weeks, not months. The one we can speak to first-person: a monolithic D7 application with millions of nodes ran as incremental migrations alongside the live site for months, with a final cutover measured in minutes because delta runs had rehearsed it for weeks. The assessment turns "it depends" into a date.
Can we stay on Drupal 7 a bit longer?
You can — with eyes open. Stabilization first: hardening, monitoring, and proven backups through the rescue practice, then the migration on your schedule instead of an attacker’s. What you cannot do safely is nothing.
Anything else, ask it in the form below or on the contact page — and the whole price list, every plan and every diagnostic, lives on the services page.
Find out what you’re actually facing
The URL, the Drupal version if you know it, and anything you already suspect. You’ll get a real answer within one business day — including when the real answer is that your situation is calmer than it feels, or that the date is far enough out that spring is the better time to do this.
Signal received
Your message is in a human inbox. Expect a reply from Dane within one business day.