Move From cPanel to DirectAdmin Without Losing Email

Don’t change your DNS first. In a move from cPanel to DirectAdmin, almost every mistake can be undone except the one where mail starts landing on a server that doesn’t have your mailboxes yet. Do the cutover in the right order and the move is boring. Do it in the wrong order and someone’s invoices go missing for a day.

This is a checklist for a site owner or small host who has already decided to move. It doesn’t argue the case for either panel. If you’re still deciding, the fair summary is that cPanel has the larger ecosystem of plugins and integrations and DirectAdmin is lighter, with simpler tooling, and the right choice depends on what you run. A migration is a project in its own right, so don’t start one because a licence fee annoyed you. Start one because you have tested the destination and it does what you need.

Before you touch anything

1. List what lives on the account. Websites, add-on domains, subdomains, databases, mailboxes, forwarders, cron jobs, SSL certificates and any custom DNS records. Write them down. Anything not on the list is something you won’t remember to test.
2. Match the software. Check the PHP version your sites use and make sure the new server offers it. A WordPress site that runs happily on one PHP version can break on another, and it’s far easier to discover that before cutover.
3. Lower your DNS TTL. The TTL on a record controls how long resolvers cache it. A day or so before the move, set it low on the records you’ll change, so that the switch takes effect quickly and, if needed, can be reversed quickly.
4. Pick a quiet window. Early in the week, outside the busiest hours for your business, is better than a Friday afternoon.
5. Take a full backup and store it somewhere other than the old server. If anything goes wrong, you want a copy that doesn’t depend on the system you’re changing. Treat that file as sensitive: it contains databases, mail and configuration. The risk of a stolen backup is one reason data breaches keep making headlines.

Build the new account

1. Create a full backup in cPanel. Use the full account backup rather than a partial one, since it carries the home directory, databases, email accounts and settings.
2. Restore it on the DirectAdmin side. DirectAdmin can restore cPanel backups through its own tooling, and your host or the DirectAdmin documentation will tell you the exact steps for your version.
3. Don’t assume everything came across. Open the restored account and look at each item on your list: sites, databases, mailboxes, forwarders and cron jobs. Restore tools are good at the bulk of the work and less reliable at details.
4. Check each WordPress site’s configuration. The database name, user and host in the configuration file need to match the new server. File permissions and ownership should be correct, and any caching or security plugins that write absolute paths may need attention.
5. Reissue SSL certificates. Certificates generally don’t move with the account in a way you can rely on. Set up the new certificate on the DirectAdmin side and confirm it covers every hostname, including the www version.

Test before the world sees it

1. Preview the new server without DNS. Edit the hosts file on your own computer to point your domain at the new server’s IP address. Your machine will load the new site while everyone else still sees the old one. Click through the pages, log in to the admin area, submit a form, and check images and links.
2. Test outgoing mail from the new server. Send a message from a mailbox to an outside address and confirm it arrives and doesn’t land in spam. Check that the sending records are in place: SPF, and DKIM, which usually generates a new key on a new server.
3. Test incoming mail. Send a message to each mailbox on the new server using its direct server name, so you know it is received before you rely on it.
4. Remove your hosts-file edit when you’re finished, so your own test doesn’t mislead you later.

The cutover

1. Update DNS records in one pass. Change the A records, and the MX records if mail moves with the site, together. If your nameservers are not changing, edit the records at your DNS provider. If they are, make sure the new nameserver already holds the zone with the full record set before you switch.
2. Leave the old account active. For several days after the change, some resolvers will still send traffic and mail to the old server. Keep it running so nothing is lost in that window.
3. Watch both mailboxes. During the overlap, mail can arrive in either place. Check the old mailboxes and copy anything that landed there to the new ones, using your mail client or an IMAP sync tool.
4. Rotate credentials. Change passwords for the control panel, FTP, email and the database on the new server, and for any WordPress admin accounts. It’s cheap, and it removes the old backup’s credentials from play.
5. Confirm backups on the new server. Make sure scheduled backups are running and test a restore from one of them. A backup you’ve never restored is a hope, not a plan.
6. Cancel the old account only after a settling period. Wait until you’re sure DNS has fully propagated, all mail is arriving in the right place, and the sites have run normally through a normal business cycle.

Where this goes wrong

The common failures are not exotic. They tend to fall into four groups:

• Email disappears because MX records changed before the mailboxes were in place.
• Sites break because the PHP version or database settings differ.
• Mail lands in spam because SPF or DKIM records were not updated for the new server.
• A certificate expires or doesn’t match because it was left behind.

Each is avoidable with the order above, and each is far less painful if you have kept the old account alive.

Where this leaves the decision

If you’ve tested the destination and you have a window and a backup, the migration is a sensible, manageable job, and DirectAdmin’s tooling will do most of the heavy lifting. If you can’t spare a few days of careful checking, or your business depends on plugins and integrations that only exist for cPanel, the safer move may be to stay put and revisit it at a quieter time. Moving panels is something to do on your schedule, not your host’s.

Sources: No third-party figures are used in this article. For restore steps and feature support, refer to the documentation published by DirectAdmin and cPanel for the versions you are running.