cPanel to DirectAdmin Migration: Step-by-Step Guide

Learn cPanel to DirectAdmin migration step by step: back up files, databases and email, restore safely, test WordPress, switch DNS and avoid errors.
, cPanel to DirectAdmin Migration: Step-by-Step Guide

cPanel to DirectAdmin migration is the process of moving your website, database, email and domain settings to a new hosting account without rebuilding everything from zero. The safest method is to create a complete cPanel account backup, restore or convert it in DirectAdmin, test the new copy, and only then change DNS.

What you need before migration

Prepare these items before you generate a backup:

  1. Access to your cPanel account, domain registrar and DNS management.
  2. A new DirectAdmin hosting account with enough storage for the full account backup and your website.
  3. A list of domains, addon domains, subdomains, databases, email addresses, forwarders and cron jobs.
  4. The current PHP version, WordPress version and important plugin settings for each site.
  5. A separate copy of the backup. Do not cancel the old hosting account until the new website and email have passed your checks.

If you are moving a WordPress website, record the administrator login and test a new post, image upload, contact form and checkout before the cutover. This gives you a clear comparison after the move. For a manual WordPress-specific route, see How to migrate your WordPress website.

For a shared hosting account, you may not have the administrator access needed to convert a cPanel package yourself. In that case, ask the new host whether it can perform the import. HostKarle includes free migration with its DirectAdmin hosting plans, so you can request the move instead of running server-level commands.

Why people switch from cPanel hosts

The control panel is not the website. Your files, database, mailboxes and DNS records are account data that can be moved to another panel, while the buttons and menu names used to manage them change.

Licence costs are one reason hosting providers and website owners consider DirectAdmin. A panel change can also make sense when you want a simpler dashboard, a different hosting provider or a plan that includes migration help. The important question is not whether the panel looks identical; it is whether the destination supports the software and services your website actually uses.

DirectAdmin has its own account backup and restore workflow, and its documentation includes a cPanel-to-DirectAdmin conversion path for cpmove-USERNAME.tar.gz packages. If you are comparing the two panels before moving, read DirectAdmin vs cPanel: which is better in 2026? and then check the destination plan’s PHP, database, email and backup tools.

What moves automatically and what does not

A full cPanel account package gives the DirectAdmin importer much more to work with than a zip of public_html. The result still needs testing because the two panels use different account structures and may offer different features.

ItemWhat to expect after a cPanel account restore
Website filesUsually restored from the home directory, including the public website files. Check each document root and addon domain.
MySQL databasesUsually restored with the account. Check database names, users, passwords and application configuration.
Email accountsMailboxes and stored mail may be included in the account package. Test webmail and every important email client.
DNS zonesA zone may be brought across, but compare every record with the source before changing nameservers.
SSL certificatesPlan to issue or enable certificates on the new host; do not assume an old certificate will remain valid there.
PHP settingsRe-select the required PHP version and review custom values such as memory limits and upload limits.
Cron jobsRecord and test them separately. Paths and PHP binary locations can change between panels.
Special servicesPostgreSQL, Ruby applications, mailing lists and panel-specific rules may need a separate migration plan.

DirectAdmin’s migration documentation specifically warns that some database names or usernames may be changed to fit DirectAdmin’s format. For WordPress, that can mean updating the database values in wp-config.php. It also notes that some features, including PostgreSQL and Ruby, are not supported by that conversion path and must be moved manually.

Step 1: Take a full cPanel backup

Why this matters: a full account package gives you a recovery point and lets a DirectAdmin administrator import the account as a unit.

  1. Log in to cPanel and open Files → Backup or Files → Backup Wizard.
  2. Choose Full Backup. If your host allows it, select Home Directory or a remote destination such as SCP.
  3. Add a notification email if you want a completion message, then start the backup.
  4. Wait for the backup to finish. cPanel stores the archive with a .tar.gz extension.
  5. Download the archive or leave it in the source account only when the new host has clearly confirmed it can read that location.
  6. Keep one copy outside the old account. If the archive is very large, check that the file size is sensible and that the transfer completed before deleting anything.

The official cPanel backup documentation explains that a full backup is a tarball and that automatic full-account restoration is performed at the WHM or hosting-provider level. As a normal shared hosting user, you may be able to create the archive but not restore it yourself.

Success looks like this: you have a readable full backup archive, a separate copy, and a written list of the domains, databases, mailboxes and DNS records that must be checked on the new account.

Step 2: Restore it in DirectAdmin or ask for free migration

Why this matters: restoring the account package preserves more of the original structure than uploading website files alone.

There are two practical routes.

Route A: use your new host’s migration service

This is the right route for most shared hosting customers.

  1. Create or order the new DirectAdmin account.
  2. Give the provider the domain list and the cPanel backup location or archive, using its secure migration process.
  3. Confirm which mailboxes, databases, addon domains and subdomains must be included.
  4. Ask the provider to tell you when the account is ready for testing. Do not change nameservers yet.
  5. Log in to the new DirectAdmin panel and check the restored account.

Do not send a permanent cPanel password in an ordinary email or chat message. Use the provider’s secure handoff method, and remove any temporary access after the migration.

, cPanel to DirectAdmin Migration: Step-by-Step Guide
HostKarle's DirectAdmin login screen for reaching the new panel.

Route B: convert the package on a server you administer

This route needs root or administrator access. It is not a set of commands to run inside ordinary shared hosting. DirectAdmin documents the single-account conversion with commands like these, where USERNAME is replaced with the cPanel account name:

On the cPanel server, run:

/scripts/pkgacct USERNAME /home/user_backups

Copy cpmove-USERNAME.tar.gz to the DirectAdmin server first. Then, on the DirectAdmin server, run:

/usr/local/directadmin/shared/cpanel_to_da/cpanel_to_da.sh \
  /home/admin/cpmove-USERNAME.tar.gz \
  /home/admin/converted_user_backup/

chown -R admin:admin /home/admin/converted_user_backup

The administrator then restores the converted directory from DirectAdmin’s Admin Backup/Transfer area. Follow the DirectAdmin cPanel migration documentation for the current paths and permissions. The DirectAdmin restore documentation explains the backup/restore workflow and how to monitor a restore.

Success looks like this: the new DirectAdmin account contains the domains, files, databases and mailboxes you expected, and no DNS change has been made yet.

Step 3: Test before changing nameservers

Why this matters: you can correct the new copy while visitors and mail still use the old account.

Test each website in a preview method supplied by the new host, or use a local hosts-file test if you administer the server. Check the following in order:

  1. Open the home page and several inner pages over HTTPS.
  2. Log in to WordPress, publish a test draft and upload an image.
  3. Test contact forms, search, login, payments and any application that writes to the database.
  4. Confirm that media files, redirects, permalinks and downloadable files work.
  5. Compare the PHP version and required extensions with the old account. Select the matching version in DirectAdmin where it is available.
  6. Open the database settings and confirm that the application’s database name, username, password and host match the restored account.
  7. Recreate or test cron jobs. A job that points to an old home directory or PHP binary can fail even when the website opens normally.
  8. Sign in to every important mailbox, send a message out and send a test message in.

If the site is WordPress and the database username or name changed during import, update wp-config.php with the new values supplied by DirectAdmin. Do not guess the password; copy it from the new database user settings.

Step 4: Switch DNS and check email

Why this matters: DNS decides which hosting account receives web visits and email.

Before the change, compare the old zone with the new one. Pay special attention to the website’s A or CNAME records, www, MX records, SPF, DKIM, DMARC, verification records and any subdomain used by an application.

When your new host gives you nameservers, replace the old nameservers at the domain registrar. If you are given an A-record cutover instead, update only the records the provider specifies. For a HostKarle account, the nameservers listed in the site instructions are ns1.fastnsdns.com and ns2.fastnsdns.com; use the exact values shown for your account if they differ.

After saving the DNS change:

  • Open the site in a private browser window and check both the root domain and www version.
  • Confirm the new SSL certificate is active.
  • Send and receive email from an address on every important domain.
  • Check that SPF, DKIM and DMARC records still exist and match the new mail service.
  • Watch form notifications and order emails for a complete test cycle.

Keep the old cPanel account available until DNS has settled and your checks pass. Some networks may continue using cached DNS answers until the previous TTL expires, so do not treat the first successful browser test as the end of the migration.

Common problems after the move

The site shows a database connection error

The database name or username may have been renamed during conversion. Compare the new DirectAdmin database details with DB_NAME, DB_USER, DB_PASSWORD and DB_HOST in the application’s configuration file. Also confirm that the database user has access to the database.

WordPress shows a blank page or a 500 error

Check the selected PHP version and required extensions first. Then disable the last plugin or theme changed on the old account, review the application’s error log, and save WordPress permalinks again after the site loads.

Cron jobs stopped running

Recreate the jobs in DirectAdmin using the new account path and the PHP command recommended by the new host. Run one job manually where possible and confirm its output rather than relying only on the schedule.

Email is not arriving

Check MX records at the active DNS provider, then review SPF, DKIM and DMARC. If mailboxes exist in DirectAdmin but messages still go to the old service, the domain is likely still using an old MX record or cached DNS response.

HTTPS is not active on the new account

Confirm that the domain resolves to the new hosting account and that the domain is added correctly. Then enable or issue the new host’s Let’s Encrypt certificate and test again in a private window.

An account feature is missing

Compare the cPanel feature with the destination plan before you cut over. Some panel-specific settings and applications do not have a direct equivalent, so export their data and configure them separately instead of assuming the importer will recreate them.

Final verification checklist

Use this checklist before cancelling the old account:

  • Every domain and subdomain opens on the new account.
  • WordPress admin, media uploads, forms and important transactions work.
  • Database names, users and permissions are correct.
  • All required mailboxes, forwarders and autoresponders have been tested.
  • MX, SPF, DKIM, DMARC and other important DNS records are present.
  • SSL works for the root domain, www and relevant subdomains.
  • Cron jobs run with the new paths.
  • You have a fresh backup of the new DirectAdmin account.
  • The old cPanel account is still available for rollback until the checks are complete.

For a new account with DirectAdmin already included, see HostKarle’s DirectAdmin hosting plans. The Professional plan is suited to freelancers and growing businesses with multiple sites, and includes free migration as part of the hosting plan.

FAQ

Can I migrate from cPanel to DirectAdmin without downtime?

You can usually keep the old site live while the new account is restored and tested, then make a planned DNS change. This can reduce interruption, but DNS caching and application changes mean no migration should be promised as completely risk-free.

Does a cPanel full backup work in DirectAdmin?

DirectAdmin has a documented conversion workflow for a cPanel cpmove-USERNAME.tar.gz account package. The destination administrator must run the conversion and restore it, so shared hosting customers should ask their new provider to perform the import.

Will my email move during the migration?

Mailboxes and stored messages may be included when a complete account package is imported, but you still need to test each mailbox, forwarder and DNS mail record. Recheck MX, SPF, DKIM and DMARC after the cutover.

Do I need to change nameservers after moving hosting?

The domain’s DNS must point to the new hosting account, either by changing nameservers or by updating the required A, CNAME and mail records. Use the exact method and values supplied by your new provider.

Can HostKarle help with a cPanel to DirectAdmin migration?

Yes. HostKarle DirectAdmin hosting includes free migration, so you can provide the required account details through the provider’s secure process and test the restored site before changing DNS.

Want to partner with us, suggest a resource or advertise on this blog? Email partnerships@hostkarle.in

Samrat Ghosh
Written by

Samrat Ghosh

Writer

Samrat Ghosh writes hands-on guides about web hosting, WordPress, domains and email for Indian small businesses, students and freelancers - the practical documentation he wishes had existed when he set up his first website.

Previous Article

HostKarle vs HostGator India: Price, Renewal & Panel

Next Article

How to Install WordPress on XAMPP and Open localhost wp admin

Write a Comment

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

This website is using cookies to improve the user-friendliness. You agree by using the website further.

Privacy policy