WHM's Transfer Tool is the supported choice when an administrator needs to move one or more cPanel accounts between servers. cPanel's migration-script 7.27 release adds an important compatibility fix for account moves from third-party servers running MariaDB 11.4. That removes one known migration obstacle, but it does not replace the normal work of matching the target environment, choosing DNS behavior, and testing the services customers use.
When the MariaDB 11.4 note matters
This release matters when the source is a third-party server using MariaDB 11.4 and the account transfer includes WordPress databases. cPanel changed the migration script to use the MariaDB client rather than the deprecated MySQL client for that source combination. Treat the fix as a reason to bring the destination cPanel & WHM server current before the move, not as a promise that every database, plugin, PHP handler, or application integration will behave the same after cutover.
Decide whether Transfer Tool fits the move
WHM Transfer Tool is designed for administrators who need to copy accounts, packages, and selected configurations from a source server to a destination cPanel & WHM server. It is a different workflow from an individual-account transfer performed with only account-level credentials. Confirm that the team has the appropriate administrative access on both sides before scheduling the work.
Use a documented change owner and maintenance window for customer-facing sites. Do not start a server update while a transfer is in progress, and do not begin a transfer while a server update is already running. Keep the migration focused rather than combining it with unrelated PHP, web-server, cache, or application redesign work.
Prepare the source and destination in WHM
- Compare the environments. Review the source and destination cPanel version, PHP availability, database family and version, web-server components, available capacity, and account package limits. cPanel advises matching the relevant software as closely as practical before a full server migration.
- Map customer services. List the domains, WordPress sites, mailboxes, DNS provider, SSL certificates, scheduled tasks, and any storefront, booking, membership, or form workflows that need a post-transfer check.
- Resolve destination conflicts first. If an account, domain, dedicated IP, or database name already exists on the destination, stop and make the intended ownership decision before the transfer. Avoid overwrite choices unless the change record explicitly covers their effect.
- Choose DNS behavior deliberately. The Transfer Tool can update DNS zones in specific DNS-cluster conditions. Decide who controls authoritative DNS and when the public cutover will happen; do not assume that copying an account changes public traffic by itself.
Run the Transfer Tool through its supported interface
On the destination server, open WHM » Home » Transfers » Transfer Tool. Connect to the approved source server, select the intended cPanel accounts, and review the account settings before copying. The interface lets administrators choose the account data and selected configuration options that belong in the transfer.
Where the server design and DNS topology support it, review whether Live Transfer is appropriate for the move. It can reduce disruption for eligible cPanel-to-cPanel transfers, but it still needs a clear cutover owner and public validation plan. Leave the transfer to complete before starting any other server maintenance.
Validate WordPress, mail, DNS, and account services
- Check the visitor path. Open each transferred site over HTTPS, then test a representative page, login, public form, and the business-critical action such as a cart, checkout, booking, or member area.
- Check the WordPress admin path. Confirm that wp-admin, the active theme, media, and the expected PHP-backed pages load normally. Use the WordPress Support hub if the issue is isolated to one application rather than the server.
- Verify email and DNS separately. Confirm the intended DNS answer, mailbox access, sending behavior, and mail routing. The WordPress migration DNS and email cutover checklist helps teams keep those checks distinct.
- Review account controls. Confirm package limits, dedicated-IP assignments, SSL, and any service configuration selected for the move. cPanel documents that account-level two-factor authentication settings do not transfer, so users who need it must configure it again on the destination.
- Record the result. Keep the transfer outcome, affected customer paths, DNS decision, and any follow-up work in the change record before closing the maintenance window.
Use capacity information before a large move
Account size, file count, and available server capacity can influence the transfer window. The Help4 Disk Usage guide explains how hosting teams can review disk and inode reporting across cPanel, WHM, and WHMCS before scheduling a large account move.
When to pause and escalate
Pause the move when a required service is unavailable, a destination conflict is not understood, public DNS does not match the agreed cutover plan, or a WordPress application does not load after the account copy. Capture the visible symptom and the affected service, then follow the vendor-supported transfer documentation or contact the relevant platform support team. Avoid repeated blind transfer attempts or unplanned configuration changes while the customer path is still unclear.
