Import a cPanel Account into Virtualmin Safely

Virtualmin can import supported cPanel account backups, but a cross-panel import requires administrator planning and verification. Webmin alone is not the Virtualmin hosting-account importer, and an archive import is not a guarantee that every source feature is recreated.

This is self-managed work, outside InterServer’s complimentary matching-panel web hosting migrations. VPS and dedicated-server migrations are not offered.

Preflight the source and destination

Confirm an authorized Virtualmin installation with the required web, database, mail and other features enabled. Inventory the source account and check software compatibility, username/domain collisions and capacity. Protect existing destination content; do not use deletion or replacement options as a routine conflict fix.

Create a complete supported cPanel archive through the source’s enabled backup route. Transfer it into private staging through authenticated encryption. Do not relax permissions for an anonymous download or place the archive in a public web directory.

Select the supported import type

In Virtualmin, use its Migrate Virtual Server workflow for the intended cPanel backup. Identify the exact local archive or approved upload, select the cPanel source type, and review domain, account owner, template and IP settings. Interfaces differ by release; use the installed version’s help.

The vendor migration documentation describes source formats and optional overrides. Do not leave every option at its default without checking the intended destination. A test/validation mode, where available, does not replace an actual isolated restore test.

Verify account and application behavior

Inspect errors and omissions, then check the imported domains, file ownership, application configuration, database users and grants, certificates, DNS and scheduled jobs. A similar-looking mailbox directory is not proof of mail-format or account compatibility; verify representative folders, messages and delivery.

Preview with the real hostname and prevent duplicate customer emails or payments from a test copy. Investigate application errors using logs rather than setting world-writable permissions or downgrading to unsupported software.

Plan final database/mail synchronization and DNS changes separately. Keep the source and original private archive until the owner accepts the destination. External DNS/mail and source-panel-only features can need their own recovery or replacement plan.

Additional reference: Virtualmin migration and account terminology FAQ. Reviewed October 14, 2026. No Virtualmin import or customer-server operation was executed.