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
Working with Drupal?
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.
What it is
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.
The honest version
No technology is all upside. This is where Drupal earns its place and where it tends to cause trouble.
Sound familiar?
The Drupal problems that bring people to us, and what you have once each one is fixed.
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
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
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
Pinned versions, abandoned contrib modules and patches applied by hand that nobody wrote down. The dependency graph will not resolve.
Composer file cleaned up
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
No render or page cache, Views running unindexed queries, and a database that has never had its slow query log read.
Cached, indexed, measured
Scheduled tasks silently stalled, search index out of date, notifications unsent, and nobody noticed because nothing visibly broke.
Cron running and watched
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
Call us for one stuck migration, or hand us the whole site.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
Estimates are free. Describe what is going wrong and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: