A Network Security Vendor Retires Box by Moving a Handful of Beta Users to Files.com

A network security vendor builds firewalls and security services for customers around the world, and it sells largely through a global ecosystem of managed service providers and resellers, who deploy and manage its products on customers' behalf.

A business built that way moves files across its own boundary all day. Partner transactions arrive as files and feed order processing. Support trades gigabyte-scale files with customers. Pre-release builds go out to testers who don't work for the vendor. Over the years, each of those patterns had picked up its own tool, and the estate held several different ways to hand a file to someone outside the company.

By moving Box's handful of beta users onto Files.com, the vendor retired a separate sharing tool and brought beta distribution under the same administration as its other external file movement.

A Separate Vendor for One Small Workload

One of those tools was Box, and at the company it existed to do exactly one job: distributing beta software builds to recipients outside the company. The footprint was a handful of users and a few gigabytes of data. Behind that small footprint sat a separate external-facing sharing surface for IT to govern and account for.

That is the real burden of tool sprawl. Every product capable of handing company data to an outsider is a product IT has to administer and answer for, and a security vendor's IT team knows that arithmetic better than most.

Redundant tools survive because nothing forces the question. Box worked, its users knew it, and its recipients were real people outside the company rather than internal habits a memo could change. Retiring an external-facing tool only becomes practical when the surviving platform can hand a file to an outsider just as easily.

The Platform Already Carrying Orders Into Oracle ERP

The company already ran a platform whose entire job was moving files across company boundaries. Files.com had been in production there for years as its secure FTP layer, and the work it carried was not peripheral: channel partner integrations deposited transaction files over SFTP, and those files fed order processing in Oracle ERP.

The same site served the company's support organization, which staged gigabyte-scale files to exchange with customers. Accounts were locked to their own home directories, while ad-hoc transfers ran through Files.com's web access over HTTPS.

So the platform already did what beta distribution required. An outside recipient could reach files in a browser with nothing to install. Every account stayed confined to its own directory, under administration the company already staffed. Rather than keep a dedicated vendor for one distribution pattern, the company's IT team selected Files.com to absorb the beta workload and retire Box.

Moved One at a Time

IT ran the move itself, and ran it incrementally. Beta users came off Box one at a time while the Files.com site kept doing its production work. Nothing about the partner exchange or the support workflow paused for the migration. External recipients now collect builds through Files.com's web access, which asks nothing of them beyond a browser.

The whole migration measured a few gigabytes, which is the point. Folding the workload into an existing platform was a small job, and maintaining a separate vendor to avoid that job was the expensive choice.

One Fewer Vendor, One Fewer Surface to Govern

With beta distribution running on Files.com, the company shut Box down, replacing a standalone product with a handful of accounts on a site IT already administered.

• The Box workload moved to the platform the company already ran, so retiring the vendor added no new tool to the estate.
• Beta software distribution is now governed like the rest of the company's external file movement, on the same site and by the same administrators, instead of on a separate collaboration tool.
• IT accounts for one fewer external-facing sharing surface. For a security company, every place where data can be handed to an outsider is a surface someone has to answer for, and there is now one fewer.
• The next external file workload has a home before anyone shops for one. Standing up a new distribution pattern on Files.com means creating accounts and a folder, not evaluating a vendor.

One Platform for Files That Leave the Building

The size of this migration is the lesson in it. A handful of users and a few gigabytes barely qualifies as a project, and it retired an entire vendor relationship. What changed at the company is the assumption underneath: a new file-sharing pattern used to mean a new product, and now it means a folder on Files.com. When a file has to leave the building, whether it is a partner order headed for Oracle ERP or a beta build headed for a tester, it moves through the same platform, under the same accounts and the same administrators.

The company never ran a consolidation program. It noticed that the platform already moving its orders was also, already, a beta distribution platform, and that retiring Box was a matter of moving a handful of users onto it.