# Small-Business Asset Purchase Agreements: What Transfers[^about]
Which assets the buyer acquires and which liabilities stay with the seller, how specific the schedules should be, liens, ownership of code and content, work still owned by contributors, customer data and security representations.
## Which assets does the buyer acquire, and which liabilities stay with the seller? {#asset-and-liability-perimeter}
**Short answer.** Commentary recommends that an asset purchase agreement make very clear which assets are included and which are excluded, and the agreement assigns responsibility between the parties for the seller's obligations, which one filed agreement does by listing the liabilities the buyer assumes and leaving every other liability with the seller. [^ratschko-clear-asset-inclusions-exclusions][^hodson-contractual-liability-allocation][^p2-grove-retained-liabilities]
The four defined categories below take their definitions from one filed asset purchase agreement for a supplement business, as examples of negotiated drafting rather than required wording:
| Category | Definition |
| --- | --- |
| Purchased assets | The assets the buyer acquires. The filed agreement defines its acquired assets as all of the seller's assets other than the excluded assets. [^p2-grove-acquired-assets] |
| Excluded assets | The assets the seller keeps. The filed agreement excludes the assets listed on a schedule and states that the excluded assets include the seller's cash. [^p2-grove-excluded-assets] |
| Assumed liabilities | The seller's liabilities that the buyer agrees to take on. The filed agreement limits them to the liabilities listed on a schedule. [^p2-grove-assumed-liabilities] |
| Retained liabilities | Every other liability of the seller. The filed agreement leaves them with the seller whether they arise before, on or after closing and whether or not they were disclosed. [^p2-grove-retained-liabilities] |
An assumed obligation can be identified by its contract type and the period it covers: one filed agreement for an online publishing business made the buyer responsible for fulfilling job listings and subscriptions sold before closing, listed those obligations on a schedule, and included refunds to subscribers who cancel. [^p2-salem-fulfillment-liability]
The following synthetic example illustrates choices for the purchase of a small software-as-a-service business, not observed terms or a mandatory allocation:
| Item | Decision the parties need to express |
| --- | --- |
| Cash and receivables | Whether the seller keeps bank balances, pre-closing receivables and payouts still pending with the payment processor, or the buyer acquires specified amounts. |
| Code and repositories | Which repositories and deployment configurations transfer, and whether any code belongs to a contractor or is licensed from a third party ([contractor-owned code](#copyright-transfer-formality), [website or app migration](/practice-guides/asset-purchase/us#website-migration)). |
| Domains | Which domain names transfer and from which registrar account ([domain transfer](/practice-guides/asset-purchase/us#domain-closing)). |
| App-store registrations | Which app listings transfer and whether the buyer's developer account can receive them ([app transfer](/practice-guides/asset-purchase/us#app-transfer)). |
| Hosting, SaaS and provider accounts | Which accounts transfer whole, which are shared with the seller's other businesses and need separating, and which the buyer replaces ([account migration](/practice-guides/asset-purchase/us#migration-timing), [shared accounts](/practice-guides/asset-purchase/us#shared-accounts), [handover check](/practice-guides/asset-purchase-closing-and-handover/us#digital-handover)). |
| Prepaid subscriptions and refunds | Whether the buyer serves annual plans paid before closing and who bears refunds and chargebacks ([customer obligations](/practice-guides/asset-purchase-after-closing/us#customer-obligation-cutoff)). |
| Customer data and records | Which customer records transfer, subject to privacy-policy and data-use restrictions ([customer data](#data-transfer-review)). |
| Supplier and customer contracts | Which agreements are included and which need a counterparty's consent to assignment ([contract consents](/practice-guides/asset-purchase-closing-and-handover/us#consent-failure)). |
A general grant of the seller's assets can miss an asset the business uses but the seller does not hold, such as intellectual property held by an owner or an affiliate; one filed agreement addresses that gap with a representation that no affiliate of the seller has an interest in intellectual property used in or necessary for the business, other than as scheduled. [^p2-luna-affiliate-ip] The [schedules question](#schedules) addresses how specific each list needs to be, [lien review](#liens-and-title) addresses encumbered assets, and [contract consents](/practice-guides/asset-purchase-closing-and-handover/us#consent-failure) addresses assets that cannot move without a third party.
A contractual allocation between buyer and seller does not by itself answer what rights a third party has, because the seller's creditors are not parties to the asset purchase agreement and, outside sales governed by bankruptcy-court orders and other judicial sales, are not bound by it. [^d1-hodson-creditors-not-bound] Third-party exposure is a separate review; this guide does not determine successor liability in any particular state, industry or transaction, and the [successor-liability question](/practice-guides/asset-purchase-structure-and-parties/us#successor-liability) describes the general rule and its recognized exceptions. [^hodson-contractual-liability-allocation]
## Which schedules do we need, and how specific should they be? {#schedules}
**Short answer.** Commentary recommends making very clear which assets are included and which are excluded, and schedules can do that work, as in one filed agreement whose acquired assets include those set forth on a schedule and whose assumed liabilities are only those listed on another schedule. [^ratschko-schedules-included-excluded][^p2-grove-acquired-schedule][^p2-grove-assumed-schedule] Another filed agreement lists every intellectual-property agreement by date, title and parties. [^ip-contracts-schedules]
Beyond the perimeter, schedules record the facts of the particular transaction: one filed agreement qualifies the seller's representation that no notice or consent is needed for the sale by the consents listed on a schedule. [^p2-luna-consent-schedule] An online publishing agreement lists on a schedule the permitted liens other than those to be released at or before closing, [^p2-salem-permitted-liens] and lists on another schedule the subscriptions and job listings sold before closing that the buyer must fulfill. [^p2-salem-fulfillment-schedule] Handover steps can be scheduled too: one agreement requires the seller to give the buyer administrative-level access to the software and application items listed on a schedule, [^p2-igourmet-admin-access] and an internet-services agreement set out its transition terms in a schedule, starting with a list of the user names and passwords to servers and software. [^p2-sitestar-transition-schedule]
Essential assets are identified item by item: for an online business, the identifiers start with the websites, domain names and social-media accounts, which one filed agreement lists on a schedule together with the website content and software code it transfers. [^p2-salem-websites-schedule] Accounts can be listed by institution and account number, as one agreement does for every bank account and the persons authorized to draw on it, [^p2-bankrate-bank-accounts] and software can be listed product by product, [^p2-bankrate-software-list] while app identifiers and code repositories are covered in the [app transfer](/practice-guides/asset-purchase/us#app-transfer) and [website migration](/practice-guides/asset-purchase/us#website-migration) questions. Replaceable items can be described by category: the same online publishing agreement transfers its office equipment, computers and inventory as a category that includes, but is not limited to, the items on a schedule. [^p2-salem-tangible-category]
Disclosure schedules have a separate job, and Tyler Conway and Tracy Belton identify two kinds of schedule information, lists and exceptions. [^conway-lists-exceptions] Exception schedules record the seller's exceptions to its representations, such as a known dispute, an unassigned contractor contribution or a lien that will be paid at closing, and an exception properly scheduled is not a breach of the representation it qualifies. [^meyers-scheduled-exception] One filed agreement ties each exception to the representation it qualifies: its intellectual-property representations are each made except as set forth in a numbered part of its schedule. [^p2-luna-ip-exception]
## What should the agreement say about who owns the code and content? {#ip-title-and-dependencies}
**Short answer.** The agreement can include a representation that the seller owns the intellectual property being sold, as one filed asset purchase agreement did by representing sole and exclusive ownership of its intellectual-property assets, free and clear of encumbrances, while expressly not representing that those rights are enforceable. [^p4-luna-ip-ownership]
The schedules show what the ownership representation covers and where the business depends on someone else's rights: the same agreement required a schedule listing all of its intellectual-property agreements, specifying each agreement's date, title and parties. [^ip-contracts-ip-title-and-dependencies] It also represented that the seller had contracts with its current and former employees and with each contributing contractor under which the contractor acknowledged the seller's ownership, presently assigned any ownership interest and waived moral rights to the extent the law permits. [^p4-luna-contributor-assignments] A disclosure schedule can record exceptions to those representations, as the same agreement did by making one of its intellectual-property representations except as set forth in a numbered part of its schedule; [^d1-luna-ip-exception] where a contributor still owns U.S. copyright, the signed-writing rule is addressed under [contributor-owned code](#copyright-transfer-formality).
Where the business depends on intellectual property the seller keeps, the agreement can grant an express post-closing use right: one filed asset purchase agreement kept code shared with the seller's other websites as an excluded asset that remained the seller's property after closing. [^p4-salem-shared-code-retained] It gave the buyer a royalty-free, perpetual, noncancellable worldwide license to use that shared code for the websites and the business. [^p4-salem-shared-code-license]
## Can the customer data move with the business? {#data-transfer-review}
**Short answer.** Privacy promises made to customers can constrain a transfer of their data: in the Facebook–WhatsApp acquisition, the FTC stated that WhatsApp must continue to honor its promises to consumers regardless of the acquisition. [^privacy-promises-data-transfer-review]
For a business covered by California's consumer privacy law, transferring a consumer's personal information as an asset in a merger, acquisition or other transaction in which the recipient assumes control of all or part of the business is not a sale, provided that the information is used or shared consistently with that law. [^p4-ccpa-merger-exclusion] If the recipient later materially alters how it uses or shares that information in a manner materially inconsistent with the promises made at collection, it must give consumers prior notice of the new or changed practice. [^p4-ccpa-changed-practice-notice]
The seller's privacy policy is the starting point, as a 2015 letter about a proposed bankruptcy sale of customer data shows, in which FTC consumer-protection staff read RadioShack's privacy policies as clearly and expressly representing that customer information would not be rented or sold to third parties. [^p4-ftc-radioshack-policy-promise] The letter warned that a sale of that information would contravene RadioShack's express promise not to sell or rent it and could be a deceptive or unfair practice under Section 5 of the FTC Act. [^d2-ftc-radioshack-section5] The same letter described the Toysmart settlement, which allowed a transfer only if the buyer agreed not to sell the customer information as a standalone asset, was in the same line of business, agreed to treat the information under Toysmart's privacy policy and agreed to seek affirmative consent before changing that policy for information gathered under it. [^p4-ftc-toysmart-conditions]
A data schedule can identify each dataset and the copies the seller keeps, as in one filed asset purchase agreement that transferred the originals, or true and complete copies, of the customer records, customer lists and databases set forth on a schedule, while letting the seller keep a copy for internal recordkeeping and other legal and accounting purposes. [^p4-salem-records-copy] The same agreement required the seller to cooperate in moving purchased files and content from the seller's servers to servers the buyer selected as soon as reasonably practicable after closing. [^p4-salem-server-migration] A buyer that does not want the seller to keep a copy can require deletion, as one filed agreement for an online survey panel did by requiring the seller to permanently delete overlapping panel members within five days of closing and to certify the deletion in writing. [^d2-greenfield-panel-deletion]
The RadioShack letter was a staff letter about one bankruptcy sale, and it stated that its views did not necessarily reflect those of the Commission or any individual Commissioner. [^d2-ftc-radioshack-staff-views] Some categories of data carry their own federal rules: the Children's Online Privacy Protection Act, for example, makes it unlawful for an operator of a website or online service directed to children, or one with actual knowledge that it is collecting personal information from a child, to collect that information in a manner that violates the FTC's regulations. [^d2-coppa-6502a]
## How does the buyer make sure the assets are free of liens? {#liens-and-title}
**Short answer.** Under the Uniform Commercial Code as Delaware enacts it, a lien can survive the sale of an asset, because a security interest generally continues in collateral after a sale unless the secured party authorized the sale free of it. [^liens-ucc-9315]
Margaret M. Salinas recommends ordering UCC, litigation and tax lien searches on the seller at the outset of every transaction, [^salinas-searches-early] and making payoff of existing liens, with evidence of their release, a condition to closing. [^salinas-payoff-condition] The UCC search runs in the seller's state of organization, because under Delaware's UCC the law of the jurisdiction where the debtor is located generally governs perfection [^d1-ucc-9301-debtor-location] and a registered organization organized under a state's law is located in that state. [^d1-ucc-9307e-registered-organization] It runs against the seller's exact legal name, because a financing statement with a defective debtor name still counts if a search under the debtor's correct name, using the filing office's standard search logic, would disclose it. [^d1-ucc-9506c-search-logic] A single filing can reach the whole business, because a financing statement sufficiently indicates its collateral by stating that it covers all assets or all personal property. [^d1-ucc-9504-all-assets]
Payoff letters tie each release to the closing payment: one filed agreement required payoff letters from each person holding a lien on the acquired assets, stating the secured amount that the seller would pay at closing, followed by filed UCC-3 termination statements after closing. [^d1-grove-payoff-letters]
After payment, the release is completed with a termination statement: under Delaware's UCC, for collateral other than the consumer goods covered by a separate rule, a secured party must send or file a termination statement within 20 days after it receives the debtor's signed demand when one of the listed conditions is met, such as no secured obligation or commitment remaining. [^liens-ucc-9513c] Except as otherwise provided in section 9-510, which governs whether a filed record is effective, the financing statement stops being effective once the termination statement is filed. [^liens-ucc-9513d] Because the statutory 20-day duty runs from the debtor's signed demand, a payoff letter can instead commit the lender to file the termination on receipt of the payoff amount. [^liens-ucc-9513c]
The seller's title representation addresses a lien the search missed: one filed agreement for an online publishing business represented that the seller had good, valid and marketable title to all of the sale assets, free and clear of any liens except permitted liens, [^d1-salem-good-title] and listed on a schedule the permitted liens other than those to be released at or before closing. [^d1-salem-permitted-liens-title] Vehicles need a separate check: under Delaware's UCC, filing a financing statement is not necessary or effective to perfect a security interest in property subject to the certificate-of-title rules for motor vehicles, among other listed statutes. [^d1-ucc-9311-certificate-of-title] The [legal due diligence guide](/practice-guides/legal-due-diligence/us#structure-consequences) places lien review within a wider liability review.
## What if a contractor or founder still owns part of the code? {#copyright-transfer-formality}
**Short answer.** A contractor or founder who still owns U.S. copyright in part of the business's code or content must sign the transfer, or have an authorized agent sign it, because 17 U.S.C. § 204(a) requires the rights owner's signed writing for a copyright ownership transfer outside operation of law. [^copyright-writing-copyright-transfer-formality]
Because the writing must be signed by the owner of the rights conveyed or that owner's authorized agent, a signature from the selling company alone does not establish a missing contributor assignment. [^copyright-writing-copyright-transfer-formality] Who owns the rights depends on who created the work and how: copyright vests initially in the author, [^d1-usc-201a-initial-ownership] and for a work made for hire the employer or other person for whom the work was prepared is considered the author and, absent a signed written agreement otherwise, owns all of the rights. [^d1-usc-201b-work-for-hire] Existing licenses also survive the files' arrival: a nonexclusive license evidenced by a writing signed by the rights owner prevails over a conflicting transfer of ownership if it was taken before the transfer was executed, or in good faith before the transfer was recorded and without notice of it. [^d1-usc-205e-nonexclusive-license]
The asset schedule identifies the relevant code, content and other works, and a separate copyright assignment can supply the conveyance, as in one filed agreement that called for an assignment of copyrights at closing alongside the assignment and bill of sale. [^d1-greenfield-copyright-assignment] When a contributor assignment is missing, the parties can make its delivery a closing condition or exclude the affected work with a price change; to accept the risk instead, the seller can give a specific representation, as one filed agreement did by representing that each contributing contractor had presently assigned any ownership interest to the seller. [^d1-luna-contractor-assignment-rep] [Third-party dependencies](#ip-title-and-dependencies) are addressed through the ownership representation and its schedules.
## What should the agreement's security representations cover? {#data-and-incidents}
**Short answer.** An agreement can address current safeguards and past security incidents in separate representations, as one filed asset purchase agreement did: one that the seller had implemented reasonable safeguards, and another, qualified by the seller's knowledge, about security incidents in the past five years involving third-party processors' systems or data. [^security-data-and-incidents][^salem-incident-history]
A known incident belongs on the disclosure schedule as an exception, because a representation is made except as disclosed, so an exception properly scheduled is not a breach at all. [^d2-meyers-scheduled-exception] The lookback period and any knowledge qualification are negotiated terms that the agreement states expressly, as that agreement's five-year period and knowledge qualifier show. [^salem-incident-history]
[^about]: By Steven Obiajulu, J.D. Published by [openagreements.org](https://openagreements.org). Last reviewed 2026-09-28. License: CC BY 4.0. Steven Obiajulu, J.D. edits this topic article for U.S. purchases of profitable businesses with $1 million or less of earnings before interest, taxes, depreciation and amortization (EBITDA), including online and software businesses; negotiation, drafting and closing of the asset purchase agreement and transfer of the assets; Delaware, California and New York law used as examples; other state, tax and industry rules require separate review coverage. It synthesizes legal sources and is not legal advice. This article is for informational purposes only and does not create an attorney-client relationship. AI-authored research draft; not reviewed by counsel. Source excerpts and linked materials belong to their owners. CC BY 4.0. Cite as Steven Obiajulu, *Small-Business Asset Purchase Agreements: What Transfers*, OpenAgreements (last updated September 28, 2026), https://openagreements.org/practice-guides/asset-purchase-what-transfers/us.
[^ratschko-clear-asset-inclusions-exclusions]: **Imke Ratschko: The Basics of an Asset Purchase Agreement (Ratschko PLLC)** — "So I recommend that the description makes it very clear which assets are included, and which are excluded." *Imke Ratschko, The Basics of an Asset Purchase Agreement, Ratschko PLLC (July 25, 2022; updated July 28, 2022).*
[^hodson-contractual-liability-allocation]: **Samuel D. Hodson: Successor Liability Risks in Asset Purchase Agreements (Taft)** — "The asset purchase agreement assigns responsibility between the parties for the seller’s obligations." *Samuel D. Hodson, Successor Liability Risks in Asset Purchase Agreements, Taft Law Bulletins (June 26, 2020).*
[^p2-grove-retained-liabilities]: **Grove–VitaMedica asset purchase agreement (2021), retained liabilities** — "With the sole exception of the Assumed Liabilities, the Seller shall retain, and the Buyer shall not be obligated to pay, perform or otherwise discharge, any other Liabilities of Seller, whether arising prior to, on or after the Closing Date, whether or not related to the Business and whether or not disclosed to the Buyer (‘Retained Liabilities’)." *§2.2(b)(i)*
[^p2-grove-acquired-assets]: **Grove–VitaMedica asset purchase agreement (2021), acquired assets** — "The term ‘Acquired Assets’ means all assets of the Seller, other than the Excluded Assets." *§2.1(a)*
[^p2-grove-excluded-assets]: **Grove–VitaMedica asset purchase agreement (2021), excluded assets** — "Notwithstanding anything to the contrary in this Agreement, the Acquired Assets shall not include the assets, properties and rights of Seller set forth on Schedule 2.1(b) hereto (collectively, the ‘Excluded Assets’). The term Excluded Assets includes without limitation cash of Seller." *§2.1(b)*
[^p2-grove-assumed-liabilities]: **Grove–VitaMedica asset purchase agreement (2021), assumed liabilities** — "‘Assumed Liabilities’ means only those Liabilities of Seller set forth on Schedule 2.2(a), which includes a list of the assumed accounts payable of Seller." *§2.2(a)*
[^p2-salem-fulfillment-liability]: **Salem asset purchase agreement (2023), fulfillment liability** — "The Assumed Liabilities include the liability to fulfill contracts for all job listings and subscriptions to products and services on the Websites sold by Seller prior to the Closing Date, all of which liabilities are set forth on Schedule 1.3(a) (such liabilities, the ‘Fulfillment Liability’), including the liability to pay refunds to any subscribers who cancel (for whatever reason) their subscriptions to any of the Website’s products and services sold by Seller." *§1.3(a)*
[^p2-luna-affiliate-ip]: **Luna–Micron asset purchase agreement (2018), affiliate intellectual property** — "No Seller Affiliate (other than as identified on Schedule 3.25(a)) owns, directly or indirectly, or has any interest (including but not limited to license-based interests) in any Intellectual Property Asset or other Intellectual Property that relates to, is used or held for use in, or is necessary for the Business." *§3.25*
[^d1-hodson-creditors-not-bound]: **Samuel D. Hodson: creditors are not bound by the asset purchase agreement (Taft)** — "A seller’s creditors are not parties to the asset purchase agreement and are not bound by it. (Sales governed by bankruptcy court orders pursuant to 11 U.S.C. 363 and other judicial sales may be an exception to this rule.)" *Samuel D. Hodson, Successor Liability Risks in Asset Purchase Agreements, Taft Law Bulletins (June 26, 2020).*
[^ratschko-schedules-included-excluded]: **Imke Ratschko: The Basics of an Asset Purchase Agreement (Ratschko PLLC)** — "So I recommend that the description makes it very clear which assets are included, and which are excluded." *Imke Ratschko, The Basics of an Asset Purchase Agreement, Ratschko PLLC (July 25, 2022; updated July 28, 2022).*
[^p2-grove-acquired-schedule]: **Grove–VitaMedica asset purchase agreement (2021), acquired-assets schedule** — "The Acquired Assets include, without limitation, those set forth on Schedule 2.1(a) hereto." *§2.1(a)*
[^p2-grove-assumed-schedule]: **Grove–VitaMedica asset purchase agreement (2021), assumed-liabilities schedule** — "‘Assumed Liabilities’ means only those Liabilities of Seller set forth on Schedule 2.2(a), which includes a list of the assumed accounts payable of Seller." *§2.2(a)*
[^ip-contracts-schedules]: **Luna–Micron asset purchase agreement (2018)** — "Schedule 3.25(b) contains a correct, current and complete list of all Intellectual Property Agreements, specifying for each the date, title and parties thereto." *§3.25(b)*
[^p2-luna-consent-schedule]: **Luna–Micron asset purchase agreement (2018), consents schedule** — "Except as set forth in Schedule 3.2(c), Seller is not required to give any notice to or obtain any Consent from any Person in connection with the execution and delivery of this Agreement or the consummation or performance of any of the Contemplated Transactions." *§3.2(c)*
[^p2-salem-permitted-liens]: **Salem asset purchase agreement (2023), permitted liens schedule** — "To Seller’s knowledge, all Permitted Liens other than those that will be released at or before Closing are set forth on Schedule 5.4." *§5.4*
[^p2-salem-fulfillment-schedule]: **Salem asset purchase agreement (2023), fulfillment liability schedule** — "The Assumed Liabilities include the liability to fulfill contracts for all job listings and subscriptions to products and services on the Websites sold by Seller prior to the Closing Date, all of which liabilities are set forth on Schedule 1.3(a) (such liabilities, the ‘Fulfillment Liability’), including the liability to pay refunds to any subscribers who cancel (for whatever reason) their subscriptions to any of the Website’s products and services sold by Seller." *§1.3(a)*
[^p2-igourmet-admin-access]: **Innovative Gourmet–iGourmet asset purchase agreement (2024), administrative access** — "Promptly following the execution of this Agreement, Seller shall provide Buyer with administrative level access to the software/application items listed on Section 5.01 of the Disclosure Schedules." *§5.01*
[^p2-sitestar-transition-schedule]: **OW Holdings–Sitestar asset purchase agreement (2007), transition schedule** — "The Parties agree to the following transition related terms at Closing; 1. Seller agrees to provide Buyer with a list of all necessary user names and passwords to servers and software on or immediately after the Transfer Date." *Schedule 2.4*
[^p2-salem-websites-schedule]: **Salem asset purchase agreement (2023), websites, domains and software** — "(d) Internet Domains, Social Media Accounts. All websites, Internet domains, social media accounts, and their related Uniform Resource Locators (‘URLs’) used in the operation of the Business (‘Websites’, ‘Domain Names’ and ‘Social Media Accounts’, respectively) listed on Schedule 1.1(d); (e) Content and Software. All content on the Websites (including all rights and interests of Seller to content created by third parties which is not owned by Seller), including e-mail addresses of registered users, technology, and any master media files in Seller’s possession, as well as all functionality of the Websites, including content management systems, and software codes and enhancements, other than the Shared Code (defined in Section 8.9);" *§1.1(d)–(e)*
[^p2-bankrate-bank-accounts]: **Bankrate asset purchase agreement (2016), bank accounts schedule** — "Schedule 4.23 is a complete and correct list of each bank or financial institution in which Seller has an account, safe deposit box or lockbox, or maintains a banking, custodial, trading or similar relationship, the number of each such account or box, and the names of all persons authorized to draw thereon or to having signatory power or access thereto." *§4.23*
[^p2-bankrate-software-list]: **Bankrate asset purchase agreement (2016), proprietary products schedule** — "Schedule 4.10(c) sets forth a true, correct and complete list of each proprietary product or service developed, licensed, manufactured, marketed or sold by Seller, including the Seller Proprietary Software." *§4.10(c)*
[^p2-salem-tangible-category]: **Salem asset purchase agreement (2023), tangible personal property** — "(a) Tangible Personal Property. All office equipment, computers, monitors, servers, modems, desk, chairs, software, parts, supplies, furniture, furnishings, tools, fixtures, leasehold improvements, inventory, and other tangible personal property used in the conduct of the Business including but not limited to the items set forth on Schedule 3.6 (collectively, ‘Tangible Personal Property’); (b) Licenses and Permits. All rights associated with the ‘Licenses’ (as that term is defined in Section 3.17) necessary to operate the Business as it is currently operated except for the Excluded Licenses;" *§1.1(a)–(b)*
[^conway-lists-exceptions]: **Tyler Conway and Tracy Belton: Tips on drafting and negotiating disclosure schedules (Arnold & Porter)** — "There are two categories of information presented in disclosure schedules: lists and exceptions." *Tyler Conway and Tracy Belton, Tips on Drafting and Negotiating Disclosure Schedules, Arnold & Porter (Dec. 4, 2015).*
[^meyers-scheduled-exception]: **Conor Meyers: Representations and warranties in a business sale, scheduled exceptions** — "A representation is made except as disclosed, so an exception properly scheduled is not a breach at all." *Conor Meyers, Reps and Warranties in a Business Sale, Clark Meyers (Aug. 21, 2026).*
[^p2-luna-ip-exception]: **Luna–Micron asset purchase agreement (2018), intellectual-property exceptions** — "Except as set forth in Schedule 3.25(c), none of the Intellectual Property Assets will be subject to any Encumbrance as a result of any written agreement or other facts or circumstances existing before the date hereof." *§3.25(c)*
[^p4-luna-ip-ownership]: **Luna–Micron asset purchase agreement (2018), IP ownership** — "Seller is the sole and exclusive legal and beneficial owner of all right, title, and interest in and to the Intellectual Property Registrations and Intellectual Property Assets, free and clear of Encumbrances (it being understood and acknowledged that the foregoing representation and warranty does not constitute a representation and warranty of enforceability of any such Intellectual Property Registrations and Intellectual Property Assets)." *§3.25(c)*
[^ip-contracts-ip-title-and-dependencies]: **Luna–Micron asset purchase agreement (2018)** — "Schedule 3.25(b) contains a correct, current and complete list of all Intellectual Property Agreements, specifying for each the date, title and parties thereto." *§3.25(b)*
[^p4-luna-contributor-assignments]: **Luna–Micron asset purchase agreement (2018), employee and contractor IP contracts** — "Seller (and its predecessor-in-interest) have entered into Contracts with each current and former employee in the form attached to Schedule 3.25(c) and has entered into Contracts with each current and former independent contractor who is or was involved in or has contributed to the invention, creation, or development of any Intellectual Property during the course of engagement with or for the benefit of Seller whereby such independent contractor (i) acknowledges Seller’s exclusive ownership of all Intellectual Property Assets invented, created or developed by such independent contractor within the scope of his or her engagement with such Seller; (ii) grants to such Seller a present, irrevocable assignment of any ownership interest such independent contractor may have in or to such Intellectual Property; and (iii) irrevocably waives any right or interest, including any moral rights, regarding such Intellectual Property, to the extent permitted by applicable Legal Requirement." *§3.25(c)*
[^d1-luna-ip-exception]: **Luna–Micron asset purchase agreement (2018), scheduled IP exception** — "Except as set forth in Schedule 3.25(c), none of the Intellectual Property Assets will be subject to any Encumbrance as a result of any written agreement or other facts or circumstances existing before the date hereof." *§3.25*
[^p4-salem-shared-code-retained]: **Salem asset purchase agreement (2023), shared code retained by seller** — "Seller and Buyer acknowledge that there has been shared use of certain assets, including certain shared code, design and functionality of the Websites, and the software code, design, and functionality of other of Seller’s websites (the ‘Shared Code’), which is an Excluded Asset and which ownership shall remain with Seller following the Closing Date." *§8.9*
[^p4-salem-shared-code-license]: **Salem asset purchase agreement (2023), license to shared code** — "Buyer shall have the royalty-free, perpetual, noncancellable worldwide license to use the Shared Code with respect to the Websites and the Business." *§8.9*
[^privacy-promises-data-transfer-review]: **FTC statement concerning the Facebook–WhatsApp acquisition** — "We want to make clear that, regardless of the acquisition, WhatsApp must continue to honor these promises to consumers." *April 10, 2014, quoting the Bureau Director’s letter*
[^p4-ccpa-merger-exclusion]: **Cal. Civ. Code § 1798.140(ad)(2)(C), transfer in a merger or acquisition** — "(C) The business transfers to a third party the personal information of a consumer as an asset that is part of a merger, acquisition, bankruptcy, or other transaction in which the third party assumes control of all or part of the business, provided that information is used or shared consistently with this title." *Cal. Civ. Code § 1798.140(ad)(2)(C).*
[^p4-ccpa-changed-practice-notice]: **Cal. Civ. Code § 1798.140(ad)(2)(C), notice of changed practices after a transfer** — "If a third party materially alters how it uses or shares the personal information of a consumer in a manner that is materially inconsistent with the promises made at the time of collection, it shall provide prior notice of the new or changed practice to the consumer." *Cal. Civ. Code § 1798.140(ad)(2)(C).*
[^p4-ftc-radioshack-policy-promise]: **FTC Bureau of Consumer Protection letter concerning RadioShack customer data (2015), privacy promises** — "For the period covered by these privacy policies, RadioShack thus clearly and expressly represented that customer information would not be rented or sold to third parties." *Letter from Jessica L. Rich, Director, FTC Bureau of Consumer Protection, to Elise Frejka, Consumer Privacy Ombudsman, In re RadioShack Corp., No. 15-10197 (Bankr. D. Del.) (May 16, 2015), at 3.*
[^d2-ftc-radioshack-section5]: **FTC Bureau of Consumer Protection letter concerning RadioShack customer data (2015), Section 5 concern** — "We are concerned, however, that a sale or transfer of the personal information of RadioShack’s customers would contravene RadioShack’s express promise not to sell or rent such information and could constitute a deceptive or unfair practice under Section 5 of the FTC Act." *Letter from Jessica L. Rich, Director, FTC Bureau of Consumer Protection, to Elise Frejka, Consumer Privacy Ombudsman, In re RadioShack Corp., No. 15-10197 (Bankr. D. Del.) (May 16, 2015), at 4.*
[^p4-ftc-toysmart-conditions]: **FTC Bureau of Consumer Protection letter concerning RadioShack customer data (2015), Toysmart conditions** — "There, the Commission entered into a settlement with the company allowing the transfer of customer information under certain limited circumstances: 1) the buyer had to agree not to sell customer information as a standalone asset, but instead to sell it as part of a larger group of assets, including trademarks and online content; 2) the buyer had to be an entity that concentrated its business in the family commerce market, involving the areas of education, toys, learning, home and/or instruction (i.e., the same line of business that Toysmart had been in); 3) the buyer had to agree to treat the personal information in accordance with the terms of Toysmart’s privacy policy; and 4) the buyer had to agree to seek affirmative consent before making any changes to the policy that affected information gathered under the Toysmart policy." *Letter from Jessica L. Rich, Director, FTC Bureau of Consumer Protection, to Elise Frejka, Consumer Privacy Ombudsman, In re RadioShack Corp., No. 15-10197 (Bankr. D. Del.) (May 16, 2015), at 5.*
[^p4-salem-records-copy]: **Salem asset purchase agreement (2023), customer records and seller copy** — "(g) Records. The originals (where available) or true and complete copies (if originals are not available) of all of the email subscriber/customer records, customer lists, customer contact information, registered user lists, databases, access codes, books, records, files, videos, logs and ledgers pertaining to the Sale Assets or used in the operation of the Business as set forth on Schedule 1.1(g) (collectively, ‘Records’); provided, that Seller may keep a copy of the Records for its internal recordkeeping and other legal and accounting purposes;" *§1.1(g)*
[^p4-salem-server-migration]: **Salem asset purchase agreement (2023), migration of content to buyer's servers** — "Seller will cooperate with Buyer to transfer title to all of Seller’s files and content purchased by Buyer and stored at Closing on Seller’s servers from those servers to servers selected by Buyer as soon as reasonably practicable following the Closing." *§8.8*
[^d2-greenfield-panel-deletion]: **Greenfield Online–Dohring asset purchase agreement (2004), deletion of overlapping panel members** — "Seller agrees that on the Closing Date it will stop sending, and will stop authorizing any other Person to send, any email messages via the YIO domain or otherwise to members of the YIO Panel that are also members of the Panel, and that within five days of the Closing Seller will permanently delete from the YIO panel all members that are also members of the Panel, and an officer of Seller shall so certify in writing to the Buyer." *§5.5*
[^d2-ftc-radioshack-staff-views]: **FTC Bureau of Consumer Protection letter concerning RadioShack customer data (2015), staff views** — "Please note that the views expressed herein do not necessarily reflect the views of the Federal Trade Commission or any individual Commissioner." *Letter from Jessica L. Rich, Director, FTC Bureau of Consumer Protection, to Elise Frejka, Consumer Privacy Ombudsman, In re RadioShack Corp., No. 15-10197 (Bankr. D. Del.) (May 16, 2015), at 1 n.1.*
[^d2-coppa-6502a]: **15 U.S.C. § 6502(a)(1), children's online privacy** — "It is unlawful for an operator of a website or online service directed to children, or any operator that has actual knowledge that it is collecting personal information from a child, to collect personal information from a child in a manner that violates the regulations prescribed under subsection (b)." *15 U.S.C. § 6502(a)(1).*
[^liens-ucc-9315]: **Delaware Uniform Commercial Code, continuation of a security interest after disposition** — "Except as otherwise provided in this Article and in Section 2-403(2): (1) a security interest or agricultural lien continues in collateral notwithstanding sale, lease, license, exchange, or other disposition thereof unless the secured party authorized the disposition free of the security interest or agricultural lien; and (2) a security interest attaches to any identifiable proceeds of collateral." *6 Del. C. § 9-315(a).*
[^salinas-searches-early]: **Margaret M. Salinas: Five issues to address when acquiring a business (Chuhak & Tecson)** — "Uniform Commercial Code (UCC), litigation and tax lien searches should be ordered on the seller(s) at the onset of every transaction." *Margaret M. Salinas, Five Issues to Address When Acquiring a Business, Chuhak & Tecson (Apr. 18, 2024).*
[^salinas-payoff-condition]: **Margaret M. Salinas: Five issues to address when acquiring a business, lien payoff** — "If the seller(s) have existing liens, it should be a condition precedent to closing that those liens are paid off and evidence of the release of such liens is provided to the purchaser." *Margaret M. Salinas, Five Issues to Address When Acquiring a Business, Chuhak & Tecson (Apr. 18, 2024).*
[^d1-ucc-9301-debtor-location]: **Delaware Uniform Commercial Code § 9-301(1), law governing perfection** — "(1) Except as otherwise provided in this section, while a debtor is located in a jurisdiction, the local law of that jurisdiction governs perfection, the effect of perfection or nonperfection, and the priority of a security interest in collateral." *6 Del. C. § 9-301(1).*
[^d1-ucc-9307e-registered-organization]: **Delaware Uniform Commercial Code § 9-307(e), location of registered organization** — "(e) Location of registered organization organized under State law. — A registered organization that is organized under the law of a State is located in that State." *6 Del. C. § 9-307(e).*
[^d1-ucc-9506c-search-logic]: **Delaware Uniform Commercial Code § 9-506(c), search under the debtor’s correct name** — "(c) Financing statement not seriously misleading. — If a search of the records of the filing office under the debtor’s correct name, using the filing office’s standard search logic, if any, would disclose a financing statement that fails sufficiently to provide the name of the debtor in accordance with Section 9-503(a), the name provided does not make the financing statement seriously misleading." *6 Del. C. § 9-506(c).*
[^d1-ucc-9504-all-assets]: **Delaware Uniform Commercial Code § 9-504, indication of collateral** — "A financing statement sufficiently indicates the collateral that it covers if the financing statement provides: (1) a description of the collateral pursuant to Section 9-108; or (2) an indication that the financing statement covers all assets or all personal property." *6 Del. C. § 9-504.*
[^d1-grove-payoff-letters]: **Grove–VitaMedica asset purchase agreement (2021), payoff letters and UCC-3 terminations** — "(xi) Payoff letters from each Person who has any Lien on or affecting any or all of the Acquired Assets, which letters shall state the outstanding amount of the obligation secured by the Lien (which amount shall be paid by Seller at Closing to such Person) and, after Closing, Seller shall provide copies of executed and filed UCC-3 termination statements and/or similar or other instruments evidencing the satisfaction of such indebtedness or other obligation in each jurisdiction where evidence of such obligation is necessary to perfect such satisfaction;" *§2.5(xi)*
[^liens-ucc-9513c]: **Delaware Uniform Commercial Code § 9-513(c), termination statement on demand** — "(c) Other collateral. — In cases not governed by subsection (a), within 20 days after a secured party receives a signed demand from a debtor, the secured party shall cause the secured party of record for a financing statement to send to the debtor a termination statement for the financing statement or file the termination statement in the filing office if: (1) except in the case of a financing statement covering accounts or chattel paper that has been sold or goods that are the subject of a consignment, there is no obligation secured by the collateral covered by the financing statement and no commitment to make an advance, incur an obligation, or otherwise give value; (2) the financing statement covers accounts or chattel paper that has been sold but as to which the account debtor or other person obligated has discharged its obligation; (3) the financing statement covers goods that were the subject of a consignment to the debtor but are not in the debtor’s possession; or (4) the debtor did not authorize the filing of the initial financing statement." *6 Del. C. § 9-513(c).*
[^liens-ucc-9513d]: **Delaware Uniform Commercial Code § 9-513(d), effect of termination** — "(d) Effect of filing termination statement. — Except as otherwise provided in Section 9-510, upon the filing of a termination statement with the filing office, the financing statement to which the termination statement relates ceases to be effective." *6 Del. C. § 9-513(d).*
[^d1-salem-good-title]: **Salem asset purchase agreement (2023), title to sale assets** — "Seller has good, valid and marketable title to all of the Sale Assets, free and clear of any Liens except for Permitted Liens." *§3.5(a)*
[^d1-salem-permitted-liens-title]: **Salem asset purchase agreement (2023), permitted liens schedule (title)** — "To Seller’s knowledge, all Permitted Liens other than those that will be released at or before Closing are set forth on Schedule 5.4." *§5.4*
[^d1-ucc-9311-certificate-of-title]: **Delaware Uniform Commercial Code § 9-311(a), property subject to certificate-of-title rules** — "(a) Security interest subject to other law. — Except as otherwise provided in subsection (d), the filing of a financing statement is not necessary or effective to perfect a security interest in property subject to: (1) a statute, regulation, or treaty of the United States whose requirements for a security interest’s obtaining priority over the rights of a lien creditor with respect to the property preempt Section 9-310(a); (2) Subchapter II of Chapter 23 of Title 21, relating to the notation of liens and encumbrances on certificates of title for motor vehicles; or (3) a statute of another jurisdiction which provides for a security interest to be indicated on a certificate of title as a condition or result of the security interest’s obtaining priority over the rights of a lien creditor with respect to the property." *6 Del. C. § 9-311(a).*
[^copyright-writing-copyright-transfer-formality]: **Execution of copyright transfers** — "A transfer of copyright ownership, other than by operation of law, is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed or such owner’s duly authorized agent." *17 U.S.C. §204(a)*
[^d1-usc-201a-initial-ownership]: **Initial ownership of copyright** — "Copyright in a work protected under this title vests initially in the author or authors of the work." *17 U.S.C. §201(a)*
[^d1-usc-201b-work-for-hire]: **Works made for hire** — "In the case of a work made for hire, the employer or other person for whom the work was prepared is considered the author for purposes of this title, and, unless the parties have expressly agreed otherwise in a written instrument signed by them, owns all of the rights comprised in the copyright." *17 U.S.C. §201(b)*
[^d1-usc-205e-nonexclusive-license]: **Copyright: priority of a nonexclusive license over a later transfer** — "A nonexclusive license, whether recorded or not, prevails over a conflicting transfer of copyright ownership if the license is evidenced by a written instrument signed by the owner of the rights licensed or such owner's duly authorized agent, and if- (1) the license was taken before execution of the transfer; or (2) the license was taken in good faith before recordation of the transfer and without notice of it." *17 U.S.C. § 205(e)*
[^d1-greenfield-copyright-assignment]: **Greenfield–Dohring asset purchase agreement (2004), copyright assignment at closing** — "Such documents shall include, without limitation, an Assignment and Bill of Sale in the form attached hereto as Exhibit 2.5, an Assignment of Trademarks in the form attached hereto as Exhibit 2.5(a), an Assignment of Copyrights in the form attached hereto as Exhibit 2.5(b), and any assignments or other documents necessary to effect such transfer and conveyance of the Transferred Assets." *§2.5*
[^d1-luna-contractor-assignment-rep]: **Luna–Micron asset purchase agreement (2018), contractor assignment representation** — "Seller (and its predecessor-in-interest) have entered into Contracts with each current and former employee in the form attached to Schedule 3.25(c) and has entered into Contracts with each current and former independent contractor who is or was involved in or has contributed to the invention, creation, or development of any Intellectual Property during the course of engagement with or for the benefit of Seller whereby such independent contractor (i) acknowledges Seller’s exclusive ownership of all Intellectual Property Assets invented, created or developed by such independent contractor within the scope of his or her engagement with such Seller; (ii) grants to such Seller a present, irrevocable assignment of any ownership interest such independent contractor may have in or to such Intellectual Property; and (iii) irrevocably waives any right or interest, including any moral rights, regarding such Intellectual Property, to the extent permitted by applicable Legal Requirement." *§3.25(c)*
[^security-data-and-incidents]: **Salem asset purchase agreement (2023)** — "Seller has implemented reasonable and appropriate administrative, physical and technical safeguards to protect the privacy, security, confidentiality, availability, and integrity of all Business Data and Business Systems, in material compliance with all applicable Data Protection Requirements." *§3.15(e)*
[^salem-incident-history]: **Salem asset purchase agreement (2023), security incidents** — "To Seller’s knowledge during the past five years there has been no Security Incident involving any Business System operated or controlled by any Third Party Processor or any Business Data under the custody or control of any Third Party Processor." *§3.15(e)*
[^d2-meyers-scheduled-exception]: **Conor Meyers: Representations and warranties in a business sale (Clark Meyers), disclosure schedules** — "A representation is made except as disclosed, so an exception properly scheduled is not a breach at all." *Conor Meyers, Reps and Warranties in a Business Sale, Clark Meyers (Aug. 21, 2026).*
For repeat use, install the skill: `npx skills add open-agreements/open-agreements` (lawyer-reviewed agreement templates + 50-state practice guides).