Migrate QNAP NAS
to or from any cloud.
QNAP Turbo NAS appliances are common in SMB and prosumer environments. The Agent connects them to Mover without inbound port changes.
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 QNAP, that means installing the Agent on a host that can reach the QNAP share, then pointing Mover at any of the supported cloud destinations on the other side.
When teams migrate QNAP
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 QNAPside runs through the Agent; the cloud side runs through Mover's native connectors.
Retiring a QNAP into the cloud
Out-of-warranty Turbo NAS units consolidating into S3, Azure Blob, GCS, OneDrive, or SharePoint as part of a hardware refresh or move to cloud-native operations.
Migrating QNAP to QNAP across sites
Replicating a QNAP's contents to a second QNAP at another office or data center as part of a refresh, relocation, or redundancy setup.
Hybrid: cloud-first plus QNAP archive
New data lives in the cloud; older or compliance-retained data archives to a QNAP. The Agent gives Mover a write path to the QNAP for the archive direction.
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.
Install the Agent.
Download the Files.com Agent for Windows, Linux, or macOS from your Mover account. Install on a host on the same network as the QNAP.
Mount the QNAP share on the Agent host.
Windows: map the QNAP SMB share (\\qnap-host\share). Linux: mount via cifs-utils or QNAP's native NFS export. macOS: mount via Finder (Cmd+K) or mount_smbfs / mount_nfs. The Agent reads or writes through the normal share.
Configure the Agent root.
Edit the Agent TOML config file, set the root path to the mounted share location. Start the Agent as a service.
Run a dry run.
Create a Files.com Agent connection in Mover, select the registered agent, run a dry run for the exact-cost estimate before launching.
Common Questions
Frequently asked.
Specific to QNAP. For the broader Agent FAQ (auto-update, logging, bandwidth limits, etc.), see the Files.com Agent page.
Does the Agent need to run on the QNAP itself?
No. The Agent runs on a Windows, Linux, or macOS host that has network access to the QNAP. QNoyAP's native OS doesn't need to run any additional software.
What about QNAP Surveillance Station files or other app-specific data?
Anything stored as a file under the share is migrated. Application-specific databases (Surveillance Station's recording index, QNAP's photo library metadata) stay attached to the QNAP — only the underlying media files transfer.
Can I throttle the Agent so it doesn't saturate the network?
Yes. The Agent's TOML config has a transfer_rate_limit option — set it to a byte-per-second cap that fits your network. Useful for migrations running during business hours.
How long does a multi-TB QNAP migration typically take?
Bottlenecked by whichever is slower: the QNAP's read rate, the network link to the Agent host, or the cloud destination's ingest rate. For typical 1 GbE setups, plan for 1-3 TB per business day; for 10 GbE links, considerably faster.
Reached through the Files.com Agent
QNAP NAS 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 QNAP via the Agent, run a free dry run, see the exact size, file count, and price.