Buyers structure deals as asset purchases instead of stock purchases for one reason: to leave the liabilities behind. Buy the equipment, the contracts, the customer relationships, the name — leave the lawsuits, the warranty claims, the unpaid taxes, and the environmental problem nobody disclosed.
Minnesota honors that general rule, and since 2006 it has honored it by statute rather than by common law alone. An asset purchaser is ordinarily not liable for the seller’s debts.
So the interesting question here is no longer “what are the exceptions.” It is how much of the old exception framework survived Minn. Stat. § 302A.661, subd. 4 — and on that, the federal courts have answered one way and the Minnesota Court of Appeals, in two unpublished decisions, has answered another. I structure deals around that disagreement, because a buyer who assumes it has been resolved is buying a fight.
Start with the statute, not the case law
The baseline first. A corporation that buys another’s assets does not, by that purchase alone, assume the seller’s liabilities. As the Minnesota Supreme Court put it, “where one corporation sells or otherwise transfers all of its assets to another corporation, the latter is not liable for the debts and liabilities of the transferor.” J.F. Anderson Lumber Co. v. Myers, 206 N.W.2d 365, 368–69 (Minn. 1973). The economics behind that rule are not subtle: without it, distressed businesses could not be sold at all, and their assets would go out the door at scrap value instead of staying in productive use. Minnesota has been notably disciplined about honoring it.
Most successor-liability discussions skip straight past the provision that actually controls. Minn. Stat. § 302A.661, subd. 4, titled “Transferee liability,” reads in full:
The transferee is liable for the debts, obligations, and liabilities of the transferor only to the extent provided in the contract or agreement between the transferee and the transferor or to the extent provided by this chapter or other statutes of this state. A disposition of all or substantially all of a corporation’s property and assets under this section is not considered to be a merger or a de facto merger pursuant to this chapter or otherwise. The transferee shall not be liable solely because it is deemed to be a continuation of the transferor.
Three sentences, three moves. Liability is limited to what the contract says and to what another statute imposes. An asset sale under this section is not a de facto merger. And the transferee is not liable “solely because” it is deemed a continuation of the transferor.
That operative language arrived in the 2006 amendment (2006 c 250 art 1 s 44) to a section originally enacted in 1981. Keep the date in mind, because a great deal of the Minnesota successor-liability case law people still quote at each other predates it.
What happened to the four traditional exceptions?
The four are real and they are the historical baseline. Before 2006, a successor corporation could be liable “(1) where the purchaser expressly or impliedly agreed to assume liability; (2) where the transaction amounted to a consolidation or merger of the corporation; (3) where the purchasing corporation was merely a continuation of the selling corporation; and (4) where the transaction was entered into fraudulently in order to escape liability for such debts.” Niccum v. Hydra Tool Corp., 438 N.W.2d 96, 98 (Minn. 1989).
Here is where each one stands today, for a Minnesota business corporation selling assets under chapter 302A:
| Traditional exception | Status after § 302A.661, subd. 4 |
|---|---|
| Express assumption | Intact and statutory. The first sentence of subdivision 4 makes contractual assumption the primary route to transferee liability. This is now the main event |
| Fraudulent transaction | Intact. “[T]he fraudulent transfer exception still exists.” Matson Logistics, LLC v. Smiens, No. 12-cv-400 (ADM/JJK) (D. Minn. June 5, 2012) |
| De facto merger | Contested, and abrogated on the federal courts’ reading. The statute says an asset disposition “is not considered to be a merger or a de facto merger … or otherwise” |
| Mere continuation | Contested, and abrogated on the federal courts’ reading. The statute says the transferee “shall not be liable solely because it is deemed to be a continuation of the transferor” |
| Implied assumption | Uncertain. Not expressly preserved or excluded by the amendment |
The federal courts have been blunt about it. Matson Logistics: “While the amended statutory language of Minn. Stat. § 302A.661 clearly abrogates the common law exceptions of de facto merger and mere continuation, the fraudulent transfer exception still exists.” On implied assumption, the same opinion: “Whether the common law exception of implied assumption of liability remains is uncertain, since it was not expressly included or excluded under the amended Minn. Stat. § 302A.661, subd. 4,” and, after working through the 2006 Reporter’s Notes, “it appears that the implied assumption of liability exception no longer applies.” Those Notes state that “[b]eyond these two explicit statutory exceptions, however, there are no common law exceptions to the rule of transferee non-liability.”
Eight years later, ResCap Liquidating Trust v. LendingTree, LLC, No. 19-cv-2360 (SRN/HB) (D. Minn. Mar. 20, 2020), described Minnesota law identically: “In Minnesota, pursuant to Minn. Stat. § 302A.661, subd. 4, successor liability is generally limited to circumstances in which there has been a contractual assumption of liability, or where liability is otherwise permitted by statute.”
The Minnesota Court of Appeals has never said so. ResCap flagged the split in a footnote: two unpublished Court of Appeals decisions have applied the de facto merger and continuation exceptions notwithstanding the statute — Johnson v. USL Products, Inc., No. A11-1774, 2012 WL 2078478 (Minn. Ct. App. June 11, 2012), review denied (Minn. Aug. 21, 2012), and Noack v. Colson Construction, Inc., No. A08-0148, 2009 WL 305114 (Minn. Ct. App.), review denied (Minn. Apr. 21, 2009). Neither has been overruled. Both have been criticized — see In re Opus East, LLC, 528 B.R. 30, 81–82 (Bankr. D. Del. 2015), which walks through why those decisions misstated Minnesota law.
My advice to a buyer is the same every time. The statute is strong medicine and the federal authority is favorable, but a plaintiff’s lawyer can put two unpublished state appellate decisions in front of a state district judge tomorrow. Do not structure a transaction on the assumption that de facto merger and mere continuation are dead letters in Minnesota state court. Structure as though they are alive and well.
What the contested theories look like in practice
A creditor can still plead all of them, so it pays to recognize the fact patterns that draw the claims. What follows is how these theories get argued, not a statement that Minnesota currently recognizes them as independent routes to liability against a chapter 302A transferee.
Implied assumption is manufactured by conduct after closing, never by drafting. A buyer who pays a few of the seller’s old obligations, honors the seller’s warranties, or tells customers “we’re taking care of everything from before” has handed the creditor an argument that the buyer assumed more than the purchase agreement says.
De facto merger is the argument that the deal was a merger wearing an asset-sale costume. The recurring red flag is stock as consideration — when the seller’s owners walk away owning the buyer, the transaction starts to look like a combination rather than a sale, and it looks worse still if the seller shuts down and dissolves within the month.
Mere continuation is the argument that the buyer is the seller in a new suit. Traditionally the theory turned on commonality of ownership — substantially the same officers, directors, or shareholders — rather than on continuity of the business alone. Section 302A.661, subd. 4 now says the transferee “shall not be liable solely because it is deemed to be a continuation of the transferor,” which is why the ownership question, and that one word “solely,” both carry weight.
Fraudulent transaction is the exception that survives whole. It overlaps Minnesota’s voidable transfer statute, Minn. Stat. § 513.44, which I covered here — and a transaction that trips this exception has usually tripped several badges of fraud on the way. The Matson court analyzed the fraudulent-transfer exception directly under § 513.44.
One thing the case law does not settle: LLCs
Section 302A.661 lives in chapter 302A, which governs Minnesota business corporations. Its transferee-liability language is written for “a corporation’s property and assets.”
Minnesota’s LLC act, chapter 322C, carries no analogous transferee-liability provision. The only “transferee liability” text in that chapter, at § 322C.0502, subd. 8, deals with transfers of a membership interest — the obligations a new member takes on under §§ 322C.0403 and 322C.0406, subd. 3 — not with asset purchases.
The apparent consequence is that an asset sale by a Minnesota LLC does not get the benefit of § 302A.661, subd. 4, and the common-law framework is not displaced by statute in the same way. I am not aware of published Minnesota appellate authority resolving that point, and I flag it as an open question rather than a settled one. If your seller is an LLC, spend an hour with counsel on this before you rely on the corporate rule.
The exception Minnesota refused to adopt
Some states recognize a “product line” exception: a buyer who keeps manufacturing the seller’s product line takes the associated product liability, whatever the ownership continuity.
Minnesota declined. In Niccum v. Hydra Tool Corp., 438 N.W.2d 96, 99–100 (Minn. 1989), the Minnesota Supreme Court refused to adopt the product line exception. Nothing since has moved that, and the 2006 amendment to § 302A.661, subd. 4 narrowed transferee liability further rather than widening it.
Later decisions citing Niccum at 99–100 read it as resting on legislative deference: a change of that magnitude in corporate law belongs to the legislature, not to a court. Courts elsewhere rejecting the product-line exception have added other criticisms — that it sits badly alongside ordinary products liability principles, and that it exposes small successor businesses that cannot insure against defects in somebody else’s products — but I state those as the general critique of the doctrine, not as the Minnesota Court’s holding.
Commercially, this is real money. A buyer acquiring a Minnesota manufacturing line carries less product-line successor exposure than a buyer doing the identical deal in a state that adopted the exception.
Do not overestimate how far that advantage travels, though. Product-line successor liability is asserted by an injured third party, not by a party to the purchase agreement, and a choice-of-law clause binds no non-signatory tort plaintiff. Which state’s successor-liability rules apply gets decided by the forum’s conflicts analysis, not by your deal documents. ResCap illustrates it: the court ran a Minnesota-versus-Delaware conflicts analysis rather than simply applying the contract’s chosen law to the successor-liability question. The Minnesota rule is an advantage of doing business here. It is not something you can draft into a contract and carry across a state line.
The liabilities that commonly follow the assets anyway
Successor liability doctrine is not the only road to the buyer, and this is where buyers get surprised most often. The statute itself points at it: § 302A.661, subd. 4 preserves liability “to the extent provided by this chapter or other statutes of this state,” and the 2006 Reporter’s Notes name environmental law and the fraudulent transfer act as examples. The categories below are the ones that turn up in my diligence. Each runs on its own body of law with its own triggers and defenses, and none of them is automatic — read this as a diligence checklist, not a set of rules:
| Category | Why it can follow |
|---|---|
| Environmental | Federal and state environmental regimes can attach liability to owners and operators of contaminated property, on their own terms, irrespective of how the acquisition was structured |
| Certain tax obligations | Bulk sale and successor tax provisions can reach a purchaser. These have specific statutory triggers and, in Minnesota, a clearance-certificate mechanism — confirm the current requirements with counsel or the Department of Revenue rather than assuming either exposure or safety |
| Secured creditors’ liens | A perfected security interest generally follows the collateral unless released. Run the UCC and title searches |
| Assumed contracts | You take them as they are, including accrued breaches and unfavorable terms |
| Employment and benefits | Multiemployer pension withdrawal liability, WARN obligations, and successorship in labor law follow their own rules — see my piece on withdrawal liability |
| Licensing and permits | Transferability varies entirely by license type and issuing agency. Where a license is non-transferable, re-application can surface the predecessor’s compliance history |
Diligence and structuring that actually reduces exposure
Before signing:
- Search the liens. UCC filings at the Secretary of State, judgment dockets, tax liens, mechanic’s liens, and title. Cheap, fast, and it catches most of what matters.
- Litigation and claims history, including threatened claims and anything reserved on the financials.
- Environmental assessment where the property or the operations warrant it. This exposure does not care what your purchase agreement says.
- Employment and benefits diligence, particularly any union contract or multiemployer plan participation.
- Confirm the seller is solvent after the deal — or, if it is not, understand that you are standing in voidable-transfer territory and price accordingly.
In the documents:
- An explicit, exhaustive list of assumed liabilities, with an express statement that all others are excluded. Under § 302A.661, subd. 4 this is the primary lever: contractual assumption is the first of the two routes to transferee liability the statute preserves, which means what you write is what you take.
- Representations and warranties with survival periods that actually outlast the risk.
- Indemnification with real security — escrow or holdback. An indemnity from an entity that dissolves after closing is a promise from nobody.
- Consider R&W insurance where the deal size supports it.
- Reasonably equivalent value, documented. Appraisal support protects against both the fraudulent-transaction exception and a voidable-transfer claim.
- Cash rather than buyer equity where practical, to keep the de facto merger indicators off the table.
After closing — the part nobody plans for:
- Do not pay the seller’s old debts. Not as a courtesy, not to keep a supplier happy, not to protect goodwill. That is the raw material of an implied-assumption argument, and it gets created by well-meaning people in accounts payable who have never heard of § 302A.661.
- Do not tell customers you are the same company. Marketing continuity is what a de facto merger claim is built out of, and your marketing team does not know that.
- Keep the entities genuinely separate — separate books, separate accounts, separate governance.
- Route predecessor claims through counsel, not through operations.
Asset or stock: decide it with your eyes open
Successor liability is one input into a decision that also turns on tax treatment, contract assignability, licensing, and employee continuity. I wrote about the broader choice here.
An asset purchase gives better liability protection than a stock purchase, and in Minnesota that protection is real — reinforced by § 302A.661, subd. 4 and by the absence of a product-line exception. It is a default, not a guarantee. Independent statutes reach the buyer on their own terms, an LLC seller may change the analysis entirely, and the exposure that does exist gets created by conduct after closing at least as often as by drafting before it. Which means the diligence list above is worth more to you than the statute is.
Madgett Law, LLC advises Minnesota buyers and sellers on acquisition structure, diligence, and successor liability exposure — and defends and pursues successor liability claims after the fact. If you are buying a business, or a predecessor’s creditor has found you, send us a message or call 612-470-6529.
Sources — statutes (Minnesota Office of the Revisor of Statutes): Minn. Stat. § 302A.661, subd. 4 (transferee liability; operative language from 2006 c 250 art 1 s 44); Minn. Stat. §§ 513.41–.51, the Uniform Voidable Transactions Act (short title, § 513.51), including § 513.44 (voidable transfer standard); Minn. Stat. ch. 322C (Minnesota Revised Uniform Limited Liability Company Act; § 322C.0502, subd. 8, is the chapter’s only transferee-liability provision and addresses transfers of membership interests, not asset sales).
Sources — cases: J.F. Anderson Lumber Co. v. Myers, 206 N.W.2d 365, 368–69 (Minn. 1973) (general rule of transferee non-liability); Niccum v. Hydra Tool Corp., 438 N.W.2d 96, 98, 99–100 (Minn. 1989) (listing the four traditional exceptions; declining to adopt the product line exception); Matson Logistics, LLC v. Smiens, No. 12-cv-400 (ADM/JJK) (D. Minn. June 5, 2012); ResCap Liquidating Trust v. LendingTree, LLC, No. 19-cv-2360 (SRN/HB) (D. Minn. Mar. 20, 2020) (collecting the split, and citing Johnson v. USL Products, Inc., No. A11-1774, 2012 WL 2078478 (Minn. Ct. App. June 11, 2012), rev. denied (Minn. Aug. 21, 2012); Noack v. Colson Construction, Inc., No. A08-0148, 2009 WL 305114 (Minn. Ct. App.), rev. denied (Minn. Apr. 21, 2009); and In re Opus East, LLC, 528 B.R. 30, 81–82 (Bankr. D. Del. 2015)). The J.F. Anderson and Niccum quotations and the 2006 Reporter’s Notes are quoted as set out in the official Matson Logistics opinion (govinfo.gov); Johnson, Noack, and Opus East are described as characterized in the official ResCap opinion (govinfo.gov). Johnson and Noack are unpublished and are not precedential.
This article is general legal information about Minnesota law, not legal advice, and reading it does not create an attorney–client relationship. Minnesota successor-liability law after the 2006 amendment to § 302A.661, subd. 4 is genuinely unsettled in the respects described above. Whether successor liability attaches to a particular transaction depends on the selling entity’s form, the transaction’s structure, its documents, and the parties’ conduct. No outcome is promised or implied.