Your whole history moves.
Nothing is switched off first.

Replacing a reporting system is not the hard part of changing platforms. Keeping a decade of history intact while you do it is. This page is for the operations lead who has to make sure nothing is lost on the way across.

What moves

• Accounts and households, with their registrations and relationships.
• Positions, transactions and cost-basis lots, across custodians.
• Performance history and composites, reconciled before anything goes live.
• Fee schedules, splits and exceptions, including the ones that live in one person’s head.
• Models, sleeves and assignments, so trading picks up where it left off.

Accounts stay at the same custodian under the same account numbers. Your clients sign nothing; the only signature is yours.

How it runs

Day zero is the transition call: a named transition lead maps your systems and everything that never quite tied out, and you leave with a plan. In week one your data is copied across and reconciled; nothing is deleted or switched off at the old system. In week two billing and reporting run side by side against your current stack. Trading follows once they match. Two to three weeks is the average across our transitions; when the custodian moves promptly, a couple of weeks. Your part is about six hours, mostly in week one. The transition, week by week.

The abort point is yours

The parallel run is where you decide. If billing and reporting do not agree line for line, nothing moves, nothing is canceled, no client is notified, and you owe nothing. You leave with cleaner records than you arrived with.

What makes a transition run long

Not the software. Held-away assets, fee schedules nobody wrote down, and above all a performance history that never reconciled. Custodians commonly retain three years of detailed transactions; many firms report composites going back ten or more. Our longest transition was a billion-dollar book in exactly that position, and reconstructing it took months. We would rather find a gap in week one than have it found in an examination. The gap in your performance history, and how to check for it yourself.

For enterprises

An aggregator runs this as one repeatable migration path for every practice it acquires, onto its own standalone instance, instead of a separate integration project per deal. For aggregators and enterprises.