Vision Makes Inherited FTP Retirement a Repeatable M&A Step—Without Re-Onboarding Municipal Customers

Vision Government Solutions has provided appraisal services and computer-assisted mass appraisal (CAMA) software to local government assessing departments since 1975. It serves more than 900 jurisdictions, from small communities to some of the largest cities in the country, and runs one of the largest appraisal businesses in the United States. The work is governed by state law: when a state requires a municipality to reassess every property to current market value, Vision's software and its appraisers are how that gets done. Assessment data, reports, and database files move constantly between Vision and the assessor offices it serves.

Vision also grows by acquisition. And every acquired appraisal company arrives with the same thing: its own file transfer infrastructure, carrying live traffic for its own municipal customers.

Every Acquisition Arrived With Another FTP Server

The inherited infrastructure was almost always an on-premises FTP server. Some of them were running plain, unencrypted FTP on port 21, open to the internet.

“We've bought a few companies that have just had FTP on port 21.”

Each of those servers was a standing cost. It was another internet-exposed endpoint moving government property data without encryption, and another box someone had to manage separately from everything else. And because the deals kept coming, the estate kept growing faster than one-off cleanup could shrink it.

The obvious fix was worse than the problem. Decommissioning a server the normal way means moving its users to a new address with new credentials. Here, those users were entire customer bases of county and municipal assessor offices, many of whom, as Schuster puts it, "aren't very technical." They had pointed their clients and their habits at the same endpoint for years, and none of them could be forced to reconfigure anything. Re-onboarding a whole customer base per acquisition was a coordination project nobody wanted to staff, multiplied by every deal.

Consolidation carried its own hazard. Folding every acquired estate into one shared environment would intermingle each company's data and customer traffic with everyone else's.

So the fix had to do three things at once: keep every customer's address and credentials exactly as they were, keep each acquired company's data in its own boundary with its own administrators, and take the exposed server off the internet. Vision made Files.com the standing destination for all of it. Schuster's policy for an inherited port-21 server was unequivocal:

“I'm not having any of that, so I just say shut it down and move to Files.com.”

A DNS Swap, a Child Site, and the Same URL

The playbook Vision built turns each inherited FTP server into a Files.com child site. Vision stands up the child site, migrates the existing usernames and passwords onto it, and swaps DNS so the legacy hostname resolves to Files.com. The assessor offices keep connecting to the same URL with the same credentials they have always used. The connection now terminates on Files.com instead of a server in someone's office, and the old box gets shut down.

“They can hit the same URL that they've always hit.”

The child site is what makes consolidation safe. Each one is a fully separate site under Vision's parent account, with its own users, folders, and administration, so the team that came with an acquisition manages its own data and its own customers. In Schuster's words, "it doesn't get all intermingled with all the other data that we have moving in and out of there." Vision keeps governance over everything from the parent account, and the same playbook applies as each new deal closes.

FTP Retirement Became a Step, Not a Project

With child sites carrying the traffic, Vision replaced a per-acquisition migration project with a repeatable integration step, and removed a category of exposure along with it.

• Every cutover was invisible to the customers on the endpoint: no communications campaign, no credential resets, no support queue of assessor offices locked out of an unfamiliar system.
• The internet-exposed FTP servers came off the network entirely. The plain-FTP endpoints Vision migrated no longer exist.
• Each acquired estate stays segmented in its own child site, run by its own team, under one set of controls at the parent, so consolidation never meant commingling.
• The platform absorbed the growth that came with the deals. One acquisition alone roughly doubled Vision's storage on Files.com, from about 5 TB to 11 TB in four months, without any new infrastructure to stand up.

The Next Acquisition Already Has a Destination

Vision never migrated its customers off the old servers. It migrated the servers out from under the customers. The address and the credentials outlived the infrastructure behind them, and that is what made retiring it possible at all.