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.
Prepare these items before you generate a backup:
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.
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.
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.
| Item | What to expect after a cPanel account restore |
|---|---|
| Website files | Usually restored from the home directory, including the public website files. Check each document root and addon domain. |
| MySQL databases | Usually restored with the account. Check database names, users, passwords and application configuration. |
| Email accounts | Mailboxes and stored mail may be included in the account package. Test webmail and every important email client. |
| DNS zones | A zone may be brought across, but compare every record with the source before changing nameservers. |
| SSL certificates | Plan to issue or enable certificates on the new host; do not assume an old certificate will remain valid there. |
| PHP settings | Re-select the required PHP version and review custom values such as memory limits and upload limits. |
| Cron jobs | Record and test them separately. Paths and PHP binary locations can change between panels. |
| Special services | PostgreSQL, 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.
Why this matters: a full account package gives you a recovery point and lets a DirectAdmin administrator import the account as a unit.
.tar.gz extension.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.
Why this matters: restoring the account package preserves more of the original structure than uploading website files alone.
There are two practical routes.
This is the right route for most shared hosting customers.
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.
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.
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:
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.
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:
www version.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.
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.
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.
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.
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.
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.
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.
Use this checklist before cancelling the old account:
www and relevant subdomains.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.
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.
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.
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.
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.
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.
Compare zoho mail alternatives for Indian businesses by rupee cost, IMAP access and mailbox limits,…
Compare Wix alternatives for Indian small businesses: see 3-year rupee costs, WordPress hosting, migration limits,…
Titan email price in India explained with mailbox costs, features, team totals and a comparison…
HostKarle vs Bluehost compares Indian shared hosting prices, renewal bills, email, SSL, backups, panels and…
Learn how to write blog in hindi with WordPress, Hindi typing tools, domain and hosting…
Compare Google Workspace alternatives in India by yearly rupee cost, email features and migration effort…
This website uses cookies.