Data movement: Data Box vs AzCopy vs Storage Explorer vs File Sync vs Migrate
Verdict: Tens of terabytes over a slow link, ship a Data Box. Scriptable one-way copy, AzCopy. Cross-platform GUI, Storage Explorer. Bi-directional server sync with tiering, File Sync. Discover and migrate a datacentre, Azure Migrate.
| Criterion | Azure Data Box | AzCopy | Azure Storage Explorer | Azure File Sync | Azure Migrate |
|---|---|---|---|---|---|
| Purpose | Offline bulk transfer appliance | Command-line copy | Graphical storage browser | Server-to-Azure file sync | Migration hub |
| Key detail | Up to 80 TB shipped by carrier | Synchronize is one-direction only | Windows, macOS, Linux; uses AzCopy backend | Bi-directional plus cloud tiering | Discovery, assessment, server, db and app migration |
| Choose when | Link too slow for the deadline | Scripted nightly copy | Browse containers in a GUI | Keep a branch file server synced | Plan and run a datacentre exit |
Rules
- Choose Azure Data Box to ship a physical appliance of up to 80 TB so bulk data travels offline when the network link is too slow to meet the deadline.
- AzCopy is a scriptable command-line utility to copy blobs and files; its synchronize option updates one side only, never both.
- Azure Storage Explorer is a cross-platform desktop GUI for files and blobs that uses AzCopy on the backend.
- Azure File Sync keeps a Windows file server bi-directionally synced with Azure Files and caches frequently used files locally via cloud tiering.
- Azure Migrate is the central hub to discover, assess and migrate servers, databases and web apps into Azure.
Traps
- AzCopy runs over the same network link, so it cannot beat a deadline that Data Box's offline shipping meets.
- AzCopy's one-direction sync cannot keep a server and Azure Files updated both ways; that is Azure File Sync.