Working with Drupal?

Drupal 7 overdue or site stuck? We fix it.

Most Drupal sites that reach us are two major versions behind, with a dozen contrib modules that never got a Drupal 10 release. We map what is actually in use, then move it, rather than rebuilding everything from zero.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

watchdog

still failing

What it is

Drupal at a glance

Drupal is an open-source content management system, first released in 2001 by Dries Buytaert. It started as a student message board and grew into a framework for building content-heavy sites that need real editorial structure, not just a page here and a post there.

It runs on PHP with a choice of MySQL, MariaDB, PostgreSQL or SQLite behind it. You find it under government sites such as the White House and parts of the Australian government, under large universities, and under publishers with thousands of articles that have to behave consistently. The appeal is structured content; the trade-off is that major version jumps tend to be rewrites rather than updates.

Type
Content management system and content framework
First released
2001
License
GPL version 2 or later, free to use
Built on
PHP with MySQL, MariaDB, PostgreSQL or SQLite
Maintained by
The Drupal Association and a global community of contributors
Typically used for
Large content sites, multi-site networks, government and higher-ed portals

The honest version

Drupal pros and cons

No technology is all upside. This is where Drupal earns its place and where it tends to cause trouble.

Where Drupal is strong

  • Content modelling that holds upFields, entities, taxonomies and references give you a real structure for articles, people, products and events, so the same data can be shown in different ways without being copied.
  • Access control built for institutionsRoles, permissions, editorial workflows and per-field access are part of core. You can put a committee of editors in front of a site without bolting on a plugin.
  • Mature multi-siteDozens of departmental sites can share one codebase and one deployment pipeline, which keeps a university or agency from running dozens of separate WordPress installs.
  • Views, without writing SQLThe Views module lets editors and site builders assemble lists, feeds and pages out of structured content, which is why Drupal is everywhere news and reference material need to be sliced many ways.
  • A real migration frameworkThe Migrate API treats imports as first-class, so moving from Drupal 7, or from another system entirely, is a defined process rather than a one-off script.

Where Drupal bites

  • The learning curve is steepEntities, bundles, view modes, display modes, config sync. A new developer needs weeks before they can change the site without breaking something subtle.
  • Major upgrades are rewritesThe 6 to 7 jump was a rewrite, 7 to 8 was another, and 8, 9, 10 and 11 share a lineage but still need module-by-module work. There is no quiet click-to-upgrade path from Drupal 7.
  • A smaller pool of developersFinding a freelancer who knows Drupal well is harder than finding one for WordPress, and the ones who do know it are usually booked.
  • Thinner module ecosystemThere is a contrib module for most things, but fewer than on WordPress, and older modules often stall at Drupal 7 or 8 with nobody porting them forward.
  • Higher hosting demandsDrupal expects Composer, a real PHP version, enough memory to actually render pages, and often Redis or Memcached in front. Cheap shared hosting is not a good fit.

Sound familiar?

Common Drupal problems we fix

The Drupal problems that bring people to us, and what you have once each one is fixed.

Drupal 7 reached end of life on January 5, 2025

The site is on Drupal 7 and out of support

Community security releases have stopped. Every month the site stays on 7, the list of modules that still have a working Drupal 10 or 11 equivalent gets shorter.

Moved to a supported version

previous agency unreachable

The previous developer walked away mid-upgrade

A half-finished Drupal 9 build sitting next to the live Drupal 7, nobody with Composer access, and a repo that hasn't been touched in a year.

Taken over and finished

The website encountered an unexpected error

The white screen is back

A deploy, a module update or a PHP version bump has left the site throwing the generic error page, and the real message is buried in the logs.

Root cause found and fixed

Composer could not find a matching version

Composer refuses to update core

Pinned versions, abandoned contrib modules and patches applied by hand that nobody wrote down. The dependency graph will not resolve.

Composer file cleaned up

field_data_body missing after migration

Content did not come across cleanly

A migration that ran green but left fields empty, taxonomies detached, or image references pointing at files that are no longer there.

Content reconciled and verified

TTFB 6.1s · LCP 9.4s

The site is slow under normal load

No render or page cache, Views running unindexed queries, and a database that has never had its slow query log read.

Cached, indexed, measured

cron ran successfully 23 days ago

Cron and queues have stopped

Scheduled tasks silently stalled, search index out of date, notifications unsent, and nobody noticed because nothing visibly broke.

Cron running and watched

last tested restore: never

No tested backup exists

Nightly database dumps that may or may not include the files directory, stored on the same server they are meant to protect.

Backups off-server, restores rehearsed

What we do

Drupal help, from rescue to upgrade

Call us for one stuck migration, or hand us the whole site.

Drupal 7 upgrades
Audit of what the site actually uses, a module-by-module plan, and a migration run on a copy before the real one.
Rescue
Down, half-upgraded or abandoned. We get it serving again first and sort out the history second.
Performance
Caching layers, Views and query work, PHP and database tuning, with numbers before and after.
Security and patching
Core and contrib updates applied in a tested order, with a record of what changed.
Custom modules and themes
Module and theme work built the Drupal way, so the next developer can still read it.
Managed Tech
Security advisories applied the day they land, core and contrib updates staged on a copy, verified nightly backups, and a human on the phone when something breaks.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Drupal alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Drupal questions

Something else? Call+1 737 727 7327

Is Drupal 7 still supported?

No. Community support for Drupal 7 ended on January 5, 2025, so there are no more free security releases. A handful of vendors sell extended support contracts, but that is a holding pattern, not a plan. Any Drupal 7 site still in production should be on a path to Drupal 10 or 11.

How much does it cost to upgrade from Drupal 7?

It depends almost entirely on how many contrib and custom modules the site uses and whether equivalents exist for Drupal 10 or 11. A small content site is a few weeks of work; a large one with heavy customisation can be several months. We audit the site first and give you a fixed price before any migration begins.

Should I move off Drupal to WordPress?

Sometimes. If the site is mostly pages and posts and the editorial workflow is simple, WordPress can be a better fit and cheaper to run. If the content is deeply structured, if access control matters, or if you are running a multi-site network, Drupal usually earns its keep. We will tell you plainly which side of that line you are on.

Why is my Drupal site slow?

The common causes are a missing or misconfigured cache, Views querying without useful indexes, a database that has outgrown its default memory settings, and PHP running on an underpowered host. We measure first, then fix the one that is actually costing you seconds.

Can you take over a Drupal site from a previous agency?

Yes, and it is a lot of what we do. We will get credentials and code into your name, audit what is actually running, and give you an honest report on the state of the site before we quote any ongoing work.

How much does Drupal help cost?

Estimates are free. Describe what is going wrong and you get a price before any work starts.

Free estimate

Drupal site giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.