Migrations

Mover enables you to transfer data between on-premises systems and cloud providers, or between different cloud platforms. A migration in Mover is the process of moving files from one connection (the source) to another (the destination). Each migration is defined by a job that you configure, and the platform provides full transparency into what is being moved, how long it will take, and what issues may arise.

Mover supports nearly two dozen connections, covering all major cloud storage platforms, content sharing and collaboration services, file transfer protocols, and file servers. This means you can migrate files between providers such as Google Cloud Storage, OneDrive, SharePoint, Box, Amazon S3, Azure Files, Azure Blob, and many more. You can also move data via FTP, SFTP, or WebDAV, as well as transfer from file servers using the Files.com On-Premise Agent. This breadth of coverage ensures that migrations are flexible and can be tailored to virtually any environment.

Migration Process

Mover migrations follow a structured, step-by-step workflow designed to ensure accuracy, reliability, and efficiency. From creating connections and configuring options to running dry runs, executing transfers, and reviewing results, each stage provides visibility and control to make migrations smooth and predictable.

Step 1: Create Connections The first step in any migration is creating connections to both the source and the destination systems. These connections allow Mover to authenticate, access data, and prepare the environment for transfer.

Step 2: Create a Migration Job Every migration begins with a job. A job links a source connection to a destination connection and acts as the container for all configuration and execution settings. It defines how the migration will run and provides the framework for tracking progress from start to finish.

Step 3: Configure Options Once a job is created, you can apply options to control how the migration behaves. These settings may include deleting files from the source after transfer, removing empty folders, or including and excluding files using patterns. You can configure an End-of-Sync Trigger Filename so that once all files in the migration have been successfully transferred, a zero-byte trigger file is delivered to the destination. This provides downstream systems with a clear signal that the migration is complete.

Step 4: Run a Dry Run Before committing to a live transfer, it is strongly recommended to perform a Dry Run. The Dry Run functions like a discovery scan, simulating the migration by listing file counts and total size. This preview confirms that your configuration is correct, highlights potential issues such as permission mismatches, and reduces the likelihood of surprises when the migration is launched.

Step 5: Launch the Migration Once you are satisfied with the configuration and Dry Run results, you can launch the migration. 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 encountered in the Run Logs. This visibility allows you to monitor performance and intervene quickly if adjustments are needed.

Step 6: Review Results After the migration completes, detailed Run Logs are available for review. These logs provide a clear report of what was successfully transferred and list any errors that occurred. Temporary issues may be resolved by rerunning the job, while others may require updates to permissions or adjustments to file handling rules.

Step 7: Run Incremental Migrations For large datasets or ongoing projects, incremental migrations can be run after the initial transfer. An incremental migration processes only the files that have changed or been added since the last run, ensuring the destination stays current. This approach reduces downtime, 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 [email protected] , or call us directly at [phone]. Our team is committed to ensuring your experience is smooth and successful, so don't hesitate to reach out.