Anonymised, illustrative composite. A departing agent’s old contract had a non-compete clause that turned out to be dead on arrival — and a confidentiality clause, from the same page, that was very much alive.
At a glance
A ten-year agent left Brokerage A for Brokerage B, carrying a 900-record client and lead database out the door: names, contact details, referral sources, renewal-date reminders, and years of relationship notes built one client at a time. The agent exported the whole CRM and re-imported it into Brokerage B’s system within days, then emailed the full list to announce the move.
Brokerage A threatened legal action, pointing to a non-competition clause in the agent’s six-year-old independent-contractor agreement barring solicitation in the same trading area for twelve months after departure. The agent’s response was correct on that specific point — but Brokerage A’s lawyer had a second, separate argument ready, and it was the one that actually mattered.
900 total records, roughly 340 of them carrying detailed, individually-built relationship notes — family details, renewal timing, negotiating history — and the remaining 560 holding nothing beyond a name, phone number, and email address. The contract creating both disputed clauses was six years old at the time the agent left.
Two separate legal questions were in play, and they resolve completely differently. First: is the non-compete clause enforceable? No — since October 25, 2021, Ontario’s Employment Standards Act has prohibited non-compete agreements with most workers, and a non-compete caught by the ban is void, with only narrow exceptions — a defined list of C-suite executives, and a person who sold a business and stayed on as an employee of the buyer — neither of which applied to an agent moving brokerages. Brokerage A’s lawyer conceded that point without much of a fight.
Second, and entirely separate: is the client database itself confidential information, independent of any non-compete? That question runs through Ontario’s breach-of-confidence doctrine, which requires showing the information was confidential in character, was communicated in circumstances importing an obligation of confidence, and was used or disclosed to the discloser’s detriment — a test that applies even without a written contract. On whether a client list specifically can be protected this way, the standard is whether reasonable steps were taken to keep it confidential and whether it is “not easily available publicly”: a list anyone could compile from a directory is unlikely to qualify, while a list “built through significant effort, with detailed contact history, pricing information, and relationship notes, is more likely protectable.” That distinction did real work here — the 560 bare-contact records looked like something reconstructable from public sign calls and MLS history, while the 340 annotated records looked exactly like what the doctrine is built to protect.
Rather than litigate, the agent’s lawyer recommended settling given how strong Brokerage A’s position was on the annotated 340: the agent kept and used the 560 bare-contact records at the new brokerage, agreed not to use the 340 richly-annotated records at all, and Brokerage A dropped its claim. The agent’s new agreement at Brokerage B swapped the old, void non-compete model for a non-solicitation clause instead — a legally live alternative where a non-compete would not be.
Had the agent used the full 340 annotated records and Brokerage A pursued it, the remedies available for a breach of confidence include an injunction ordering the information’s use stopped and materials returned, damages for the economic harm caused, or an accounting of profits requiring the wrongdoer to pay over whatever they made using the information. Courts have granted injunctions in trade-secret cases promptly — meaning an order freezing use of that segment of the agent’s own pipeline could have landed in the first months at the new brokerage, exactly when the income from those relationships mattered most.
Even setting the confidentiality clause aside entirely, the database is personal information under PIPEDA, and using it for a new purpose — soliciting business on behalf of a different brokerage — without the individuals’ knowledge goes beyond the purpose for which it was originally collected. That is a second, independent problem sitting on top of the contract dispute, not a substitute for it: winning the contract argument does not automatically clear the privacy one.
If a database would need explaining to a stranger before they understood why it was valuable — the notes, the dates, the history behind each name — that is the signal it is the protected kind, not the bare-directory kind. And a non-compete being void does not mean nothing else in the same contract still has teeth; it means checking the rest of the page before assuming the whole document is dead.
Related reading: independent contractor status, defined a related failure, inside one brokerage
A 30-minute call is enough to tell you whether AI pays for itself here.
