An Enterprise Data Migration Firm Replaces Box With Files.com, Turning Each ERP Client's Transfer Requirements Into Folder Settings

An enterprise data migration firm migrates, cleans, and governs enterprise data for complex ERP programs, combining consulting services with a SaaS product. When an enterprise consolidates onto a new ERP, the firm is often the one carrying the data across.

Carrying data means exchanging it. Every engagement puts project data files in motion between the firm and its client, from bulk data movement to the deliverables of the migration itself. And every client is a large enterprise with its own security requirements, its own transfer tooling, and its own rules about where data may live. The exchange layer between the firm and its clients is not a convenience at this company. It is part of the product.

Every New Client Arrived With Its Own Transfer Rules

Until 2022, that exchange layer was Box. Box is a collaboration platform, and what the firm's clients brought to each engagement were managed file transfer requirements: data-file exchange over SFTP driven by scripts and command-line tooling, GPG encryption mandated on the files themselves, data that had to be hosted in a specific region for a specific customer, and hard separation between one client's data and another's. The firm's own account team recorded the pattern plainly: each new client engagement arrived with its own transfer method and its own regional placement needs.

Those requirements called for more than collaboration. Customer-facing download URLs also did not carry the firm's name, and the firm's Director of Support tied the URL directly to how customers respond to a delivery. The firm was handing clients links that looked like somebody else's product.

As the client roster grew, so did the requirements pulled into the estate. What the firm needed was an exchange layer that could take each client's rules as configuration rather than as a new project: one folder per client with its own access boundary, encryption configurable per folder, endpoints that clients' existing scripts and tooling already speak, regional placement per customer, and customer-facing delivery on the firm's own domain.

The firm selected Files.com as that layer and moved off Box in 2022, standing the new estate up on its own branded domain.

One Folder Per Client, Carrying That Client's Rules

Files.com became the client-facing exchange layer of the firm's delivery model: a single platform where each client's requirements are settings applied to that client's folder.

The firm's VP of Cloud Operations designed the structure the way a SaaS company structures tenants: one folder per client, each with its own distinct access restrictions, enforced by Files.com's per-folder access controls. Client staff hold logins on the site scoped to their own folder, and the firm's teams deliver files to them by share link and over SFTP. One client never has a path into another's data.

Encryption follows the same boundary. Using Files.com's folder-level GPG, encryption is applied automatically to files moving through a client's folder over SFTP, so a client whose mandate requires encrypted exchange gets it on every file with nobody running keys by hand, and a client whose workflow does not can be configured without it. Regional obligations are handled the same way: with Files.com's multi-region storage, a customer whose data must be hosted in a particular region gets a folder placed in that region, on the same site as everyone else's.

Delivery itself carries the firm's brand. Share links and publicly served folders are served from the firm's own domain, so what a client clicks reads as the firm end to end.

The cloud operations team drives the estate through the Files.com CLI, and it watches the exchange as well as running it. Files.com's share-link access history gives the team a timestamped record of who accessed which link and which file, which the team pulls for review.

A New Client Is Now a Folder, Not a Project

Onboarding a new client now means creating a folder and applying that client's access boundary, encryption, and region. No new infrastructure gets built per engagement.

The model also carries real migration volume. One newly onboarded client moved hundreds of gigabytes on a recurring cycle through Files.com, and terabyte-scale upload workloads were in scope.

The Exchange Layer Behind the Migrations

Today, the exchange side of an engagement matches the rest of it. A client's team works inside its own boundary, in the region its obligations require, under encryption where its mandate demands it, downloading deliverables from the firm's own domain. Before the move, a new client's transfer requirements opened a question about what the platform could handle. Now they are settings a cloud operations engineer applies to a folder.

The firm did not swap Box for another place to put files. It made Files.com part of how it delivers: an exchange layer that absorbs each client's rules, instead of asking every client to work by the firm's.