Minnesota Federal Court Rules on Nonsolicitation Agreements

Minnesota may have kicked most noncompetes to the curb, but nonsolicitation agreements are still alivelike that one houseplant you forgot to water for three weeks that somehow refuses to die.

A recent decision from the U.S. District Court for the District of Minnesota offers a practical, business-friendly roadmap for a question employers and employees keep tripping over: When does a “heads-up” about a job change become unlawful solicitation? In plain terms, the court drew a bright-ish line: a neutral announcement is generally okay, but persuasionespecially the “let me move your accounts over and here’s why my old shop is going downhill” flavorcan cross into solicitation.

This article breaks down what the court said, why the facts mattered, and how to use the ruling to draft, negotiate, and follow nonsolicitation agreements without stepping on a legal rake. (Standard disclaimer: this is general information, not legal adviceplease don’t use it as your only GPS.)

The big picture: Minnesota’s restrictive-covenant landscape is changing fast

If you’ve been watching Minnesota employment law lately, you know it’s been busy. The state banned most new post-employment noncompete agreements starting in 2023, but it did not ban nonsolicitation agreements in the typical employee-employer context. That means employers can still try to protect client relationships and workforce stabilityjust not by broadly blocking someone from working for a competitor.

Add to that Minnesota’s growing skepticism of “end-run” tactics (like forcing Minnesota-based workers into out-of-state venues and laws), and you get a state where precision matters. If your agreement is vague, bloated, or drafted like it’s trying to win a spelling bee instead of a court hearing, it’s more likely to face trouble.

What is a nonsolicitation agreement (and what is it trying to protect)?

A nonsolicitation agreement is a restrictive covenant that typically limits a departing worker’s ability to initiate contact with certain people connected to the former employeroften customers, clients, vendors, or employeesfor a defined period.

Two common types

• Customer (or client) nonsolicitation: aims to protect goodwillthink client relationships, trust, and revenue streams.
• Employee nonsolicitation: aims to prevent “team lifts” and preserve workforce stability (often used for sales teams, recruiters, and managers).

In Minnesota, these covenants can be enforceable, but courts often scrutinize them for reasonableness and legitimate business purpose. In other words, they’re not a magical spell. They’re more like a contract-based seatbelt: effective if properly designed, not very helpful if installed backwards.

The ruling everyone’s quoting: “solicitation” requires persuasion, not just a job update

In U.S. Bank National Association v. Kirk, Frederickson, and Beumer, U.S. Bank sued three former wealth managers who left to join another firm. The bank sought emergency court relief, arguing the former employees violated a customer nonsolicitation agreement and a confidentiality provision.

The court’s analysis turned on a deceptively simple question: What counts as solicitation? The court treated solicitation as involving an invitation, encouragement, or attempted persuasionnot merely letting clients know where you landed next.

What the court treated as generally not solicitation

• Client-initiated contact: if a client reaches out first, that matters. Courts often view “responding” differently than “recruiting.”
• Neutral announcements: a straightforward notice that you’ve moved employerswithout a pitchcan be treated as something short of solicitation.

This is a practical point with huge real-world impact. People change jobs. Clients notice. LinkedIn exists. The court’s approach recognizes that basic professional communication isn’t automatically a breach.

What the court treated as solicitation (or at least enough to justify an injunction request)

The record included allegations that one former employee went beyond a neutral update and into “sales pitch” territoryoffering to facilitate account transfers and making negative comments about the former employer’s direction. That combination mattered because it looked less like “FYI” and more like “come with me.”

Put differently: announcing is safer than advocating. And advocating is safer than advocating while holding the transfer paperwork.

Why the court enjoined only one defendant: evidence, specificity, and the “vague-and-conclusory” trap

A headline like “Court enforces nonsolicitation agreement” can make it sound like the employer won across the board. It didn’t. The court granted a preliminary injunction against one defendant, while denying the requested nonsolicitation relief as to the others based on the evidence presented at that early stage.

Lesson #1: Courts want details, not vibes

The employer alleged that multiple customers were contacted and encouraged to move business. But when allegations lumped defendants together without specificswho said what, to whom, when, and howit wasn’t enough. Courts are generally reluctant to issue emergency restrictions based on generalized claims.

Lesson #2: “They considered next steps” is not the same as “we pushed them to take next steps”

In at least one example, the employer pointed to a customer saying they would consider their “next steps” after a call. The court essentially treated that as consistent with a neutral update unless there was evidence the caller encouraged a move. That’s a key nuance for industries where clients often follow relationship managers: the client’s reaction alone doesn’t always prove unlawful solicitation.

Lesson #3: A confidentiality claim still needs a connection to real conduct

The employer also argued the former employees used or retained confidential information. But at this stage, the court did not see enough evidence tying accessed files or data to improper use. “Access” is common in many roles; “misuse” is what the court is looking for, especially when seeking an immediate injunction.

What this means for everyday business communications

Most nonsolicitation disputes are won or lost in the gray zone: the calls, emails, texts, DMs, and social posts that sit somewhere between “hello” and “hire me.” The Minnesota federal court’s framing helps translate that gray zone into workable guardrails.

Safer communications (generally)

• Short message announcing a new role and basic contact information
• Responding to inbound client questions without urging them to move accounts
• Avoiding comparisons, critiques, or “why you should switch” talking points
• Keeping the tone informational rather than persuasive

Riskier communications (especially under a client nonsolicit)

• Offering to “handle” or “facilitate” transfers
• Disparaging a former employer’s strategy, stability, pricing, or service
• Repeated outreach to the same clients or targeted “check-in” campaigns
• Using internal client lists or contact databases you shouldn’t have

A simple litmus test: If your message would feel comfortable being read out loud in court, it’s probably closer to “announcement.” If it would be awkward… well, courts are great at identifying awkward.

Drafting takeaways for employers: make it enforceable, not just intimidating

The best nonsolicitation agreements do three things well: define the restricted conduct, narrow the restricted audience, and justify the restriction with a legitimate interest (like goodwill or confidential client information). The goal is a covenant that’s protective without being punitive.

1) Define “solicit” in plain English

If you want “solicit” to include certain conduct (like offering to move accounts, sending transfer forms, or repeated targeted outreach), say so. If you want to allow neutral announcements, consider stating that too. Courts don’t love guessing games, and neither do juries.

2) Limit the scope to relationships the employee actually had

Agreements are often more defensible when limited to customers the employee serviced, managed, or learned about through the jobrather than “anyone the company has ever met since the invention of email.”

3) Keep the time period reasonable

Duration depends on industry and role, but shorter restrictions tied to legitimate protection needs are usually easier to defend than multi-year bans that function like a noncompete in disguise.

4) Prepare for the “evidence” moment before the dispute happens

If you ever need emergency relief, you’ll want documented specifics: timelines, client names, copies of messages, and clear descriptions of what was said. “Multiple customers reported…” is a starting point, not a finish line.

Practical takeaways for employees: how to switch jobs without triggering a nonsolicit

If you’re covered by a nonsolicitation agreement, the biggest risk isn’t usually the job change itselfit’s the first week afterward, when your phone starts lighting up and you’re tempted to be “helpful.”

1) Keep announcements neutral

“I’m excited to share I’ve joined X” is different from “I’ve joined X and can get you better pricing and I’ll start the transfer.” The first is information. The second is persuasion.

2) Let the client steer (and document it)

If a client initiates contact, note that fact and keep the response businesslike. Many disputes turn on who reached out first and whether the response turned into encouragement.

3) Don’t take what isn’t yoursespecially lists

Even when you “know” your clients, taking contact lists, account data, or confidential materials can create a separate legal problem that’s harder to defend.

4) Treat gray-zone messages as if they’ll be Exhibit A

Because they might. The casual “Want me to get that moved over?” text can end up doing more damage than a dozen formal emails.

Important Minnesota wrinkle: the service-provider non-solicitation ban (a different animal)

When people say “Minnesota and nonsolicitation,” they might mean employee agreements like the federal court case above. But Minnesota also took aim at a different type of restriction: clauses in service contracts that prevent a client from hiring or soliciting a service provider’s workers (a “no-hire” or “no-poach” style restraint).

That newer Minnesota law generally prohibits service providers from restricting customers from soliciting or hiring the service provider’s employees, with a narrow exemption for certain computer-related consulting situations. For staffing-heavy industrieshealth care, managed services, professional servicesthis is a big deal.

Bottom line: employee-to-employer nonsolicits are still a common tool in Minnesota, but service-provider “don’t hire our people” clauses have new constraints. If your organization uses both, don’t assume one rule covers them all.

FAQ: Minnesota nonsolicitation agreements after the ruling

Does Minnesota’s noncompete ban automatically void nonsolicitation agreements?

Not automatically. Minnesota’s 2023 law targets noncompetes, while leaving room for nonsolicitation agreements (though they can still be challenged if drafted too broadly or enforced unfairly).

Can I tell clients I changed jobs?

The court’s reasoning supports the idea that a neutral announcementwithout persuasionmay not be “solicitation.” The risk increases when the message turns into a pitch, repeated outreach, or transfer facilitation.

If the client contacts me first, am I safe?

Client-initiated contact can reduce risk, but it’s not a free pass. How you respond matters. A calm, informational response is different from using that opening to recruit.

What’s the #1 employer mistake in these disputes?

Relying on broad claims without specifics. If you want emergency relief, you need evidence with names, dates, communications, and clear descriptions of what was saidnot just conclusions.

Conclusion: the court’s message is simplebe clear, be fair, and don’t confuse “announcement” with “sales pitch”

The Minnesota federal court’s ruling is a reminder that nonsolicitation agreements can be enforceable, but enforcement is fact-driven and language-driven. Courts look for persuasion, targeted outreach, and evidence that someone crossed the line from “I changed jobs” to “come with me.”

For employers, the win is in drafting: define solicitation, narrow the scope, and document the facts you’ll need if a dispute arises. For employees, the win is in discipline: keep announcements neutral, avoid transfer assistance, and don’t turn a friendly update into an accidental solicitation.

Minnesota’s restrictive-covenant era is not overit’s evolving. And as this case shows, the details are not just important. In court, the details are the whole show.

Real-World Experiences: What This Dispute Looks Like in Practice (and What People Learn the Hard Way)

In day-to-day business, nonsolicitation fights rarely start with a dramatic villain speech. They start with a regular Tuesday. Someone resigns, the team throws a polite goodbye lunch, and thentwo days latera client emails: “Hey, are you still my person?” That’s the moment where good intentions can accidentally become evidence.

One common pattern is the “helpful handoff” that becomes a “helpful transfer.” A departing employee thinks they’re being courteous: they answer a client’s question, confirm the new company name, and then offer to “make the move easy.” In industries like wealth management, insurance, recruiting, and SaaS, “making it easy” often means doing something concrete: sending forms, coordinating introductions, or giving step-by-step instructions. That’s where employers argue the conversation stopped being informational and started being persuasive.

Another frequent flashpoint is tone. People underestimate how quickly a message can shift from neutral to nudging. A neutral announcement is short and factual. But add one sentence like, “I’m excited because the new platform is better,” or “I didn’t love the direction we were heading,” and suddenly the communication sounds like a recommendation. Even without explicitly saying “move your business,” the subtext can read like encouragementespecially if it’s sent to a list of specific clients rather than posted generally.

Employers, for their part, often learn that “everybody knows” is not the same as “we can prove it.” Leaders may hear rumors that clients were contacted. Sales teams may report that “the competitor is calling everyone.” But when a court asks for specificswho called, what was said, which clients, and how the message was deliveredsome companies realize they’re holding fog in their hands. The result can be a partial win, a partial loss, or a court order limited to the clearest incident rather than the broad narrative.

The best-run transitionson both sidestend to share a few habits. Employers maintain clean client-ownership records (who serviced which clients and when), so a dispute doesn’t devolve into “I think they were mine.” They also train managers on how to respond when clients ask where someone went, so the company’s message is consistent and calm. Employees who want to stay out of trouble keep their communications brief, avoid transfer assistance, and let the client do the choosing. When a client insists on moving, the employee’s safest move is often to slow down and get guidance rather than speed up and get sued.

The practical lesson behind the Minnesota federal court’s ruling is that most nonsolicitation disputes are preventable. They’re rarely about whether someone got a new job. They’re about whether communications looked like relationship maintenance or relationship conversion. If you treat every post-resignation message like it could be read by a judgebecause it canyou reduce the odds that your “quick update” turns into a very expensive story.

SEO Tags