A Lifestyle Apparel Brand Replaced Its FTP Server and Cron Jobs With Files.com Without Missing a Just Enough Planning Cycle

A US lifestyle apparel brand, one of several labels in an apparel group, sells men's and women's sportswear through its own stores, e-commerce, and wholesale.

A retail operation at that scale runs on weekly data. Sales, inventory, and order files move constantly between the distribution center, the stores, the e-commerce platform, and the vendors who turn that data into merchandise decisions. At the brand, ten vendor and internal file exchanges ran through a single on-premises FTP/SFTP server in the corporate data center. The most consequential fed Just Enough, the planning system that helps steer purchases years ahead. The brand moved all ten exchanges to Files.com without missing a weekly planning cycle, then closed the inbound firewall paths behind them.

Ten Directories of Vendor Exchange, Held Together by Hand

The server carried ten directories of vendor and internal file exchange. Around it sat a layer of hand-written machinery: bash scripts on cron jobs, firing three times an hour from 2 a.m. to 9 p.m., pushing files to vendors, pulling responses back, enumerating batches, cleaning up old data, and sending alerts through Postfix. Vendors connected inbound through holes in the corporate firewall. Security policy required rotating every vendor password every 90 days, and each rotation meant the network administrator personally emailing every vendor in advance. He wrote a two-phase notification script just to manage the emails.

The estate worked, but only because its administrators kept it working by hand. The scripts were aging, the knowledge of how they fit together lived in the people who wrote them, and the inbound firewall paths stayed open the whole time. Then corporate IT issued a mandate: the on-prem server had to move to a cloud environment.

The Feed That Steers Purchases Two Years Out

The mandate would have been simple except for what the server's most complex directory carried: the feed to Just Enough, the brand's demand-planning system.

Every week, that data drove a 6 to 8 hour overnight processing run on the vendor's side, with exception reports flowing back for automatic retrieval. The feed could not break, and the calendar made caution mandatory: a retail holiday change freeze from early November to mid-January ruled out production cutovers for months at a stretch.

So the replacement had a specification before it had a name. It had to present the same SFTP interface the vendors already connected to, accept the same keys, run the scripted push-pull-cleanup logic without scripts, and connect outbound only, so the firewall could finally close. Rebuilding all of that in-house was possible on paper, and the team knew exactly what that would cost.

The brand's network team selected Files.com to take the estate over.

One Directory Every Two Weeks, Hardest First

The migration was deliberately conservative: roughly one directory every two weeks, starting with the most complex one, the Just Enough exchange. Directory structures were replicated on Files.com ahead of each cutover, and data owners were consulted about pruning before anything moved.

The critical feed was proven in parallel while the legacy path stayed live. Test-account validation ran through the holiday freeze, and production cutover happened once it lifted without interrupting the weekly planning cycle.

Bash Scripts Became Automations, With SSH Keys Where Supported

On the platform side, each vendor got its own Files.com account jailed to its own root folder, so no partner can see past its own exchange. Files.com Automations took over the transfer and routing logic the cron jobs used to run, retention and folder-expiration settings replaced the cleanup scripts, and Files.com email notifications on uploads and expiring credentials replaced the Postfix alerting bolted onto the old scripts.

Authentication moved with it. Vendors that support SSH keys were moved onto keys, which the brand's security policy rotates every two years instead of every 90 days.

The Server Is Off and the Firewall Is Closed

With the last directory cut over, the brand retired the on-prem server and replaced an estate of hand-maintained scripts with a managed platform.

• All ten vendor and internal exchanges run on Files.com, connecting outbound only. No inbound firewall opening remains for file transfer.
• The demand-planning feed never missed a cycle through the migration. Weekly sales, inventory, and planning data flows to Just Enough and exception reports come back automatically, with no script in the path.
• For vendors moved to SSH keys, credential upkeep dropped from a 90-day password rotation, each round requiring vendor emails, to keys rotated every two years.
• Onboarding the next vendor exchange is an account, a jailed folder, and an automation, not a firewall request and another script for someone to maintain.

Vendor File Exchange Without a Server to Keep Alive

Vendor file exchange at the brand used to mean a server to patch, open paths through the corporate firewall, and a library of cron jobs that only their authors fully understood. Now the same feeds run on Files.com, supported vendors can move from quarterly password emails to two-year SSH-key rotations, and the data that decides what the brand will stock two years from now moves every week without anyone watching it go.