# Find out which Drupal version your website runs — and what it costs to fix. > Type the web address. The version and the date its security updates stopped come back on screen in about five seconds — no email, no form, nothing installed. The fixed price to move it follows on the same screen. Most Drupal websites built more than a few years ago no longer receive security updates. Drupal 7, 8 and 9 are already out of support; Drupal 10 support ends on 9 December 2026. Nothing about an out-of-date website looks different from the outside. It loads, the pages are there, the editors carry on. That is exactly what makes it easy to miss. Drupal 10 support ends 9 December 2026 · Nothing installed, no access needed · No call to book 10+ years on Drupal · Acquia Certified · Warsaw · CET [Check my website — free](https://shandaliuk.dev/drupal-version-check.html) ## 01 — Where your site stands ### Every version has a date. Most have already passed. Security support, as published by drupal.org: | Version | Security updates | |---|---| | Drupal 7 | Stopped — 5 January 2025 | | Drupal 8 | Stopped — 17 November 2021 | | Drupal 9 | Stopped — 1 November 2023 | | Drupal 10 | Stops — 9 December 2026 | | Drupal 11 | Current | A Drupal 10 site cannot move straight to Drupal 12. It has to pass through Drupal 11 first, and Drupal 12 arrives the same week Drupal 10's support ends. Doing both jumps at once, in a hurry, is the expensive way. Not sure which one you have? Send the web address and you get the answer in writing, at no cost. Nothing needs to be installed and nobody needs to give access. ## 02 — What this actually means 1. **Known holes stay open.** When a weakness is found in supported software, a fix is published. When it is found in unsupported software, the weakness is published and the fix is not. 2. **It stops being only an IT problem.** If contact forms, applications or staff logins hold personal information, a break-in is something the organisation has to report, explain and answer for. It also has a name in whatever framework you answer to: GDPR and NIS2 in Europe, SOC 2, HIPAA, PCI DSS or a cyber-insurance renewal in the United States. That is usually how this reaches people — as a question on a form from an auditor or an insurer, and those are the words that release the budget internally. 3. **Ordinary changes get slow and expensive.** A new section, a working search, something that displays properly on a phone — on unsupported software each becomes a negotiation about what will break. 4. **Waiting makes the job bigger, never smaller.** A site left long enough stops being an update and starts being a rebuild. This is not an emergency. It is a known date on a calendar, and the point of knowing about it now is that it can be handled calmly. ## 03 — What you can actually do ### Four options, and only one of them is mine. Moving the site is not the only answer, and anyone who says it is has something to sell. | | Do nothing | Buy extended support | Move to Drupal 11 | Leave Drupal | |---|---|---|---|---| | Who publishes the fixes | Nobody | A commercial vendor writes the patches itself | The Drupal project | Whoever maintains the new platform | | What is covered | Nothing | Core and some modules — not everything your site runs | All of it | All of it | | Cost in year one | €0 | A yearly subscription | €8,000–30,000 once | Usually more than moving inside Drupal | | Cost over three years | €0, plus whatever the risk turns into | Three subscriptions, and the move is still ahead of you | The one payment, plus €150–350 a month if you want it looked after | The one payment, plus retraining your editors | | Links and search rankings | Kept | Kept | Kept — part of the work | At risk | | Your content archive | As it is | As it is | Carried across whole, with its history | Often carried across in part | | What an auditor says | Does not pass | Depends what is being asked — sometimes enough | Passes | Passes | | Where you are in three years | The gap has grown; it is a rebuild now, not a move | Paying for a fourth year, with the same move still to do | Current, and the next step is an ordinary update | On a new platform with an end-of-life date of its own | | Who it suits | A site being retired soon anyway | Anyone who genuinely cannot fit the move into this year | Most organisations | Sites where Drupal really is more than the job needs | **On paying for extended support.** Once a version reaches end of life the Drupal project stops publishing fixes, and certified vendors — HeroDevs and Tag1 Consulting among them — write their own patches and sell them as a subscription. It is a real option and if the move genuinely cannot happen this year, buying a year of it is sensible. Two things it does not do: it covers core and a set of modules rather than everything installed on your particular site, and it buys time without reducing the work. It answers "what do we do now". It does not answer "what do we do next". **On leaving Drupal altogether.** Moving inside Drupal keeps the content structure, the web addresses, the editor accounts and the editors' habits; moving off it rebuilds all four. Where leaving makes sense: if the site is in practice ten pages and a news feed, and none of what makes Drupal worth its weight is being used. If that is your site, that is what the free check will tell you. ## 04 — What it costs There are two prices here because there are two different jobs. A Drupal 10 site needs an update — the software underneath brought current, nothing else touched. A Drupal 7, 8 or 9 site needs a move — it is rebuilt on supported software and the content is carried across. Which of the two your site needs is exactly what the free check tells you. Either way it is one fixed price per project, agreed before it starts — not an hourly rate and not a number that grows once the work is under way. ### A — Drupal 10 → 11: an update, not a rebuild The site stays as it is — the same design, the same content, the same web addresses, the same way your editors work. What changes is the version underneath: core and modules brought up to Drupal 11, code that no longer works updated, everything checked before the switch. | Kind of site | What that usually means | Price | Time | |---|---|---|---| | **Simple** | Built largely out of the box, with little written specially for it. | €1,500–3,000 | 1–2 weeks | | **Typical** | Custom modules, or a theme built for you rather than bought. | €3,000–6,000 | 2–4 weeks | | **Complex** | A lot of code written specially, or connected to systems you already run. | From €6,000 | Scoped individually | Doing this before December 2026 means the later move to Drupal 12 is a small step, not a second rebuild. ### B — Drupal 7, 8 or 9 → 11: a move, with the site live throughout There is no update path from these versions. The site is rebuilt on Drupal 11 alongside the one you have, your content is carried across, and the switch happens at the end. The old site keeps running until it does. | Size of site | What that usually means | Price | Time | |---|---|---|---| | **Small** | Up to around 300 pages, one standard design, nothing plugged into other systems. | €8,000–12,000 | 5–7 weeks | | **Standard** | Roughly 300–2,000 pages, several kinds of page — news, events, staff, documents — and working forms. | €15,000–30,000 | 8–12 weeks | | **Large** | Over 2,000 pages, more than one language, or connected to systems you already run. | From €30,000 | 14–20 weeks | Included: the written plan and fixed price (free, before committing); the rebuild on supported software; all content carried across and checked; every existing web address kept working; the switch outside working hours; a session with the editors and a short written guide; thirty days afterwards for anything missed. Where a site lands between those rows depends on how much of it was built specially rather than out of the box, and on how tidy the content is underneath. Both are things the free look tells you before you decide anything. After either of the two, keeping the site current is optional and priced separately: €150–350 a month. ### If you are reading this from the United States American agencies bill this by the hour — one Drupal-certified partner publishes $155 an hour, adds a quarter again for testing and a fifth for project management, and puts a typical Drupal 7 migration at $39,000 to $54,000. Industry rates run roughly $20–50 an hour in India, $35–75 in Eastern Europe, $60–140 in Western Europe and $80–250 in North America. Warsaw is an Eastern European rate delivered on European working practice, in a time zone that overlaps your morning. The price above is not lower because the work is smaller — it is lower because of where I sit. ## 05 — How the move works ### Four stages, and the site stays live through all of them. The four stages below describe the move from Drupal 7, 8 or 9. A Drupal 10 update runs the same way but shorter: the copy built alongside is your own site on the new version, so there is no content to carry across and the third stage falls away. 1. **A look at what you have** — the version, the size and what it does, then a written plan with one fixed price. Free, and yours to keep either way. 3–5 working days 2. **A new copy, built alongside** — rebuilt on the current version at a private address. Same look, same structure, same menus. 3–4 weeks 3. **Your content moved across** — pages, news, images, documents and accounts carried over and shown to you for review. 2–3 weeks 4. **The switch** — done outside working hours, on the same web address. The old site is kept untouched. One night **What stays exactly as it is:** the content, with its history; every existing web address, so old links keep working; the site's place in search results; and the way the editors work, with one session and a short written guide where something has genuinely changed. Typical time from plan to switch: eight to twelve weeks. The stage times above are for that middle size. ## 06 — Who does the work Serhii Shandaliuk. Over ten years on Drupal websites and nothing else. You deal with me directly from the first email to the switch and after it. 10+ years Drupal · Acquia Certified Developer · Warsaw · CET · English, Ukrainian, Russian drupal.org profile: https://www.drupal.org/u/serhii-shandaliuk ## 07 — Work you can look at ### Three I can name, and the ones I can't. All three are the job this page describes: a site taken off a version that had run out of road and put onto one that has not, with the content, the web addresses and the search rankings intact. One of them was seventy sites at once. The other two were agencies handing over the site they could least afford to have broken: their own. Ten years of work, and most of it went out under an agency's name and stays there — so three are named here and the rest are below without names, with the shape of each job intact. **01 — The largest version move I have done: seventy sites at once.** Imerys is a French industrial minerals group — €3.6bn revenue, listed in Paris, present in more than 40 countries. Its websites, around seventy of them — one per country, per division, per project — were all sitting on the same ageing Drupal, each needing its own updates and each drifting further from the others. Rather than do the same update seventy times, I led the work that brought them onto one current version, with country and language versions handled properly inside it instead of by copying the whole thing again. Everything above had to hold seventy times over: the content carried across, every existing web address still working, the search rankings kept, and every division still able to edit its own pages the morning after the switch. Imerys · 40+ countries · 2022–2025 · as technical lead. **02 — An update done while the version was still current.** AnyforSoft build websites and platforms for education and media — Verifone, Stage Entertainment, Game Informer. Their own site was moved onto Drupal 8 while Drupal 8 was the supported version, and I did the migration work behind it — the same job people now put off for Drupal 10 to 11. Done on time it is unremarkable, which is rather the point. It has since been rebuilt on another platform, so what is on the page is the archived capture: https://web.archive.org/web/20171001183024/https://anyforsoft.com/ · AnyforSoft · 2015–2018. **03 — The same switch, on software that was not Drupal.** Bilberrry is a Seattle agency whose own clients include GoFundMe.org and Business Wire. I moved their site, and not a Drupal one — which is rather the point. Whatever the software underneath, the part of an update that can go wrong is the same every time: the web addresses, the search rankings and the working day, all of which have to survive the switch. All three did. https://bilberrry.com/ · Bilberrry · 2025 —. Anonymised, under NDA — four more of the same job, an old version off and a supported one on, delivered under an agency's name so the names stay out of it. The shape of each does not have to: | Move | Content | Timeline | Outcome | |---|---|---|---| | Drupal 9 → 11 | ~8,000 pages, 3 pieces of custom software | 4 weeks | Old code cleared out; the next version will be a routine update, not another project | | Drupal 9 → 11 | 3,500 pages, feeding a separate front end | 6 weeks | The front end untouched, the connection to it unchanged | | Drupal 8 → 11 | ~40,000 pages, 6 languages | 9 weeks | 14 add-ons replaced, the way editors work unchanged | | Drupal 7 → 10 | ~12,000 pages, 4 pieces of custom software | 11 weeks | Web addresses and search rankings carried across, switched over with no downtime | ## 08 — The free check Send the web address. You get back which version the site runs, whether it still receives security updates, and what moving it would involve — in writing, within one working day. No call to book, no obligation, no follow-up sequence. **What you get, free and in writing:** - Which version your website runs, and the date security updates for it stopped. - One fixed price to bring it current. Not a range you have to interpret, not an hourly rate, not a "from". - A one-page written plan, made to be forwarded — to a budget holder, an auditor or a board. - An answer within one working day, including an honest "yours is fine, do nothing". What is needed from you: the web address. That is the whole list — nothing is installed and no access is required. The version alone, with no email at all, comes back on screen from the [Drupal version checker](https://shandaliuk.dev/drupal-version-check.html). Email: shandalyuk94@gmail.com --- Are you an agency looking for a Drupal subcontractor? See [white-label capacity for agencies](https://shandaliuk.dev/agencies).