Retiring Plain FTP

Somewhere on your network there is a server that was installed as a temporary measure, and it is still temporary. Plain FTP predates most of the people now asked to retire it. It sends usernames, passwords, and file contents across the network unencrypted. It survives anyway, held in place by old scripts, devices that speak FTP and nothing else, and partners nobody wants to call. Retiring it is rarely a technical challenge. It is a discovery and coordination project wearing a technical costume.

This series is the coordination playbook. It covers making the case in language leadership funds and finding every plain-FTP flow you own (including the ones nobody remembers). It covers sequencing the retirement so early wins build momentum and moving partners without drama. It explains how to contain the devices that can never upgrade. It also covers proving at the end that cleartext is actually gone rather than merely quiet. The hands-on protocol conversion lives in our migration guide. This series gets the organization through it, and gets the temporary server, at long last, retired.

Articles in This Series

• Why Plain FTP Has to Go (and How to Say It)
  The cleartext problem made concrete, compliance and insurance pressure, and a business case template written in risk language leadership acts on.
• Finding Every Plain-FTP Flow You Own
  Port scans, firewall log mining, and the script-and-scheduled-task sweep — building the retirement inventory, including the shadow FTP nobody documented.
• The FTP Retirement Plan: Sequence and Timeline
  Grouping flows by owner and partner, sequencing easy wins first, parallel-run strategy, and setting a shutdown date that actually holds.
• Moving Partners Off FTP: Communication That Works
  Notice templates, offering the new endpoint with test windows, tracking partner progress, and handling the laggards without burning bridges.
• When a Device Only Speaks FTP: Containment
  The scanner or instrument that will never learn SFTP — isolation segments, the local-drop-and-secure-relay pattern, and documented risk acceptance.
• Proving Plain FTP Is Actually Gone
  Final verification scans, disabling with monitoring for reappearance, closing the loop with compliance, and keeping it gone.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.