How to migrate all Azure Storage Queue data between two different Storage Accounts with Python

Background
This article describes how to migrate all Azure Storage Queues data between two different storage accounts.
For this, we will use Azure Storage SDK for Python to copy all queues (and the respective data) from one Azure Storage Queue to another Azure Storage Queue. This approach will keep the data in the source queues, and will create new queues with the respective data in the destination Azure Storage Queue.
This script was developed and tested using the following versions but it is expected to work with previous versions:
- Python 3.11.7
- azure-identity (version: 1.15.0)
- azure-storage-queue (version: 12.9.0)
Approach
In this section, you can find a sample code to copy all queues data between two Storage Accounts using the Azure Storage SDK for Python.
This Python sample code is based on Azure Storage SDK for Python. Please review our documentation here Quickstart: Azure Queue Storage client library for Python.
- azure-identity (more information here azure-identity · PyPI). To install, please run:
pip install azure-identity - azure-storage-queue (more information here azure-storage-queue · PyPI). To install, please run:
pip install azure-storage-queue
- azure-identity (more information here azure-identity · PyPI). To install, please run:
Please see below the sample code to copy all the queues data between two Azure Storage Accounts using the storage connection string.
After executing this sample code, it is expected that you will find all the queues from the source Storage Account in the destination Storage Account, as well as the data/messages from those queues.
Disclaimer:
- These steps are provided for the purpose of illustration only.
- These steps and any related information are provided "as is" without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
- We grant You a nonexclusive, royalty-free right to use and modify the Steps and to reproduce and distribute the steps, provided that. You agree:
- to not use Our name, logo, or trademarks to market Your software product in which the steps are embedded;
- to include a valid copyright notice on Your software product in which the steps are embedded; and
- to indemnify, hold harmless, and defend Us and Our suppliers from and against any claims or lawsuits, including attorneys’ fees, that arise or result from the use or distribution of steps.
Published on:
Learn moreRelated posts
Microsoft Fabric: Changes to delegation capabilities for Microsoft Azure OpenAI tenant settings
Starting May 12, 2025, Microsoft Fabric will update tenant settings to allow tenant admins to control the “Users can use Copilot and oth...
Copilot Studio – Connect your data to Azure OpenAI for generative answers
We are announcing the Connect your data to Azure OpenAI for generative answers feature for Copilot Studio. This feature allows you to connect ...
Microsoft Azure: You’re not eligible for an Azure free account
Got the below message, while trying to setup the Microsoft Azure Trial for 30 days. You’re not eligible for an Azure free account Don...
How to create Microsoft Azure 30 days trial?
Microsoft Azure is a comprehensive cloud computing platform developed by Microsoft. It provides a wide range of cloud services, including comp...
Azure SDK Release (April 2025)
Azure SDK releases every month. In this post, you find this month's highlights and release notes. The post Azure SDK Release (April 2025) appe...
Getting Started with Azure Cosmos DB Using the Python SDK
If you’re new to Azure Cosmos DB and looking to build applications with Python, you’re in the right place. I’ve created a four-par...
Fast, Accurate, and Affordable: Sharded DiskANN for Multitenant Vector Search in Azure Cosmos DB
Introduction Azure Cosmos DB now includes Sharded DiskANN, a powerful capability that optimized for large-scale multitenant apps by splitting ...