When your fund administrator changes hands

What it is

Every outsourced operating model has a seam: the boundary where the asset manager's processes end and the administrator's begin. Contracts sit on one side, service schedules on the other, and in between lives a layer that is rarely drawn anywhere: the data feeds, reconciliation runs, reporting packs, escalation paths and informal phone calls through which the fund actually gets kept. The seam is not a line on an org chart. It is a component of the operating model with interfaces on both sides, and most firms have never drawn it.

Last week showed why that matters. In the space of two days, three major seams moved. UBS announced it will exit fund administration altogether, transferring the former Credit Suisse fund administration businesses in Switzerland and Luxembourg to Northern Trust in a phased migration expected to run for two years after a closing targeted for the second quarter of 2027. KKR agreed to acquire Gen II Fund Services, which administers more than $2 trillion across more than 275 private markets managers, for a total enterprise value of $5.1 billion. And CACEIS agreed to acquire the entirety of Edmond de Rothschild's third-party asset servicing business in Luxembourg, subject to CSSF approval. Three separate deals, one shared event: a large number of funds will soon keep their contracts but change their administrator, or keep their administrator but change its owner.

Why it matters now

Three forces are converging on the seam.

First, economics. UBS's head of global asset servicing put it bluntly when announcing the exit: "Fund administration is increasingly technology-led and scale-driven." The servicing business is consolidating around platforms that can afford the technology investment cycle, and a global bank has now twice concluded the business is not core to it. That changes the supply side of every manager's outsourcing decision, whether or not the manager's own contract is touched.

Second, the migration itself. A two-year phased migration is two years of parallel running. The old seam and the new seam both have to work, and the operating model has to show both versions at once. Nobody's model is drawn for that. The interim state, the model with two administrators live simultaneously, is where handovers actually fail: missed feeds, duplicated reconciliations, exceptions that belong to neither party because the model assigns them to a seam that no longer exists.

Third, the multi-administrator strategy. A meaningful share of managers deliberately run two administrators, for optionality and risk diversification. That strategy only works if each seam can survive the other one moving, and consolidation means the alternatives are getting bigger and fewer. Optionality is worth what the available alternatives are worth.

What firms should do

Three things, in order.

First, draw the seam. Inventory every interface that touches the administrator: files, feeds, reports, signatures, controls, and the spreadsheets nobody listed in the contract. If the map shows the seam, the transition conversation starts with a shared picture of what is moving. If it does not, the transition will draw it for you, one missed feed at a time.

Second, treat the handover as an operating model change, not a vendor change. Name an owner for the interim state: who runs the model while both seams are live, who signs off the new interfaces, who owns the dual-running period. A migration plan with no owner for the interim operating model is a schedule, not a plan.

Third, use the transition to fix the seam rather than just move it. An administrator migration is the one moment both parties are contractually present and commercially motivated. The data quality issues, exception queues and SLA gaps that have survived for years are all on the table, and the handover is the cheapest moment to fix them, because the cost is already being paid.

The opmodal perspective

This is where the Architecture Canvas earns its keep. Drawn honestly, a canvas shows the administrator boundary as a component with owners, controls and failure modes, not as a dotted line between two logos. Firms whose model can show the seam can run a handover as a project with a beginning, a middle and a testable end state. Firms whose model cannot will run it as a fire drill, discovering the seam one missed feed at a time while the clock on the two-year migration runs down.

The consolidation trend will continue, and the seam will keep moving. The firms that treat the seam as a designed part of their operating model will take each handover as an opportunity to redraw it better. The others will take each handover as a surprise, and the surprise will arrive on a Friday, in the form of a reconciliation that stopped matching.

Keep reading: Process ownership: the discipline that keeps operating models alive, and The business blueprint: one connected picture of how your organisation works.