cPanel to DirectAdmin: Conversion, Restore and Verification

DirectAdmin provides tools to convert supported cPanel account archives, but cPanel-to-DirectAdmin is a cross-panel administrator workflow. It is not covered by InterServer’s complimentary migrations, which are limited to cPanel-to-cPanel and DirectAdmin-to-DirectAdmin web hosting transfers. VPS and dedicated-server migrations are not offered.

Plan the compatibility and ownership mapping

Use supported source/destination versions and confirm the current conversion tool. Inventory users, resellers, domains, databases, mail, runtime/extensions, certificates and scheduled jobs. Check username/database-name limits and existing destination collisions before converting anything.

Identical software versions are not universally required, and copying an end-of-life version to the destination is not a safe general fix. Identify the application’s supported runtime and test it separately. Features differ between panels, so unsupported source services need another plan.

Create and deliver the supported archive

An authorized cPanel administrator can create an account archive with pkgacct; it packages the selected account, not every account or an “account password.” Ordinary cPanel users must use the provider’s available full-backup route instead.

Use the format and naming accepted by the current converter. Transfer privately through authenticated encryption and preserve the original archive. Do not copy a whole directory blindly, add deletion flags, expose a public download or treat a renamed partial backup as a valid full account.

Convert and restore one representative account first

Follow the current DirectAdmin migration documentation for the installed tool and release. The vendor distinguishes cPanel archive conversion from restoring the resulting DirectAdmin backup through Admin Backup/Transfer.

Inspect conversion warnings and account/database-name changes. Review reseller ownership, package/IP mapping, archive access and DNS settings. Make only the specific permission/ownership changes required for that staging path; never recursively assign the entire restored account to the admin user or chmod every file as a blanket fix.

Verify and reconcile before moving more accounts

Check websites, database grants and configured names, mailboxes/messages, certificates and jobs. Secret files and application-specific paths may require tighter permissions than generic file/directory examples. Use error logs to diagnose failures rather than changing permissions until a page loads.

Test with real hostnames while preventing duplicate mail/payments from a test copy. Arrange final writes/mail synchronization and deliberate DNS cutover. Retain the cPanel source and original archives until accepted, then revoke temporary access.

Reviewed October 14, 2026. Vendor conversion requirements were checked; no package update, conversion, permission change or customer migration was executed.