--- title: "Migrating Data to Wasabi Using Movebot" slug: "how-do-i-use-couchdrops-movebot-with-wasabi" updated: 2026-03-27T17:31:57Z published: 2026-03-27T17:31:57Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt > Use this file to discover all available pages before exploring further. # Migrating Data to Wasabi Using Movebot Multiple [Couchdrop](https://couchdrop.io) [Movebot](https://movebot.io/)features have been validated for use with Wasabi. This article describes the general process for migrating data to Wasabi using Movebot. For detailed instructions on how to configure Movebot for migrations from specific services to Wasabi, refer to the appropriate link below. - To migrate your data stored on AWS Cloud Object Storage to Wasabi, review [Couchdrop to Migrate Data From AWS S3 to Wasabi](https://docs.wasabi.com/docs/how-do-i-use-couchdrop-to-migrate-data-from-aws-s3-to-wasabi). - To migrate your data stored on On-premises file servers and Network Attached Storage to Wasabi, review [Using Movebot to Migrate Data From Windows File Server to Wasabi](https://docs.wasabi.com/docs/how-do-i-use-couchdrop-to-migrate-data-from-windows-file-server-to-wasabi). - To migrate your data stored on Google Cloud Platform object storage to Wasabi, review [Using Movebot to Migrate Data From Google Cloud Platform to Wasabi](https://docs.wasabi.com/docs/how-do-i-use-couchdrop-to-migrate-data-from-google-cloud-platform-to-wasabi). - To migrate your data stored on Microsoft Azure Blob to Wasabi, review [Using Movebot to Migrate Data From Azure Blob to Wasabi](https://docs.wasabi.com/docs/how-do-i-use-couchdrop-to-migrate-data-from-azure-blob-to-wasabi). ## Prerequisites - An active Wasabi Cloud Storage account. - Access to the Wasabi Console. - Wasabi access and secret keys. It is recommended to create a sub-user with their own set of keys for this purpose rather than using your root keys. See [Creating a User](https://docs.wasabi.com/docs/creating-a-user-account-and-access-key#creating-a-user) for more details. You may also restrict what access the sub-user has, such as access to a specific bucket, using IAM policies. See [Policies in Wasabi Hot Cloud Storage](https://docs.wasabi.com/docs/policies-1) for details. - An active Movebot subscription. - Access to the Movebot portal. ## Connecting Wasabi to Movebot Connecting Wasabi to Movebot is a short and simple process that involves a few quick steps. After making the connection, the connected Wasabi bucket can then be used as a destination for data migrations. Follow the steps below to connect Wasabi to Movebot. 1. Create an account and log in to [Movebot](https://admin.movebot.io/). ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.05.00 PM.png) 2. Go to **Administration > Storage Connections**and click **Add Storage Connection.** Optionally, you can add storage connections as part of setting up a migration project. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.08.56 PM.png) 3. Choose **Wasabi**from the list. Name the Connection for identification, then add the details for the Wasabi bucket you wish to connect to, including your Wasabi access and secret keys. Click **Save and Test Connection**. When successful, the Status dot will turn green and give a verification message. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.10.51 PM.png) 4. You can now use the Wasabi connection as a destination in migrations. ## Configuring a Migration With Wasabi 1. To use your Wasabi connection for a migration, return to the home screen and start a new migration by clicking **Create Project**. Name your Project and choose the type of data to move. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.16.39 PM.png) 2. Choose your source platform. If you have not connected your source yet, you can create a new storage connection using **Connect New Storage**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.17.56 PM.png) 3. Choose your destination connection. If you are migrating into Wasabi and have not configured the connection yet, click **Connect New Storage** to be taken to the wizard and follow from Step 3 in the previous section. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.19.54 PM.png) 4. Choose what type of data to move. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.32.10 PM.png) 5. Set any content rules, such as files to ignore. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.44.03 PM.png) 6. Complete the Project Options to Finalize setup. You can modify any of these settings at any time in the Settings tab. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.46.06 PM.png) 7. Add transfers using Movebot’s Folder to Folder browser or by adding a CSV Upload. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.47.33 PM.png) 8. Choose which Options you’d like to use for the transfer job. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.48.47 PM.png) 9. Choose what kind of migration to run. You can also run a free pre-migration scan at this stage if you wish. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.49.59 PM.png) 10. The migration will run and show Finished when complete. You can view a post-migration report by clicking into any transfer. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-02-18 at 12.51.02 PM.png)