Skip to content

Powered by Grav

Backdrop CMS sites

Backdrop CMS sites

Backdrop CMS as a first-class citizen: the same panel tasks as your Drupal sites, automatic caching and cron, and bee — Backdrop's own CLI — next to drush.

Backdrop CMS is the community fork of Drupal 7 — the same content model and admin instincts you know from Drupal 7, kept alive on modern PHP, with the most popular Drupal 7 modules (Views, Date, Entity reference, Redirect and more) built straight into core.

On a BOA instance a Backdrop site is a first-class citizen: it lives on its own Backdrop platform, shows up in your Ægir control panel with the same tasks as your Drupal sites (Verify, Clone, Migrate, Backup, Restore), gets the same automatic caching and cron, and answers to the command line — both to bee, Backdrop's own CLI, and to the drush you already use.

The pages below cover the everyday work, both built-in upgrade paths (Drupal 7 in one task, Drupal 6 in two), and the database conversion task that clears the way for upgrading imported sites.

Good to know

  • bee is to Backdrop what drush is to Drupal — and on BOA you have both. Try bee status next to drush @example.com status.
  • Backdrop stores site configuration as files, not only in the database. Those files live inside your site's private directory and ride along with every backup automatically.
  • Cron just works. The panel triggers Backdrop's secure web cron on schedule; you don't set anything up and you shouldn't add your own crontab entry for it.

© 2026 BOA Documentation. All rights reserved.