How to transfer accounts from another server (Transfer Tool)
On this page
The Transfer Tool connects to your old server over SSH as root, lists its accounts and copies the ones you choose. It works with cPanel/WHM, DirectAdmin and Plesk. The old server is not changed.
Before you start
- Root SSH access to the old server, with its root password or an SSH key. See what the Transfer Tool needs.
- Packages on this server for your old plans (the Transfer Tool can match them by plan name).
- Free disk space on both servers.
Step 1: Connect to the old server
- Log in to the administrator panel (
https://<server>:2087). - Open Transfer Tool in the menu (section Move to this server).
- Under Connect to a server, enter the Server IP or hostname (for example
203.0.113.10) and the SSH port (22by default). - Choose the Authentication:
- Root password — enter it in Root password. It is stored encrypted and only used by the agent.
- SSH key (add this server's public key on the source) — in Key-based access, click Generate SSH key, click Copy and add the line to
/root/.ssh/authorized_keyson the old server.
- Click Connect & list accounts.
The page says Connecting and listing accounts… this page refreshes automatically. The server appears in the Servers table with the detected panel. Click Open if you left the page.
Step 2: Choose the accounts
The list Accounts on … shows each account with its Domain, Plan and Disk use.
- Tick the accounts to move, or tick the box in the header to select all.
- suspended — the account is suspended on the old server. It stays suspended here.
- exists here — the same username or domain already exists on this server. The account will wait for your review.
Step 3: Choose the options
- Package for transferred accounts — Match the source plan name (fallback: default), or one package for all.
- Import automatically when there are no conflicts — leave ticked to import at once; untick to review each account first.
- Point DNS A records to this server — A records with the old server's IP get this server's IP.
- What to transfer — Website files, Email accounts & mail, MySQL databases, DNS zones, Cron jobs.
Click Transfer selected accounts and confirm.
Step 4: Follow the progress
The Transfers table shows each account and refreshes by itself:
| Status | Meaning |
|---|---|
| queued | Waiting its turn |
| transferring | Being packaged on the old server and copied here |
| analyzing | The archive is being read |
| importing | Files, mail and databases are being copied into the new account |
| needs review | Something needs your decision; click Review |
| done | Imported; Imported as links to the new account |
| failed | Click Details to read the error and Retry |
See needs review and transfer failed.
Step 5: Before and after switching DNS
- Run the final sync to copy what changed since the transfer.
- Verify the websites.
- Switch DNS.
- When everything is moved, click Delete password on the server page (or remove the key line from the old server).
Good to know
- Accounts are moved one after another. On cPanel, packaging runs at the lowest priority so the old server's live websites are not slowed down much.
- While an account is being transferred, other tasks of this server (for example creating an account) wait until it is finished. Plan large transfers for a quiet time.
- Click Rescan to list the old server's accounts again, for example after new accounts were created there.
- Delete the stored password only after the final sync: the sync needs it.
- You can also add the source on the command line:
sahaab transfer:add 203.0.113.10, or during installation with--migrate-from=203.0.113.10.
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 run the final sync before switching DNS
Copy only what changed on the old server since the transfer — new files, new email and fresh databases — just before you point the domains here.
- Transfer failed or stuck: how to fix a failed migration
Fix common Transfer Tool and backup import errors: SSH connection or authentication failed, not enough disk space, unrecognized backup, stuck tasks.