Migrate Accounts
Migrate Accounts imports supported hosting resources from cPanel, Plesk, DirectAdmin, or another SHM server into reviewed SHM migration jobs.
Where to find it: Open the Server menu and choose Migrate Accounts. Conditional items appear only when their service is installed and available.
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 | Remote scan | Backup archive | Important current limits |
|---|---|---|---|
| cPanel / WHM | Supported | Supported | DNS-only zones and PostgreSQL may be selected when their prerequisites are met. Archive mailing lists include definitions, not Mailman members or settings. |
| Synconix / SHM | Supported | Supported | Remote DNS-only zones are supported on a best-effort basis. SHM archives do not currently import PostgreSQL databases or users. |
| Plesk | Supported | Not offered in the current UI | Mailing lists, per-mailbox filters, autoresponders, per-mailbox Roundcube data, and PostgreSQL databases/users are not currently imported. |
| DirectAdmin | Supported | Not offered in the current UI | Mailing lists, per-mailbox filters, autoresponders, per-mailbox Roundcube data, and PostgreSQL databases/users are not currently imported. |
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
- Select the source platform and remote or archive mode.
- For remote mode, enter the host, valid SSH port, and credentials, then scan again after any source setting changes.
- Select the accounts or archive and the exact copy scope.
- Set destination overrides, conflict policy, and concurrency.
- Read every capability warning in Review Plan.
- Start the job and follow it in Migration Jobs until every required account reaches a final state.
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.
Theme color