American Psychiatric Association Replaces Its Progress MOVEit Book-Order Relay—and the Scripts Behind It—with Files.com

The American Psychiatric Association is the oldest medical association in the United States, founded before the AMA, and the largest psychiatric association in the world, representing 39,000 physician members. Its best-known product is a book: the Diagnostic and Statistical Manual of Mental Disorders, which APA has published since 1952 and which defines how mental disorders are diagnosed. Publishing is the association's largest operating department and one of its main revenue drivers, producing books and journals that include the American Journal of Psychiatry, the most widely read psychiatric journal in the world.

APA does not print, bind, warehouse, or bill for those books itself. Six external vendors do: the vendor that runs the e-commerce storefront, the printers and fulfillment houses that produce and ship the orders, and the vendor that handles billing. Those companies have no relationship with one another. Every book order has to be relayed between them, and APA sits in the middle as the intermediary they all connect to.

But the pipeline that moved APA's publishing revenue depended on an aging Progress MOVEit automation server and script logic that only its author fully understood, documented nowhere except a spreadsheet. APA expected the vendor network to grow beyond six connections, and every new connection would have meant more scripts, more spreadsheet rows, and more logic in one administrator's head.

The Relay Ran on MOVEit, Scripts, and a Spreadsheet

Around MOVEit sat a pile of custom scripts and scheduler jobs that carried the actual logic: which files to pick up, how to rename them, and where each copy had to go. The details of every job lived in an Excel spreadsheet.

“They don't trust each other or they don't really know about each other. They don't really have a relationship. We are the relationship.”

The relay also carried security debt that had survived for years because there was never a project to hang a fix on: one vendor connection ran over unencrypted FTP, moving order data across the internet in plaintext, and another vendor had spent years logging in with APA's own credentials. On that endpoint, APA could not tell its own activity from the vendor's.

None of this was easy to replace. The counterparties are publishing and fulfillment companies, not IT organizations, and some do not control their own transfer endpoints. APA could not dictate the other side of any connection. A replacement had to reproduce the per-job filtering, renaming, scheduling, and archiving exactly, speak the SFTP and FTP those vendors already ran, and ask nothing of them.

APA selected Files.com to be the new hub of the relay.

Every Job Proven Against a Mock Vendor Network Before Cutover

Cesar Pocai did not cut over blind. He stood up an FTP server on site, with folders mimicking each vendor endpoint, and rebuilt every production job as a Files.com Automation against that mock network: the file renaming, the weekday schedules, and the filtering logic that selects only that day's order files. Every automation was proven working before any business unit or vendor was involved.

The rollout then ran in sequence. Internal divisions were shown the new system first. Then each vendor was given the new source IP addresses to clear through its firewall, because the trust in this arrangement runs in one direction only: the vendors do not fully trust APA either, and their access lists admit nothing they have not been told about. Production cutover followed in July 2026.

The automations reproduce the relay exactly. Scheduled Move automations pull order files from the storefront vendor and deliver them downstream to the fulfillment vendors, with confirmations routed onward to billing. Each run applies the required filtering and file naming, while retaining an archive copy so APA has a record whenever a vendor disputes what was sent.

The cutover was also the moment the security debt got retired. One fulfillment vendor stood up an SFTP endpoint, and the last unencrypted connection in the relay closed. The vendor that had shared APA's credentials for years received its own account, authenticating with a key.

What Retired With MOVEit

With the Files.com automations in production, APA replaced an automation server, a pile of scripts, and a spreadsheet of job logic with a relay it can see.

• Progress MOVEit and the custom scripts around it are gone. APA confirmed the migration complete in July 2026.
• Every relay job now runs as a logged Files.com Automation. The schedule, the files touched, and the outcome of every run are on the record, instead of in script logic documented in a spreadsheet.
• Order data no longer crosses the internet in plaintext, and no vendor signs in with APA's credentials.

The compounding result is what the growth ahead now costs. APA can add another fulfillment connection by repeating an existing pattern—a scheduled automation pointed at a new endpoint—rather than adding another script and another spreadsheet row. The relay that supports book order fulfillment can grow past six vendors without growing the pile of machinery underneath it.

The Migration Was the Moment the Debt Got Paid

A legacy MFT relay held together by scripts does not have to be replaced blind. Rebuilt job by job on Files.com and proven against a mock vendor network, it was already working before the first real order file moved. The migration turned out to be the one project big enough to carry the fixes nobody could justify on their own.