An Automotive Dealer Group Uses Files.com to Retire the FTP Server Its Vendors Kept On-Premises

A regional automotive dealer group operates dozens of sales and service locations across two US states and carries several franchise brands.

A dealer group at that scale runs on vendor data. Leads come in from marketing platforms. Inventory goes out to listing sites. Appointments move between the CRM and the tools each rooftop depends on. The group's IT team keeps its CRM and dealer management systems connected to the automotive vendor stack: VinSolutions, CDK, eLead, Autotrader, HomeNet, CarWars, Text2Drive. Those connections move as files, every day.

For years, every one of those files passed through a single self-hosted FTP server. The challenge was not preserving that particular machine. It was giving outside platforms a compatible cloud endpoint without interrupting the daily exchanges they depended on.

The Server the Vendor Ecosystem Pointed At

The group ran a local FTP server that it hosted and maintained itself. Staff and vendor flows read and wrote against it daily, and the workflow around it was manual: files moved between the group's CRM and DMS on one side and its automotive vendors on the other by hand. The data the dealerships sell from—their leads, their inventory, their appointments—depended on a machine the IT team had to keep alive on its own.

The server lasted as long as it did because everything pointed at it. Automotive vendors set the terms of their own integrations, and each one decides which protocol its platform speaks. The group controls its own systems and none of its vendors'. An endpoint that outside platforms exchange files with every day cannot simply be switched off.

That is what turned the server into a problem when the group planned its move to cloud infrastructure. Other workloads could migrate. The FTP server was anchored on-premises by dependencies the group did not own. The replacement had to be cloud-hosted, speak the standard protocols the vendors' platforms already use, and absorb the daily read and write load in a clean cutover.

The dealer group selected Files.com to be that endpoint.

A Single-Step Cutover in 2023

The group's Files.com site went live in a single-step cutover. The daily read and write traffic that had run against the local server moved to a cloud SFTP endpoint on Files.com, and the self-hosted machine came out of service.

The core vendor flows now run over SFTP: lead, inventory, and appointment files moving between the group's CRM and DMS and its automotive vendors. Files.com speaks every protocol the vendor ecosystem requires, so each provider connects on the terms its own platform sets and the group never forces a protocol change on systems it does not control.

Files.com also collects inbound vendor feeds through inboxes, so a feed that arrives outside SFTP lands in the same platform as the SFTP traffic.

With the cutover complete, file transfer stopped being the one workload vendor dependencies kept on-premises. The group retired the server it had to host and maintain while keeping the vendor data exchange underneath its dealerships moving.

What the Vendors Needed Was Never the Server

Today the same data moves every day: leads arriving for the sales floors, inventory going out to the listing platforms, appointment files landing from VinSolutions. What changed is what carries it. The exchange runs on Files.com instead of on a machine the group kept alive itself.

The old server had survived for years on the strength of one argument: too many outside platforms depended on it to touch it. The migration showed the argument pointed the wrong way. The vendors never depended on the server. They depended on an endpoint that speaks their protocols, and an endpoint can live in the cloud. The group moved it there in one step, and its IT team got out of the business of running file transfer hardware.