Transfer Tool requirements: root SSH access, keys and disk space

For server administrators · Updated 2026-10-29

On this page
  1. On the old server
  2. On this server
  3. Use an SSH key instead of the root password
  4. Security of the stored password
  5. Good to know

The Transfer Tool logs in to the old server as root over SSH, runs that panel's own backup tool there and copies the result here. Check these points before you start.

On the old server

  • cPanel/WHM, DirectAdmin or Plesk is installed. Other servers are refused with No supported control panel found (cPanel/WHM, DirectAdmin or Plesk).
  • Root can log in over SSH (PermitRootLogin allows it). A user with sudo is not enough: the tool connects as root.
  • With a password: password logins must be allowed for root.
  • With a key: this server's public key is in /root/.ssh/authorized_keys (see below).
  • The SSH port is reachable from this server. If the old server has a firewall, allow this server's IP.
  • Free disk space in /root/sahaab-transfer: about the account's size plus 10%, plus 1 GB. The account is packaged there and the archive is removed after it is copied.

On this server

  • Free disk space in /backup: about twice the account's size, plus 1 GB (the archive plus its extraction).
  • The agent is running (systemctl status sahaabd).
  • A license or the trial. After the trial ends, new transfers are paused until the full version is activated.

Use an SSH key instead of the root password

  1. Open Transfer Tool (section Move to this server).
  2. In Key-based access, click Generate SSH key.
  3. Click Copy and add the line to /root/.ssh/authorized_keys on the old server, for example:
echo 'ssh-ed25519 AAAA… [email protected]' >> /root/.ssh/authorized_keys
  1. Under Connect to a server, choose SSH key (add this server's public key on the source) and click Connect & list accounts.

The key is an ed25519 key created on this server; its private part never leaves the server.

Security of the stored password

  • The root password is stored encrypted and only used by the agent; it is passed to SSH through an environment variable, never on a command line.
  • Click Delete password on the server's page when you are done. Do this after the final sync, which needs it.
  • With a key, remove its line from /root/.ssh/authorized_keys on the old server when you are done.

Good to know

  • On the first connection, the old server's host key is accepted and remembered in /etc/sahaab/transfer_known_hosts. If the old server is reinstalled later, its host key changes and the connection is refused; remove its line from that file.
  • Websites, email and accounts on the old server are not changed. The tool uses the temporary folder /root/sahaab-transfer (its logs stay there). On DirectAdmin, the backups are made in /home/admin/admin_backups, and older admin backups of the same user in that folder are deleted first.
Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.