10 Things to Know Before You Take Any Client Data If You're Not Protocol
If your firm isn't in the Broker Protocol, you've probably noticed that no one will give you a straight answer about what you can take with you. Your recruiter is vague because vagueness is safer for them. Your friends who moved have half-remembered stories. And the firm you're leaving has no incentive to clarify anything. So here is the honest version, ten points, in the order they'll matter to you.
This is orientation, not legal advice, and it is deliberately not a list of workarounds — there aren't any that are worth your license. The goal is to make you a clear-eyed reader of your own situation so that when you spend money on counsel, you spend it on judgment. Read all ten before you touch a single file.
1. Without the Protocol, your contract is the entire ruleset
The Broker Protocol is a safe harbor. Without it, there is no harbor — there is only what you signed. Your non-solicit, your confidentiality clause, your notice period, and any non-compete are the complete set of rules governing your exit, interpreted under your state's law. There is no industry truce sitting on top to soften them. And enforceability turns heavily on your state and your exact contract: California and Minnesota void most non-competes outright, while many states enforce a "reasonable" one, and several enforce them above an income threshold most advisors clear. The same clause can be toothless in one state and binding in the next. This is why the first move is not talking to a client or a recruiter. It's reading the documents, because in a non-Protocol move the documents are all there is.
2. "Confidential information" and "trade secrets" are different things
Your contract almost certainly labels client data "confidential." That label creates a contractual duty. It does not, by itself, make the data a trade secret — that's a separate, higher legal standard your firm has to actually prove, under the federal Defend Trade Secrets Act or your state's Uniform Trade Secrets Act. Trade-secret status carries bigger remedies and a wider reach. The distinction matters because the two travel together in practice: a firm will sue on both, and the "confidential" contract claim is the easier one for them to win. Don't comfort yourself that "they'd have to prove it's a trade secret." They may not have to, to make your life difficult.
3. Publicly available contact info is not automatically safe to use
This is the trap that catches careful people. You reason: my client's name and number are in the phone book, on LinkedIn, findable anywhere — so a list of them can't be protected. Wrong. A compiled client list — the fact that these particular people are your firm's clients, have assets, and trust an advisor — is routinely protected as a trade secret even when every individual data point on it is public. The law protects the compilation, not the datapoint. Courts look at how the firm stored and guarded the list and who had access to it, not whether you could theoretically have rebuilt it from public sources. "I could have found it anyway" is not the defense it feels like.
4. Forwarding anything to personal email creates a record that outlasts the dispute
Emailing a client spreadsheet to your Gmail, dropping files in a personal Drive, copying to a USB stick — this is the single most common self-inflicted wound, and it is close to unwinnable once done. It creates documentary proof of intentional copying that dramatically strengthens the firm's case even if you never use the data. The act is the evidence. And since the 2024 amendments to Regulation S-P, exporting client nonpublic personal information to a personal account may also be treated by the firm as a reportable security incident, layering a privacy violation on top of the trade-secret exposure. There is no version of this that helps you. Whatever you're tempted to forward, don't.
5. Memory is treated differently from records — but don't get clever about it
The law does generally treat what's in your head differently from a copied file. Client information you genuinely remember is far harder for a firm to prove you took than a document with a timestamp on it. That is a real evidentiary difference, and it is the honest reason "just remember your clients" is common advice. Here is the limit, stated plainly: memory is not a legal free pass. Using memorized client information to solicit can still be misappropriation; the difference is what the firm can prove, not what's permitted. Handle this the boring way. Don't build a memorization system, don't write yourself notes to "reconstruct from memory," don't get clever. Clever is what gets read aloud in arbitration.
6. Announcement and solicitation are different, and the line is narrower than you think
You may generally make a bare announcement: I've moved to Firm X, here's my new contact information. You may not solicit: asking a client to move their account, inviting them to call about coming over, telling them the new firm is better for them. The line is drawn by the content of what you said, not your intent — and it moves the instant an announcement starts asking for the business. "I wanted you to know where I am" is one side. "I'd love to bring your accounts over" is the other, and there is less room between them than most advisors assume. Passively taking a call a client initiates is generally fine; actively inducing the move is not. Courts have gone both ways on where exactly the line sits, which is precisely why you don't want to be the test case — get the wording of any announcement in front of counsel before it goes out, not after.
7. A TRO moves in days, sometimes over a weekend, before any accounts move
A temporary restraining order is the firm's fast weapon. It's emergency court relief that can bar you from using firm information and from contacting clients, and firms seek it within days of a departure — sometimes over a weekend, before you've moved a single account. The procedural bar to file is low. The effect is that your transition can be frozen before any court has ruled on the merits: you're enjoined from contacting the very clients you were counting on, while the underlying dispute goes to expedited FINRA arbitration. Non-Protocol firms with a litigation history will do this regardless of how large your book is. Plan for the possibility that your first week looks like a court filing, not a client call.
8. The receiving firm has its own exposure — and its own opinion
Your new firm is not a bystander cheering you on. It can be sued for tortious interference or for helping you misappropriate, and it knows it. That's why its compliance team will often police what you bring in — refusing data you offer, insisting you took only what you were entitled to, documenting that you imported none of the old firm's nonpublic information. Don't read that as unfriendliness. Read it as a second party whose license is also on the line and whose caution is, usually, correct. If your new firm's compliance officer tells you not to bring something, that is not an obstacle to route around. It's the closest thing to free counsel you'll get.
9. Your professional record is the asset genuinely at risk — not the accounts
Advisors fixate on the accounts and the damages. The thing that actually follows you for the rest of your career is your record — your U4, the U5 your firm files when you leave, and the BrokerCheck page any client or future employer can pull up. A hostile U5 narrative, a settlement, or an arbitration finding is durable and public in a way a lost account never is. Firms know this and use U5 language as leverage; FINRA has had to warn firms not to file misleading or obfuscating U5s, which tells you how routinely the form gets used as a weapon. You can rebuild a book. A damaging disclosure on a public record is far harder to undo, and it prices into every conversation you have for years. When you weigh a risk in this move, weigh it against your record first — the accounts are recoverable, the record is not.
10. Involve counsel earlier than you think you need to
Most advisors call a lawyer after something has gone wrong — after the TRO, after the demand letter. In a non-Protocol move that's backwards. The decisions that determine your exposure — what you read, what you don't touch, how you word an announcement, when you resign relative to what you've said — are made in the weeks before you leave, and they're cheap to get right and expensive to fix. Retain specialist transition counsel, not a generalist, the moment you're serious, because the non-Protocol path has no safe harbor and the whole game is in the sequencing. A single early consult is a fraction of the cost of one week of litigation.
One rule the firm can't hold over the client. There is a limit on what your old firm can do, and it runs in your client's favor, not yours. Under FINRA Rule 2140, a firm cannot interfere with a customer's own request to transfer their account when the transfer is tied to your change of employment. The firm can protect its data and come after you for how you left. It cannot block a client who has decided to move. The client's right to choose their advisor is real — it's your handling of the firm's data, not the client's freedom to follow you, that creates the risk.
One cautionary case makes the stakes concrete. In a recent Delaware matter, an advisor at a non-Protocol firm downloaded the firm's files to a personal Google Drive shortly before resigning and mass-contacted clients the day he left. The result was a judgment reported around $765,000 plus a fresh multi-year non-solicit, and the Protocol was no defense because neither firm was a member. The court's line was that a signed agreement is not a suggestion. Nothing in this piece would have changed his outcome except the parts he ignored: don't copy files, don't blast clients, don't treat the contract as theater.
If any of this is new to you, you are not behind — you're being told the truth later than you should have been. Start by reading what your contract actually says in Read Your Contract Before You Make a Move, and if you're still unsure what you're even allowed to take, Rep-Owned vs. Firm-Owned lays out the difference between owning the relationship and possessing the file. In a non-Protocol move, understanding that difference correctly, before you act on it, is the entire margin of safety you have.
