# Migrations Mover transfers data between on-premises systems and cloud providers, or between cloud platforms. A migration is the process of moving files from one connection (the source) to another (the destination). Each migration is defined by a job, and the platform shows what is being moved, how long it will take, and what issues come up. Mover supports nearly two dozen connections covering major cloud storage platforms, content sharing and collaboration services, file transfer protocols, and file servers. You can migrate files between providers like [Google Cloud Storage](/connections/google-cloud-storage.md), [OneDrive](/connections/onedrive.md), [SharePoint](/connections/sharepoint.md), [Box](/connections/box.md), [Amazon S3](/connections/amazon-s3.md), [Azure Files](/connections/azure-files.md), and [Azure Blob](/connections/azure-blob-storage.md). You can also move data over [FTP](/connections/ftp-ftps.md), [SFTP](/connections/sftp.md), and [WebDAV](/connections/webdav.md), and transfer from file servers using the [Files.com On-Premise Agent](https://github.com/Files-com/gitbook-mover-documentation/blob/master/connections/any-server-with-files.com-agent). ## Migration Process A Mover migration runs through seven steps, from creating connections to running incremental transfers after the initial cutover. **Step 1: Create Connections**\ Create connections to both the source and destination systems. Connections let Mover authenticate, access data, and prepare for transfer. **Step 2: Create a Migration Job**\ Every migration starts with a job. A job links a source connection to a destination connection and holds all configuration and execution settings. It defines how the migration runs and tracks progress from start to finish. **Step 3: Configure Options**\ Apply options to control how the migration behaves. Options include [deleting files from the source after transfer](/migrations/migration-settings.md#managing-source-files-after-migration), removing empty folders, and [including or excluding files using patterns](/migrations/migration-settings.md#include-and-exclude-patterns). **Step 4: Run a Dry Run**\ Run a [Dry Run](/migrations/dry-runs.md) before the live transfer. The Dry Run is a discovery scan that simulates the migration by listing file counts and total size. It confirms the configuration is correct, surfaces issues like permission mismatches, and reduces surprises when the migration launches. **Step 5: Launch the Migration**\ Once the configuration and Dry Run results look right, [launch the migration](/migrations/executing-migration.md). While it runs, Mover displays real-time details about the transfer, including the amount of data moved, the number of files processed, and any issues recorded in the Run Logs. You can monitor performance and intervene if adjustments are needed. **Step 6: Review Results**\ After the migration completes, the Run Logs report what transferred successfully and list any errors. Temporary issues are often resolved by rerunning the job; other issues require updates to permissions or file handling rules. **Step 7: Run Incremental Migrations**\ For large datasets or ongoing projects, run incremental migrations after the initial transfer. An incremental migration processes only the files that have changed or been added since the last run, keeping the destination current. This shortens the final cutover window and keeps systems synchronized until the migration is complete. ## Getting Help The Files.com Support Team is here to help you get the most out of Mover. Rely on our support engineers for help setting up Mover connections, guidance and best practices to configure migrations, reviewing dry run results, understanding usage pack balances, or troubleshooting error messages. Support is included at no extra cost, ensuring your migrations can be completed successfully and with confidence. You can reach the Files.com Support Team by email at `support@files.com` , or call us directly at (800) 286-8372. Our team is committed to ensuring your experience is smooth and successful, so don't hesitate to reach out. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://moverdocs.files.com/migrations.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.