Migrate NetApp
to or from any cloud.
NetApp filers running ONTAP — FAS, AFF, or virtualized — share data via NFS and CIFS. The Agent reads them like any other network share and pipes to the cloud.
Mover is the one-time cloud migration tool from Files.com — built for moving data between 20+ cloud providers and any on-prem storage reachable through the Files.com Agent. For NetApp, that means installing the Agent on a host that can reach the NetApp share, then pointing Mover at any of the supported cloud destinations on the other side.
When teams migrate NetApp
The common situations.
Three or four real triggers below. Decommissioning aging hardware, consolidating into a cloud, tiering cold data to discount storage, or running hybrid setups where both sides need to stay in sync — the NetAppside runs through the Agent; the cloud side runs through Mover's native connectors.
Decommissioning a NetApp into cloud object storage
Aging FAS or out-of-support hardware moving into S3, Azure Blob, or GCS as part of a data center exit or hardware-refresh-into-cloud strategy.
Tiering cold NetApp data to discount cloud
Inactive shares on a NetApp moved to Wasabi or Backblaze B2 for archive — frees up filer capacity without losing access, and the Agent provides the read path.
Compliance archive from cloud to NetApp
Reverse direction: pulling specific cloud datasets back to a NetApp for regulatory retention, legal hold, or disaster recovery on hardware the organization controls.
Setup
4 steps to first dry run.
The Agent installs and configures the same way regardless of the source — what changes is the mount or share path it reads from. For the full Agent install reference, see the Files.com Agent page.
Mount the NetApp export on a Linux or Windows host.
NFS export: mount on Linux via /etc/fstab or mount -t nfs. CIFS share: mount on Windows, Linux, or macOS with the appropriate domain credentials. The host needs read or write permissions on the paths being migrated.
Install the Files.com Agent on that host.
Download the Agent for Windows, Linux, or macOS from your Mover account. Install as a system service so it survives reboots.
Point the Agent root at the mounted NetApp path.
In the Agent's TOML config, set the root to the mount point (e.g., /mnt/netapp on Linux). Configure permission_set as read_only for source-only operations or read_write for bidirectional migrations.
Run a dry run.
Create a Files.com Agent connection in Mover, select the registered Agent, run a dry run for the exact byte total and cost before launching the live migration.
Common Questions
Frequently asked.
Specific to NetApp. For the broader Agent FAQ (auto-update, logging, bandwidth limits, etc.), see the Files.com Agent page.
Does this work with ONTAP cluster-mode and Vserver SVMs?
Yes. Mount the SVM's exported volume on the Agent host the same way any client would — through the SVM's LIF. The Agent reads or writes through the normal NFS/CIFS stack.
What about Snapshot copies and SnapMirror?
Mover migrates the current state of the volume. Historical snapshots are NetApp-side metadata and don't transfer to a cloud destination. If you need point-in-time copies on the cloud side, the destination's versioning feature (S3 versioning, etc.) is the right tool — not snapshot-equivalent semantics.
Can the Agent run on a NetApp-adjacent jumphost in a locked-down network?
Yes — this is the most common deployment. The Agent only makes outbound connections to the Mover/Files.com cloud, so it operates within the existing firewall posture. No inbound port changes required.
How do I throttle the Agent so the NetApp's production workload isn't affected?
The Agent's TOML config exposes transfer_rate_limit (bytes per second) and override_max_concurrent_jobs. Cap both to leave headroom for the NetApp's primary workload during business hours; run the bulk transfer overnight or on weekends.
Reached through the Files.com Agent
NetApp migrations run the same way as every other Agent setup.
The Agent is the same component across every on-prem or network-share source. Install once, point at a path, migrate to any of the 20+ Mover destinations.
Run a dry run before any data moves.
Connect NetApp via the Agent, run a free dry run, see the exact size, file count, and price.