Migration Jobs
Follow your account transfers and see which steps have completed or need attention.
Where to find it: Open the Server menu and choose Migration Jobs.
Available to: Root only.
What this page does
Use it to follow job and account progress, see the active step, read failure messages, stop or resume where supported, and confirm that a job reached a final state.
Before you start
Do not launch a second migration simply because a long-running copy appears quiet. Refresh the existing job, inspect its current step and timestamps, and use Resume only for a job state that exposes that action.
What progress means
| State | Meaning | Action |
|---|---|---|
| Queued | The job is waiting for a worker or prerequisite. | Wait and refresh; do not duplicate it. |
| Running | At least one account or job-level step is active. | Read the current step and latest message. |
| Waiting / resumable | The job stopped at a recoverable boundary. | Resolve the stated cause, then use Resume. |
| Error | A required step failed. | Preserve the message and logs; retry only after the cause is understood. |
| Completed | All selected required steps reached a final success state. | Perform customer-facing verification. |
Verification after copy
Check the transferred account in SHM, then test its website, database connection, email, DNS and HTTPS. Confirm that the customer can sign in and that scheduled tasks and applications still work.
How to use it
- Open the job and identify the active account and step.
- Refresh before concluding that progress stopped.
- Read the exact error and correct its cause.
- Resume only when the page offers a resumable state.
- After completion, perform the destination verification checklist and plan DNS cutover.
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
The job retains a step-by-step outcome for every selected account. Completion proves the SHM worker finished its plan; the final service checks prove the migrated customer environment is usable.
Theme color