A Hedge Fund Retired Parent-Owned Box and Moved Its SEC Retention Archive to Files.com

A multi-manager, multi-strategy hedge fund manages money for institutional investors: endowments, foundations, sovereign wealth funds, and pension funds. Independent portfolio manager teams run their own books across global developed markets on the firm's shared infrastructure and portfolio construction tools. The platform model is the business.

The firm did not start out independent. It launched as the public markets hedge fund division of a larger investment manager, and in early 2025 it took a new name and registered with the SEC as the investment adviser for its funds. Registration was the easy part. Operating independently meant taking over the systems the parent had been running on the firm's behalf, and the biggest of those was the file share. The firm completed the exit by splitting the Box estate between Microsoft 365 and Files.com, which already ran its external file exchange and could absorb the multi-terabyte retention archive without adding another product.

The File Share Belonged to the Parent

The parent had always administered file sharing for the business, on a Box tenancy the parent owned. Users who had been with the firm for years had their files there, including some very large ones. Nothing about that arrangement was broken while the firm was a division. The moment the firm registered independently, the same arrangement became a transitional service to wind down, and the tenancy had to be decommissioned.

Most of the content had an obvious destination. The firm is a Microsoft 365 shop, and everyday collaboration content moved to SharePoint and OneDrive. Then the migration stopped. What remained on Box was material SharePoint could not take, and until it had somewhere to go, the tenancy could not be shut down. The blocker was that simple: no place to put the large files, no decommission, and a transitional tenancy still to wind down.

Files That Can Never Be Deleted, in Folders SharePoint Cannot Hold

The remainder was the firm's retention estate.

Those files get touched rarely, and only when something happens: a production issue that reaches back a few months, or a records request that reaches back further. Purging them to make the migration easier was never an option.

The firm's posture is to delete nothing, so the archive only grows. And it had grown past what the collaboration suite could carry. SharePoint cannot accommodate very large folders, meaning tens of thousands to hundreds of thousands of files or terabytes of content, and that is precisely what sat on Box: multi-terabyte, retention-bound user archives. Content that can never be deleted, at a volume the collaboration suite cannot hold, on a platform that had to be shut down. That was the shape of the problem.

The Fix Could Not Mean Adding a Product

The separation set the requirements. The archive needed a durable, access-controlled home that could hold multi-terabyte folders, sit untouched for months, and produce a file on demand when an event called for it. And it could not mean adding a product. The firm's CTO had joined in 2025 with a mandate to consolidate the firm's technology, and the team was explicit that it did not want another tool to buy, learn, and operate for a workload that mostly sits still.

Files.com was already running in production at the firm as its external exchange layer. Counterparties and vendors deliver trade files to the firm over SFTP, and automated processes pick them up and route them into downstream trading and vendor systems. The firm selected Files.com to hold the retention archive as well, creating a deliberate division of labour: SharePoint and OneDrive for user collaboration, and Files.com for automated processes and retention.

Retention fits the Files.com side of that line. An archive is not something people collaborate on. It is something the business must be able to produce.

Two Streams Out of Box

The exit ran as two streams in parallel. Everyday collaboration content went to SharePoint and OneDrive, while the retention-bound remainder went to Files.com, and the two moves together are what let the decommission close. Using the existing Files.com Desktop App, the firm moved the archives without special migration tooling, retained access through Microsoft Entra ID single sign-on, and retired Box once both streams were complete.

Box Decommissioned, Transition Complete

With the archives on Files.com, the firm closed the Box decommission and replaced a parent-administered file share with a two-tier estate it runs itself.

• Box is fully retired. The firm's records live on infrastructure the firm administers, and the transition off parent-run services is complete.
• The SEC retention posture is now structural. The don't-delete-anything archive has a governed home, and when a production issue or a records request reaches back months, producing the file is a lookup.
• Nothing was added to the toolset. Retention rides on the same Files.com platform that already runs the firm's automated trade-file exchange, so there is no separate archive product to license, patch, or train anyone on.
• The archive absorbs growth by default. New retention-bound material lands there without a new decision each time.

A Filing Cabinet, Not Another Product

The firm did not need a dedicated archive product to complete its operational separation. It needed the transfer platform already in its estate to take the workload the collaboration suite could not hold. Files.com became the firm's filing cabinet, on the same platform that moves its trade files every day.