American Farmers & Ranchers Replaced a Synology NAS With a Governed Files.com Site for Its Co-op

American Farmers & Ranchers goes back to 1905, when the Oklahoma Farmers Union formed a mutual fire and lightning insurance company to serve rural Oklahoma. Today its mutual and life insurers and AFR Cooperative operate as legally separate companies under one umbrella, sharing a headquarters and an IT team.

That structure shaped the problem. AFR needed to move the co-op’s 18-year image and video archive off a struggling Synology NAS without folding the data into another company’s file environment. A separately governed Files.com child site preserved the legal boundary while letting off-site staff bypass the VPN and reach files directly.

A Terabyte of Co-op Media on One Box Behind the VPN

The archive sat on a Synology NAS at headquarters: roughly a terabyte of pictures and video, organized one folder per year, going back eighteen years. Inside the building, it was just a network drive. For everyone else, reaching it was a two-step process: connect to the corporate VPN, then pull large media files through the tunnel from a device that was already struggling. Downloads slowed to a crawl. Some failed outright with errors partway through.

The cost fell on the people farthest from the hardware. For an organization whose work happens across Oklahoma, the standing condition was that anyone working off-site could not count on getting a file out of the co-op’s own archive. It was not an occasional bad day. It held every time, because the path always ran through the same tunnel to the same device.

Why a Faster Tunnel Was Never Going to Fix It

Two facts ruled out the obvious answers.

First, the bottleneck was the NAS itself. The group’s network and security team considered mounting the device so users could reach it without the VPN, and rejected the idea: put a smarter front end on failing hardware and the crawl comes along with it. Whatever the fix was, it had to take the data off the device, not build a better road to it.

Second, the co-op is a separate company. Its archive could not simply be folded into another entity’s file environment, because the group’s structure depends on keeping each company’s data in a space that is legally and administratively its own.

So the requirements were clear: storage that off-site users reach directly with nothing in between, held apart as the co-op’s own environment, and administered under the group’s existing identity and controls rather than as one more island. AFR moved the archive onto Files.com, standing up a child site that belongs to the co-op: a fully separate site with its own domain, branding, users, and permissions, running under the group’s parent account.

The Whole Migration Was a Laptop and a Drag

The move needed no migration tooling and no server-side project. A Windows 11 laptop on the NAS’s network ran the Files.com Desktop App with the NAS mapped as a drive, and the team dragged the year-folders into the child site until all eighteen, about a terabyte in total, were across.

The child site carries the co-op’s custom domain, while Microsoft Entra ID sign-in, SCIM provisioning, and group-based folder permissions let AFR preserve separate ownership and access without creating another administrative island. Off-site users open the archive directly in a browser or through the Files.com Desktop App, which presents it much the way the old network drive did.

Off the VPN, Off the Failing Hardware

With the archive on the child site, AFR retired the access path along with the device.

• Off-site users now reach the archive directly, without a VPN connection or an aging NAS between them and their files.
• Eighteen years of co-op media no longer depend on a single box in a single building. The archive lives on Files.com storage that co-op staff can reach from anywhere.
• The legal boundary between companies is now enforced by the platform instead of the network. AFR administers the co-op’s separately governed site from the group’s parent account.
• The pattern extends to the group’s mutual insurance company, which runs as another child site under the same parent. Giving a separate legal entity its own governed environment is now a site to configure rather than a network to build.

The Boundary Moved From the Network Into the Platform

Today, a co-op staffer working anywhere in Oklahoma, or in Washington, opens the archive the way they would open any folder. What used to begin with a VPN connection and end, sometimes, with a failed download now begins and ends in the Files.com app.

The move carries a lesson for anyone still nursing an office NAS: when the file server itself is the bottleneck, no tunnel to it gets faster. AFR did not build a quicker path to the failing device. It took the VPN and the hardware out of the access path while giving a legally separate company the separately governed home its structure had always required.