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

# Migration Planning

A successful migration begins with the source, destination, scope, and cutover plan. Decide those boundaries before creating jobs so dry-run results and usage estimates describe the work you actually intend to perform.

## Source and Destination

Confirm that Mover supports both systems in [Connections](/connections.md). The source account must be able to list and read everything in scope. The destination account must be able to create folders and upload files. Source deletion and some destination behaviors, including SharePoint's handling of uploaded Office files, also require write access to the source.

Use a Files.com Agent connection when storage is on a private network or is not reachable from Mover over the internet. Use a direct protocol connection only when the server is publicly reachable and its firewall accepts Mover's traffic.

## Migration Approach

Use one migration for a direct cutover when the full source fits within Mover's folder limits, the providers can sustain the transfer, and users can stop changing the data during the final run.

For a large source, divide the work into non-overlapping jobs by starting folder or include and exclude patterns. Run the batches one at a time, verify each result, and use a final rerun to pick up changes made before cutover. This approach reduces the effect of provider throttling and makes failures easier to isolate.

When several sources feed one destination, create a separate migration for each source and choose destination paths that cannot collide. When one source must be copied to several destinations, create a separate migration for each destination. Connections can be reused across those jobs.

## Compatibility and Limits

Review [File and Folder Compatibility](/migration-behavior/file-and-folder-compatibility.md) for case-only duplicates, unsupported characters, maximum folder size, and maximum folder depth. Then check both connection pages for provider-specific file-size limits, conversions, permissions, and locking behavior.

Collaboration services such as Box, Dropbox, Google Drive, and SharePoint can take substantially longer than object storage because their APIs may throttle large migrations. Use [Performance and Rate Limits](/migration-behavior/performance-and-rate-limits.md) to choose batch boundaries and reduce competing activity.

## Verification and Cutover Plan

Run a dry run for every job. Resolve permanent failures and confirm that the selected paths and patterns describe the intended scope. Purchase usage only after the estimate is stable.

Choose when users and applications will stop changing the source. After the final live run, review every failure and use a separate checksum or inventory process when the project requires content-level verification. Do not delete or decommission the source until the destination has passed your acceptance checks.