File server to Google Drive,
without opening a port.
Teams retiring a file server land its shares in Google Drive shared drives without a staging copy, a VPN, or an inbound firewall rule.
Mover moves file servers to Google Drive through the Files.com Agent. Install the Agent on a host that can reach the share, authorize Google Drive, pick the folders, run a free dry run. The first byte moves only after you see the price.
From
Files.com Agent
To
Google Drive
Why teams move a file server to Google Drive.
The file server is the last on-premises box in a company that already runs on Google Workspace. Its shares move to shared drives, and the box gets turned off.
Retiring the last server in the office
Patching, backups, a lapsed warranty, and the disk that will fail on a Saturday. Once the shares are in Google Drive the machine is powered down and the risk goes with it.
Shares that only work in the building
A mapped drive works at a desk and over a VPN. A shared drive works anywhere the team signs in. Remote and multi-office teams move the shares to where they can actually reach them.
One place for files in a Workspace company
Identity, mail, and documents already live in Google Workspace. The file server is the one system outside it, with its own permissions and its own backup. Moving the data closes the gap.
Storage priced per gigabyte instead of per appliance
A NAS is bought in units of hardware; Google Drive pooled storage is bought in units of gigabytes. Cold shares and archives cost far less in the pool than on a maintained appliance.
4 steps to Go.
From credential to first byte in a handful of clicks. The dry-run is free, every time, and shows the exact cost before you commit a byte.
Install the Files.com Agent.
Install the Agent on a Windows, Linux, or macOS host that can reach the share — the file server itself, or any machine on the same network. It connects outbound to Mover; no inbound firewall change, no VPN.
Connect Google Drive.
Sign in to Google Workspace through Mover with an account that has rights to the destination shared drives. Mover writes to shared drives and to My Drive.
Run a free dry run.
Mover walks the share through the Agent, counts files, sums bytes, and tells you the exact cost. The dry run is free, every time. You see the number before any data moves.
Launch the migration.
Live progress, automatic retries, and a structured log of every file moved. Run the bulk pass while people keep working on the share, then re-run to pick up what changed before you cut over.
The pricing math, honestly.
A file server charges no egress. Google Drive charges no ingress. The only line item is Mover — as low as $0.15/GB on a 10 TB pack. The dry run shows the exact total before you commit.
5 TB file server → Google Drive migration
The dry run is what to trust — it runs against your actual share and reflects the actual pack size you need.
Frequently asked.
Most teams launch their first migration in under 15 minutes. The dry run is free, every time.
Mover migrates file content and folder structure. NTFS access-control lists and Google Drive sharing are different models, so permissions do not transfer 1:1 — land each share in a shared drive and attach the right Google group to it. The data is what Mover moves; access is what Google Workspace owns.
Folder hierarchy is preserved. Google Drive accepts the original modified time on upload, so file modification timestamps carry across intact.
Yes. Run the bulk pass while the share stays in use, then re-run: Mover compares source and destination and moves only what is new or changed. When the delta is small, point people at the shared drive and run one last pass.
Yes. After the Agent is connected, pick the specific paths to include. Filters and date ranges let you narrow it further — useful for staging the move one department at a time, or for leaving an archive behind.
It depends on the size, your office uplink, and Google Drive API rate limits, which Mover respects automatically. The dry run gives you the size; the Agent runs the bulk pass over as many days as the uplink needs, and the final incremental pass takes minutes.
Transient failures are retried automatically. Anything that cannot be transferred — typically a path that exceeds Google Drive limits or a file locked by an application — is logged and reported, so you can review and remediate before turning the server off.
Move the file server to Google Drive before you turn it off.
Install the Agent, connect Google Drive, run a free dry run, and see the exact cost before a single byte moves. Migrate when you are ready.