drupal alternatives · upgrade, replace or decouple
Drupal 10 stops receiving security releases on 9 December 2026, and Drupal 7 already lost community support on 5 January 2025. Compare six routes, from upgrading Drupal to replacing it, by what your team keeps and what has to be rebuilt.
6 routes to evaluate
Staying on Drupal
Upgrade if Drupal still fits your content model and your team can maintain it. Drupal 10 reaches end of life on 9 December 2026, so the upgrade is the baseline every other route should be compared against.
Budget the upgrade even if you plan to stay.
Read the documentationDrupal 7 sites
Consider Backdrop if your Drupal 7 site works and you want the smallest step. It is a fork of Drupal 7, and its upgrade runs on your existing database, with Views, Pathauto, Redirect and Token shipped in core.
Check every contributed module you rely on.
Read the documentation Keep the content model
Keep Drupal as the content backend. Build a new frontend in Astro or Next.js on top of the core JSON:API module. Editors keep their workflow while you rebuild the public site.
You still run, secure and upgrade Drupal.
Read the documentation
Simpler publishing
Move to WordPress when the site is mostly pages and articles. The FG Drupal to WordPress plugin imports articles, pages, categories, tags and images. It has been tested from Drupal 4 to 11.
Check what the free importer leaves behind.
Read the guide
Custom content models
Shortlist Sanity when your Drupal content model is the valuable asset and you want to redesign the editing experience around it. But you still need to connect visual editing to your frontend.
Scope the Studio, previews and frontend together.
Read the guide
Visual page composition
Shortlist Storyblok when editors build landing pages from reusable blocks and want to see them as they work. Your developers implement those blocks and the preview connection.
Test the blocks your editors actually need.
Read the guideDrupal 7 lost community security support on 5 January 2025. Drupal 10 follows on 9 December 2026, according to the Drupal core release schedule. That is the week Drupal 12 is scheduled for release. 10.6 is the final minor version of Drupal 10.
If you run Drupal 10, you need to decide: upgrade to Drupal 11, or move. If you are still on Drupal 7, the deadline has passed. Your choices are paid extended support, an upgrade or a move.
One change matters for Drupal 7 sites planning to stay on Drupal. The Migrate Drupal module, which imports Drupal 6 and 7 content into modern Drupal, is deprecated in Drupal 11 and removed in Drupal 12. Plan that migration on Drupal 11.
The Drupal Association's extended security support programme lists HeroDevs and Tag1 Consulting as certified Drupal 7 vendors. That cover is useful while you plan a move. As The DropTimes explains, it patches Drupal core and named projects. Your custom code, integrations, hosting and the eventual exit remain your responsibility.
Treat extended support as a fixed-term contract with an end date you choose, and start the migration brief alongside it.
| Route | What you keep | What you rebuild | Fits when |
|---|---|---|---|
| Upgrade to Drupal 11 | Platform, editors' habits, most content types | Custom modules and themes that use removed APIs | Drupal still suits the content model and you have Drupal skills |
| Backdrop CMS | Drupal 7 database and much of its module set | Modules with no Backdrop version | A Drupal 7 site works and you want the smallest step |
| Decoupled Drupal | Content model and editorial workflow | The public frontend, on Astro or Next.js | The backend is sound but the site is slow or hard to redesign |
| WordPress | Pages, articles, taxonomy and media | Custom fields, Views listings and complex workflows | The site is mostly publishing and the team wants simpler editing |
| Sanity or Storyblok | Content, once it is remodelled | Content model, editing interface and frontend | You want a hosted content platform and a modern frontend |
Drupal sites bury their complexity in configuration, not in pages. Before pricing any route, list the following:
Start with a sample that includes the hard cases: reused Paragraphs, translated nodes, filtered Views and embedded media. Let editors review that sample in the destination before anyone estimates the full migration.
Keep upgrading in the mix if Drupal still fits how you model content, your editors work well in it and you can staff the upgrades. Large, structured, multilingual or permission-heavy sites are where Drupal tends to justify its running cost.
Drupal CMS, released on 15 January 2025, packages Drupal with ready-made features for marketing teams. It is worth testing if editing friction, rather than the platform itself, is driving you away.
Bring your Drupal version, the inventory above, a URL export and the integrations the site depends on. Add the editorial tasks the new system must support, and the date you need to be off Drupal 10 or 7.
The outcome should be a recommended route, the work that transfers, the work that is rebuilt, and the conditions for launch. For help with that brief, read about legacy CMS migration or headless CMS development. If WordPress is the destination, the Drupal to WordPress migration guide covers the SEO side.
Drupal 10 reaches end of life on 9 December 2026, the same week Drupal 12 is scheduled for release. After that date there are no more Drupal 10 releases. By then, a Drupal 10 site needs to be on Drupal 11 or on another platform.
Community security support for Drupal 7 ended on 5 January 2025. The Drupal Association lists HeroDevs and Tag1 Consulting as certified providers of paid extended support. That support covers patches for core and named modules, not your custom code, integrations or hosting.
Backdrop runs its upgrade on your Drupal 7 database, so it is the smaller step if the site works and its modules exist for Backdrop. Moving to Drupal 11 is a rebuild with a migration. Plan that move on Drupal 11, because the Migrate Drupal module that imports Drupal 7 content is removed in Drupal 12.
No platform can guarantee that. Export the URL aliases. Decide which pages stay, move or redirect, carry over titles and descriptions, and verify internal links before launch. Put all of this in the migration scope from the start.
I plan and build CMS migrations, including moves off Drupal and upgrades that keep it. That work informs these recommendations. Staying on Drupal is sometimes the right answer. Release dates and product facts come from the documentation linked below. The suitability judgements are my assessment.
from shortlist to plan
Book a 30-minute call and bring your current platform, the website URL and the problem you want solved. We will look at what to keep, what would need rebuilding and whether a migration is worth it at all. The aim is a clear next step: a scoped migration plan, or a reason to improve the setup you already have.