SFTP migrations,
without legacy pain.
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 any SFTP server with Mover. Pull files from a partner's SFTP, push deliveries to one, or retire an aging SFTP server into modern cloud storage — all without writing scripts.
SFTPWhat's in the SFTP migrations
Why SFTP migrations happen
B2B file exchange runs on SFTP everywhere. Most migrations are either retiring an aging SFTP server into modern storage, or pulling files from a partner's SFTP into a cloud pipeline. Hundreds of executed moves; the patterns are consistent.
Pushing deliveries to a partner's SFTP server
B2B file exchange runs on SFTP everywhere. Customers, vendors, banks, and trading partners all have SFTP servers expecting your data on a schedule. Mover handles the push without a custom script.
Backing up cloud data to an SFTP archive
Some compliance regimes require offline or self-hosted copies. Mover pushes cloud-resident data to an SFTP target on your network or your DR site.
Staging data on an SFTP server for downstream tools
Legacy tools that only know SFTP get fed by Mover pulling from cloud sources and writing to a staging SFTP.
Pulling files from a partner's SFTP server
The other side of B2B exchange. Customers, vendors, and partners drop files for you on their SFTP servers; Mover pulls them on a schedule into wherever they belong.
Retiring an old SFTP server into cloud storage
Modernizing off a self-hosted SFTP appliance, an aging Linux box, or a vendor-managed SFTP server into S3, Azure Blob, GCS, or a SaaS file platform.
Consolidating data from many SFTP sources into one cloud destination
Some workflows have data scattered across dozens of partner SFTPs; Mover pulls from each and consolidates into a single destination bucket or library.
Common pairings
Pair SFTP with any cloud.
SFTP 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.
Connection
How Mover connects.
Mover supports 2 standard IETF authentication methods. Pick the one that matches how your team manages credentials.
Username + password
The simplest method. Mover connects with the credentials you provide. Recommended only when the SFTP server doesn't support key-based auth.
Username + SSH key
Recommended for production. Generate or upload an SSH private key; Mover authenticates against the server's matching public key. Stronger than password auth and rotatable without changing the username.
The price
The pricing math, honestly.
Mover charges as low as $0.15 / GB when purchasing a 10 TB pack. Your IETF-side cost depends on direction. No invoice math, no surprises — the dry-run shows the exact number before you commit.
Provider side
your own server
Mover
When purchasing a 10 TB pack
SFTP doesn't charge a per-GB fee — the cost on the SFTP side is whatever you pay for the server itself (hosting, bandwidth, the SFTP service if you use a managed one like Files.com's SFTP service).
Provider side
your own server
Mover
When purchasing a 10 TB pack
Same as above. There is no egress fee on a generic SFTP server; you pay for what you've already provisioned.
Pricing example
10 TB migration to or from an SFTP server
The exact dry-run estimate is the number to trust — it includes both line items, run against your actual data.
Getting started
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 SFTP.
Provide the host, port (usually 22), username, and either a password or an SSH private key. Mover validates the connection and lists the directories the SFTP user can see.
Choose source and destination paths.
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.
Launch.
Live progress, automatic retries on transient failures. Pause, resume, or cancel at any time.
Common Questions
Frequently asked.
Most teams launch their first migration in under 15 minutes. The dry run is free, every time.
Host, port (usually 22), username, and either a password or an SSH private key. SSH key auth is recommended for production. The SFTP user needs read or write access to the directory you're migrating, depending on direction.
Start the move. finish.
Run a free dry run on your SFTP data. See the exact size, file count, and price before you commit a single GB.