What Does It Really Cost to Move Your Website Off Drupal 7?

If your website runs on Drupal 7, here's the short version: that version of the software stopped being supported in January 2025. No more security fixes, no more safety net. So the real question isn't "should I move to the newer version?" — it's "how much is this going to cost me, and what am I actually paying for?"

The honest answer is: it depends on your website. But once you understand what drives the price, it stops feeling like a mystery.

Why you can't just "update" your website

Think of it less like updating an app on your phone, and more like moving from an old house to a brand new one built with completely different materials. The newer version of the software (Drupal 11) was built from the ground up, years after your current site was made. There's no simple button that turns one into the other. Everything — your pages, your design, any special features — has to be carefully rebuilt or moved into the new house.

That's why this kind of project costs more than a typical software update, and also why the price can vary so much from one website to the next.

What actually drives the price

How big and complicated your site is. A simple website with a handful of page types is cheaper to move than a large site with lots of different kinds of content — product pages, staff directories, event listings, and so on. It's not just about how many pages you have, but how many different kinds of pages, and how they're all connected.

Any special features built just for you. If someone built custom tools specifically for your website over the years — a special search feature, a booking system, a members-only area — none of that comes across automatically. It has to be rebuilt for the new version, which takes real development time.

Add-on tools your site depends on. Most Drupal websites use extra plug-in-style tools to add features (similar to apps on a phone). Some of these have modern versions ready to go. Others don't exist anymore and need to be recreated from scratch. Checking this list early is one of the best ways to avoid surprise costs later.

Your website's look and design. The way pages are styled and laid out also has to be rebuilt using the newer system's design approach. This is often a good chance to freshen up your site's look, but it's also a real cost, especially if your current design is old or doesn't work well on phones.

Moving your actual content. Your existing pages, images, and files need to be carefully transferred and checked. Most sites accumulate some mess over the years — old pages nobody remembers, inconsistent formatting — and cleaning that up before the move is usually cheaper than moving the mess and fixing it afterward.

Connections to other tools. If your site talks to other systems — email marketing tools, customer databases, analytics — those connections need to be tested and sometimes rebuilt.

Testing everything. Before launch, everything needs to be checked: forms, search, mobile display, and all your key pages. The bigger and busier your site, the more testing this takes.

Roughly, what should you expect to pay?

These numbers vary a lot by region and complexity, but as a general guide: a simple website often costs in the low tens of thousands of dollars to move. A typical mid-sized business site commonly falls somewhere between $20,000 and $60,000. Larger, highly customized websites can run well over $200,000. Treat any number — including these — as a starting point for a conversation with a developer, not a final quote.

What it costs to do nothing

It's tempting to put this off, but staying on the old, unsupported version has its own hidden costs. Your site is more exposed to security problems. Many modern marketing and business tools are dropping support for the old version, so things may quietly stop working. And teams tend to get noticeably slower at making changes to an old, outdated website compared to a modern one, which adds up in staff time over the year.

A few ways to keep costs down

• Move the essentials first, and add nice-to-have extras after you're up and running.
• Ask your developer about "ready-made building blocks" the new version offers — these can set up common features (like a blog or a basic content workflow) much faster than building everything from scratch.
• Get a clear list of your current pages, features, and add-on tools before asking for quotes. A vague request gets a vague — and often inflated — estimate.

Moving off Drupal 7 isn't optional anymore, but it doesn't have to be a financial mystery. Understanding where the cost actually comes from puts you in a much stronger position going into the conversation with your development team.