What Data Should Advisors Organize Before Leaving a Firm?
If you’re planning a move, the question “what data should advisors organize before leaving a firm?” is not busywork. It determines whether account opening is clean, whether transfers go NIGO, and whether your team can run a tight completion phase once access changes.
The goal isn’t to hoard data. It’s to build a transition-ready picture of each household—registrations, accounts, assets, banking features, and any known exceptions— so you aren’t rebuilding the map after the lights are off.
For client-facing “what happens during a move?” questions, the main hub is here: https://gocontinuity.com/faq/.
Quick Answer
Before leaving a firm, advisors should organize household and account inventories, exact registrations and tax IDs, holdings detail (including CUSIPs), cost basis availability, banking features (ACH/checkwriting/bill pay), margin/options status, retirement distribution needs (RMDs), and a follow-up plan for missing paperwork. The best data set is accurate, current, and tied to a workflow.
Why this data matters more than you think
Most transition friction comes from two places: unknown complexity and missing “proof”. If your team doesn’t know what’s in the book (or how it’s titled), the move becomes reactive. If you can’t prove the right authority, identity, or registration, the receiving side can’t open accounts and transfers stall.
This is also why “ACATS is fast” doesn’t mean your transition is fast. Transfers run clean only when the inputs are correct. If you want the timeline reality check, this ties in: How Long Does an Advisor Book Transition Really Take?.
Three rules for collecting pre-transition data (so it’s actually usable)
- Collect at the household level first. Account-level data is meaningless if household relationships and decision-makers aren’t clear.
- Match “how it’s recorded,” not how you say it. Exact registrations, exact tax IDs, exact trustee/authorized signer roles. Precision wins.
- Collect to a workflow. Your dataset should map to: account opening → transfer submission → NIGO cures → completion/cleanup.
Continuity’s approach to this sits inside readiness and execution workflows: Transition Readiness Assessment and Transition Execution.
Pre-move data checklist (what to gather, and why)
This table is built for ops reality—what you need to open accounts, submit transfers, and reduce NIGO/rework. Use it as your “minimum viable dataset.”
| Category | What to capture | Why it matters | Common miss |
|---|---|---|---|
| Household map | Primary contacts, decision-makers, related accounts, entity/trust relationships | Prevents fragmented outreach; keeps paperwork coherent | Multiple contacts with conflicting “owner” assumptions |
| Account inventory | Account numbers, account types, delivering firm/custodian, status (open/closed) | Defines scope; drives transfer tracking and completion | “Hidden” small accounts that later create residuals |
| Registrations & tax IDs | Exact title, SSN/EIN, trust/entity legal name, authorized signer roles | Reduces rejects and NIGO; enables clean account opening | Trust/entity authority docs not packaged together |
| Holdings detail | Ticker/CUSIP, quantity, description, restrictions, pending activity | Determines in-kind eligibility and exception workflows | Mutual fund share class support not checked |
| Cost basis visibility | Covered vs non-covered indicators, inherited lot history where known | Prevents post-move tax reporting surprises and cleanup churn | Assuming cost basis “will just show up” later |
| Banking features | ACH links, recurring deposits/withdrawals, bill pay, checkwriting, debit features | These require separate workflows; clients feel pain if disrupted | Recurring withdrawals not identified before the move |
| Margin/options status | Margin balances, options level approvals, pledged assets/lending ties | Receiving approvals can gate movement and trading continuity | Options approvals assumed to “transfer” (they don’t) |
| Retirement timing | IRA types, inherited IRA specifics, RMD needs, distribution schedules | Avoids year-of-move RMD/distribution errors | RMD tracking not assigned to an owner |
| Client follow-up plan | Outstanding forms, missing IDs/docs, preferred contact cadence | Reduces stalled paperwork and long-tail asset recovery | No defined “who follows up” and when |
What to look for inside the data (the stuff that causes real delays)
Registrations that don’t match cleanly
Tiny differences matter: middle initials, suffixes, trust naming conventions, entity legal names, tax IDs, even outdated address standards in some systems. If the receiving registration doesn’t match the delivering record, transfers get rejected or marked NIGO.
Related: Why Account Titles and Registrations Matter in Advisor Transitions.
Assets that look “normal” but aren’t in-kind compatible
The common trap is mutual funds and anything proprietary. If you can’t custody the security on the receiving platform, you need a replacement or liquidation plan. Do that work early, not mid-transfer.
Related: Which Assets Transfer In-Kind During an Advisor Move? and How to Handle Non-ACAT Assets During an Advisor Transition.
Banking instructions hiding in plain sight
ACH links, recurring withdrawals, bill pay, and checkwriting are often the #1 “my life is disrupted” issue for clients. They also require separate enablement and testing. Treat banking as its own workstream, period.
Related: What Happens to ACH Links, Deposits, Withdrawals, and Checkwriting During a Move?.
RMD and retirement distribution risk
Year-of-move retirement accounts deserve special handling. If a client has an RMD requirement or scheduled distributions, you want that tracked like a deliverable—not a note. Honestly, this is where teams get surprised.
Related: RMDs During an Advisor Transition: What Advisors Need to Watch.
How to package the data so it stays usable after access changes
Collecting information is one part. Packaging it so ops can execute is the other.
- Use a single household record as the anchor: registration + signers + account list + known exceptions
- Attach supporting docs once (trust/entity authority, IDs) instead of drip-feeding them
- Tag special workflows: banking features, margin/options, inherited IRAs, non-ACAT assets
- Assign an owner for follow-up and a cadence (48 hours, then weekly until complete)
If you’ve ever dealt with repeated rejects, you’ll recognize why this matters: Why Advisor Transfers Get Rejected, Delayed, or Marked NIGO.
Want a readiness plan that doesn’t depend on guesswork?
Continuity supports operational transition execution—readiness prep, transfer tracking, exception workflows, and completion-phase cleanup—alongside your platform, legal, compliance, and operations partners. If your book has complex registrations, banking features, or a lot of households, data prep is where you win.
Explore: Readiness Assessment • Account Transfer Tracking • Completion Phase
Frequently Asked Questions
Is it enough to export a client list and account numbers?
Usually not. You’ll still need exact registrations and tax IDs, signer authority details, holdings data, and any special workflows (banking, margin/options, retirement timing). Account numbers alone don’t prevent NIGO or delays.
What’s the single most important data point to get right?
Exact account registrations and tax IDs. A mismatch here cascades into account opening issues and rejected transfers, especially for trusts and entities.
Should we gather holdings detail by ticker or by CUSIP?
Both is ideal. Tickers are convenient, but CUSIPs and security descriptions help identify share class issues, fixed income positions, and assets that don’t behave like simple equities.
How early should we identify banking features like ACH and bill pay?
As early as possible. Banking features often require separate enablement steps and testing. If you discover them late, the client experiences disruption even if the transfer “worked.”
Do we need to collect cost basis information before moving?
You don’t always need every detail up front, but you should know where cost basis is likely to lag or be missing (taxable accounts, inherited positions, legacy holdings). That helps you plan post-move cleanup instead of reacting to it.
What’s the best way to reduce stalled paperwork?
Use a signature map, package required docs once (especially trusts/entities), and run a predictable follow-up cadence. It’s simple, but it works when it’s owned by one person.
Conclusion
The best pre-move dataset is the one that lets ops execute without guessing: household structure, exact registrations, accounts, holdings compatibility, banking features, margin/options status, and retirement timing. If you collect that to a workflow, you reduce NIGO, shorten timelines, and make completion feel controlled.
For more advisor transition FAQs and practical explanations, start here: Continuity Advisor Transition FAQ.
For broader context on why firms treat records and documentation seriously, the SEC’s overview of broker-dealer books and records is a useful authority reference: SEC: Books and Records Requirements for Brokers and Dealers .