A Public School District Runs a District-Controlled Files.com Hub for Ten Data Feeds

A US K–12 public school district serves several thousand students across more than a dozen schools.

Behind those classrooms runs the data estate every modern district accumulates: a student information system (Genesis), a financial system (SchoolFi), an assessment platform, a graduation-progress tool, and an analytics dashboard, each from a different vendor. Every vendor holds a piece of the district's data. When the district set out to pull all of that data into one dashboard, it wanted a hub the district itself controls, where every system drops its files and the dashboard collects them. Files.com gave its data team that hub.

Ten Systems Feeding One Dashboard

The dashboard was Abre, and it needed file ingestion from roughly ten external systems and vendors. Getting those files was manual.

Of the departments feeding a given dashboard, roughly half could drop their reports over SFTP automatically. The rest needed a person to generate the file and upload it by hand, every time the data had to refresh. Teachers and counselors, meanwhile, reached into system after system to assemble the picture they needed on a student.

The one piece of exchange infrastructure inside the district, an on-premises SFTP server, was run by the networking team, so every change the instructional technology team needed to its own pipelines went through a request to networking.

The instructional technology team wanted to run the district's data pipelines end to end: one staging area every system drops into, routing that needs no person, and changes it can make itself the day it needs them. A districtwide analytics dashboard cannot run on hand-carried files, so the hub had to be in place before the dashboard could be.

What the fix had to do was clear before any product entered the picture. The district needed a staging area in the middle, run by the team that owned the pipelines, where systems could drop files and Abre could collect them. It had to speak the SFTP those systems already used. It had to place files into specific storage locations automatically once they arrived. The district selected Files.com to be that hub.

A Hub the Data Team Runs Itself

Files.com became the district-controlled exchange point for connected systems moving files in either direction. The instructional technology team configured the site itself, without a ticket to anyone.

Abre draws on roughly ten external systems and vendors. Feeds land at the district's hosted SFTP endpoint, giving source systems a common destination instead of requiring their vendors to integrate directly with one another.

Routing runs without people. Files.com Automations fire as files land, moving each drop into the specific folder Abre expects, so data from an automated source travels from system to dashboard with nobody generating, downloading, or re-uploading anything along the way.

The hub carries data both ways. Graduation-progress files from Zello flow through it to the district's counselors, who work the data, and their changes flow back into the dashboard. Teachers and principals make decisions on current numbers instead of last month's export.

The same endpoint retired the on-premises server. Genesis and SchoolFi now run against Files.com as their secure exchange point, trading files daily, hourly, and on demand. The district also centralized access control with sign-in federated across its Microsoft Azure and Google directories and IP whitelisting alongside it.

From Hand-Carried Files to a Standing Pattern

With the hub in production, the district replaced hand-carried files with a staging layer its own team runs.

• Roughly ten systems and vendors feed Abre, with Files.com serving as the common exchange point for the sources already connected.
• Every automated source runs end to end with nobody touching a file: the system drops it, a Files.com Automation places it, and the dashboard collects it.
• The instructional technology team changes its own file exchange the day it needs to, with no request to networking and no waiting on another team's server.
• The student information and financial systems exchange files through the same endpoint on daily, hourly, and on-demand cadences, and the on-premises SFTP server is gone.

The immediate result is a dashboard whose automated feeds refresh without hand-carried files. Teachers and principals can open one dashboard instead of assembling a view across several vendor systems. The compounding result is a pattern: for any system that can deliver its file, connecting it to the district's data no longer requires new exchange infrastructure. It becomes another drop point on a hub that is already running.

The District Controls the Ground Its Data Crosses

A staging layer on Files.com, controlled by the district's data team, connects systems without requiring their vendors to integrate directly with one another. Any source that can deliver a file has a district-controlled destination already waiting for it.