An agent resigns on a Friday. By Monday the broker’s desk has three questions on it: who gets their pipeline, who tells their clients, and what is the departing agent allowed to take. If the answers depend on memory or on the CRM’s default settings, the brokerage has a problem. This is a policy question first and a software question second. The brokerage that answers it in writing, before anyone resigns, keeps both its data and its composure. One caveat up front: we are not lawyers and this is not legal advice. Your state’s license rules and your attorney get the final word.
There is no single default answer
Lead ownership is governed by a mix of your independent contractor agreement, your state’s license law and regulations, and where the lead came from. Some states lean toward the brokerage owning business generated under its license, brand, and systems. Agreements can widen or narrow that. Because the mix varies, the workable move is to write your own policy, put it in front of counsel, and have every agent sign it at onboarding, not at the exit interview.
A policy signed on day one is a boundary everyone agreed to. The same policy drafted the week someone quits is a fight you have already half lost.
Revisit the policy once a year, and whenever your state association or counsel flags a rule change. A policy that was solid when you wrote it can drift out of date quietly, and the drift only surfaces during the exact dispute it was written to prevent.
Where the lead came from matters
- Brokerage-generated leads: sign calls on your listings, your website inquiries, your portal registrations, your open house traffic, relocation relationships the company built. These are the strongest case for brokerage ownership.
- Agent-generated leads: the agent’s sphere, their own marketing spend, past clients from before they joined. Many brokerages let these travel with the agent, with conditions.
- Gray-zone leads: shared marketing, team-generated business, referrals traded between agents. These cause the disputes, and this is where a written policy earns its keep.
Sort every lead source into one of those buckets before you need to, and say plainly in the policy what happens to each bucket on departure. Vagueness here is not neutral. It always resolves in favor of whoever is holding the data. Platform choice tilts that balance before anyone resigns — the eXp Realty tech stack and Fathom Realty tech stack guides show how differently brokerages treat agent data and fees.
An offboarding checklist that protects the data
The exit itself should be procedure, not improvisation:
- Suspend the agent’s CRM and platform access the same day, before the goodbye email goes out
- Export a snapshot of their pipeline for the file: stages, notes, last contact dates
- Reassign brokerage-owned leads to a covering agent within the number of days your policy sets
- Preserve every transaction record, since brokers generally carry retention obligations for deal files regardless of who worked them
- Redirect or retire the agent’s company email address and route it to the brokerage
- Send written notice to active clients naming the new point of contact
Two details make the handoff stick. Name the covering agent in the policy itself, so a pipeline is never assigned to a queue. And script the client message: short, factual, focused on who handles the transaction from here, with no commentary about the departure. Clients remember how that message went long after they forget the agent’s name.
Your software decides how much of that checklist is one click versus one week. Role-based access, audit logs, and clean exports are brokerage features, not niceties. We built BrokerDIY with that exit day in mind: access drops with the role, the log shows what changed and when, and the leads stay where your policy says they stay. For the full policy walkthrough, see our guides section. When a departure does happen, replacing that production is its own line item — our recruiting break-even calculator works the cost of a seat going empty. And if you are re-platforming at the same time, the Follow Up Boss comparison covers the data-export questions to ask before you sign anywhere.
Questions brokers ask
Can a departing agent take their client list?
For leads they generated themselves, often yes, subject to your agreement and state rules. For leads the brokerage generated, usually no. The honest answer is that your signed policy plus your state law decide it, which is exactly why you write the policy while everyone is still smiling.
What about contacts the agent imported on day one?
Your policy should have answered that before the import happened. The common practice is to distinguish imported personal contacts from company-assigned leads, and to define both in writing. If the policy is silent, you are negotiating without a position at the worst possible time.
How long must we keep transaction files after an agent leaves?
It varies by state, and some retention windows run longer than people expect. Ask your state association or attorney for the period that applies to you, and confirm your software can export a complete file, documents included, when that clock runs.