You Bought the Assets, Not the Company. In Minnesota, a Statute Now Decides Whether You Bought the Liabilities Too.

The entire reason buyers structure deals as asset purchases rather than stock purchases is to leave the liabilities behind. Buy the equipment, the contracts, the customer relationships, the name — leave the lawsuits, the warranty claims, the unpaid taxes, 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.

The interesting question in Minnesota is no longer “what are the exceptions.” It is how much of the old exception framework survived Minn. Stat. § 302A.661, subd. 4 — a question the federal courts have answered one way and the Minnesota Court of Appeals has, in two unpublished decisions, answered another.

The general rule, and why it exists

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 rule makes economic sense: without it, distressed businesses could not be sold at all, and the assets would be liquidated at scrap value instead of continuing in productive use.

Minnesota adheres to this rule and has been notably disciplined about it.

Start with the statute, not the case law

This is the provision most successor-liability discussions skip, and it is the one that 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 (1) what the contract says and (2) 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.

The operative language came from the 2006 amendment (2006 c 250 art 1 s 44) to a section originally enacted in 1981. That date matters, because much of the frequently quoted Minnesota successor-liability case law 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).

Where each one stands now, for a Minnesota business corporation selling assets under chapter 302A:

The federal courts have been direct 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 reviewing 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 the same way: “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.”

But the Minnesota Court of Appeals has not 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 analyzes why those decisions misstated Minnesota law.

What that means for a deal. If you are a buyer, the statute is strong medicine and the federal authority is favorable, but a plaintiff can point to two unpublished state appellate decisions going the other way. Nobody should structure a transaction on the assumption that de facto merger and mere continuation are dead letters in Minnesota state court. Structure as if they are live.

What the contested theories look like in practice

Because a creditor can still plead them, it is worth knowing the fact patterns that draw the claims. These are practitioner observations about 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 created by conduct after closing, not by drafting. A buyer who pays some of the seller’s old obligations, honors the seller’s warranties, or tells customers “we’re taking care of everything from before” hands the creditor the argument that the buyer assumed more than the purchase agreement says.

De facto merger is the argument that the transaction was a merger dressed as an asset sale. The recurring red flag is stock as consideration — when the seller’s owners end up owning the buyer, the transaction starts to look like a combination rather than a sale, particularly if the seller then ceases operations and dissolves promptly.

Mere continuation is the argument that the buyer is simply the seller in new clothes. Traditionally the theory turned on commonality of ownership — substantially the same officers, directors, or shareholders — rather than on mere continuity of the business. 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 the word “solely,” both do work.

Fraudulent transaction is the one that survives intact. It overlaps with Minnesota’s voidable transfer statute, Minn. Stat. § 513.44, which we covered here — and a transaction that trips this exception usually trips several badges of fraud as well. The Matson court analyzed the fraudulent-transfer exception directly under § 513.44.

One thing the case law does not settle: LLCs

Section 302A.661 is part of 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, contains no analogous transferee-liability provision. The only “transferee liability” text in that chapter, at § 322C.0502, subd. 8, concerns transfers of a membership interest — the obligations a new member takes on under §§ 322C.0403 and 322C.0406, subd. 3 — not 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. We are not aware of published Minnesota appellate authority resolving that point, and we flag it as an open question rather than a settled one. If your seller is an LLC, this is worth an hour with counsel before you rely on the corporate rule.

The exception Minnesota refused to adopt

Some states recognize a “product line” exception: a buyer who continues manufacturing the seller’s product line takes the associated product liability, regardless of 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 changed that, and the 2006 amendment to § 302A.661, subd. 4 narrowed transferee liability further rather than expanding it.

Later decisions citing Niccum at 99–100 treat it as resting on legislative deference: a change of this magnitude in corporate law is better addressed by the legislature than by a court. Courts elsewhere that have rejected the product-line exception have added other criticisms — that it fits poorly with ordinary products liability principles, and that it exposes small successor businesses that cannot insure against defects in a predecessor’s products — but we state those as the general critique of the doctrine, not as the Minnesota Court’s holding.

This matters commercially. A buyer acquiring a Minnesota manufacturing line faces less product-line successor exposure than a buyer doing the same deal in a state that has adopted the exception.

One caution about how far that advantage travels. 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 in a purchase agreement does not bind a non-signatory tort plaintiff. Which state’s successor-liability rules apply is decided by the forum’s conflicts analysis, not by the deal documents. ResCap is an illustration: the court ran a Minnesota-versus-Delaware conflicts analysis rather than simply applying the contract’s chosen law to the successor-liability question. Treat the Minnesota rule as an advantage of doing business here — not as something you can write into a contract and carry across state lines.

The liabilities that commonly follow the assets anyway

Successor liability doctrine is not the only route to the buyer, and this is where buyers most often get surprised. Note that the statute itself points here: § 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 we see most often in diligence. Each is governed by its own body of law with its own triggers and defenses, and none of them is automatic — treat this as a diligence checklist, not a set of rules:

Diligence and structuring that actually reduces exposure

Before signing:

1. Search the liens. UCC filings at the Secretary of State, judgment dockets, tax liens, mechanic’s liens, and title. This is cheap and catches most of what matters.
2. Litigation and claims history, including threatened claims and anything reserved on the financials.
3. Environmental assessment where the property or operations warrant it. This exposure does not care about your purchase agreement.
4. Employment and benefits diligence, particularly any union contract or multiemployer plan participation.
5. Confirm the seller is solvent after the deal — or, if it is not, understand that you are in voidable-transfer territory and price accordingly.

In the documents:

6. 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.
7. Representations and warranties with survival periods that actually outlast the risk.
8. Indemnification with real security — escrow or holdback. An indemnity from an entity that will dissolve after closing is a promise from nobody.
9. Consider R&W insurance where the deal size supports it.
10. Reasonably equivalent value, documented. Appraisal support protects against both the fraudulent-transaction exception and a voidable-transfer claim.
11. Cash rather than buyer equity where practical, to avoid the de facto merger indicators.

After closing — and this is the part nobody plans for:

12. Do not pay the seller’s old debts. Not as a courtesy, not to keep a supplier happy, not to preserve goodwill. That is the raw material of an implied-assumption argument, and it is created by well-intentioned people in accounts payable.
13. Do not tell customers you are the same company. Marketing continuity is what a de facto merger claim is built from, and the marketing team will not know that.
14. Keep the entities genuinely separate — separate books, separate accounts, separate governance.
15. Route predecessor claims through counsel, not through operations.

The asset-versus-stock decision

Successor liability is one input into a decision that also turns on tax treatment, contract assignability, licensing, and employee continuity. We wrote about the broader choice here.

The short version: an asset purchase gives better liability protection than a stock purchase, and that protection is real in Minnesota — reinforced by § 302A.661, subd. 4 and by the absence of a product-line exception. But it is a default, not a guarantee. Independent statutes reach the buyer on their own terms, the seller’s LLC status may change the analysis, and the exposure that does exist is created by conduct after closing at least as often as by drafting before it.

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.