Two Acquired Brands, One Acquisition-Ready Files.com Estate at a Transportation Software Group

A transportation software group is an operating unit of a software holding company whose businesses run autonomously under their own names. It operates two brands acquired from a previous owner. One is a longstanding automated traffic enforcement business serving state transportation departments, police agencies and municipalities. The other is a longstanding parking and curbside management business serving municipalities and parking authorities.

The data both brands run on is evidentiary. Camera and incident images are captured in the field, reviewed by people, and become citations issued under statute. Moving that data between field operations, review staff and government clients is the business.

The holding company's model keeps acquired companies facing their markets under their own names. So the two businesses arrived as two independent brands and one integration problem: each had its own clients, its own identity arrangements and its own ways of moving files, and one corporate IT team at the group had to govern all of it. The structure the group built would not only bring the two brands under one governing model; it would give the next acquisition somewhere ready to land.

Two Brands' Worth of Everything, One IT Team

After the acquisition, the three entities operated separately: the group's corporate entity, the enforcement brand and the parking brand. Identity was managed entity by entity, which meant three user populations and no single place to create an account, disable one, or answer who had access to what. File transfer was just as fragmented, and exchanges with government clients and third parties ran ad hoc and by hand. Every new client connection was a one-off arrangement, and every one of them landed on corporate IT.

For a business whose product is moving evidentiary image data to government agencies, that made each client relationship an infrastructure decision. And the arrangement had a deadline built in. The acquired infrastructure had to come out of the previous owner's environment, and whatever the data landed on had to be something one team could actually govern. The group had inherited three file-transfer estates and could administer none of them as a whole.

Separate to Clients, Central to Corporate IT

The obvious consolidation was not available. Each brand serves its government clients under its own name: an enforcement client connects to the enforcement brand, not to a corporate parent. The brands needed their own domains, their own dedicated IP addresses, and user populations that never mix. The opposite move, standing up a separate platform per brand, would have recreated exactly the fragmentation corporate IT was trying to escape.

Timing added a second constraint. The enforcement brand had the largest user count and the most urgent need; corporate and the parking brand would come on later and start light. The structure had to be built before most of its tenants arrived.

So the fix had a specific shape: give each brand a fully separate, fully branded transfer site, while identity, administration and the audit trail stayed with one corporate team, and let brands join in phases as each was ready. The group selected Files.com to provide that structure.

A Parent Site for Governance, a Child Site per Brand

Corporate IT stood up a parent Files.com site for IT and security, with a Files.com child site for each brand beneath it. A child site is a fully separate site in its own right: each brand's carries its own custom domain and its own dedicated IP addresses, so both brands face their clients entirely under their own names. Group-based permissions keep the two brands' user populations apart.

Identity runs the other direction: one provider, Microsoft Entra ID, spans the whole estate. Single sign-on came up on the enforcement brand's child site first, because that was where the users were, with the other sites following as each brand came on. Corporate IT owns user, client and folder creation across all three sites, keeping access centrally controlled while integration accounts for automated jobs remain isolated to their respective child sites.

Delegated log visibility and folder-scoped history reports give designated reviewers the necessary audit record without handing out admin rights.

The enforcement brand went first. The parking brand onboarded later as the second child site, dropped into a structure that was already built.

One Team Now Governs Three Branded Estates

With the structure in production, the group replaced entity-by-entity identity and ad hoc file exchange with one governed platform that presents to clients as independent brands.

• One corporate IT team owns users, clients and folders across all three sites, while each brand leads its own projects and integrations on top of the platform.
• Onboarding client and integration accounts is routine administration rather than a per-entity project, handled on the appropriate brand's site.
• ISO 27001 audit work ran with Files.com in scope and completed in November 2025, with delegated log visibility giving review groups the record they need without adding administrators.
• The platform carries tens of terabytes of file traffic a month across the brands' sites.

The larger result is that another brand no longer requires another governing structure. The parking brand proved the model: the second brand came onto a child site with its own domain and dedicated IP addresses, its users separated by group and its sign-in on the same identity provider, with nothing new stood up to receive it.

The Next Acquisition Is a Child Site, Not a Project

The holding company acquires companies continuously, and the group's file estate now has a shape those acquisitions can land in. Before, each entity meant its own identity stack, its own transfer arrangements and its own one-off client connections for corporate IT to chase. Now a brand gets a Files.com child site under the parent: its own domain, its own addresses, its own client-facing identity, with corporate identity, administration and audit already waiting above it. The group never had to choose between the brands' independence and corporate control. To a government client, the two brands are still two companies. To the team that governs them, they are one platform.