{"id":366,"date":"2026-11-10T08:50:00","date_gmt":"2026-11-10T08:50:00","guid":{"rendered":"https:\/\/backendside.com\/blog\/?p=366"},"modified":"2026-11-21T12:05:22","modified_gmt":"2026-11-21T12:05:22","slug":"migrating-off-plain-ftp-checklist","status":"publish","type":"post","link":"https:\/\/backendside.com\/blog\/2026\/11\/10\/migrating-off-plain-ftp-checklist\/","title":{"rendered":"Moving Off Plain FTP: A Migration Checklist for Small Teams"},"content":{"rendered":"<p class=\"lead\">In a lot of small businesses, plain FTP is the system nobody chose and nobody wants to touch. It was set up years ago for the web designer, the scanner that drops PDFs on a server, or the supplier who uploads price lists every Monday &mdash; and it still sends every password in cleartext. Turning it off is rarely hard technically. What makes it stall is not knowing who depends on it. This checklist walks a small team through the whole move, from inventory to finally closing port 21.<\/p>\n<p>If you need the background on why plain FTP is a risk and how the secure alternatives differ, read our overview of <a href=\"https:\/\/backendside.com\/blog\/2026\/06\/23\/ftp-ftps-and-sftp-in-2026-choosing-a-secure-file-transfer-client-for-the-ai-era\/\">FTP, FTPS and SFTP in 2026<\/a> first. This post is purely the practical &ldquo;how do we actually get off it&rdquo; plan.<\/p>\n<h2>Phase 1: Inventory &mdash; find out who really uses FTP<\/h2>\n<p>The single biggest migration risk is the forgotten user: the device or partner that breaks silently on cutover day. Spend real time here.<\/p>\n<ul>\n<li><strong>List every account<\/strong> on the FTP server, including ones that look unused.<\/li>\n<li><strong>Read the logs<\/strong> for the last 60&ndash;90 days to see who actually logs in, from where, and how often. Monthly and quarterly jobs are easy to miss with a shorter window.<\/li>\n<li><strong>Classify each user<\/strong>: a person with a desktop client, a script or scheduled job, a device (scanner, camera, CNC machine, backup appliance), or an external partner.<\/li>\n<li><strong>Note what each one needs<\/strong>: upload only, download only, or both; which folders; any automation that must keep working.<\/li>\n<\/ul>\n<p>A quick way to summarise logins on a Linux server running vsftpd:<\/p>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code># Successful logins per user and client IP (vsftpd default log format)\ngrep \"OK LOGIN\" \/var\/log\/vsftpd.log \n  | sed -E 's\/.*[([^]]+)] OK LOGIN: Client \"([^\"]+)\".*\/1 2\/' \n  | sort | uniq -c | sort -rn<\/code><\/pre>\n<p>Write the results into a simple table &mdash; user, type, owner, protocol it can support, status &mdash; and keep it as your migration tracker.<\/p>\n<h2>Phase 2: Choose the destination protocol<\/h2>\n<table>\n<thead>\n<tr>\n<th>Situation<\/th>\n<th>Recommended<\/th>\n<th>Why<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>You control the server and it has SSH<\/td>\n<td>SFTP<\/td>\n<td>One port (22), key-based login, no data-channel firewall issues<\/td>\n<\/tr>\n<tr>\n<td>Shared hosting with FTP accounts but no SSH<\/td>\n<td>Explicit FTPS<\/td>\n<td>Same accounts, now encrypted; insist on encrypted data too<\/td>\n<\/tr>\n<tr>\n<td>A device that only supports FTP or FTPS<\/td>\n<td>FTPS, or an isolated FTP drop<\/td>\n<td>Keep it on a separate, firewalled account and network segment<\/td>\n<\/tr>\n<tr>\n<td>External partners with their own automation<\/td>\n<td>SFTP with keys<\/td>\n<td>The most widely supported secure option in scripts and integration tools<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For most teams the answer is SFTP for people and scripts, with FTPS reserved for the odd device or host that cannot do SSH.<\/p>\n<div style=\"border:1px solid #c5d3f8;background:linear-gradient(135deg,#eef2fd 0%,#ffffff 72%);border-radius:14px;padding:1.5rem 1.65rem;margin:2rem 0;\">\n<div style=\"font-size:.7rem;font-weight:700;letter-spacing:.08em;text-transform:uppercase;color:#2d5be3;margin-bottom:.55rem;\">&#128295; BackendSide Tool<\/div>\n<h4 style=\"margin:0 0 .45rem;font-size:1.15rem;color:#1a1916;font-weight:700;\">BackendsideFTP &mdash; One Free Client for Every Protocol You&rsquo;re Migrating Between<\/h4>\n<p style=\"margin:0 0 1.05rem;color:#3d3c38;font-size:.92rem;line-height:1.65;\">During a migration you need the old server and the new one open at the same time. <strong>BackendsideFTP<\/strong> connects over plain FTP, FTPS (explicit or implicit TLS) and SFTP, with as many servers as you like in <strong>tabs<\/strong>, and drag-and-drop in both directions &mdash; drop a folder and the whole tree comes along. It is free on the Microsoft Store, with no subscription and no ads, so standardising the whole team on it costs nothing.<\/p>\n<p>  <a href=\"https:\/\/backendside.com\/backendsideftp.php\" style=\"display:inline-flex;align-items:center;gap:.4rem;background:#2d5be3;color:#ffffff;font-weight:600;font-size:.85rem;padding:.6rem 1.2rem;border-radius:6px;text-decoration:none;\">Explore BackendsideFTP &rarr;<\/a>\n<\/div>\n<h2>Phase 3: Build the new service properly<\/h2>\n<p>If you are setting up SFTP on a Linux server, OpenSSH already includes it. Lock file-transfer users into their own folder and deny them a shell:<\/p>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code># \/etc\/ssh\/sshd_config\nSubsystem sftp internal-sftp\n\nMatch Group sftpusers\n    ChrootDirectory \/srv\/sftp\/%u\n    ForceCommand internal-sftp\n    AllowTcpForwarding no\n    X11Forwarding no\n    PasswordAuthentication no      # keys only for this group<\/code><\/pre>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code>sudo groupadd sftpusers\nsudo useradd -g sftpusers -s \/usr\/sbin\/nologin supplier1\nsudo mkdir -p \/srv\/sftp\/supplier1\/upload\nsudo chown root:root \/srv\/sftp\/supplier1          # chroot dir must be root-owned\nsudo chown supplier1:sftpusers \/srv\/sftp\/supplier1\/upload\nsudo sshd -t &amp;&amp; sudo systemctl reload ssh<\/code><\/pre>\n<p>Checklist for this phase:<\/p>\n<ul>\n<li><strong>One account per person or system<\/strong>, never a shared login &mdash; it is the only way to revoke access cleanly later.<\/li>\n<li><strong>Keys over passwords<\/strong> wherever possible. Each user generates a key pair and sends you only the public half for <code>authorized_keys<\/code>.<\/li>\n<li><strong>Least privilege<\/strong>: upload-only partners get an upload folder, nothing else.<\/li>\n<li><strong>Publish the host key fingerprint<\/strong> to your users through a separate channel (your intranet, a signed email) so they can verify it on first connect.<\/li>\n<li><strong>Back up first.<\/strong> Copy the existing FTP data before you start moving folders around.<\/li>\n<\/ul>\n<p>Generating a key on a Windows 10 or 11 machine needs no extra software &mdash; the OpenSSH client is built in:<\/p>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code>ssh-keygen -t ed25519 -C \"anna@yourcompany\"\n# then send ONLY the .pub file to the server admin\ntype %USERPROFILE%.sshid_ed25519.pub<\/code><\/pre>\n<div style=\"border:1px solid #c5d3f8;background:linear-gradient(135deg,#eef2fd 0%,#ffffff 72%);border-radius:14px;padding:1.5rem 1.65rem;margin:2rem 0;\">\n<div style=\"font-size:.7rem;font-weight:700;letter-spacing:.08em;text-transform:uppercase;color:#2d5be3;margin-bottom:.55rem;\">&#128295; BackendSide Tool<\/div>\n<h4 style=\"margin:0 0 .45rem;font-size:1.15rem;color:#1a1916;font-weight:700;\">BackendsideFTP &mdash; SSH Keys and Host-Key Trust Without the Terminal<\/h4>\n<p style=\"margin:0 0 1.05rem;color:#3d3c38;font-size:.92rem;line-height:1.65;\">Non-technical colleagues should not need a command line to use SFTP. In <strong>BackendsideFTP<\/strong> they log in with a password or an <strong>SSH private key (with passphrase)<\/strong>, including servers that only allow keyboard-interactive login. The server&rsquo;s host key is checked against a known-hosts store with a plain <strong>Trust once \/ Trust always \/ Reject<\/strong> prompt and a warning if it ever changes, and saved site passwords are encrypted with their Windows account &mdash; never written to disk in plain text.<\/p>\n<p>  <a href=\"https:\/\/backendside.com\/backendsideftp.php\" style=\"display:inline-flex;align-items:center;gap:.4rem;background:#2d5be3;color:#ffffff;font-weight:600;font-size:.85rem;padding:.6rem 1.2rem;border-radius:6px;text-decoration:none;\">Explore BackendsideFTP &rarr;<\/a>\n<\/div>\n<h2>Phase 4: Run both side by side<\/h2>\n<p>Do not do a &ldquo;big bang&rdquo; cutover. Keep the old FTP service running while you move users across in small groups:<\/p>\n<ol>\n<li><strong>Pilot with your own team<\/strong> for a week. Fix the paper cuts &mdash; permissions, folder layout, key formats &mdash; before anyone external sees it.<\/li>\n<li><strong>Move internal people next<\/strong>: give each one their new site details, help them connect once, and confirm they can see their files.<\/li>\n<li><strong>Update scripts and scheduled jobs<\/strong>, testing each one against the new server and watching its next real run.<\/li>\n<li><strong>Contact external partners<\/strong> with a clear date, the new host, port and fingerprint, and an offer to help test. Give them weeks, not days.<\/li>\n<li><strong>Tick each row off<\/strong> in your inventory table only after you have seen that user succeed on the new service.<\/li>\n<\/ol>\n<p>If files need copying from the old server to the new one, do it in passes: a bulk copy early, then a final catch-up of anything changed just before each group switches.<\/p>\n<h2>Phase 5: Cut over and switch FTP off<\/h2>\n<ul>\n<li><strong>Disable, don&rsquo;t delete.<\/strong> Turn off each migrated FTP account individually as its owner moves, and watch the logs for failed logins &mdash; those are the users you missed.<\/li>\n<li><strong>Announce a final date<\/strong> and stick to it. Leave the server running but with FTP stopped for a couple of weeks so you can roll back a single account if needed.<\/li>\n<li><strong>Close the port<\/strong> once logs are quiet:<\/li>\n<\/ul>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code>sudo systemctl disable --now vsftpd\nsudo ufw delete allow 21\/tcp\nsudo ufw delete allow 50000:50100\/tcp       # the old passive range\nsudo ss -tlnp | grep ':21 '                 # should print nothing<\/code><\/pre>\n<ul>\n<li><strong>Rotate every password<\/strong> that was ever used over plain FTP. Assume it has been seen. If the same password was reused for email or a control panel, change those too.<\/li>\n<li><strong>Update documentation<\/strong> &mdash; onboarding guides, supplier instructions, internal wikis &mdash; so nobody sets up a new FTP account out of habit.<\/li>\n<\/ul>\n<h2>Common snags<\/h2>\n<ul>\n<li><strong>The device that only speaks FTP.<\/strong> Put it on its own account, restricted to one folder and only reachable from the local network, and plan a hardware replacement.<\/li>\n<li><strong>&ldquo;Permission denied&rdquo; on upload in a chroot.<\/strong> The chroot folder itself must be owned by root; give the user a writable sub-folder inside it.<\/li>\n<li><strong>Partners with key format errors.<\/strong> Some older tools export keys in a different format; ask for the public key as a single <code>ssh-ed25519 &hellip;<\/code> or <code>ssh-rsa &hellip;<\/code> line.<\/li>\n<li><strong>Corporate firewalls blocking port 22 outbound.<\/strong> Rare, but it happens. Explicit FTPS on port 21 is the fallback.<\/li>\n<\/ul>\n<div style=\"border:1px solid #c5d3f8;background:linear-gradient(135deg,#eef2fd 0%,#ffffff 72%);border-radius:14px;padding:1.5rem 1.65rem;margin:2rem 0;\">\n<div style=\"font-size:.7rem;font-weight:700;letter-spacing:.08em;text-transform:uppercase;color:#2d5be3;margin-bottom:.55rem;\">&#128295; BackendSide Tool<\/div>\n<h4 style=\"margin:0 0 .45rem;font-size:1.15rem;color:#1a1916;font-weight:700;\">BackendsideFTP &mdash; Big Copies You Can Trust<\/h4>\n<p style=\"margin:0 0 1.05rem;color:#3d3c38;font-size:.92rem;line-height:1.65;\">Moving a whole site or shared folder? <strong>BackendsideFTP<\/strong> puts every upload and download in one unified queue with live progress and speed, <strong>pause and resume<\/strong> that picks up where it left off, automatic retries (0&ndash;10 times, your choice), <strong>Retry all<\/strong> for every failure in one click, and a marker that tells you exactly why a file failed or was skipped. Choose whether existing files are overwritten, skipped or renamed, and use the visual <strong>CHMOD editor<\/strong> to fix permissions afterwards.<\/p>\n<p>  <a href=\"https:\/\/backendside.com\/backendsideftp.php\" style=\"display:inline-flex;align-items:center;gap:.4rem;background:#2d5be3;color:#ffffff;font-weight:600;font-size:.85rem;padding:.6rem 1.2rem;border-radius:6px;text-decoration:none;\">Explore BackendsideFTP &rarr;<\/a>\n<\/div>\n<h2>Key takeaways<\/h2>\n<ul>\n<li><strong>Inventory first.<\/strong> Two to three months of logs reveal the scripts, devices and partners that would otherwise break silently.<\/li>\n<li><strong>Default to SFTP<\/strong> for people and scripts; use explicit FTPS only where SSH is not available.<\/li>\n<li><strong>One account per user, keys over passwords, least privilege<\/strong> &mdash; and publish the host key fingerprint out of band.<\/li>\n<li><strong>Migrate in groups with both services running<\/strong>, ticking users off only after you have seen them succeed.<\/li>\n<li><strong>Disable accounts one by one, watch for failed logins, then close port 21<\/strong> and rotate every password that ever crossed plain FTP.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Plain FTP is still quietly running in plenty of small businesses. This step-by-step checklist covers inventorying who uses it, choosing SFTP or FTPS, setting up accounts and SSH keys, running both side by side, cutting over and finally switching port 21 off.<\/p>\n","protected":false},"author":1,"featured_media":435,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,8],"tags":[41,39,42,50,40,51],"class_list":["post-366","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-networking","category-security","category-tutorials","tag-backendsideftp","tag-ftp","tag-ftps","tag-migration","tag-sftp","tag-ssh-keys"],"_links":{"self":[{"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/posts\/366","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/comments?post=366"}],"version-history":[{"count":1,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/posts\/366\/revisions"}],"predecessor-version":[{"id":436,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/posts\/366\/revisions\/436"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/media\/435"}],"wp:attachment":[{"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/media?parent=366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/categories?post=366"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/tags?post=366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}