Equivalents from other panels ​
If you administer cPanel and WHM or DirectAdmin today, most of what you do every day exists in AdminBolt under a different name. This section is the lookup table: you bring the script, command, or screen you already know, and you get the AdminBolt counterpart together with the page that documents it.
How to read the tables ​
- They are a selection. Each page covers the commands and screens people ask about most, not every item in either panel.
- Menu paths match the AdminBolt menu. Entries are written as Group > Entry, and tabs as "Page page, Tab tab". A page with no menu entry is marked as such, with the address its documentation gives.
- The command tables answer with a command or a page. A row names a
bolt-clicommand where one exists. "No command" means the job is done in the panel, on the page named right after it, not that it cannot be done. - Modules and licences are marked. [module] is installed separately from Modules; [module + licence] also needs a licence from its vendor. Everything unmarked is part of the panel.
- "No documented equivalent" means AdminBolt has neither a page nor a documented command for that job.
Differences that explain most of the tables ​
Server-wide work has its own pages. Updates, backups, PHP versions and the web server are managed from Settings > System > System Updates, Backups, Settings > PHP > PHP Versions and Web Server. A small set of bolt-cli commands has its own guide under Commands. The generated CLI reference lists what the binary registered in the panel version it was generated from, including internal commands that are not supported for direct use.
Server-level work outside the panel pages is done over SSH. Account owners have an SSH Terminal in the client panel.
An equivalent is not a promise of identical behaviour
The two sides match on purpose, not on implementation. A command or screen with a similar name can cover a different scope, so read the linked page before you run anything on a production server.
Moving a server, not just learning the names ​
Mapping the interface is the last step of a switch, not the first. The tools that move the data are documented separately:
- Migrating to AdminBolt with
bolt-migrate: a whole cPanel or DirectAdmin server becomes an AdminBolt server, run from the source server. - External migrations: selected accounts move from a cPanel or DirectAdmin server into one AdminBolt server, driven from that server's admin panel.
- Migration: which one do you need? if you are not sure which of the two applies to you.