> 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/migration-runs.md).

# Migration Runs

Start the live migration only after reviewing its [dry run](/migration-guide/dry-runs.md) and confirming that your [usage pack](/billing-and-usage-packs.md#usage-packs) has enough transfer capacity.

When the run begins, Mover lists the source and destination, compares their contents, and copies the files that need to be transferred. Folder listing happens in sequence, while file transfers run in parallel where possible. Files can arrive in any order.

Mover reports the amount of data moved, the number of files processed, and file-level activity while the migration is running. Options such as deleting successfully transferred source files or removing empty source folders are applied as the relevant files complete.

Avoid changing files in scope or running another migration against the same locations while the job is active. Concurrent changes can produce locks, repeated transfers, or an incomplete copy. This is especially important when the migration deletes successfully transferred source files.

Temporary provider and network errors are retried automatically. A run can take longer than its data size suggests when it contains many small files or when a provider limits requests. See [Performance and Rate Limits](/migration-behavior/performance-and-rate-limits.md) for Mover's retry behavior and planning recommendations.

When the run finishes, continue to [Results and Reruns](/migration-guide/results-and-reruns.md).