Transfer failed or stuck: how to fix a failed migration
On this page
A transfer or import that fails shows failed with the reason. Most failures are about SSH access or disk space, and a retry continues where it stopped.
Symptoms
- The server in the Transfer Tool shows failed and Could not scan the server: with an error.
- An account in the Transfers table, or a line in Migrations, shows failed.
- A transfer stays queued and nothing happens.
Causes and fixes
"Authentication failed (wrong root password, or password logins are disabled on the source server)."
Check the root password. If the old server only accepts keys for root, use SSH key authentication: Generate SSH key and add the line to /root/.ssh/authorized_keys on the old server. Then add the server again.
"Could not connect over SSH." or a timeout
- Check the IP or hostname and the SSH port.
- Allow this server's IP in the old server's firewall.
- Check that root may log in over SSH on the old server.
"Host key verification failed"
The old server was reinstalled and its host key changed. On this server, remove its line from /etc/sahaab/transfer_known_hosts and try again.
"No supported control panel found (cPanel/WHM, DirectAdmin or Plesk)."
The old server does not run one of these panels. For a server running this control panel, see moving accounts between two servers.
"Not enough free disk space on the source server" / "on this server"
The message says how much is needed. Free space in /root/sahaab-transfer on the old server (account size + 10% + 1 GB) or in /backup on this server (twice the account size + 1 GB), then click Retry.
"The source server did not produce a backup archive."
The old panel's backup tool failed. Look at its log in /root/sahaab-transfer on the old server (for cPanel pkgacct-<user>.log), fix the cause, and click Retry.
"The saved password was removed. Re-enter the server credentials."
You clicked Delete password. Add the server again in the Transfer Tool.
"Unrecognized backup: …"
The uploaded archive is not a cPanel, DirectAdmin or panel backup, or it is incomplete. Make a new full backup and upload it again.
"Some statements in … failed" (in the warnings)
Parts of a database could not be imported, often because of features the database server does not support. Check the website; restore the missing parts from the old server if needed.
The transfer stays queued
The page may say The connection task has been waiting … seconds without starting. The agent is not running. On this server run:
systemctl restart sahaabd
Retry
Open the account with Details and click Retry. A retry reuses the archive already copied, so the old server does not package the account again. When the account was already created, the retry repeats only the copy of files, mail and databases.
Still not working?
Open Task Queue on this server, filter Failed, and read the output of the transfer.account, migration.analyze or migration.restore task.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- Transfer Tool requirements: root SSH access, keys and disk space
What the Transfer Tool needs from the old server: root SSH login with a password or key, an open SSH port and enough free disk space on both servers.
- Transfer shows "needs review": username or domain already exists
Why a transferred account waits for review, and how to fix a taken username, an existing domain or a database name before you start the import.
- How to transfer accounts from another server (Transfer Tool)
Connect to a cPanel/WHM, Plesk or DirectAdmin server over SSH, pick the accounts, and copy websites, email, databases, DNS and cron jobs here.
- How to import a cPanel or DirectAdmin backup file
Upload a cpmove or DirectAdmin user backup (or copy a large one to /backup/import), review what is inside and import it as a new account.