The problem
The tooling for Azure-to-S3 is one-directional and manual: azcopy to disk, then the AWS CLI up, twice the transfer and no record. For a few containers it is an afternoon. For a media archive it is a project nobody wants.
> Measured from the product, September 2026: 240M+ objects indexed, 50 TB under management, across Amazon S3, Cloudflare R2, Google Cloud Storage and customers' own servers.
What BucketPilot does
- •Connect the storage account under Credentials with its name and an account key.
- •Pick a container and a destination bucket — Amazon S3, Cloudflare R2, Google Cloud Storage or BucketPilot Cloud — in the migration form. Blob names become object keys under the prefix you choose.
- •Stream, don't stage. Objects go from Azure to the destination through BucketPilot without being written to disk in between; nothing is persisted on the way.
- •Incremental re-runs copy only blobs that are new or changed, so the cut-over is a short last run.
- •Per-file log, live progress, retries.
How to start
- 1.Under Credentials, add Azure Blob Storage: the storage account name and an account key.
- 2.Under Backups & Migrations, press Create, choose Azure as the source, the container, and a destination bucket.
- 3.Run. Re-run before you close the Azure account.
Connecting Azure Blob Storage is on the Business plan (Amazon S3 is on every paid plan); the 14-day trial includes it. Azure is a source: BucketPilot does not write to Azure.
Questions
- Is Azure egress charged?
- By Microsoft, yes, at their published rate — BucketPilot adds nothing on top. Into BucketPilot Cloud there are no ingress, request or transfer fees on our side.
- Are blob metadata and content types kept?
- Content type is set on the destination object. Blob-level metadata and tags are not copied; the log lists every blob so you can reconcile.
- Can I go the other way?
- Not today. Azure is supported as a migration source only.
Go deeper
Start an Azure migration
Full Pro access for 14 days. No card. Connect an account in seconds.