cPanel to DirectAdmin Migration: 10 FAQs [2026]

What is the recommended method for migrating a single cPanel account to DirectAdmin?

Generate a full account backup from cPanel first. Log into cPanel, navigate to Backup or Backup Wizard, and select 'Download a Full Account Backup.' This creates a compressed archive containing website files, databases, email accounts, and forwarders.

In DirectAdmin, create a user account with matching resource limits (disk quota, bandwidth, database count). Then go to User Backup → Restore Backup, upload the cPanel .tar.gz file, and start the restore process. DirectAdmin extracts files to the correct public_html location and imports MySQL databases automatically.

After restore completes, manually check SSL certificates, cron jobs, and DNS zone records. These items often require separate configuration because cPanel and DirectAdmin store them differently. Test the website by adding a temporary hosts file entry pointing the domain to the new server IP before updating DNS.

How do I handle DNS cutover without downtime?

Lower the TTL on all DNS records to 300 seconds at least 48 hours before migration. This tells DNS resolvers to cache records for only five minutes, speeding up propagation when you change nameservers or A records.

Replicate the DNS zone in DirectAdmin before cutover. Copy all A, CNAME, MX, TXT, and SPF records from the cPanel DNS zone editor into DirectAdmin's DNS management interface. Verify MX priority values match exactly to avoid email routing issues.

Update nameservers at your domain registrar to point to DirectAdmin's nameservers, or change the A record to the new server IP if using third-party DNS. Monitor the domain using dig @8.8.8.8 yourdomain.com to confirm when Google's public DNS resolver sees the new IP. Keep both servers online for 48 hours while propagation completes. Email and web traffic will gradually shift to the new server as caches expire.

Why do SSL certificates fail after migration?

cPanel backups exclude private keys by default for security reasons, so SSL certificates don't transfer automatically. Even if the certificate file appears in the backup, DirectAdmin can't use it without the matching private key.

Re-issue free Let's Encrypt certificates through DirectAdmin's SSL certificate manager immediately after migration. For paid or wildcard certificates, locate the private key from the old cPanel server (WHM → SSL Storage Manager) and manually import both the certificate and key into DirectAdmin under SSL Certificates → Paste.

• Test HTTPS functionality after certificate installation using curl -I https://yourdomain.com
• Check for mixed content warnings in the browser console if pages load over HTTP
• Update any hardcoded http:// URLs in the database to https:// using wp search-replace or manual SQL queries

What happens to email during the migration window?

Email continues delivering to the old cPanel server until DNS propagation completes. MX records still point to the old server IP for 24-48 hours after you update DNS, depending on TTL and resolver cache behavior.

Set up email accounts in DirectAdmin before DNS cutover using the same usernames and passwords. This prevents delivery failures once MX records propagate. Messages sent during the transition window arrive at whichever server DNS resolvers consider authoritative at that moment.

For zero email loss, configure IMAP sync between old and new servers using tools like imapsync. This copies existing messages from cPanel to DirectAdmin mailboxes while both servers are active. Alternatively, instruct users to leave mail on the old server and configure DirectAdmin as a new account in their email client, then manually move folders after migration completes.

Can I migrate multiple cPanel accounts at once?

DirectAdmin does not include a bulk migration tool comparable to cPanel's Transfer Tool in WHM. You must restore accounts one at a time using the User Backup interface.

For servers with dozens of accounts, use command-line scripts to automate restoration. Generate cPanel backups for all accounts via WHM, transfer the archives to the DirectAdmin server using rsync or scp, then loop through them with DirectAdmin's CLI restore commands. This requires root access and familiarity with bash scripting.

Third-party migration services and scripts exist but introduce risk. They often modify DirectAdmin's database directly instead of using official APIs, which can corrupt account data if the script fails mid-process. Test any automated approach on a staging server with non-production accounts first.

Do cron jobs transfer automatically?

No. cPanel stores cron jobs in user-specific crontab files, but DirectAdmin's backup restore process does not parse or import them. You must manually recreate each scheduled task.

Before migration, document all active cron jobs by running crontab -l as the cPanel user or viewing them through cPanel's Cron Jobs interface. Note the schedule (minute, hour, day, month, weekday) and the full command path.

In DirectAdmin, navigate to Advanced Features → Cron Jobs and add each task with the same schedule and command. Pay attention to script paths—DirectAdmin uses /home/username/domains/domain.com/public_html/ instead of cPanel's /home/username/public_html/, so adjust paths in scripts that reference absolute file locations. Test each cron job by setting it to run one minute in the future and checking the output.

How do I verify the migration was successful?

Start by testing web service. Add a hosts file entry on your local machine mapping the domain to the DirectAdmin server IP, then browse the site. Check that all pages load, forms submit correctly, and image uploads work. Review the error_log in DirectAdmin's file manager for PHP warnings or database connection errors.

Send a test email to an account on the migrated domain and verify it arrives. Then send an outbound message from that account to an external address like Gmail to confirm SMTP is working. Check SPF and DKIM records in DirectAdmin's DNS zone match the old configuration to prevent deliverability issues.

Test database connectivity by triggering any database-dependent features (user login, search, checkout). Run a MySQL connection test from the command line using mysql -u dbuser -p and executing a simple SELECT query. Verify all cron jobs execute on schedule by checking /var/log/cron or DirectAdmin's cron log viewer. Monitor Apache or Nginx error logs for 48 hours post-migration to catch issues users might not report immediately.

What are the most common migration failures?

Database name mismatches cause the majority of post-migration errors. cPanel prefixes database names with the username (username_dbname), and DirectAdmin does the same, but if the username changes during account creation, all database connection strings in config files break. Check wp-config.php, Joomla configuration.php, or .env files and update DB_NAME values to match the new prefixed database name shown in DirectAdmin's MySQL management interface.

File permission problems surface when DirectAdmin sets ownership to a different user ID than cPanel used. Web applications that write to cache or upload directories fail with 'permission denied' errors. Run chown -R username:username /home/username/domains/domain.com/public_html/ to fix ownership, and verify that writable directories have 755 permissions while files have 644.

Missing PHP extensions break applications that rely on GD, mbstring, or curl. DirectAdmin's default PHP build may not include every extension cPanel had enabled. Check phpinfo() output on both servers, then install missing extensions using DirectAdmin's CustomBuild system (./build php with the appropriate options) or by enabling them in php.ini.

Should I keep the old cPanel server online after migration?

Yes. Keep it running for at least 7-14 days as a rollback option. If critical issues surface after DNS cutover, you can quickly revert by updating nameservers back to the old cPanel IPs.

During this window, the old server continues receiving email from resolvers that cached the old MX records. Log in periodically and forward any new messages to the DirectAdmin server manually, or set up a catch-all forwarder to relay everything automatically.

Once two weeks pass without issues, archive the cPanel server's data to offsite storage, then decommission it. This grace period has saved dozens of migrations I've handled when subtle application bugs or missing cron jobs only became apparent under production load.

Quick Reference: Migration Task Checklist

Below is a condensed checklist for tracking migration progress. Each task maps to a step detailed in the sections above.

• Generate cPanel backup (full account archive, .tar.gz format)
• Lower DNS TTL to 300 seconds 48+ hours before cutover
• Create DirectAdmin user account with matching quotas
• Upload and restore cPanel backup via DirectAdmin User Backup interface
• Manually recreate cron jobs in DirectAdmin Cron Jobs interface
• Re-issue or import SSL certificates for all HTTPS domains
• Replicate DNS zone records in DirectAdmin DNS management
• Update nameservers or A records at domain registrar
• Configure email clients with new DirectAdmin server settings (IMAP 993, SMTP 587)
• Test website functionality: page loads, form submissions, database queries
• Verify outbound and inbound email delivery
• Monitor error logs (Apache, PHP, MySQL) for 48 hours
• Keep old cPanel server online for 7-14 days as fallback