An Investment Adviser Builds a Repeatable Path From Microsoft 365 and Box Into SharePoint With Files.com

A national independent investment adviser, SEC-registered, provides wealth management, tax, and financial planning services through its advisor network.

Its growth runs through acquisition. The firm expands by buying other advisory practices, with each deal bringing a newly acquired firm, its client families, and its content sitting on whatever platform it happened to run.

To make that model scalable, the firm needed a standing layer that could reach into a Microsoft 365 tenant that was not its own, connect to Box and other platforms acquired firms arrived on, move large file estates, record who retrieved what while everything was in motion, and be operated by the firm’s own administrators, deal after deal. The firm built that repeatable layer on Files.com.

Every Deal Closed With Client Data in Someone Else’s Tenant

The data an acquisition brought was the most sensitive kind a wealth firm held: client financial records, tax documents, and planning files. That content had to move into the firm’s Microsoft 365 environment, where SharePoint was the system of record. And it had to move during the transition window, while the acquired firm’s people, systems, and permissions were all in motion.

The obstacle was structural. The firm controlled neither the source platform nor the identity domain it lived in. One acquisition arrived as a separate Microsoft 365 tenant. Another arrived on Box. Each platform kept its files behind its own logins, inside a domain that had belonged, until the deal closed, to somebody else.

The transition itself raised a second problem: accountability. The firm needed a shared record of who retrieved each file and when.

Acquisition Growth Called for a Repeatable Pattern

Treating each acquisition as its own migration project would have meant platform-specific work built once and discarded when the deal was done. That might have been survivable when deals were occasional. It could not keep pace when acquisition was the growth model itself, because the next firm might arrive on a different platform than the last.

One Connection Per Acquisition, Whatever the Platform Behind It

Files.com created a layer between the firm’s SharePoint environment and whatever platform an acquired firm arrived on, presenting both as folders on one site.

Using Files.com Remote Server Mounts and syncs, the firm’s administrators connected an acquired Microsoft 365 tenant and pulled its SharePoint content into the firm’s own environment. The connection avoided per-user provisioning in the acquired tenant and eliminated an export-and-reimport step.

The firm applied the same operating pattern to Box, mounting the source as a folder and moving its content through scheduled syncs.

Every retrieval along the way was on the record. Files.com logged each download with who performed it and when, giving the M&A transitions team an audit trail throughout the hand-off.

A Microsoft 365 Connection Running Within a Day

With that pattern in place, consolidating an acquisition became a connection rather than a new integration project.

• A recently acquired firm’s Microsoft 365 tenant was connected and pulling SharePoint content within a day, in the middle of a live transition.
• Client records now cross between the two companies over one governed path, with every download logged.
• The firm’s own administrators run each consolidation end to end, so the work does not depend on a specialist migration effort.

The larger result is what each future deal now requires. The next acquired firm can follow the same operating pattern whether it arrives as a Microsoft tenant or a Box account. Files.com absorbs each new deal instead of each deal spawning a new integration.

The Next Acquisition Already Has a Path In

Today, when the firm closes a deal, the acquired firm’s data has a known way home. An administrator connects the tenant or mounts the platform, Files.com pulls the content into the firm’s SharePoint, and throughout the transition the M&A team can see who downloaded each file.

Data consolidation is now part of how the firm onboards an acquired practice. The platform an acquired practice happens to run no longer demands a new migration design.