Perk Replaced AmTrav's Microsoft Windows File Share With One Hardened Files.com Landing Zone for Future Acquisitions

Perk (formerly TravelPerk) is a corporate travel and spend management platform with operations across Europe and the US. Its growth has included acquisitions such as Click Travel and AmTrav.

Every one of those deals delivers more than customers and revenue. It delivers a company, with its own IT estate, including whatever that company had been using to move files. Someone at the group has to decide whether each piece of that estate gets absorbed or carried indefinitely.

Perk's answer was to turn the Files.com tenant inherited with one acquired company into a hardened landing zone for the next. AmTrav's Windows file share became the proof of that broader acquisition strategy.

Every Acquisition Arrives With Its Own File Infrastructure

When Perk acquired AmTrav in 2024, AmTrav's file transfer ran on a legacy Windows file share. To the group's security team, that share was a transfer surface it had not built and did not govern. It sat outside the controls the group ran on its own platform, and the team wanted it retired outright.

The harder part was structural. Folding an acquired US business unit into shared infrastructure meant keeping its data and its users cleanly separated from the rest of the group. And a company absorbing multiple acquisitions was not going to stand up a separate transfer platform for each one.

The Tenant Was Hardened Before AmTrav Needed It

Perk already ran a Files.com tenant, and it had arrived the same way AmTrav did: inside an acquisition. It entered the group with Click Travel, and Matt McKay, Perk's Security Operations Manager, inherited it. He took ownership of the configuration and hardened it: two-factor authentication enforced for every user, unused protocols locked down, permissions scoped by group and by folder. That work is what turned an inherited tool into something he was willing to recommend across the group.

“I really came to respect what Files.com does. It's actually really solid.”

So when an acquired unit needed off a legacy file server, the requirements were already met inside the estate: transfer infrastructure the security team governed, with entities kept apart by permissions rather than by separate platforms. AmTrav's file transfer moved onto the group's Files.com tenant.

Group Permissions Carved Out AmTrav's Own Space

AmTrav's own team started the move. They came to Matt wanting to migrate off the Windows share, and his answer was to retire it at once and land the work in the tenant instead.

“I want you to remove that from a security point of view straight away, so here's a good solution.”

Using Files.com group permissions and folder-level access control, AmTrav got its own space inside the shared tenant. Its users belonged to their own groups, and those groups reached AmTrav's folders and nothing belonging to the other entities. The controls Matt had already built applied to AmTrav's users from the day they landed, including enforced two-factor authentication and the locked-down protocol surface. Nothing new was stood up: no server, no second platform, no separate administration. The Windows share was decommissioned.

The Share Came Off, and the Pattern Held

• The Windows share was retired straight away, taking a legacy transfer surface the group did not govern off its books.
• AmTrav landed on controls that already existed, with access scoped to its own folders, and never had to run a hardening project of its own.
• Perk replaced a standalone server with a permission-scoped space on infrastructure its security team already governed.

The ongoing administrative overhead is close to zero. Matt describes a platform he barely touches day to day, and that keeps running anyway. That low-touch model matters across repeated acquisitions because each new entity can be absorbed without adding another transfer platform to administer.

Files.com, which itself entered the group inside an acquisition, became the place later acquisitions land. Retiring an acquired company's legacy file transfer stopped being a project at Perk. It became the default.