Imagenet Uses Files.com to Hand Off Hundreds of Millions of Documents With an Automatic Audit Copy

Imagenet is the digital mailroom for the healthcare payer industry. Health plans, managed care organizations, and government agencies send it their incoming paper and electronic documents: claims, correspondence, enrollment forms, and everything else that arrives by mail, email, fax, or SFTP. Imagenet digitizes, classifies, indexes, and validates that intake and returns finished data to clients.

Being the mailroom carries a consequence: Imagenet is also the custodian. Years of each client's document history accumulate inside Imagenet's systems, reachable through a hosted portal built for viewing and searching individual documents. In healthcare, that custody is regulated. The work runs under HIPAA, with the auditability obligations that come with holding protected health information on someone else's behalf. And custody cuts both ways. When a client's business changes, its entire history has to be able to move.

When a long-standing client's merger put hundreds of millions of documents in motion, Imagenet built an unattended Files.com pipeline in which each successful delivery automatically created the required audit copy.

A Client's Merger Put Its Entire Document History in Motion

One of Imagenet's long-standing clients went through a merger, and the history Imagenet held for that client had to be handed off in full: terabytes of data, spread across hundreds of millions of individual files, spanning January 2019 forward.

Two things made that more than a large copy job. The first was Imagenet's own compliance obligation. An archive copy of everything delivered had to survive on Imagenet's side, so that if a question came later about why a given file was or wasn't part of the data set, the delivery could be re-inspected and audited. The second was that nothing at this scale could be verified by hand. Done manually, the archive requirement means either moving every terabyte twice or keeping a ledger of what has been delivered, what has been archived, and what remains, batch by batch, across years of monthly data. Whoever keeps that ledger becomes the single point of failure for the audit copy.

Small Files, a Slow Source, and a Retention Clock

Hundreds of millions of small files are the worst case for bulk transfer. Throughput dies in per-file overhead long before bandwidth becomes the limit.

The source made it harder. The data lived in the portal clients use to view and search their documents, a system built for retrieval rather than bulk export, so each period of data had to be extracted and staged on a local file server before it could move at all. The extractions were slow, especially for the earlier years, where paper originals meant far more images per document. The retention clock was real enough to shape the project's scope: data from 2018 was excluded entirely, because it would age past its retention period before the project could reach it.

A hand-off this size was never going to be a cutover weekend. The pipeline had to deliver in increments the client could pick up on its own schedule, over the standard SFTP client already in the client's hands. It had to carry small-file volume that would choke a naive transfer. It had to run unattended for months. And it had to leave a verifiable archive copy of every delivered batch without anyone reconciling what had cleared.

Sync the Batch, Confirm It, Then Archive It

The hand-off runs as a rolling, batch-by-batch pipeline. Data is extracted from the document portal onto local staging servers and organized by year and month. Multiple Files.com Agents installed on those staging servers connect the storage to Imagenet's Files.com site over outbound-only connections and carry the transfer volume in parallel.

The step that makes the compliance requirement automatic lives in the Files.com CLI. A script, authenticated with an API key, runs a sync push from the staging folders into the client's folder on Files.com, using the CLI's option to move source files to a new location only after the sync completes successfully. Every batch that lands on Files.com leaves its originals relocated into an archive area on Imagenet's own servers. A batch that fails to sync stays exactly where it was, still in the staging path, still visibly undelivered. The archive is not a second job someone performs after the transfer; it is the transfer's own receipt.

The client connects the way Imagenet's clients always connect: over SFTP, picking up each batch from its folder as it appears.

A Migration-Sized Hand-Off That Runs on Its Own

In production since October 2025, the ongoing pipeline replaced what would have been a months-long manual project of extracting, delivering, double-moving, and reconciling with an incremental process that largely runs itself.

• Terabytes of data, in hundreds of millions of files, move to the client in year-and-month batches, and the client picks them up over standard SFTP with nothing new to install.
• Nobody keeps the ledger. Delivered batches have retained originals in the archive, while batches that have not successfully synced remain visibly undelivered in staging. The state of the folders is the state of the project.

An Exceptional Hand-Off Becomes Standard Work

What changed for Imagenet is larger than one client's exit. A document bureau's custody obligation runs in both directions: it holds a client's history securely for years, and it hands that history back completely, verifiably, and with its own compliance copy intact.

The next engagement of this shape, whether another client merger, a wind-down, or an auditor's request to pull back a data set, is the same Files.com pipeline pointed at a different folder. A hand-off that would once have been an exceptional project is now standard work.