Amazon S3 to Microsoft Azure Blob Storage,
without the scripting project.
The cross-cloud object-storage move. Teams shifting to Azure as a primary cloud — or splitting workloads across both — move S3 content into Blob without the bespoke scripting.
Mover handles S3 → Azure Blob end to end. Authorize an S3 access key, authorize an Azure storage account, see the price before a single byte moves. The dry run is free.
From
Amazon S3
To
Azure Blob
Why teams move from S3 to Azure Blob.
Most S3 → Blob migrations are about strategy: Azure is the new primary cloud, a contractual requirement landed, or a workload is being colocated with Microsoft 365 and Synapse on the Azure side.
Switching primary cloud to Azure
A strategic shift — often paired with an enterprise agreement, M365 commitment, or a data-platform consolidation on Synapse and Fabric — that has to bring the existing S3 estate along.
Compliance or sovereignty requirements
Data residency, regulatory, or contractual requirements that map cleanly onto Azure regions. Moving the data is what makes the policy real.
Colocating storage with Azure compute and analytics
When the analytics, ML, or app workloads are running on Azure, keeping the storage on S3 means paying egress on every query. Moving the data to Blob ends that line item.
Ending an AWS engagement or contract
Sunsetting an AWS account, ending a vendor relationship, or finishing a project hosted on AWS — all require the data to land somewhere durable. Blob is the obvious target if Azure is where the rest of the company lives.
4 steps to Go.
From credential to first byte in a handful of clicks. The dry-run is free, every time, and shows the exact cost before you commit a byte.
Connect Amazon S3.
Provide an IAM access key with read on the source bucket. Mover supports scoped, least-privilege credentials and never stores keys outside of an encrypted credential store.
Connect Azure Blob Storage.
Provide a storage account name and an account key or SAS token with write access to the destination container. Mover supports hot, cool, and archive access tiers.
Run a free dry run.
Mover walks the S3 source, sums bytes, and produces an exact-cost estimate that includes S3 egress and request fees. The dry run is free, every time.
Launch the migration.
Live progress, multipart parallelism, automatic retries on transient API failures, and a structured audit log of every object moved.
The pricing math, honestly.
S3 charges egress. Azure Blob does not charge ingress. The line items are Mover (as low as $0.15/GB on a 10 TB pack) and AWS egress (typically $0.09/GB at standard rates). The dry run shows both line items at the dollar.
10 TB S3 → Azure Blob migration
AWS egress varies by region and committed-use discounts. The dry run shows the exact AWS-side cost for your data.
Frequently asked.
Most teams launch their first migration in under 15 minutes. The dry run is free, every time.
Run a free dry run. Connect Amazon S3 and Azure Blob Storage, and Mover walks the source, counts every file, sums the bytes, and returns the exact file count and price before you commit. Buy the matching usage pack, launch, and Mover handles the transfer — re-running later moves only what changed or failed.
Mover migrates the current version of each object by default. Versioned migrations — pulling every historical version of every object — are supported on request; this typically multiplies the byte count, so the dry run is the right place to confirm what you actually want to move.
Object metadata (Content-Type, custom headers) is preserved. ACLs and bucket policies on S3 do not map 1:1 to Blob — access is re-established on the Azure side through RBAC, SAS, or container-level policies. Storage class on the destination is something you choose when configuring the migration.
The dry run estimates AWS egress at standard rates. If you have committed-use discounts or a direct-connect arrangement, the actual cost on the AWS invoice will be lower. For very large migrations, AWS Snowball and Azure Data Box are alternatives — though for most migrations under ~100 TB, network transfer through Mover is cheaper and faster end-to-end.
Yes. Filters on the S3 side narrow the source to specific prefixes, date ranges, or object-name patterns. Useful for staged cutovers where you move one workload at a time.
Mover runs multipart, parallel transfers and respects S3 and Azure API rate limits. For multi-TB migrations, the bottleneck is usually the S3 read rate or the Azure write rate — both of which Mover saturates without manual tuning.
Move S3 to Azure Blob with the price up front.
Connect both sides, run a free dry run, see the exact cost — including AWS egress. Launch when you are ready.