DirectAdmin-to-DirectAdmin Account Migration: Safe Backup Workflow

Moving an account between DirectAdmin installations is different from cloning an entire server. Use supported account backups and a deliberate restore plan; do not copy all of a server’s home directories over an existing destination as a routine final step.

InterServer’s complimentary service covers DirectAdmin-to-DirectAdmin and cPanel-to-cPanel on web hosting plans only. VPS and dedicated-server migrations are not offered. A server-owner transfer is self-managed or work for your own administrator. See the hosting migration policy.

Inventory the accounts and destination

Confirm administrative permissions on both installations, account ownership, usernames, domains, packages, quotas and required software versions. Identify existing destination accounts and domain conflicts before restoring. Record websites, databases, mailboxes and any server-level services that account archives do not capture.

Create complete account archives

Use DirectAdmin’s Admin Backup/Transfer interface for the intended accounts, with all required account data selected. Review the destination path and wait for successful completion. Keep a private verified copy and an account-to-archive inventory.

Do not enable skip_domains_in_backups=1 merely to prepare an ordinary full transfer. The former procedure excluded domain data and relied on a separate broad filesystem copy. Such a split recovery requires a specialist plan, not an assumption that the generated archive contains the website.

Transfer and restore the agreed archives

Use authenticated encrypted transport to a private destination directory. Confirm server identity and the exact source/destination paths, ownership and available space. Do not upload archives to public_html, weaken permissions for a public download or give unnecessary source-server root credentials to a third party.

On the destination, use the supported restore interface and inspect username/domain collisions, package/IP mapping and local-versus-backup DNS settings. Protect existing destination data first. A successful import report is a starting point for testing, not proof that every service works.

Reconcile changes without a blanket /home copy

The old guide’s final rsync command copied all of /home and contained a malformed remote path. It is withdrawn. Copying unrelated users, live mail or changing database files can corrupt or overwrite destination data. Plan final synchronization per application and mailbox, with any write pause agreed in advance.

Preview each site with its real hostname and verify database operations, scheduled jobs, certificates, mail and relevant DNS records. Prevent test copies from taking real payments or sending duplicate mail. Keep the old service and rollback archives until acceptance, then revoke temporary access.

References: DirectAdmin account backup/restore and DirectAdmin configuration values. Reviewed October 14, 2026. No server transfer or live rsync was executed.