Migration guide

Switching from cPanel

Move deliberately: inventory accounts, domains, websites, mailboxes, databases, DNS zones, certificates, cron jobs, redirects, and customer expectations before changing production traffic.

Discuss migration
1. Inventory

Export account lists, domains, DNS records, mailboxes, databases, filesystem roots, SSL certificates, redirects, cron jobs, PHP versions, Node apps, and reseller relationships.

2. Stage

Create matching Outlaw Panel hosting accounts and websites in a non-disruptive window. Validate document roots, ownership, permissions, mail routing, DNS rendering, and database grants.

3. Validate

Use preview hosts, local hosts-file checks, mail authentication tests, IMAP/SMTP client checks, backup verification, and rollback evidence before DNS cutover.

4. Cut over

Lower TTLs, move DNS/MX only after successful validation, monitor logs, and keep rollback access until customer traffic is stable.

Migration checklist

  • Account and reseller mapping
  • Website files and document roots
  • Databases and users
  • Mailboxes and aliases
  • DNS zones and MX records
  • TLS certificates
  • Cron jobs and redirects
  • Backup and rollback plan

Important cautions

  • Do not assume cPanel plugin behavior exists in Outlaw Panel Version 1.
  • Do not change MX records until mailbox authentication and external delivery are verified.
  • Plan staff training for the new customer and Owner workflows.

Plan before cutover

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

Back to comparisonsRead documentation