Migration guide

Migrating from DirectAdmin

DirectAdmin migrations should account for user accounts, domains, reseller assignments, mailboxes, databases, DNS, package limits, custom scripts, and backup strategy.

Discuss migration
1. Export the operating map

List users, resellers, domains, domain pointers, mailboxes, FTP accounts, databases, DNS zones, PHP settings, and backup locations.

2. Recreate account boundaries

Create Outlaw Panel hosting accounts with matching system users and domain-centered resources. Confirm permissions and managed-root containment.

3. Validate service parity

Check website rendering, database connections, IMAP/SMTP, DNS records, TLS, file permissions, and backup verification.

4. Migrate traffic

Cut over only after logs, customer access, and recovery evidence are clean.

Migration checklist

  • Users and resellers
  • Domains and pointers
  • Mailboxes and forwarding
  • Database names and grants
  • FTP accounts
  • PHP versions
  • Custom scripts
  • Backups and restore proof

Important cautions

  • Do not reduce the comparison to account limits; DirectAdmin has an unlimited Standard license option.
  • Validate custom hooks or scripts before replacing them.
  • Document every customer-visible change before migration.

Plan before cutover

Validate web, mail, DNS, TLS, backup, and rollback evidence before moving production traffic.

Back to comparisonsRead documentation