Content management system

Migrating Drupal to static

Drupal sites tend to be older, larger, and built by an agency that disappeared. The maintenance budget vanished long before the site did. The site keeps going because Drupal is admirably stubborn about not breaking.

Migration candidate · €600 flat

What Drupal is

Drupal is a CMS built for institutional sites: structured content types, taxonomy, user roles. When that institutional life stops but the content needs to stay online, static migration is the right exit.

We've migrated parish sites, university department sites, club sites, and small-municipality sites that all share a profile: built around 2014, content updated through ~2018, then frozen because the agency stopped returning calls. They keep running on Drupal 7 because Drupal 7 keeps running.

Drupal's strength — its module ecosystem — is also what makes the hosting expensive: every module is more PHP to execute on every request. When the content stops changing, none of that needs to keep happening. We render the public pages, ignore the admin tree, and ship the result.

What to know before migrating

Drupal 7 is past end-of-life as of January 2025. If you're still on it, you're already in 'static is safer' territory.
Webform module submissions need a static replacement (Cloudflare Forms, Formspree).
Views (dynamic listing pages) get rendered as static pages. If the content changes, we re-render — included in your content updates.
Authenticated areas (logged-in members seeing different content) cannot be migrated. If your site has those, we're not the right fit.

Stays the same

Every URL — Drupal's path aliases are preserved 1:1
Every taxonomy archive page
Every node, every block, every menu
Sitemap.xml, robots.txt, and meta tags exactly as they render today

What changes

No more security updates to chase
No more module compatibility audits
No more 'we should upgrade to Drupal 10' email thread
Hosting cost drops from $30–80/month to €600 once

Our take

Drupal sites are often the best static-migration candidates: structured content, careful URL hygiene, and a maintenance burden that no one wants to keep paying. The output is static-friendly because Drupal was always opinionated about clean output.

Questions

What if my Drupal site is on Drupal 7?

That's a strong reason to migrate now. Drupal 7 reached end-of-life in January 2025, which means no more security patches. Static doesn't have a CMS to patch.

We have a multi-language site with the i18n module. Will it work?

Yes, up to a point. Two languages migrate cleanly. More than two means more redirect QA and is usually a Premium-tier project — see the assessment.

Our Drupal site has 600 pages. Is that too many?

It's at the upper end of the standard plan. Above 500 pages we recommend a custom quote, mostly because the redirect map and image optimization take more attention.

Get an automated assessment

Free. 30 seconds. We'll tell you whether your specific Drupal site is a fit for the standard plan.

Check my site