> 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.md).

# Migration Guide

This guide follows one migration from preparation through final review. A migration connects one source to one destination, stores the options for that job, and keeps the history and file-level results from each run.

Read [How Mover Works](/how-mover-works.md) and [Migration Planning](/migration-planning.md) before beginning a large or consequential transfer.

## Connections

Create one connection for the source and one for the destination. Start with [Connections](/connections.md) to choose the correct connection type and confirm its credentials, permissions, accessibility, and provider-specific behavior.

The source connection needs permission to list and read every item in scope. The destination needs permission to create folders and upload files. If the migration will delete source files, or if SharePoint is the destination, the source must also be writable.

## Migration Configuration

Create a migration, choose the source and destination connections, and select the starting folder on each side. Use [Migration Options](/migration-guide/migration-options.md) to limit the transfer with include or exclude patterns and to decide whether successfully transferred source files should be kept or deleted.

## Dry Run

[Run a dry run](/migration-guide/dry-runs.md) before transferring data. The dry run lists both sides, applies the migration settings, estimates transfer usage, and exposes many permission, naming, case, and limit problems without copying or deleting files.

## Usage Pack

Use the dry-run estimate to choose a prepaid [usage pack](/billing-and-usage-packs.md#usage-packs). Dry runs and failed transfer attempts do not consume transfer usage; only data that is successfully transferred counts.

## Migration Run

[Start the live migration](/migration-guide/migration-runs.md) after reviewing the dry run and purchasing enough usage. Mover reports progress and file-level activity while the run is in progress.

## Results and Reruns

[Review the completed run](/migration-guide/results-and-reruns.md), correct permanent failures, and rerun the same migration when you need to retry temporary failures or pick up source changes. Mover does not schedule reruns or continuously synchronize the two systems.

Files.com Support can help configure Mover connections and migrations, review dry-run results, explain usage pack balances, and troubleshoot errors. Support is included at no extra cost.

Email `support@files.com` or call (800) 286-8372.