Serhii Shandaliuk / Senior Drupal

Drupal migration & long-term support · Warsaw · CET

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 a second — no email, no form, nothing installed. The fixed price to move it follows on the same screen.

  • Drupal 10 support ends 9 December 2026
  • Nothing installed, no access needed
  • No call to book

01 — Where your site stands

Every version has a date. Most have already passed.

Drupal is the software your website is built on. Each version is looked after by its makers for a fixed number of years, and then it is not. These are the published dates.

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

If your website was built before about 2021, it is most likely on one of the first three rows. If it was rebuilt more recently, it is probably on Drupal 10 — which has a date of its own, and one more catch: 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.

Find out which version I run

Not sure which row you are on? That is the free check, and it is the whole answer you need before deciding anything.

02 — What this actually means

Four things, none of them technical.

  1. Known holes stay open

    When a weakness is found in supported software, a fix is published and every site applies it. When it is found in unsupported software, the weakness is published and the fix is not. The list of affected sites is public knowledge, and yours is on it for as long as it stays where it is.

  2. It stops being only an IT problem

    Contact forms, applications, registrations, staff logins — if any of it holds personal information, a break-in is something your organisation has to report, explain and answer for. That conversation happens at board level, not in the web team.

    It also has a name in whatever framework you are answerable to. Running software that no longer receives security fixes is something you can be asked about under GDPR and NIS2 in Europe, and under SOC 2, HIPAA, PCI DSS or a cyber-insurance renewal in the United States. That is usually how this reaches people: not as a technical worry, but as a question on a form from an auditor, an insurer or a parent organisation — and those are the words that release the budget internally.

  3. Ordinary changes get slow and expensive

    A new section, a new form, a working search, something that has to display properly on a phone. On current software these are small jobs. On software nobody supports any more, each one turns into a negotiation about what will break — and quotes rise to match.

  4. Waiting makes the job bigger, never smaller

    The distance between where your site is and where it needs to be only grows. A site left long enough stops being an update and starts being a rebuild, and the difference between those two words is most of the budget.

Check where my site stands

None of the four is urgent this week. All four get more expensive the longer the site sits where it is.

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 tells you it is has something to sell. There are four, they are all legitimate in some circumstance, and the differences between them are the same handful of practical questions.

The four routes open to a site on an unsupported version
  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 — that is 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

It is a real option and it is worth knowing about. Once a version reaches the end of its life the Drupal project stops publishing fixes, and a handful of certified vendors — HeroDevs and Tag1 Consulting among them — write their own patches and sell them as a subscription. If your site is on Drupal 7 and the move genuinely cannot happen this year, buying a year of that is a sensible thing to do, and I will say so.

Two things it does not do. It covers core and a set of modules, not everything installed on your particular site. And it buys time without reducing the work: the migration you are postponing is the same size in twelve months, at a slightly higher price, having paid a year's subscription for the privilege. It answers “what do we do now”. It does not answer “what do we do next”.

And on leaving Drupal altogether

Also a fair question, and one nobody in my position asks out loud because the honest answer is sometimes yes. It comes down to how much of the site there is.

Moving inside Drupal against moving off it
  Drupal 7/8/9/10 → 11 Onto a different platform
How your content is structured Moved by the platform's own tools Rebuilt by hand
Web addresses Kept exactly as they are Change; every one needs a redirect
Editor accounts and permissions Carried across Set up again from scratch
What your editors have to learn Almost nothing — the screens are recognisable A new system, from the beginning
Complicated page types Move across Often simplified or dropped

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 actually being used. If that is your site, that is what the free check will tell you — and you can take that answer to somebody who builds on something simpler.

Find out which of the four applies

The check says which version you are on and what the move would cost. What you do with that is your call, and one of the four answers is “nothing yet”.

04 — What it costs

One fixed price per project, agreed before it starts.

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 number, not an hourly rate you have to watch and not a figure that grows once the work is under way. If the scope changes because you ask for something new, you are told what it costs before it is done.

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.

Drupal 10 → 11 · fixed price, agreed before anything starts
Kind of site What that usually means Price
Simple1–2 weeks Built largely out of the box, with little written specially for it. €1,500–3,000
Typical2–4 weeks Custom modules, or a theme built for you rather than bought. €3,000–6,000
Complexscoped individually A lot of code written specially, or connected to systems you already run. From €6,000

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.

Drupal 7, 8 or 9 → 11 · fixed price, agreed before anything starts
Size of site What that usually means Price
Small5–7 weeks Up to around 300 pages, one standard design, nothing plugged into other systems. Most non-profits and smaller offices sit here. €8,000–12,000
Standard8–12 weeks Roughly 300 to 2,000 pages, several kinds of page — news, events, staff, documents — and working forms. The usual shape for a council or a faculty. €15,000–30,000
Large14–20 weeks Over 2,000 pages, more than one language, or connected to systems you already run — a payment provider, a register, a booking tool. From €30,000
  • The written plan and the fixed price — free, before you commit to anything.
  • The rebuild on current, supported software.
  • All of your content carried across and checked.
  • Every existing web address kept working.
  • The switch itself, done outside working hours.
  • A session with your editors and a short written guide.
  • Thirty days after the switch, for anything that turns out to be 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 — and if your site turns out to sit between two rows, you are told which one it is being priced as and why.

If you are reading this from the United States

The same work is priced very differently depending on where the invoice comes from. 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. Rates across the industry 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. That is the whole of the arbitrage, and it is worth being blunt about it: the price above is not lower because the work is smaller. It is lower because of where I sit.

Get my fixed price — free

The free check says which of the two your site needs, and turns the range into one number for it, before you commit to anything.

05 — How the move works

Four stages, and your site stays live through all of them.

The current website keeps running exactly as it does now until the last step. Nothing is switched off, and there is no period where visitors see a holding page.

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

    I read the site from the outside, work out the version, the size and what it does, and send back a written plan with one fixed price. Free, and yours to keep whether or not you go ahead.

    3–5 working days

  2. A new copy, built alongside

    The site is rebuilt on the current version at a private address only you and I can reach. Same look, same structure, same menus — on software that is supported again.

    3–4 weeks

  3. Your content moved across

    Pages, news, images, documents and people’s accounts are carried over, checked, and shown to you on the private copy. You go through it and say what is wrong while it costs nothing to change.

    2–3 weeks

  4. The switch

    Done outside working hours. The new site takes over the same web address; the old one is kept, untouched, in case anything needs checking against it. Visitors notice nothing.

    One night

What stays exactly as it is:

  • Your content. Every page, article, image and document, with its history — not retyped, not summarised, not “most of it”.
  • Your web addresses. Every link that works today still works afterwards: printed leaflets, other people’s links, bookmarks, the address in someone’s email signature from 2019.
  • Your place in search results. Rankings follow the addresses. Keeping the addresses intact is what protects the traffic, and it is planned at the start rather than repaired at the end.
  • How your editors work. The people who add news and update pages should recognise what they see. Where something has genuinely changed, they get shown it — one session, plus a short written guide.
Start with the free check

Eight to twelve weeks, and it starts with a written plan that costs nothing.

06 — Who does the work

One person, ten years on this one thing.

I am Serhii Shandaliuk. I have worked on Drupal websites for over ten years and nothing else — no other platform, no other speciality. You deal with me directly from the first email to the switch and after it; there is no account manager in between, and nobody hands your project to someone junior once it is signed.

My drupal.org profile ↗ shandalyuk94@gmail.com

  • 10+ years Drupal
  • Acquia Certified Developer
  • Warsaw · CET
  • English · Ukrainian · Russian

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.

  1. Homepage of the consolidated Imerys website, showing the global navigation and search that replaced roughly seventy separate sites.
    imerys.com — the single site, on a current version

    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 the country and language versions handled properly inside it instead of by copying the whole thing again. Everything described further up this page 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
  1. The AnyforSoft homepage as archived in 2017, headlined ‘Drupal 8 web and mobile apps development team’.
    anyforsoft.com — archived 2017, the Drupal 8 build

    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 you see here is the archived capture.

    AnyforSoft · 2015–2018 · See the archived build ↗
  2. The Bilberrry homepage, showing client logos including Business Wire, GoFundMe.org, Deloitte, MIT and Delta.
    bilberrry.com — live

    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.

    Bilberrry · 2025 — · bilberrry.com ↗

Anonymised, under NDA

Four more of the same job — an old version off, 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.

  1. Drupal 9 → Drupal 11
    Content
    ~8,000 pages, 3 pieces of custom software
    Timeline
    4 weeks
    Outcome
    Old code cleared out; the next version will be a routine update, not another project
  2. Drupal 9 → Drupal 11
    Content
    3,500 pages, feeding a separate front end
    Timeline
    6 weeks
    Outcome
    The front end untouched, the connection to it unchanged
  3. Drupal 8 → Drupal 11
    Content
    ~40,000 pages, 6 languages
    Timeline
    9 weeks
    Outcome
    14 add-ons replaced, the way editors work unchanged
  4. Drupal 7 → Drupal 10
    Content
    ~12,000 pages, 4 pieces of custom software
    Timeline
    11 weeks
    Outcome
    Web addresses and search rankings carried across, switched over with no downtime

08 — The free check

Send the web address. That is all it takes.

You get back which version your website 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 I need from you: the web address. That is the whole list — nothing is installed and no access is required.

The only thing I genuinely need. Nothing is installed and no access is required.

Only have one question? Ask it in one sentence — answered within the working day, no check, no thread.

Or email shandalyuk94@gmail.com Replies within one working day, Warsaw time Ten years of it, on drupal.org ↗

The same offer, written for the sector you are in:

Universities and colleges ↗ Non-profits and foundations ↗ Agencies needing a subcontractor ↗
Free · in writing · 1 day Check my website