Who owns leads when an agent leaves a team?

The team agreement owns this question: leads belong to whoever the contract says they belong to, and when the contract is silent, the departure turns into a negotiation between an agent holding relationships and a team holding the database. The prevailing norm — where teams bother to write it down — is source-based: team-generated contacts stay with the team, self-generated contacts leave with the agent.

The default is contract, and silence is expensive

No regulator allocates lead ownership inside a team; it is private contract, like the splits. Well-drafted team agreements define the two pools explicitly — what counts as team-sourced (ads, website, sign calls, pond pickups) versus agent-sourced (sphere, past clients, personal referrals) — and state each pool’s fate at exit. Poorly drafted ones say “the database belongs to the team” and nothing else, which invites the classic fight: the agent argues relationships, the team argues investment, and the only certain loser is the follow-up that stalls while they argue.

Why source-based allocation became the norm

It mirrors who paid. The team funded the ads and the routing infrastructure that produced team leads, so it keeps them; the agent brought their sphere in the door, so it leaves with them. The same logic already governs who pays for leads and how splits differ by source — exit terms are just that logic applied one last time. The edge cases deserve explicit clauses: leads the agent nurtured for two years but the team sourced, referrals from team-sourced past clients, and anything picked up from a shared pond.

The privacy-law overlay most agreements ignore

Contacts are personal information, and Canadian privacy law cares how it moves. Consent collected by the team — on the team’s website, under the team’s privacy notice — does not automatically transfer to a departing agent’s new marketing list, and email consent under CASL has its own rules about who may send what, covered in depth by any CASL-compliant CRM setup. The practical posture: transfer data under the agreement, then re-establish your own consent footing with contacts you take, rather than assuming the old consent travels with the spreadsheet.

Write the clause on day one

Everything above is cheap to settle at signing and expensive to settle at departure. A workable exit clause fits in a paragraph: define the two source pools, name each pool’s owner at exit, grant the agent an export of their pool in a standard format within a stated window, handle pending-deal tails, and require the team to stop marketing to contacts the agent takes. Teams that offer fair terms here recruit better — database hostage-taking is a story that travels fast in a local agent community.

The system makes the clause enforceable

A clause that says “agent-sourced contacts leave with the agent” is only executable if the database knows the source. That is a CRM discipline: stamp origin on every contact at creation, keep it immutable, and the exit export becomes a filter instead of a forensic project. BrokerFold records the entry point and full history on each contact — and the same question at the next level up, an agent leaving a brokerage, has its own ownership answer.

Handling the transition without burning the leads

However the pools divide, someone must keep working them the week of the departure, because the leads themselves did not resign. The clean handover sequence: freeze new assignment to the departing member immediately, reassign their active team-pool leads with a note that introduces the new contact honestly, and give the agent’s own pool a short written transition window for pending conversations. Skip the theatrics of mass “your agent has left us” emails — contacts respond better to continuity than to drama, and the fastest way to lose a lead both parties claim is to let it sit unworked while the paperwork gets argued.