The Transfer Tool in cPanel & WHM allows you to copy multiple hosting accounts from a remote server to your current server. To use this tool, you need root-level access on the remote server (with su or sudo privileges), and both servers must be able to communicate over port 2087. This guide walks you through the requirements, warnings, and best practices for successful account transfers.
What You Need Before Starting a Transfer
Before you begin transferring accounts, make sure you have:
- Root-level privileges on the remote server with the su or sudo commands
- Port 2087 access between both servers for communication
- No active system updates running on either server
- DNSSEC records removed from the domain registrar (if applicable)
Critical Warnings Before You Transfer
To avoid data loss or failed transfers, follow these important guidelines:
- Do not shut down or restart any processes on either server during the transfer and restoration process
- Do not start a transfer during a system update (upcp) or start a system update during a transfer, as the system update will fail
- Remove DS records from the domain registrar before transferring domains that use DNSSEC, then re-add them after the transfer completes
- Avoid using skip-name-resolve in your MySQL configuration, as this setting can cause problems during account transfers, especially with remote MySQL servers
How DNS Zones Are Handled During Transfers
When transferring accounts between servers in the same DNS cluster, the Transfer Tool overwrites the target server's existing zone files with the source server's zone files. This happens when both of these conditions are true:
- The target server resides in the same Domain Name System (DNS) cluster as the source server
- The source server uses the Synchronized Changes DNS role
The Transfer Tool does not transfer custom DNS zone templates. If custom DNS zone templates exist on the remote server, the system ignores these templates when it recreates the account on the destination server.
IPv6 and AAAA Records During Transfers
Account transfers process AAAA records (IPv6) differently than A records (IPv4). Here's what happens:
- The target server will not alter AAAA records that point to servers other than the source server or servers related to the source
- A target server without IPv6 enabled will strip locally-managed AAAA records that pointed to the source server
- A target server with IPv6 enabled will point any source-related AAAA record to the account's shared IPv6 address in the domain's locally-managed zone file
Document Root Structure Preservation
In cPanel & WHM version 70 and later, the server disregards the Restrict document roots to public_html Tweak Setting during server transfers. The Transfer Tool retains any pre-transfer public_html directory structures, even those that place addon and subdomain document roots outside of the primary website's document root.
However, after the transfer completes, any new addon domains and subdomains that the restored user creates will follow the current Tweak Settings configuration on the new server.
Best Practices for Smooth Transfers
Follow these tips to ensure your account transfers complete successfully:
- Plan transfers during low-traffic periods to minimize disruption to website visitors
- Verify connectivity between source and target servers before starting
- Check disk space on the target server to ensure it can accommodate all transferred accounts
- Document custom configurations that may not transfer automatically
- Test websites after transfer to confirm all features work correctly
Frequently Asked Questions
What happens if I start a system update during an account transfer?
The system update will fail if you start it during an active transfer. Always wait for transfers to complete before running system updates, and never start a transfer while a system update is in progress.
Will custom DNS zone templates transfer to the new server?
No, the Transfer Tool does not transfer custom DNS zone templates. The system will ignore custom zone templates from the remote server when recreating accounts on the destination server. You'll need to manually recreate any custom DNS zone templates on the new server.
How do I handle DNSSEC-enabled domains during transfers?
You must remove Domain Server (DS) records from the domain registrar before transferring domains that use DNSSEC. After the transfer completes successfully, re-add the DS records to the registrar for the domain to restore DNSSEC functionality.
Will my addon domain document roots change after transfer?
No, existing document root structures are preserved during transfer, even if they're outside the public_html directory. However, any new addon domains or subdomains created after the transfer will follow the current Restrict document roots to public_html setting on the new server.
If you need assistance with account transfers or encounter any issues during the process, the OBHost support team is available 24/7 to help. Visit our contact page or email support@obhost.org for technical support.
