Fleet Accounts
The Fleet Accounts page lets the hub browse and act on hosting accounts across every connected node from one place. It is also where account migration between AdminBolt nodes is started.
Migration between AdminBolt nodes, not from another panel
The Migrate action on this page moves an account from one AdminBolt node to another under the same hub, and it moves the account configuration only. To bring a cPanel or DirectAdmin server into AdminBolt, with its files, databases, and mailboxes, use bolt-migrate instead - see Migrating to AdminBolt. The two are compared side by side in Migration: which one do you need?.
Overview
URL: /admin/hub/node-accounts - under Cluster → Fleet Accounts
Browse and migrate hosting accounts across fleet nodes.
A Select a node… dropdown at the top chooses which member to inspect - This hub (local) or any connected node. The heading then shows the selected member and its account count (for example, This hub (local) - 1 account).
Accounts table
| Column | Description |
|---|---|
| Username | The hosting account's username. |
| Domain | The account's primary domain. |
| Status | Account state, such as active. |
Row actions
Each account row has two actions:
- Migrate - opens the Migrate account to another node dialog (below).
- Suspend - suspends the account on its current node.
Migrate account to another node
Moves the account configuration (domains, databases, mailboxes, DNS, etc.) to the target node via its panel API, then repoints the cluster DNS. Files, database contents and maildirs are not transferred. The source copy is kept.
The dialog makes the scope explicit: it migrates only the account configuration. It does not copy account content.
What moves: the hosting plan and feature lists, domains (including subdomains and addon domains), databases and database users, mailboxes (accounts, forwarders, autoresponders, and the catch-all), DNS records, SSL, cron jobs, FTP accounts, redirects, error pages, directory privacy, git repositories, mailing lists, IP blocks, and hotlink protection.
What does not move: website files, database contents, and mailbox (maildir) contents. The source copy is kept, so move that data across separately if you need it on the target node.
| Control | Description |
|---|---|
| Target (required) | The destination member. The hub itself can host accounts too. Node roles are shown in brackets. |
| Suspend the account on the source node after a successful migration | Optional checkbox; suspends the original copy once the migration succeeds. |
Click Submit to start the migration (tracked on Account Migrations) or Cancel to close.