Backdrop CMS is worth considering for exactly one situation: a Drupal 7 site that still works, run by people who cannot afford or do not want a full rebuild.
That is a narrower recommendation than most write-ups give it, and it is deliberate. Backdrop is not a Drupal competitor to be argued about; it is a specific answer to a specific budget problem, and it either fits your situation or it plainly does not.
A note on sourcing before we start. I work in Drupal, not Backdrop. Everything below about Drupal is checked against core on my disk. Everything about Backdrop comes from the Backdrop project's own documentation and published case studies, and you should verify current details against backdropcms.org before committing a budget to it.
What Backdrop is
In 2013, a group of Drupal core contributors forked Drupal 7. Their reasoning was that Drupal 8's move to Symfony, object orientation and a service container served large teams well and served small ones badly, and that the Drupal 7 way of working deserved to continue somewhere.
Backdrop keeps Drupal 7's architecture and improves it incrementally. Practically, that means:
- Hook-based extension. A developer who can write a Drupal 7 module can write a Backdrop one. No service container, no plugin discovery, no Symfony.
- In-browser installation and updates. Modules, themes and core update from the admin interface. No Composer, no command line, no build step.
- Common modules folded into core. Views, CKEditor, Token, Pathauto, Redirect and others ship with it, so the dependency hunt that defined a Drupal 7 install largely disappears.
- A Layouts system for building page structures without relying only on theme regions.
- Ordinary PHP hosting. No special server requirements.
The decision, stated plainly
| If this is true of you | Lean |
|---|---|
| The site works and the complaint is only that it is unsupported | Backdrop |
| Nobody on staff uses a command line | Backdrop |
| Heavy investment in custom Drupal 7 PHP you cannot afford to rewrite | Backdrop |
| You need real multilingual with translated configuration | Drupal |
| Something else will consume the content over an API | Drupal |
| You need the widest possible contributed module ecosystem | Drupal |
| The site is an application, not a content site | Drupal |
| You are starting from nothing | Drupal |
That last row matters. Backdrop's whole value proposition is preserving an existing investment. For a greenfield build it offers a smaller ecosystem and a smaller talent pool with no offsetting benefit.
Why it is cheaper, mechanically
The saving is not a discount. It comes from work that does not have to happen.
A Drupal 7 to Drupal 11 move rewrites the custom modules against a different API and rewrites the theme from PHPTemplate to Twig — the full picture is in why that move is a rebuild rather than an upgrade. A Drupal 7 to Backdrop move keeps the hook system and the templating model, so custom code is adapted rather than reimplemented, and editors do not need retraining because the admin interface is recognisably the same.
Aten Design Group has published case studies of Backdrop migrations they carried out for Stanford University and Penn State, both citing cost and timeline advantages over a modern Drupal rebuild. Read them directly rather than through a summary — the details of what each site needed are the part that tells you whether your site is similar.
What you are accepting
Be honest with yourself about the trade, because it is real:
- A much smaller ecosystem. Fewer modules, fewer themes, fewer people who have solved your problem before.
- A smaller hiring pool. Drupal 7 experience transfers, which helps, but "Backdrop developer" is a short list.
- A ceiling. The things Drupal 7 could not do well, Backdrop largely still cannot. If you need them later, you are doing the Drupal rebuild then, at a later date and a higher price.
- A second migration eventually, possibly. Budget for it as a possibility rather than assuming it away.
If you are unsure which side of that line you sit on, the question is worth an hour of someone's time before it is worth a project — that is precisely what an architecture review is for, and it applies whichever platform you end up on.
How to decide in an afternoon
- List every custom module and what it does. If the list is short and the modules are simple, both paths are cheap and Drupal wins on future-proofing. If it is long, Backdrop's saving becomes real money.
- Write down what the site must do in three years. If that list contains an API, an app or a second language, Backdrop is the wrong answer today.
- Name who maintains it. No one? In-browser updates matter enormously and that points at Backdrop. A retained agency? The maintenance argument disappears.
- Get both quotes. The gap is the actual decision, and it is site-specific.
Common questions
Is Backdrop a dead-end fork?
It has been maintained continuously since 2013, which is longer than many commercial platforms last. Check its current release activity yourself rather than trusting anyone's characterisation, including mine.
Can I move from Backdrop to Drupal later?
Content, yes, using the same kind of migration you would have run from Drupal 7. You are deferring the rebuild, not cancelling it, and deferred work is not free.
Will my Drupal 7 contributed modules work?
Not unmodified, but they are ported rather than rewritten because the hook architecture is the same. Many common ones already have Backdrop versions; check for yours specifically before assuming.
Is it secure?
It has its own security team and advisory process. The relevant comparison is not Backdrop against Drupal 11 — it is Backdrop against the unsupported Drupal 7 you are running today, and on that comparison it is unambiguously better.
Does choosing Backdrop mean leaving Drupal?
No. Plenty of organisations run both, and plenty of developers work in both. Matching the tool to the site is not a loyalty test.
Next steps
If your Drupal 7 site is genuinely simple and the rebuild cost is the only obstacle, get a Backdrop quote. If the three-year list has an API or a second language on it, spend the money once and go to Drupal — the wider platform comparison covers where that leads.
Either way, the module inventory is the artefact that decides it. Send me yours and I will tell you which column your site falls in, or start with Drupal services if you already know you are rebuilding.
