Migrate Accounts

Move hosting accounts from cPanel, Plesk, DirectAdmin or another SHM server.

Where to find it: Open the Server menu and choose Migrate Accounts.

Available to: Root only.

What this page does

Use it to scan a remote source or select a supported backup archive, choose accounts and copy scopes, define destination ownership and package policy, resolve conflicts, then start a job that can be inspected and resumed.

Before you start

Migration is root-only and should be planned as a data move, not a button test. Confirm source access, free space, destination uniqueness, DNS cutover, customer maintenance expectations, backups, and which provider capabilities are not portable before starting.

Source matrix

Source options

Remote server uses the selected provider, hostname, SSH port, and source credentials to scan visible accounts. Backup archive accepts a supported local archive from the server or a direct download URL for one account.

Copy scope

Choose only the resources required for the job: account metadata, files, databases and users, mail, DNS, SSL, cron, and provider-specific resources offered by the current source. Unsupported choices are disabled and explained before the job starts.

Destination and conflicts

Optional destination overrides can assign a package, owner, or IP. Account, domain, and DNS conflict policies decide whether SHM should stop, keep existing data, or overwrite only where the selected workflow explicitly supports it. Read the review panel; conflict settings are not boilerplate.

PostgreSQL notes

PostgreSQL migration requires globally unique database and role identifiers, no destination ownership collision, and a usable SCRAM-SHA-256 verifier from the source. A cPanel archive with only an MD5 verifier, or no verifier, may not be able to recreate the role safely.

How to use it

1. Select the source platform and remote or archive mode.
2. For remote mode, enter the host, valid SSH port, and credentials, then scan again after any source setting changes.
3. Select the accounts or archive and the exact copy scope.
4. Set destination overrides, conflict policy, and concurrency.
5. Read every capability warning in Review Plan.
6. Start the job and follow it in Migration Jobs until every required account reaches a final state.

Source providers, jobs, and re-synchronization

Remote-server sources include cPanel (WHM), SHM, Plesk, and DirectAdmin. Archive import is offered for the supported cPanel cpmove and SHM backup formats. Select the actual source type, host, SSH port, and available authentication or archive; the formats are not interchangeable.

Scan first, review discovered accounts and DNS-only zones, and confirm target conflicts and the items to move. Jobs expose details, integrity evidence, resume/stop/delete, and re-sync controls. Selective re-sync lets you choose accounts, concurrency, and whether to re-sync DNS-only zones.

Verify websites, PHP, mail, databases, DNS, SSL, ownership, and quotas on the destination before switching public traffic. A resumed or re-synced job still needs per-account result checks; do not assume one successful source-provider test proves the others.

Result and next check

A successful job creates or updates the selected SHM accounts and resources, rebuilds the generated runtime state, and records each completed step. Finish with application, DNS, SSL, mail, database, ownership, and login checks; migration success does not change registrar delegation for you.