A major upgrade is looming
Moving between major versions means rewriting custom code, themes, and modules, often at rebuild cost.
Leaving Drupal? Here’s where to go.
Major Drupal upgrades are projects in their own right. If you’re facing one, it’s the right moment to ask whether the next version of the site should be on Drupal at all.
Should you move off Drupal?
If your content is complex, structured, or used beyond the website, move to a headless CMS such as Sanity or Contentful with an Astro frontend. If the site is mainly marketing content and editors want a simpler experience, move to Astro with a visual CMS.
If you have an experienced Drupal team, rely on complex permissions and workflows, and the upgrade path is well understood, staying on Drupal is a legitimate choice.
Signs it’s time to leave Drupal.
Drupal talent is hard to find
Hiring or contracting experienced Drupal developers is getting harder and more expensive.
Editors find it hard to use
The admin experience slows publishing and needs training to use well.
Custom modules have become a risk
Business logic lives in code few people understand and fewer want to maintain.
Hosting and security take real effort
Keeping the stack patched, scaled, and secure is an ongoing operational cost.
Where Drupal teams usually go.
Drupal sites tend to carry complex content, so most land on a headless architecture that keeps that structure while simplifying everything around it.
| Option | Best for | Who edits content | Watch out for |
|---|---|---|---|
| Astro with a visual CMS | Content-heavy or performance-critical sites with custom integrations | Marketing, in the CMS; developers own templates and components | New templates need a developer |
| Headless CMS (Sanity or Contentful) | Content reused across the website, product, and other channels | Editors, in structured content models | More architecture to plan before you build |
Option
Astro with a visual CMS
- Best for
- Content-heavy or performance-critical sites with custom integrations
- Who edits content
- Marketing, in the CMS; developers own templates and components
- Watch out for
- New templates need a developer
Option
Headless CMS (Sanity or Contentful)
- Best for
- Content reused across the website, product, and other channels
- Who edits content
- Editors, in structured content models
- Watch out for
- More architecture to plan before you build
Stay on Drupal, or go?
Not every site needs to move. Here’s the honest version.
Leaving Drupal makes sense when
- An upgrade would cost as much as a rebuild
- You struggle to find or keep Drupal developers
- Editors want a simpler publishing experience
- Content needs to reach channels beyond the site
- You want to reduce hosting and security overhead
Staying on Drupal is fine when
- You have a strong in-house Drupal team
- You depend on complex roles, permissions, and workflows
- The site is already on a current major version
- Integrations are deeply tied to Drupal modules
- The upgrade path is clear and budgeted
What comes with you.
Content types, fields, taxonomies, users, and media are mapped to new content models, with governance and workflows rebuilt in the new CMS.
- Content types, fields, and taxonomies
- URLs, with a tested 301 redirect map
- Editorial roles and publishing workflows
- Titles, descriptions, and structured data
- Integrations and single sign-on
- Media libraries, re-optimised
Leaving a different platform?
Leaving Gatsby
Gatsby’s momentum has stalled since Netlify’s acquisition and the Gatsby Cloud shutdown. Compare moving to Astro, Framer, or Next.js, and see when staying makes sense.
Read the guideLeaving HubSpot CMS
Want to move your website off HubSpot CMS but keep HubSpot CRM? Compare Framer and Astro, and see when staying on HubSpot CMS is the better call.
Read the guideLovable to Production
Your Lovable app works and people are starting to rely on it. Here's how to tell when it needs a production rebuild, what we keep, and how the move works.
Read the guide
Leaving Drupal: common questions.
Should we upgrade Drupal or migrate to another platform?
If an upgrade means rewriting most custom code and themes, compare it with a rebuild on a modern stack. Many teams find the cost is similar and the result is easier to run.
What is the best alternative to Drupal?
For complex, structured content, a headless CMS such as Sanity or Contentful with an Astro frontend. For marketing-led sites, Astro with a visual CMS.
Is Drupal 7 still supported?
No. Drupal 7 reached end of life in January 2025, so sites still running it no longer receive community security updates.
Can a headless CMS handle our Drupal content model?
Yes. Content types, fields, references, and taxonomies map well to structured content in Sanity or Contentful, often more cleanly than in the original.
How long does a Drupal migration take?
Most take twelve to twenty weeks, depending on content volume, integrations, and editorial workflows. We scope it after a discovery audit.