enterprise

2 posts with the tag "enterprise"

How to Transfer Files from AWS S3 to Azure Blob Storage

May 11, 2026

Moving Between the Two Largest Cloud Providers

AWS S3 and Azure Blob Storage are the two most popular object storage services in the world. Companies move data between them for all sorts of reasons: switching primary cloud vendors, setting up multi-cloud redundancy, following compliance requirements, or simply taking advantage of Azure's pricing for certain workloads.

The transfer itself is the hard part. Both providers have their own tools (AWS DataSync, Azure Data Box, AzCopy), but those tools are designed for their own ecosystem. Cross-cloud transfers with native tools usually require intermediate steps, scripting, or third-party managed services that charge per-GB.

The Usual Approaches

AzCopy + AWS CLI

You can download from S3 using the AWS CLI and upload to Azure using AzCopy. This requires local disk space for the intermediate files, separate authentication for each tool, and scripting to coordinate the two.

Managed Migration Services

Services like Flexify charge per-GiB transferred. For large migrations (10 TB+), the fees add up. Your data also routes through their infrastructure, which may not meet compliance requirements.

rclone

rclone supports both S3 and Azure Blob. It works, but you need to configure both remotes, handle multipart upload settings, and manage the transfer from the command line.

How Blober Handles It

Blober connects to both AWS S3 and Azure Blob Storage natively. You configure both providers with their respective credentials, create a workflow, and run the transfer. Files stream from S3 through your machine to Azure without intermediate storage.

What Blober Does That Matters for This Transfer

Parallel uploads to Azure. Blober uses Azure's uploadStream with configurable concurrency. Large files are streamed in parallel chunks, which makes a noticeable difference on fast connections.

S3 multipart downloads. On the source side, Blober downloads from S3 using the AWS SDK with multipart support. Large objects do not bottleneck the pipeline.

Azure tier selection. When setting up Azure as your destination, you choose which storage tier new blobs land on: Hot, Cool, Cold, or Archive. This means you can migrate directly to the tier that matches your access pattern without a second step to change tiers after upload.

Write behavior options. You can configure Blober to overwrite existing blobs, skip files that already exist at the destination, or skip only archived blobs. This is useful for incremental migrations where you want to resume without re-transferring what is already there.

Step-by-Step

1. Connect AWS S3: Add S3 as a provider with your Access Key ID, Secret Access Key, and region. Blober lists your buckets.
2. Connect Azure Blob: Add Azure Blob Storage with your connection string. Blober verifies and lists your containers.
3. Create a workflow: Set S3 as source, Azure Blob as destination. Browse and select files or entire buckets.
4. Choose Azure options: Pick the storage tier and write behavior.
5. Run: Blober transfers with progress tracking and auto-resume.

Migrating Buckets in Bulk

Most S3-to-Azure jobs are not a single file, they are whole buckets or whole prefixes. Blober is built for that.

• Select an entire bucket or prefix. Browse your S3 bucket in Blober, select everything at the top level or drill into a prefix, and queue it all in one workflow. You do not enumerate keys by hand or script a loop.
• Mass transfers run in parallel. Blober downloads from S3 with multipart support and uploads to Azure with parallel streams, so a bucket with thousands of objects moves as a continuous pipeline rather than one object at a time.
• Resumable with skip-existing. Set the write behavior to skip blobs that already exist at the destination. If a multi-terabyte run is interrupted, or you stop and continue tomorrow, re-running the workflow picks up only what has not transferred yet. That is what makes a mass migration practical: you are never forced to start over.
• Land directly on the right tier. Pick the Azure tier for the whole job, so a bulk archive migration writes straight to Cool, Cold, or Archive instead of landing on Hot and needing a second pass.

For a move of 5 TB across 200,000 objects from us-east-1 to westeurope, you point Blober at the bucket, choose the destination container and tier, turn on skip-existing, and let it run. Progress is tracked per file, and the run survives a dropped connection.

Cross-Region Awareness

If your S3 bucket is in us-east-1 and your Azure storage account is in westeurope, Blober handles the cross-region transfer. S3's cross-region copy limitations (which affect native S3-to-S3 copies) do not apply here because the data flows through your machine.

The tradeoff is that transfer speed depends on your internet connection. For very large migrations (50 TB+), this is slower than a datacenter-to-datacenter transfer. But for migrations under 10 TB, running through Blober on a fast connection is often faster than coordinating managed services.

Pricing Comparison

	AWS S3 Standard	Azure Blob Hot	Azure Blob Cool
Storage (per TB/mo)	$23	$18	$10
Egress (per GB)	$0.09	$0.087	$0.087
PUT requests (per 10K)	$0.005	$0.065	$0.10

Azure is generally cheaper for storage. S3 is cheaper for write-heavy workloads. The right choice depends on your access patterns.

Frequently Asked Questions

How do I copy data from S3 to Azure Blob without AzCopy or scripts? Connect both providers in Blober, create a workflow with S3 as the source and Azure Blob as the destination, select your buckets, and run. There is no AzCopy command, no AWS CLI loop, and no intermediate download to your disk. Files stream from S3 straight to Azure.

Can I migrate a whole bucket, or only individual files? Either. Select a single object, a prefix, or an entire bucket. Whole-bucket and mass-data migrations are the common case.

Does the data land on the tier I want? Yes. You choose the Azure access tier (Hot, Cool, Cold, or Archive) for the destination, and new blobs are written to that tier on arrival. There is no second pass to re-tier after upload.

Who pays for the data transfer? AWS charges egress (data transfer out) when data leaves S3, billed per GB. Azure does not charge to ingest. So the transfer cost sits on the AWS side, the same as it would with any tool that reads from S3. Blober adds no per-GB fee of its own.

How large a migration can this handle? Transfers run through your machine, so speed depends on your connection. For migrations up to roughly 10 TB on a fast link, running Blober is often faster than setting up a managed service. For datacenter-scale moves of 50 TB and up, a provider appliance may finish sooner, but Blober still works and resumes if interrupted.

Related Guides

• How to Bulk Change Azure Blob Storage Access Tiers once your data is on Azure
• How to Move Azure Blob to Cloudflare R2 for moving off Azure later
• Provider setup: AWS S3 and Azure Blob

Get Blober

Migrate S3 buckets to Azure Blob in bulk, with no AzCopy scripts and no per-GB transfer fee from us. One-time purchase, no subscription.

Download Blober at blober.io

Tags:

• blober
• aws s3
• azure blob storage
• cloud migration
• enterprise
• cloud transfer

Data Holders: How Blober Fits Your Workflow

Mar 14, 2026

Who Are Data Holders?

Data holders are individuals and organizations that accumulate, manage, and preserve large volumes of digital files as a core part of their work. They aren't just storing files - they're responsible for keeping data accessible, organized, and safe across years and even decades.

Data holders include:

• Photographers and videographers with terabytes of RAW footage and project archives
• Researchers and academics maintaining datasets, papers, and experimental outputs
• Small businesses managing client records, invoices, contracts, and media assets
• IT administrators responsible for infrastructure backups and compliance archives
• Content creators with libraries of video, audio, and design files across platforms
• Legal and medical professionals bound by retention requirements for sensitive records
• Personal archivists preserving family photos, home videos, and documents

What unites them is a common problem: data grows, scatters, and becomes harder to manage over time.

---

The Data Holder's Problem

Most data holders didn't plan to end up with files in five different places. It happens organically:

1. Files start local - on a laptop, NAS, or external drive
2. Cloud adoption fragments storage - Google Drive for sharing, Dropbox for syncing, an S3 bucket for backups
3. Platform lock-in creeps in - GoPro Cloud holds your footage, iCloud holds your photos, OneDrive holds your documents
4. Manual management breaks down - folder naming conventions drift, backups become inconsistent, some files have three copies while others have none

The result is a scattered, fragile data footprint where no single tool gives you visibility across all your storage.

Symptom	Root Cause
"I know I have that file somewhere"	Files spread across 3-5 providers with no unified view
"My backup is months out of date"	Manual backup processes that require constant attention
"I'm paying for storage I barely use"	Redundant copies in expensive tiers that should be archived
"I can't move my data without paying egress"	Provider lock-in via egress fees and proprietary APIs
"Organizing everything would take weeks"	Flat folder structures with no metadata-driven automation

---

How Blober Solves This

Blober is a desktop application purpose-built for data holders who need to move, organize, and back up files across cloud providers and local storage - without recurring fees.

1. One Interface for All Your Storage

Blober connects to the storage providers data holders actually use:

Provider	Typical Use Case
AWS S3	Production infrastructure, enterprise backups
Backblaze B2	Affordable long-term archive
Wasabi	Hot storage with no egress fees
Cloudflare R2	CDN-adjacent delivery, zero egress
Google Cloud Storage	Workspace-integrated projects
Azure Blob Storage	Enterprise and compliance workloads
DigitalOcean Spaces	Dev team object storage
GoPro Cloud	Action camera footage (Blober exclusive)
Dropbox	File sharing and synchronization
Local / NAS	On-premise primary storage

No other single tool covers this range - especially GoPro Cloud, which Blober is the only application to support.

2. Direct Cloud-to-Cloud Transfers

Instead of downloading files to your machine and re-uploading them, Blober transfers data directly between providers. This matters for data holders because:

• Saves time - a 2 TB migration doesn't bottleneck on your home internet
• Saves bandwidth - your ISP data cap stays intact
• Reduces failure points - no half-downloaded files sitting on your local disk

3. Metadata-Driven Organization

Data holders accumulate files over years. Manually sorting them into folders is unsustainable. Blober supports path templates that use file metadata to auto-organize during transfer:

/{year}/{month}/{camera_model}/{filename}

A flat dump of 50,000 files becomes a clean archive:

/2025/06/HERO13 Black/GX015742.MP4
/2025/06/Canon EOS R5/IMG_4521.CR3
/2026/01/iPhone 15 Pro/IMG_0032.HEIC

This works for any transfer - cloud-to-cloud, cloud-to-local, or local-to-cloud.

4. Scheduled and Resumable Transfers

Backup workflows for data holders need to be reliable, not heroic. Blober supports:

• Resumable transfers - if your connection drops or your machine restarts, pick up where you left off
• Incremental syncs - only transfer files that are new or changed since the last run
• Large-file handling - multi-part uploads for files in the tens of gigabytes

No babysitting required. Set up a transfer, let it run, and come back to a completed job.

5. One-Time Pricing

Most cloud migration tools charge per-GB or require annual subscriptions with data caps. For data holders who move terabytes regularly, those costs compound:

Tool	Pricing Model	Cost for 10 TB/year
Flexify.io	~$0.03/GiB per migration	~$300+ (plus egress)
MultCloud	$99.98/year for 2.4 TB cap	~$400+ (need multiple renewals)
rclone	Free but manual	$0 (but hours of CLI configuration)
Blober	One-time purchase	One price, unlimited transfers

You buy Blober once. Transfer 1 TB or 100 TB - the price doesn't change.

---

Real-World Workflows

The Freelance Videographer

Setup: 8 TB of footage across GoPro Cloud, a local NAS, and Google Drive. Delivers finals via Dropbox.

With Blober:

• Connects GoPro Cloud and pulls all footage to Backblaze B2 as a cold archive
• Moves finished projects from local NAS to Cloudflare R2 for client delivery
• Uses path templates to organize by project date and camera model
• Runs periodic syncs from Google Drive to B2 to keep a second backup

Result: One tool replaces four manual processes. Total cost: one Blober license.

The Small Business IT Admin

Setup: 500 GB of compliance documents in Azure Blob Storage. Daily operational files in Google Workspace. Regulatory requirement for off-site backup.

With Blober:

• Transfers compliance archive from Azure to Backblaze B2 as a secondary backup
• Syncs critical Google Drive folders to a local NAS nightly
• Uses Blober's incremental sync so only changed files move each day

Result: Meets audit requirements for geographic redundancy without provisioning a second enterprise cloud account.

The Research Lab

Setup: 12 TB of experimental datasets in AWS S3. New data generated weekly. Grants require data preservation for 10 years.

With Blober:

• Migrates completed datasets from S3 Standard to Backblaze B2 (80% storage cost reduction)
• Keeps active datasets in S3 for compute-adjacent access
• Uses metadata templates to organize by experiment ID and date
• Resumable transfers handle multi-GB dataset files without corruption

Result: Storage costs drop dramatically while preservation requirements are met.

---

Why Not Just Use rclone?

rclone is a powerful open-source CLI tool, and many data holders start there. But it has real limitations for ongoing data management:

Capability	rclone	Blober
GUI for browsing files	No (CLI only)	Yes
GoPro Cloud support	No	Yes (exclusive)
Dropbox support	Yes	Yes
Visual transfer progress	Limited	Full progress dashboard
Resumable multi-part uploads	Partial	Built-in
Path template organization	Manual scripting	Visual template builder
Error handling and retry	Config flags	Automatic
Setup time	Hours (config per remote)	Minutes (OAuth flows)

rclone is great for scripted, automated pipelines. Blober is built for data holders who want reliable transfers without writing shell scripts.

---

Getting Started as a Data Holder

1. Audit your storage - list every provider and local device where you keep files
2. Identify your archive tier - choose an affordable destination like Backblaze B2 or Wasabi for long-term storage
3. Connect everything in Blober - add each provider via OAuth or API key
4. Set up your first migration - pick a source, pick a destination, configure a path template
5. Let Blober handle the rest - resumable transfers, incremental syncs, and metadata organization do the heavy lifting

---

Your Data, Your Infrastructure

Data holders shouldn't need a subscription to manage their own files. Blober runs locally on your machine - your credentials never pass through third-party servers, your transfer bandwidth isn't metered, and your workflow isn't gated by monthly caps.

One license. Unlimited providers. Unlimited data.

Get Blober and take control of your data workflow.

Tags:

• blober
• data management
• cloud migration
• backup
• workflow
• object storage
• enterprise
• local-first