Start Migration

Review what you are about to copy before starting an account migration.

Where to find it: Open the Server menu and choose Start Migration.

Available to: Root only.

What this page does

It turns the selected accounts, provider capabilities, copy options, destination overrides, conflict policy, and concurrency into one explicit job definition.

Before you start

If the source host, port, password, provider, or mode changed after the last scan, scan again. SHM rejects stale remote selections because yesterday's account list is not a reliable plan for today's server.

Review Plan

• Confirm the provider and exact source host or archive.
• Confirm the number and names of selected accounts.
• Review copy scopes and provider capability warnings.
• Review package, owner, and IP overrides.
• Review account, domain, and DNS conflicts.
• Choose conservative concurrency when the source or destination is already busy.

Archive mode

Archive mode migrates one account from a selected cPanel or SHM archive. Choose a readable local archive or a direct download URL. Plesk and DirectAdmin are remote-only in the current interface.

How to use it

1. Complete the source step and obtain a successful scan or valid archive selection.
2. Select accounts and scopes.
3. Open Review Plan.
4. Resolve warnings or consciously accept documented limits.
5. Start the migration once and wait for the job identifier.
6. Open Migration Jobs rather than submitting the same job repeatedly.

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

SHM creates a durable migration job with the selected source, policy, accounts, and steps. The transfer then moves to Migration Jobs, where progress and resumable failures are tracked.