# Executing Migration When a migration runs, Mover transitions from planning into action. The platform evaluates the source and destination, identifies which files need to be transferred, and begins copying them. As with Files.com Remote Sync jobs, files are checked for differences in size or presence before being copied or moved, and transfers run in parallel where possible. Configuration choices like removing empty folders or deleting files from the source after transfer are applied automatically as the job runs. Mover reports progress in real time, showing the amount of data moved, the number of files processed, and any issues that occur. After the migration finishes, Mover generates a detailed report listing what was transferred successfully and what failed. Some failures clear on a rerun. Others require updates to permissions or to file handling rules before the job will succeed. For larger projects, schedule incremental migrations to process only the files that have changed since the last run. Incremental runs keep the destination current and shorten the final cutover. --- # 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/executing-migration.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.