Guide

Migrating from FileZilla Server to cloud storage

FileZilla Server keeps files on a Windows box's local disk. Here's how to move to managed SFTP backed by your own cloud bucket, with a one-time file copy and no server to run.

FileZilla Server is a free, capable FTP/SFTP server, but it has one structural limit: it runs on a Windows machine and stores files on that machine’s local disk. That means you own the box, the patching, the backups, and the capacity planning, and your file drop-zone is only as durable as one server. Moving the storage to a cloud bucket (and the server to a managed gateway) removes all of that.

Here’s how to migrate without disrupting your partners.

What you’re moving from and to

  • From: FileZilla Server on Windows, files on local disk, you operate everything.
  • To: a managed SFTP gateway in front of a cloud bucket you own (Amazon S3, Azure Blob, Google Cloud Storage, or S3-compatible). Files gain cloud durability; you run no server.

One difference to weigh up front: FileZilla Server speaks FTP and FTPS as well as SFTP. Firepipe is SFTP only. If a partner can only use FTP/FTPS, factor that in before switching.

Step 1, pick and create a bucket

Choose where the files should live: an S3, Azure Blob, GCS, or S3-compatible bucket in an account you own. Keep it private.

Step 2, copy your existing files up (one-time)

Move what’s currently on the FileZilla Server’s local directories into the bucket once, preserving your folder layout so each user’s prefix matches their old home directory:

# Amazon S3
aws s3 sync "C:\FileZilla\users" s3://your-bucket/ --exclude "*.tmp"

# Azure Blob
azcopy copy "C:\FileZilla\users\*" "https://acct.blob.core.windows.net/container" --recursive

# Anything (S3/Azure/GCS/S3-compatible)
rclone copy "C:\FileZilla\users" remote:your-bucket

Step 3, connect the bucket to the gateway

Point Firepipe at the bucket. For S3 you grant a scoped cross-account role; for Azure, GCS, and S3-compatible stores you provide a scoped access key that’s stored encrypted and is revocable at any time.

Step 4, recreate your users

For each FileZilla user, create a Firepipe SFTP credential (SSH key or password) and path-jail it to the prefix that matches their old home directory. Each partner lands in the same place they’re used to.

Step 5, repoint clients and cut over

Hand each partner the new hostname and credential. Run both in parallel briefly if you can, then once traffic has moved, stop the FileZilla Server service and retire the Windows box.

What you gain

  • No server to run. No Windows patching, no disk to fill, no single point of failure.
  • Cloud-durable storage in a bucket you own, with nothing custodied on the gateway side.
  • Per-user credentials, path jails, and an exportable audit trail out of the box, plus instant revoke and optional source-IP pinning per credential.

See the SFTP to S3 walkthrough, or how to give a client SFTP access to your bucket for the access model in more depth.

Try it on your own bucket

Connect a bucket you already own, Amazon S3, Azure Blob, Google Cloud Storage, or an S3-compatible store, and hand out a clean SFTP endpoint in minutes. Your files stay in your cloud.

Start free

← All guides