Migrating accounts with the WHM Transfer Tool

Confirm root-level or equivalent authorised access to both servers, a verified backup and sufficient destination space. Compare cPanel versions, database engines, PHP runtimes, extensions, mail configuration and custom software. Inventory external DNS, DNSSEC, cron jobs, remote storage and IP allowlists.

1. Prepare an exact account list and check destination username, domain and database collisions. Resolve existing objects deliberately; do not overwrite an unrelated destination account to make a transfer proceed.
2. Open Transfer Tool on the destination and enter the source server connection details through the supported authentication workflow. Verify the server identity and required network access.
3. Retrieve the available accounts and select a small representative account first. Review the per-account components and options rather than accepting every default blindly.
4. Decide whether Live Transfer fits the migration plan. It can change source-side DNS and service handling, so understand its effects before using it for a staging copy.
5. Review Update DNS Zone carefully. Disabling it can leave destination zones and mail routing uncreated; maintain an explicit manual plan if that is intentional.
6. Start the transfer and monitor both transfer and restoration results. Avoid server updates, reboots or service changes during the operation. Save warnings about skipped data or renamed objects.
7. Test the destination using the real hostnames through a controlled local resolution method. Verify HTTPS, application login, database writes, uploads, mail and scheduled tasks without producing duplicate customer actions.
8. After the pilot succeeds, transfer the remaining approved accounts and execute the separate DNS and mail cutover plan. Keep the source available for the agreed validation period.

Each transferred account should pass functional checks and have documented handling of any skipped or altered component. The destination should also enter its intended backup policy and monitoring system before the source is retired.

If an account fails, use its detailed transfer/restore log to identify the failed stage. Do not repeatedly retry with overwrite options without checking existing destination data. For busy applications, use a write freeze or application-aware final synchronisation so the last source changes are not lost.

Do not assume it can modify an unrelated authoritative provider. Inspect the actual delegation and published records, then make required changes through that provider’s authorised account.

After destination validation, DNS and mail transition, recent-data reconciliation and backup verification are complete. Retain a clear rollback decision point; deleting the source immediately after a copy removes an important recovery option.

• Planning DNS and mail cutover after a WHM transfer
• Configuring WHM backups and retention for the available storage
• Terminating a hosting account after a verified handover
• Choosing which accounts participate in WHM backups

• cPanel: Transfer Tool
• cPanel: Select What To Transfer