FTP 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 FTP server with Mover. Most FTP migrations are about getting off it — pulling files from a legacy FTP server into modern cloud storage — and Mover handles that without scripts.

SourcesDestinations
Amazon S3
Amazon S3
Microsoft Azure Blob Storage
Azure Blob
Google Cloud Storage
GCS
Microsoft SharePoint
SharePoint
WebDAV
WebDAV
Amazon S3
Amazon S3
Azure Blob
Microsoft Azure Blob Storage
GCS
Google Cloud Storage
SFTP
SFTP
Files.com Agent
Files.com Agent
FTPFTP

The modernization move

Why FTP migrations happen

Most FTP migrations are about getting off it — a compliance review, an aging server, a partner finally accepting SFTP. Some are still partner-driven pushes. Hundreds of moves later, the inbound and outbound piles tell different stories.

Into FTP

Pushing deliveries to a partner who still requires FTP

Some long-standing B2B relationships still run on plain FTP. If a customer or vendor's intake server only speaks FTP, Mover delivers to it on schedule without a custom script.

Feeding a downstream tool that only knows FTP

Legacy applications and middleware that expect an FTP source get fed by Mover pulling from cloud and writing to a staging FTP.

Out of FTP

Decommissioning a legacy FTP server

The dominant FTP migration: retiring an aging FTP server into cloud storage. Move the data into S3, Azure Blob, GCS, SharePoint, or any other modern destination, then turn the FTP server off.

Modernizing to SFTP or a SaaS file platform

Compliance reviews regularly flag plain FTP as a finding — unencrypted, password-only, hard to audit. Migrating off it to SFTP or a managed file-sharing platform closes the finding.

Pulling files from a partner's FTP into cloud workflows

Partners who still run FTP can be a one-way source: Mover pulls from their FTP into your cloud destination on a schedule, even though your side runs entirely cloud-native.

Common pairings

Pair FTP with any cloud.

FTP 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.

01Method

Username + password

The standard method for FTP. Mover connects with the credentials you provide. FTP authentication is password-only — there is no key-based equivalent.

Scope:Mover connects to the host, port, and username you provide. Scope the FTP user's permissions on the server side to the specific directory you're migrating.
02MethodRecommended

FTPS (FTP over TLS)

Use FTPS if your server supports it. Wraps the FTP session in TLS to encrypt credentials and data in transit. Strongly preferred over plain FTP wherever possible.

Scope:Mover connects to the host, port, and username you provide. Scope the FTP user's permissions on the server side to the specific directory you're migrating.

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.

Migrating into FTP

Provider side

Free

your own server

Mover

$0.15 / GB

When purchasing a 10 TB pack

FTP doesn't charge a per-GB fee. The cost on the FTP side is whatever you pay for the server itself — hosting, bandwidth, whatever the FTP service costs you to run.

Migrating out of FTP

Provider side

Free

your own server

Mover

$0.15 / GB

When purchasing a 10 TB pack

Same as above. There is no egress fee on a generic FTP server.

Pricing example

10 TB migration to or from an FTP server

The exact dry-run estimate is the number to trust — it includes both line items, run against your actual data.

Mover fees
10 TB pack
$1,499
FTP server side
no per-GB transfer fees
$0
Total
$1,499

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.

01

Connect FTP.

Provide the host, port (usually 21 for plain FTP or 990 for implicit FTPS), username, and password. Mover validates the connection and lists the directories the FTP user can see.

02

Choose source and destination paths.

Apply filters and a date range if you want a partial migration.

03

Run a dry-run.

Mover walks the source, counts files, sizes the transfer, and produces an exact cost estimate.

04

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.

If you can avoid it, no. FTP is unencrypted by default — credentials and data travel in plain text. SFTP (over SSH) and FTPS (FTP over TLS) are both more secure and widely supported. If you're still on plain FTP, getting off it is the highest-leverage thing this Mover migration can do for you.

Start the move. finish.

Run a free dry run on your FTP data. See the exact size, file count, and price before you commit a single GB.