Microsoft Azure Files migrations,
without scripts.
Mover is the data-migration tool from Files.com. One-time moves between 20+ providers — no subscriptions, no surprises, no scripts.
Migrate data to or from Azure Files with Mover. Azure Files is Microsoft's managed SMB and NFS file-share service — Mover lifts existing file shares into it, or pulls data out to wherever you need it next.
Azure FilesWhy teams move data through Azure Files.
Azure Files is the home for SMB workloads that need to keep their file-share semantics in the cloud. Inbound is almost all on-prem-to-Azure lift-and-shift. Outbound migrations are usually toward SharePoint (for collaboration) or to Azure Blob (for cost). Hundreds of moves; two stories.
Retiring on-prem Windows file servers
The biggest Azure Files migration: lifting SMB shares from Windows file servers, NAS appliances, or aging VMs into Azure Files as part of an Azure-first cloud push. Mover pulls from SFTP, FTP, the Files.com Agent, or any S3-compatible source on the other side.
Lift-and-shift of legacy SMB workloads
Applications that expect a mounted file share don't always survive the move to object storage. Azure Files keeps the SMB/NFS interface and lets the workload move to the cloud without rewriting.
Hybrid file storage with Azure File Sync
Customers using Azure File Sync to cache cloud shares on-prem land their cloud-side data in Azure Files. Mover backfills the cloud side from existing on-prem sources.
Switching to SharePoint for collaboration
Customers whose Azure Files content is actually collaborative documents — not lift-and-shift application data — often move to SharePoint to pick up the M365 sharing and collaboration features.
Multi-cloud rebalance
Moving file workloads to AWS EFS, GCS FUSE, or back to on-prem as Azure costs grow or strategy shifts.
Archiving inactive shares to object storage
Inactive file shares moved to Azure Blob, S3, or a discount storage tier at a fraction of the per-TB Azure Files cost.
Pair Azure Files with any cloud.
Azure Files migrations rarely happen in isolation. These are the providers we pair with most often — one-click setup on either side, same dry-run flow, same audit trail.
How Mover connects.
Mover connects to Microsoft the standard way. Provide the credential, nothing more — generate a scoped token if you want minimum-privilege.
Storage account access key
Standard for accounts you control. Mover uses the storage account access key to connect to the file share.
The pricing math, honestly.
Mover charges as low as $0.15 / GB when purchasing a 10 TB pack. Your Microsoft-side cost depends on direction. No invoice math, no surprises — the dry-run shows the exact number before you commit.
Provider side
Mover
When purchasing a 10 TB pack
Azure Files inbound is free. Azure Files storage is priced by tier — Premium (SSD-backed) is the most expensive; Hot, Cool, and Cold tiers are progressively cheaper. Azure Files is generally more expensive per-GB than Azure Blob; pick the tier that matches your access pattern.
Provider side
first 10 TB / month
Mover
When purchasing a 10 TB pack
Azure egress from Azure Files is roughly $0.087/GB for the first 10 TB/month, dropping with volume — the same as Azure Blob. Same-region transfer between storage accounts is typically free.
10 TB migration out of Azure Files
The exact dry-run estimate is the number to trust — it includes both line items, run against your actual data.
Customers using Azure Files for archival or infrequent-access data often save by moving it to Azure Blob (Cool/Archive) or to discount object storage like Wasabi or Backblaze. The Azure Files premium pays off when workloads actually need SMB/NFS semantics — not when the data is just sitting there.
4 steps to Go.
From credential to first byte in four clicks. The dry-run is free, every time, and shows the exact cost before you commit a byte.
Connect Azure Files.
Paste a storage account access key. Mover validates the credential and lists the file shares it can see.
Choose source and destination shares.
Apply filters and a date range if you want a partial migration.
Run a dry-run.
Mover walks the source, counts files, sizes the transfer, and produces an exact cost estimate — Mover fees + Azure egress.
Launch.
Live progress, automatic retries on transient failures. Pause, resume, or cancel at any time.
Frequently asked.
Most teams launch their first migration in under 15 minutes. The dry run is free, every time.
Run a dry run before you buy anything. Mover connects to Microsoft Azure Files, walks it, counts every file, sums the bytes, and returns an exact file count and price before a single byte moves — with nothing charged. The dry run is always free, and you can re-run it as often as you want as you scope the migration.
Azure Files is a managed SMB and NFS file-share service — you mount it as a network drive. Azure Blob is object storage — you access it via the S3-like blob API. Use Azure Files when an application expects a file share with directory semantics, file locks, and the SMB protocol. Use Azure Blob when an application speaks object storage natively.
A storage account access key for the storage account hosting the file share. Mover connects via the storage account credential.
Yes. Provide the access key for each storage account; Mover connects to both independently.
Mover charges as low as $0.15/GB when purchasing a 10 TB pack. Azure charges egress separately — roughly $0.087/GB for the first 10 TB out, less at higher volumes. For a 10 TB migration out, expect ~$1,499 in Mover fees and roughly $891 in Azure egress.
For archival or infrequent-access data, often yes. Azure Blob's Cool and Archive tiers are dramatically cheaper than Azure Files at rest. The trade-off is the access pattern: Azure Files exposes SMB/NFS; Azure Blob exposes object storage. If the workload doesn't need file-share semantics, Blob is usually the cheaper home.
Start the move. finish.
Run a free dry run on your Microsoft Azure Files data. See the exact size, file count, and price before you commit a single GB.