Skip to content
All insights

Technology checklist for RIA acquisitions: what to check before close and in the first 100 days

By Richard Mabbun, Founder and Principal, 1AltX ·

Advisory-firm acquisitions are judged on clients, people and revenue, but they are often won or lost in the weeks after close, when an office joins a new platform and advisors find out whether their email, CRM and client portals still work.

Our founder has been on both sides of a technology acquisition: he sold his company and then led the integration of its platform, clients and team inside the buyer. This checklist is what we look at for acquiring firms and aggregators, split into before close and the first 100 days.

Before close: inventory

  • Every system the firm uses, including the ones not on the official list: CRM, portfolio and reporting, financial planning, document management, e-signature, phone, website and marketing tools.
  • Every vendor contract, with the renewal date, the notice period, the per-seat or minimum commitment, and who signed it.
  • Where client data lives, in which system, and who can export it.
  • Who supports the technology today: an IT provider, an internal person, a contractor, or nobody.

Before close: contracts and change of control

  • Change-of-control clauses that let a vendor reprice, renegotiate or terminate when ownership changes.
  • Auto-renewals that fall just before or after the planned close or migration date.
  • Contracts that cannot be assigned to the buyer and will need to be re-signed.
  • Data export terms: what format you get, how long it takes and whether there is a fee.

Before close: security, identity and access

  • How many Microsoft 365 or Google tenants the firm runs, and who administers them.
  • Whether multi-factor sign-in is enforced for everyone, including shared and service accounts.
  • Accounts for former staff that still work, and shared mailboxes with no clear owner.
  • How devices are managed and protected, and whether personal devices access client data.
  • Any security incidents the firm knows about, and how they were handled.

Before close: AI tools and data quality

  • Which AI tools advisors and staff use, including note-takers, writing assistants and browser extensions, and where client data goes when they use them.
  • Whether the firm has an AI acceptable-use policy, and whether anything technical supports it.
  • CRM data quality: duplicate households, inconsistent fields, missing relationships and notes kept outside the CRM.
  • How households and accounts line up between the CRM and the portfolio platform, which drives how hard the data migration will be.

Deliverable before close: a written risk summary

All of the above should end in a short written summary for the deal team: what is fine, what needs a decision before close, what affects price or timing, and what can wait for the integration plan. Keep it in plain language. The people reading it are deciding a deal, not configuring servers.

Day 1

  • Every advisor and staff member can sign in to email and core systems on the first morning.
  • Client-facing systems, such as portals, e-signature and scheduling links, are tested and working.
  • Advisors know what changes, what does not, and who to call.
  • A short list of known issues and owners exists, so problems are tracked instead of rediscovered.

The first 100 days

  • Identity, email and Microsoft 365 tenant consolidation, scheduled so mailboxes and files move in a planned order.
  • A CRM and portfolio data migration plan: field mapping, cleanup, test migrations on copies and a cutover date.
  • Vendor and stack rationalization: which tools stay, which go, and the cost impact, timed against contract renewals.
  • AI tools brought under the acquiring firm's policy and controls, with your compliance team making the compliance decisions.
  • An office onboarding checklist written as you go, so the next acquisition starts from a template instead of from scratch.

Who should own the plan

An acquisition has many people touching technology: the deal team, the acquiring firm's IT provider, the target firm's IT provider, vendors, and advisors who each have their own tools. Without one accountable owner, every group assumes another is handling the hard parts, and the gaps show up on Day 1.

The owner does not have to do all the work. They have to keep the inventory, the risk summary and the integration plan in one place, make sure decisions are written down, and make sure each task has a name next to it. For firms doing more than one deal, that owner is also the person who turns lessons from one office into a checklist for the next. That can be an internal leader, a fractional CTO or an outside advisor, as long as it is clearly someone.

Common mistakes

The mistakes we see most are predictable. Technology review starts after the purchase agreement is signed, when contract findings can no longer shape terms. Data migration is planned around the vendor's timeline instead of the advisors' calendar. And the onboarding lessons from one office are never written down, so the next one repeats them. Each of these is avoidable with a written plan and one accountable owner.

If you are looking at a deal and want help with any of this, our RIA technology due diligence work covers the full list, at a fixed scope per acquisition.

Tell us what is not working.

A system that should talk to another one and does not. An automation nobody can explain. A technology decision you would rather not make alone. Book 30 minutes and you will leave with a straight answer and a next step.

Book a 30-minute call

No cost. No obligation. You talk to the person who leads the work.

What happens on the call

  • We listen to what is not working.
  • We tell you honestly whether we are the right fit.
  • You leave with a next step, and if useful, a written scope within two business days.