If your website still runs on Drupal 7, you probably already know it is not ideal.

Maybe your previous agency no longer supports it. Maybe small changes have become difficult. Maybe you have been told that the whole website needs to be rebuilt. Or maybe the site still works well enough, so replacing it has never become urgent.

That is a very common situation.

The important thing is not to panic. But it is also not a good idea to ignore it.

Drupal 7 is now an old platform, and keeping it online without a plan creates risk. That does not always mean you need a big, expensive rebuild tomorrow. It does mean you should understand the current state of the website and make a few practical decisions.

First: find out what you actually have

Many small organisations do not really know what is inside their website anymore.

That is normal. Websites grow over time. Agencies change. People leave. Modules get added. Content piles up. What started as a simple site can slowly become something nobody fully understands.

Before you decide anything, get a clear picture of the basics:

  • Who hosts the website?
  • Who has access?
  • Are backups being made?
  • Can the site be restored if something goes wrong?
  • Which parts of the site are still used?
  • Which forms or features are important?
  • Who updates the content?
  • Are there pages or features that can be removed?
  • Is there a staging version for safe changes?

This does not need to become a huge technical audit. For many smaller sites, even a short review can already make things much clearer.

Do not start with “we need a new website”

A new website may be the right answer. But it should not be the automatic first answer.

Sometimes the best first step is simply to stabilise what you already have. Sometimes it is to remove unused features. Sometimes it is to fix a few important accessibility or usability issues. Sometimes the site is so small that the future version does not need Drupal at all.

The better question is:

What does this website still need to do?

If the answer is “show our services, publish occasional news and let people contact us”, then a lighter website may be enough. If the site has many editors, structured content, permissions, multilingual workflows and integrations, then a more advanced CMS may still make sense.

The goal is not to replace Drupal 7 with the biggest possible new platform. The goal is to choose what fits your organisation now.

Make sure the basics are safe

If the site needs to stay online for a while, start with the boring but important things.

Check that there are reliable backups. Not just “there should be backups somewhere”, but actual backups that can be restored.

Check who has administrator access. Remove accounts from old employees, previous agencies or people who no longer need access.

Check whether your hosting is still maintained. An old website on an old server is a much bigger problem than an old website on a carefully managed environment.

Check whether important forms still work. Contact forms, application forms and donation forms often break silently. Someone should test them regularly.

These actions are not glamorous, but they reduce risk quickly.

Avoid unnecessary new features

If your site is still on Drupal 7, be careful with large new features.

Every new feature adds more complexity to a platform you probably want to leave at some point. That does not mean you cannot change anything. It means you should be selective.

Good temporary changes:

  • Fixing broken pages
  • Improving important forms
  • Making the site easier to use
  • Updating key content
  • Improving accessibility
  • Removing unused features
  • Making the site more stable

Risky temporary changes:

  • Building large new custom functionality
  • Adding many new modules
  • Redesigning everything inside the old theme
  • Creating complex workflows that will soon need to be migrated

For a Drupal 7 site, maintenance should usually be about keeping the site useful and stable while preparing the next step.

Fix the things visitors actually notice

You do not have to fix everything at once.

Start with the pages and features that matter most to users:

  • Homepage
  • Contact page
  • Main service pages
  • Search
  • Navigation
  • Forms
  • Downloads
  • Login pages, if used
  • Important landing pages

Look at these with simple questions: can people find what they need, does the page work on mobile, are forms clear, can the site be used with a keyboard, is the text still accurate and does the site feel trustworthy?

A small amount of focused work can often make an old website much more usable.

Think about accessibility before the rebuild

Some accessibility issues can be fixed now, even on an old Drupal 7 site.

For example:

  • Missing form labels
  • Unclear link text
  • Poor heading structure
  • Low contrast
  • Bad focus styles
  • Inaccessible menus
  • Missing alt text
  • Confusing error messages

You may not be able to make every part perfect, especially if old modules generate poor markup. But you can often improve the most important pages and user journeys.

This is useful even if you plan to migrate later. It helps you understand what the next website should do better.

Decide: maintain, simplify or migrate

For most smaller organisations, there are three realistic options.

Option 1: Maintain for now

This means keeping the current Drupal 7 site online for a limited period, while reducing the most obvious risks. This can make sense if the site is stable, the budget is limited or a larger decision is needed later.

Option 2: Simplify

Sometimes the current website is more complex than the organisation actually needs. Maybe you do not need user roles, complex content types or a large CMS anymore. In that case, the best next step may be a lighter website with fewer moving parts.

Option 3: Migrate

If the site has important content, workflows, integrations or active editing needs, migration to a newer platform may be the right choice. That does not have to mean copying the old site exactly. A migration is a good moment to remove what is no longer needed.

A small practical checklist

If you are responsible for a Drupal 7 website, start here:

  • Make sure backups exist and can be restored
  • Check who has admin access
  • Remove old users
  • Test important forms
  • Check whether the host still supports the site properly
  • List the pages and features that are still important
  • Remove or ignore what is no longer used
  • Fix the most visible usability and accessibility issues
  • Avoid large new features on the old platform
  • Decide whether the next step is maintenance, simplification or migration

You do not need to solve everything in one week. But you do need a plan.

Conclusion

A Drupal 7 website is not automatically a disaster. Many of these sites are still online because they have been useful for a long time.

But it is no longer something you should leave unmanaged.

The practical approach is simple: understand what you have, keep the basics safe, avoid adding unnecessary complexity and decide what the website really needs to become next.

For some organisations, that will be a modern Drupal website. For others, a lighter static website or simpler CMS may be a better fit.

The right answer depends on your content, your team and your budget.