A retiring agent's client base is two different things wearing one name — a personal contact list, and active client files that were never really the individual agent's to sell.
Key takeaways
A retiring agent’s “client base” is really two different things wearing one name, and which one you’re actually buying changes which law governs the deal. There’s the personal sphere — past clients, referral relationships, a mailing list built up over years of newsletters and closing gifts — and there’s the active client files, which under Ontario’s framework were never the individual agent’s to sell in the first place.
Under RECO’s Bulletin 2.3 (Representation Agreements), a representation agreement is defined as an agreement “between a brokerage and a person” — not between a person and an individual agent. A brokerage representation agreement lets every agent employed by the brokerage represent that client; a designated representation agreement names one or more specific agents as the client’s designated representative and, critically, says the brokerage and all other agents at that brokerage are not representing the client under it. Either way, the retiring agent was never the counterparty on paper — the brokerage was. That means the file itself, and the trust obligations attached to it, don’t transfer in a private sale between two agents; they stay exactly where TRESA already put them.
Checked directly and confirmed not to help here: Bulletin 3.4 (Personal Trades and Property Interests) governs an agent buying or selling real estate for themselves — their own home, a rental property — not the purchase of another agent’s book of business. There is no RECO bulletin that speaks to agent-to-agent client-base sales at all. That gap is real, and the honest answer is to say so rather than stretch an adjacent bulletin to cover it.
What can genuinely change hands is the retiring agent’s own contact list — names, addresses, emails, transaction history for people they’ve worked with — and that is personal information governed by the Personal Information Protection and Electronic Documents Act, s.7.2. PIPEDA lets two organizations that are party to a “prospective business transaction” use and disclose personal information without each individual’s consent, provided they’ve signed an agreement restricting the receiving party to using the information solely for the transaction, requiring it be safeguarded, and requiring it be returned or destroyed if the deal falls through. The Act’s own definition, at s.2(1), is broad enough to cover this: a “business transaction” “includes the purchase, sale or other acquisition or disposition of an organization or a part of an organization, or any of its assets” — a book of business built up over a career is a reasonable reading of “assets” of a one-person practice.
Two conditions matter more than the rest. First, once the deal closes, s.7.2(2)(c) requires that one of the parties notify each individual, within a reasonable time, that the transaction has completed and that their personal information was disclosed — the people on the list have to be told, even though they don’t have to consent in advance. Second, and this is the trap: s.7.2(4) says the whole exception does not apply where “the primary purpose or result” of the transaction is the purchase, sale, or lease of personal information itself. If what’s really happening is “I’ll pay you $X for your spreadsheet of 400 names,” with nothing else about the retiring agent’s practice changing hands, that reading pulls the deal out of the business-transaction exception entirely — and ordinary consent rules apply instead, meaning each person on the list would need to consent to having their information disclosed to a new recipient.
The practical fix is to make the transaction genuinely broader than a data sale: the retiring agent’s goodwill, an introduction period where they personally reintroduce the buying agent to past clients, a transition of any listings still in the pipeline (handled through the brokerage, per Bulletin 2.3, not privately), and the contact list as one component of that package rather than the whole of it. A written agreement — the s.7.2(1) requirement either way — should specify what the buying agent may and may not do with the information before and after closing, and who is responsible for sending the post-closing notice the Act requires.
How the purchase price itself gets paid also touches RECO’s Bulletin 3.3 (Financial Benefits): an agent is prohibited from receiving payment directly from any source other than the brokerage that employs them, in connection with a trade. A lump-sum buyout for a client list sits outside a specific trade, so it isn’t squarely the same fact pattern the bulletin addresses — but a structure that pays the retiring agent per closed transaction from the introduced list looks much closer to a referral fee tied to trades, and that is exactly the kind of arrangement Bulletin 3.3 requires to be disclosed and routed through the brokerage. Get advice on the payment structure before you assume a flat buyout price sidesteps it.
Before pricing anything, confirm what you’re actually inheriting. Ask whether the list is genuinely the retiring agent’s own sphere — past clients they personally served, people who know them by name — or a purchased or scraped list dressed up as a “book of business,” which carries a much weaker consent history and a higher risk profile under PIPEDA’s ordinary rules. Ask how the list has been used: a database that’s been actively nurtured with newsletters and check-ins is worth more, and is more defensible under a business-transaction reading, than a static spreadsheet nobody has contacted in years. And confirm the retiring agent is actually retiring, rather than moving to another brokerage — a brokerage change raises a different set of questions about who has any claim on a shared marketing list at all. If continuity of service matters to the sale — clients expecting a warm handoff rather than a cold introduction — the same structural question comes up in how a practice keeps running when the named agent can’t personally show up: representation follows the brokerage and the agreement in place, not an informal handshake between two agents.
There’s no RECO rule that prohibits it, and PIPEDA’s business-transaction exception (s.7.2) can cover it if the deal is genuinely broader than a bare data sale and the required agreement and post-closing notice are in place. What you can’t buy is the retiring agent’s active client files — those belong to the brokerage relationship under TRESA, not the individual.
Not in advance, if the deal qualifies as a PIPEDA business transaction under s.7.2 — but they must be notified after closing that the transaction happened and their information was disclosed. If the deal is really just a purchase of the list itself with nothing else changing hands, s.7.2(4) removes that exception and ordinary consent applies.
No. Bulletin 3.4 governs an agent’s own personal real estate purchases, not client-base sales, and no other bulletin addresses agent-to-agent goodwill transactions directly. That’s a genuine gap in the published guidance, not a settled rule either way.
A 30-minute call is enough to tell you whether AI pays for itself here.
A 30-minute call is enough to tell you whether AI pays for itself here.
