Skip to Content
Browse documentation

Transfer Details, Results and Logs

Interpret Eenos transfer and restore progress, account and owner outcomes, component warnings and logs, and pending-start or stop actions.

From Review Transfer, open a job's progress or details action. Check the transfer ID before taking any action; the copy control copies this ID for reference. All transfers returns to the list.

Migration overview

Inspect job status, source information, timestamps and account/package outcome counts. Completed includes outcomes with warnings, so also inspect With warnings and the actual messages. Owners such as Plesk reseller/customer identities have separate results when the provider reports them; do not confuse their count with hosting subscriptions.

State or resultInterpretation
PendingPrepared job awaiting execution; eligible for the start control.
Starting / RunningBackground controller is starting or processing work.
StoppingCancellation is being processed; verify the final state.
StoppedJob stopped; existing restored data still needs review.
CompletedProcessing finished; inspect warnings and component results.
FailedWork failed; inspect job/account logs before deciding recovery.
CancelledSelected work did not finish because it was cancelled.

The detail page normally refreshes about every three seconds while visible and unfinished. Closing it does not stop background migration. If the connection is interrupted, check the last update and refresh before relying on the displayed status.

Transfer and Restore sections

Each section has an overall progress bar, package results, applicable reseller/customer cards and hosting account cards. Expand account details to inspect domains, operation, activity, component results and messages. Copying a username helps identify the intended account when reviewing it elsewhere in WAP.

Use Search accounts to match usernames or domains independently in each section. Load more increases the non-active rows loaded in that section by 25. Active work remains included even when it does not match the search, so the view can contain more than the requested limit. A filtered or partially loaded view is not the complete job inventory.

Typical stages include reading inventory, checking conflicts, creating/downloading a source backup, converting or preparing it, restoring settings and databases, copying home files, repairing permissions, verification, source DNS updates and SSL scheduling. The applicable sequence depends on the provider.

Interpret progress with the result

An account that failed or was cancelled can show 100% in both sections because its workflow has ended. Overall percentages include package processing. Use state, errors, warnings and component verification to judge the outcome rather than the percentage or bar color alone.

Component and package results

Account results can include websites, databases, mail, DNS, SSL, settings and autoresponders, depending on the provider. Verified, Scheduled, Skipped, Unsupported and Needs attention describe different outcomes. In particular, scheduled SSL is not proof that a certificate has been issued, and a skipped database component requires review before cutover.

Package rows show the source/destination mapping and reported outcome, such as Created, Reused, Failed or Awaiting results. Review package warnings as well as hosting account results. Reused owner identities may show that a previously restored account was reused; inspect the current ownership outcome.

Read logs

Open the job log for overall context or an account's log for its restore details. Owner cards link to the job log. The log window displays the latest 400 lines, bounded to 64 KB, and refreshes automatically while open. It is a tail, not the entire historical log. An empty log can mean no log has been created yet; check the job state and startup failure information rather than assuming success.

Sensitive entries are redacted by the viewer. Still review any copied diagnostic text before sharing it, and include the transfer ID, affected username, state and relevant error context.

Start a pending migration

Start migration is shown only for a pending job. Review the job identity and intended selection before choosing it. The action starts work in the background; confirm that status advances and inspect errors if it does not. Running or terminal jobs cannot be restarted with this control, and demo sessions cannot start jobs.

For a failed or stopped attempt, review partial destination data and conflicts before preparing a new migration. Repeatedly selecting Start is not a recovery method for a terminal job.

Stop an unfinished migration

Choose Stop transfer, read the confirmation and confirm only for the intended job. The action requests cancellation of the migration and its active workers. Wait for the latest status to confirm the result. If the server cannot confirm stopping, inspect current status before trying again; a failed confirmation is not proof that no work remains active.

Stopping is not rollback

Accounts already restored remain on the destination. Unfinished accounts can contain partial data and need administrative review. Stopping does not automatically restore source DNS or reverse completed operations.

After a terminal result, verify restored services and ownership and resolve warnings before cutover. Return to Review Transfer when you are ready to manage finished history.