> For the complete documentation index, see [llms.txt](https://moverdocs.files.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moverdocs.files.com/migration-guide/results-and-reruns.md).

# Results and Reruns

Each migration keeps results for its dry runs and live runs. After a run finishes, use its summary and detailed log to understand what Mover processed, identify problems, and decide whether another run is needed.

## Run Results

Open the migration's *Runs* tab and select a *Run ID*. The run history distinguishes dry runs from live runs and shows their start time, completion time, status, and total size. The selected run's *Results* summary also shows the number of files and folders compared and the run time. *Total Size* is the data successfully transferred in a live run, or the estimated transfer size in a dry run.

The overall run status summarizes the outcome. *Partial Failure* means some operations succeeded and at least one failed. *Success* means the run finished without a reported failure; it can still contain skipped items or require no transfers because matching files already exist. Review the detailed messages before treating the migration as complete.

## Migration Log

The detailed log is available when the run finishes. It records transfer results, folder creation, source deletion when enabled, skipped items, and problems encountered while listing or processing files and folders. These entries explain the actions Mover took and the conditions that prevented work from completing.

| Column    | Meaning                                                                                                                       |
| --------- | ----------------------------------------------------------------------------------------------------------------------------- |
| *Date*    | When the log entry was recorded, rather than the file's modified time.                                                        |
| *Status*  | The outcome of that action: *Success*, *Skipped*, or *Failure*. This column is shown for live runs.                           |
| *Type*    | Whether the entry concerns a file or folder, when available.                                                                  |
| *Message* | The reason for the action, skip, or failure. Read it together with the status.                                                |
| *Path*    | The file or folder involved in the action. Read it with the message to understand which operation was attempted.              |
| *Size*    | The file size associated with the entry, when available. A folder or deletion entry does not represent transferred file data. |

For live runs, use the *Status* filter to narrow entries to *Success*, *Skipped*, or *Failed*. The counts beside these statuses count log entries, which can include folder operations and more than one action for a file. They are not counts of unique transferred files. Large logs remain paginated even when status filtering is unavailable.

### Messages and Outcomes

A successful entry with the message "File did not exist on destination" records a transfer to a missing destination file. "File already existed on destination" records a transfer that replaced an existing file because its reported size differed. "Folder did not exist on destination" records folder creation. When source deletion is enabled, "Deleted file from source" is a separate result from the transfer. A successful transfer and a failed source deletion can therefore appear for the same file.

*Skipped* means Mover did not complete the action. The message distinguishes an intentional exclusion from a condition that needs attention. Examples include include or exclude patterns, duplicate names that differ only in case, a file that changed during the transfer, or a lock on the remote system. Review skips as well as failures so that an unintended exclusion or naming conflict does not leave required files behind.

A failed entry provides the available error message and affected path, such as for a permission, filename, size, or folder-limit problem. Errors that concern the whole run can have no path or item type. A folder-listing failure can prevent Mover from discovering the files beneath that folder, so it does not necessarily produce a separate failure row for every affected file. Temporary errors are [retried automatically](/migration-behavior/performance-and-rate-limits.md); individual retry attempts are not separate entries in the results table.

### Log Coverage

The log records actions and problems rather than a complete inventory of both locations. Comparing a file does not by itself create an entry. For example, when source files are kept, a file already present at a matching destination path with the same reported size needs no transfer and produces no separate result row. If source deletion is enabled, that same comparison can instead result in a source-deletion entry. Files inside an excluded folder are not each listed as separate skips.

Read the log together with the run summary and the migration's [file-matching rules](/migration-behavior/file-matching-and-data-integrity.md). An empty log can mean there was nothing to transfer; it does not establish that every source file was copied during that run.

### Dry-Run Results

A [dry run](/migration-guide/dry-runs.md) uses the same log columns except *Status*. Its entries describe proposed actions and any problems found during the scan. Messages about destination files or folders describe why an action would be needed, and "Would delete file from source" previews source deletion. No files are copied or deleted. The estimated size helps plan transfer usage, but a successful dry run does not prove that a later upload or deletion will succeed.

## Correction or Rerun

Temporary rate limits, locks, provider interruptions, and network errors can clear without a configuration change. Run the same migration again after the temporary condition ends.

Permission errors, unsupported names, oversized files, folder-limit failures, and case conflicts require a source, destination, connection, or migration-setting change before another run can succeed. Correct the underlying problem first, then rerun the existing migration.

## What a Rerun Transfers

A rerun lists and compares the source and destination again. Files that are still missing or report a different size transfer. Files at matching paths with the same reported size are skipped, even if their modified times or contents differ.

Use reruns to retry failed items, pick up source changes, or complete a phased migration. Mover does not schedule these runs automatically or continuously synchronize the two locations.

## Cutover Completion

Review the final results and perform any separate inventory or checksum validation required by your project. Do not delete or decommission the source until the destination has passed those checks and users or applications have been redirected to the new location.