---
title: "Migrate Veeam Backup for Microsoft 365 v7 From AWS S3 to Wasabi Using WCSM"
slug: "how-do-i-migrate-veeam-backup-for-m365-from-aws-s3-to-wasabi-using-wcsm"
updated: 2026-06-08T17:35:44Z
published: 2026-06-08T17:35:44Z
---
> ## 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.
# Migrate Veeam Backup for Microsoft 365 v7 From AWS S3 to Wasabi Using WCSM
###
Veeam Backup for Microsoft 365 v7 empowers customers to securely back up Microsoft 365 to on-premises or cloud object storage. Wasabi has been validated to work with Veeam Backup for Microsoft 365 v7 and higher.
This article details the procedure to migrate a non-immutable Veeam Backup for M365 repository from AWS S3 to Wasabi using Wasabi Cloud Sync Manager (WCSM).
The data restoration process is handled by your specific backup software application. As there are many, potential variables that will affect your unique environment, Wasabi strongly recommends that you seek the guidance of your backup software's technical support team in the event that you encounter difficulty or have application-specific inquiries.
#### Requirements
- Veeam Backup for Microsoft 365 v7 or higher installed and licensed. This solution was tested with v7.1.
- Active Microsoft 365 account with multi-factor authentication turned On.
- Active AWS S3 cloud storage account.
- A standard AWS S3 non-Object-Locked (OL) (non-immutable) bucket with access keys.
- An active Veeam Backup for M365 repository with your M365 organization backed up to it.
- Active Wasabi Cloud Storage account.
- A Wasabi non-Object-Locked (OL) (non-immutable) bucket created with access keys.
## Signing Up for Wasabi Cloud Sync Manager
Wasabi Cloud Sync Manager (WCSM) is a paid migration service. Refer to [Getting Started With Wasabi Cloud Sync Manager](https://docs.wasabi.com/docs/wasabi-cloud-sync-manager-wcsm-getting-started) to begin the migration process.
After your data has been migrated, verify that your data is available in Wasabi by logging into the [Wasabi Console](https://console.wasabisys.com), navigating to the bucket used for migrating Veeam Backups for Microsoft 365 from AWS S3 to Wasabi, and looking for data. Below is an example of one of the folders in a bucket used during testing.
After the data has been fully migrated to Wasabi and verified, proceed with the next section.
## Deleting Current Backup Job
Navigate to the Organizations tab and select your organization. Select the existing backup job that backs up to AWS S3. Click **Delete**at the top. Click **Yes** when asked if you want to delete the selected job.
## Deleting Current AWS S3 Repository
1. Navigate to the Backup Infrastructure tab and select **Object Storage**. Select your existing AWS S3 repository. Click **Remove Repository******at the top. Click **Yes**when asked if you want to delete the selected job.
2. Click **Yes**when asked to confirm.
## Deleting AWS S3 Object Storage in Veeam
1. Navigate to the Backup Infrastructure tab and select **Object Storage**. Select the AWS S3 object storage. Click **Remove Object Storage**at the top. This will NOT delete your backups in AWS S3.
2. Click **Yes**.
## Adding Wasabi Object Storage in Veeam
1. Navigate to the Backup Infrastructure tab and select **Object Storage**. Click **Add Object Storage**.
2. Give your Wasabi storage a name. Click **Next**.
3. Select Wasabi Cloud Storage. Click **Next**.
4. Enter the Service Point URL and data center region that your Wasabi bucket is located in. Click **Add**to add your Wasabi Access and Secret key account credentials.This configuration example discusses the use of Wasabi's us-east-1 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL, as described in [Wasabi Service URLs](https://docs.wasabi.com/v1/docs/what-are-the-service-urls-for-wasabis-different-storage-regions).
5. Input the Access key and Secret key for your Wasabi account. Click **OK**.
6. Once the credentials have been added, click **Next**.
7. Select your Wasabi bucket from the drop-down menu.
8. For the Folder, click **Browse.**Select the existing top-level folder in the bucket and click **OK.**
9. Click **Finish**.
You will now see Wasabi under Object Storage.
## Adding the Wasabi Repository
1. Navigate to the Backup Infrastructure tab and select **Backup Repositories**. Click **Add Repository**.
2. Give the Repository a name. Click **Next.**
3. Select **Backup to Object Storage**. Click **Next.**
4. Select the appropriate backup proxy. Under Local cache path, click **Browse**. Create a new folder and click **Next.**You must create a new folder and cannot use an existing cache folder.
5. Select the Wasabi object storage created previously. Click **Next.**
6. Select the appropriate Retention policy for your organization. Click **Finish.**
7. You will be presented with a popup window that asks "Start synchronization now?" Click **Yes**.
You will now see Wasabi under Backup Repositories.
## Adding a Backup Job
1. Navigate to the Organizations tab. Under Organizations, select your **M365 organization**. Click **Backup Jobs** at the top**.**
2. Give the job a name. Click **Next.**
3. Select the appropriate object to be backed up. Click **Next.**
4. Select any objects in which to exclude. Click **Next.**
5. Select the appropriate backup proxy and select the Wasabi backup repository created previously.
6. Select the appropriate scheduling options. Click **Create.**
7. Because "Start the job" under "When I click Create" was selected in this example, a backup job will be run to Wasabi. Below is an example of a successful job.
## Viewing Available Backups
1. Navigate to the Organizations tab. Under Organizations, select your**M365 organization**. Right-click on your organization and select **Explore Exchange point-in-time stat****e**.
2. Select the **Use the following point in time**radio button.
3. Click the **Calendar**icon. You will see available restore points.
4. Verify that your previous restore points from AWS S3 are now available in Wasabi.