PLATFORM
Azure Blob Storage Migration Tool
MigrationFox moves files in and out of Azure Blob Storage with streaming transfers and parallel block uploads. Consolidate storage accounts, move from AWS S3 to Azure, or archive SharePoint libraries and file shares to blob containers, in a single job.
Container-to-Container Migration
Copy blobs from one Azure container to another, across storage accounts, subscriptions, or regions. Each blob streams through the transfer engine, several at a time, and keeps its content type.
Uploads are split into 8 MB blocks, up to four in flight per blob, and committed as one block blob, so large files never need to fit in memory.
Cross-Cloud: S3 to Azure
Moving out of AWS? Point MigrationFox at an S3 bucket and an Azure container. Each object streams from S3 to Azure without being stored on disk along the way. The reverse path (Azure to S3) works the same way.
Authentication
Connect with the storage account name, a storage account access key (key1 or key2 from the Azure portal) and the container name. A custom endpoint URL is optional, for example for the Azurite emulator or a non-default Azure cloud. Credentials are encrypted at rest and never written to logs.
Supported Migration Paths
Amazon S3 to Azure Blob Storage
Bucket to container transfers with streaming and parallel block uploads.
SharePoint to Azure Blob
Archive SharePoint document libraries to low-cost blob storage for compliance retention.
File shares to Azure Blob
A file share is read from inside your network and sent straight to a container: on MigrationFox web with the File share agent on a server (paid with credit), or with MigrationFox for Windows on a PC or server (MigrationFox Pro or the free trial).
Azure Blob to Amazon S3
Exit Azure or build a multi-cloud copy. Azure Blob works as a source and a destination.
Key Features
- Streaming transfer: blobs flow from source to destination with no local disk writes
- Parallel blocks: 8 MB blocks with 4 concurrent blocks per blob
- Content type kept: each blob is written with the source file’s content type
- Verified writes: every upload must return a valid result before the file is marked done
- Incremental re-runs: re-run a job and replace only files that are newer at the source