Every investment manager has a different technology stack. Some run on established PMS platforms. Others have built proprietary systems over decades. Most have a mix of both, supplemented by specialist tools for risk, compliance, and client reporting. The idea that a single platform can replace all of this — or that firms should migrate to a common infrastructure — is rarely realistic.
The vendor trap
Many data integration projects fail because they're framed as platform decisions rather than integration decisions. A vendor proposes a new system that will 'solve' the data problem — but the real problem isn't the systems themselves, it's the connections between them. Replacing a PMS to improve data flow is like replacing a car because the sat-nav is out of date.
The firms that make the most progress on data integration do so by building the layer between their existing systems — not by replacing those systems. They invest in the pipelines, transformations, and validation logic that make their existing technology stack work together effectively.
What technology-agnostic means in practice
A technology-agnostic approach starts with the data requirements — what needs to flow where, in what format, at what frequency — and then builds the most practical path to meet those requirements using whatever systems are already in place. It might involve APIs, file-based transfers, database connections, or a combination. The method is determined by what works, not by what a vendor supports.
This approach has a significant advantage: it preserves optionality. When a firm eventually does want to change a system — upgrade their PMS, adopt a new risk platform — the integration layer can be updated without rebuilding everything from scratch. The investment in good integration architecture compounds over time.