Migrating Between Transfer Platforms
"Just move everything over." That is the whole ticket. Everyone who has done it knows that "everything" is where the weekend goes. A platform swap has two halves. The coordination half — partners, notice periods, cutover strategy, validation — is covered in our series on migrating transfer workloads. This series is the other half: the technical mechanics of carrying a server's contents and identity from one platform to another. The details are unforgiving and quietly so. Password hashes do not travel. The host key decides whether every partner sees a warning on the same morning. Permission models translate the way idioms do, roughly. And the inbox is still receiving files while you cut over.
Six articles follow the order the work happens. We start with what actually moves in a swap and what only looks as if it should. Then we cover migrating accounts and permissions without a password amnesty. Next, we move SSH keys and TLS certificates without breaking anyone's trust. Then we carry folder trees and live inboxes across under a freeze. Next comes the cutover-night runbook, written to be read at two in the morning. We finish with the cleanup, hardening, and decommission proof that let the old server finally go dark.
Articles in This Series
- What Actually Moves in a Transfer Platform Swap
The layers of a transfer server include accounts, permissions, keys and certificates, folders, jobs, endpoints, and history. The article maps them from old to new. It shows which ones move cleanly and which ones never do. - Migrating Accounts, Permissions, and Home Directories
The article covers export and import realities. It explains why password hashes cannot follow you and what to do instead. It covers directory-integrated authentication as the escape hatch, translating permission models, and verifying per-partner isolation on the new platform. - Migrating SSH Keys and TLS Certificates Between Platforms
The article compares carrying the host key with issuing a new one. It explains what each means for every partner's fingerprint prompt. It also covers authorized-key carry-over, moving certificates and private keys safely, and re-checking chains on the new platform. - Migrating Folder Structures and In-Flight Files
The article covers recreating the taxonomy, translating access rules, and the final delta of live inboxes. It explains freeze windows for arriving files. It also covers preserving the temp-name and marker conventions your partners rely on. - The Cutover Night: A Technical Runbook
The article covers address switching by alias or IP, firewall and passive port range changes, and service start order. It covers protocol-by-protocol smoke tests and the partner-visible changes to expect. It also covers the rollback switch you rehearsed. - Post-Migration: Cleanup, Hardening, and Decommission Proof
The article covers removing migration-era shortcuts and applying the hardening baseline to the new platform. It explains how to keep log continuity across the switch. It also covers the decommission checklist that lets the old server finally power off.
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.