---
title: "Migrate Veeam v10 Backups From Microsoft Azure Blob to Wasabi"
slug: "how-do-i-migrate-veeam-backups-from-microsoft-azure-blob-to-wasabi"
updated: 2026-04-29T19:42:53Z
published: 2026-04-29T19:42:53Z
---

> ## 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 v10 Backups From Microsoft Azure Blob to Wasabi

Wasabi is a member of Veeam's cloud partner ecosystem. We have worked with Veeam closely to offer both a seamless implementation and a smooth transition to cloud storage. For more information on how Veeam works with Wasabi, review [Veeam with Wasabi Solution Overview](https://wasabi.com/veeam/).

Historical backups that are stored on Microsoft Azure Blob accounts can be migrated to Wasabi using Veeam's Backup Copy Job feature.

> [!NOTE]
> If you are going to leverage immutable Veeam backups, follow the steps from this KB article: [Object Lock: Enabling](https://docs.wasabi.com/docs/object-locking).
> 
> Enabling bucket versioning only is not a proper configuration for immutable Veeam backups and can cause problems.
> 
> If you are simply going to use regular Veeam backups with Wasabi buckets, bucket versioning is not required.

#### **Prerequisites**

- Use Veeam's copy job feature to migrate backups stored on Azure to Wasabi.
- A Scale out Repository has been created for backups stored on Azure.
- Backup(s) have been written to Azure.
- A Scale out Repository has been created for storing data on Wasabi.

**

**CAUTION: When backups are migrated from Azure to Wasabi, the backup chain is interrupted because backup jobs need to point to Wasabi. A new backup job needs to be created for the same VMs to be pointed to Wasabi as an Object Storage Repository target in the Scale-out Backup Repository.**

Follow the instructions below to configure a Veeam copy job to migrate Veeam backups from Azure blob storage to Wasabi Hot cloud storage.

1. Navigate to the **Home** tab. Click **Backup Copy** and select **Virtual machine**

![mceclip0.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/hgghxvjxuuboturcznbgmceclip0.png)

1. Provide a Name. Click **Next**.

![mceclip1.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/x3zzggrmkyoebklxmshamceclip1.png)

1. Click **Add**. Choose the backup job that has backup stored on Azure. Click **Next**.

![mceclip2.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/pllw8e8ki8fgcavnweuqmceclip2.png)

1. In Target, select **Azure2Wasabi** Scale out Repo. Click **Next**.

![mceclip3.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/f7vvfkvoducohjzosqgfigmceclip3.png)

1. Maintain the default values for Data Transfer, Schedule, and Summary. Click **Next**.

![mceclip4.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/haikl6wx3k6kfikixtmsogmceclip4.png)

1. The Veeam copy job will download the backup to the local drive and upload to Wasabi.

![mceclip5.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/z8tx1an2k2y1ya3h1toqmceclip5.png)

1. Since the Instant Copy feature is enabled, the offload process commences immediately after the download completes.

![mceclip6.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/7oeqcjffs0chdz73efpnzamceclip6.png)

1. Confirm the backup stored on Wasabi.

![mceclip7.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/m1ncgch7kysfamgilhjcamceclip7.png)

1. At this point, a new backup job with VMs that were configured in the Azure Backup job needs to be created with the SOBR pointing to Wasabi storage. All new backups will be written to Wasabi based on this backup job.