Your Drupal version stopped receiving security fixes. Now what?
A two-week readiness assessment that turns a vague, frightening decision into a costed plan — then the migration itself.
The deadlines that put you here
Start with the assessment, not the quote
Nobody can price a migration honestly without looking inside first. Anyone who quotes a large site over a phone call is either padding heavily or about to have a difficult conversation with you in month three.
So this starts with a fixed-price assessment. At the end you have a document that tells you what the migration involves, what it costs, and what the phases are. If you take that document to a different supplier, that's a legitimate outcome — it's still cheaper than finding out mid-project.
What the assessment covers
- Full module inventory: what's contrib, what's abandoned, what has no successor on the target version
- Custom code audit — the part that actually determines the cost
- Theme and front-end assessment: reuse, rebuild, or redesign
- Content model complexity, entity counts, translation coverage
- Integrations and what breaks when the platform moves
- Accessibility position on the current site, since a migration is the cheapest moment to fix it
- Infrastructure and hosting implications
- A phased path with effort estimates per phase, and what can be deferred
| Deliverable | Written assessment with findings, risks, phased migration plan and costed estimates. Walkthrough call included. |
|---|---|
| Duration | 2–3 weeks from access being granted |
| What I need | Read access to the codebase and a database dump, or a staging environment. No production access required. |
| Then | The migration itself, priced from the assessment. Or your own team executes the plan — both are fine. |
Relevant experience
Seven years carrying a Czech government estate through successive Drupal 8, 9 and 10 upgrades without a rebuild — the continuity is the point. Currently lead developer on an EU agency platform running Drupal 11 with 150+ modules and 500,000+ users, where the legacy Drupal 9/10 codebase had to be stabilised before anything could move.
Earlier: a two-year Drupal 7/8 programme for Czech Radio, still the largest Drupal integration in the Czech Republic.
Tell me your version and your node count
Two numbers and a URL are enough for me to tell you roughly what you're facing. Reply within 24 hours.