Wind-downs and transitions
Selling the company's IP vs licensing its operational records
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Selling company IP after shutdown and licensing its operational records are two different deals. An IP sale transfers ownership of patents, trademarks, domains, code and trade secrets. A license grants limited use of prepared support tickets or job histories while ownership stays put. Settle the IP sale's asset schedule first, so records are not swept in.
Key takeaways
- An IP sale moves ownership once; a records license grants a defined use and can be non-exclusive.
- Asset purchase agreements often define purchased assets to include books, records and data, which can sweep operational archives into the IP sale.
- Records that reveal sold code or trade secrets may need the IP buyer's consent before they are licensed, depending on what the agreement transferred.
- Running both deals works best when one inventory splits assets into an IP schedule and a records schedule.
How does an IP sale differ from licensing operational records?#
An IP sale and a records license differ in what moves and what the company keeps. In an IP sale, title to patents, trademarks, domain names, software copyrights and trade secrets passes to the buyer, and the seller usually walks away with no further rights. In a records license, the company or its successor grants a defined use of prepared copies of support tickets, CRM histories, engineering discussions or job records, and ownership stays where it was.
The two deals also attract different counterparties and different diligence. IP buyers ask about chain of title, registrations and liens. Data licensees ask about provenance, permitted use, privacy preparation and whether the records connect a request to a decision and an outcome.
| Question | Selling the IP | Licensing operational records |
|---|---|---|
| What moves | Ownership of registered and unregistered IP | A permitted use of prepared copies |
| What the seller keeps | Usually nothing in the sold assets | Ownership and, if non-exclusive, the right to license again |
| Typical counterparty | Competitor, strategic acquirer, brand or patent buyer | AI developer seeking records of real business work |
| Core diligence | Chain of title, registrations, liens, founder and employee assignments | Provenance, contract and privacy limits, de-identification, linkage |
| Ongoing obligations | Reps and warranties, sometimes an escrow or holdback | Use limits, deletion terms, audit or reporting under the license |
| Main risk at shutdown | Assets sold too broadly or too cheaply | Records lost before anyone assesses them |
Which assets are IP and which are operational records?#
Most closing companies hold a clear IP group, a clear records group and a gray zone in between. The IP group is what an asset buyer or a liquidation marketplace would list: patents and pending applications, registered trademarks, the domain name, the product codebase and documented trade secrets such as pricing models. The records group is the history of how the company worked.
The gray zone causes most disputes. Source code is IP, yet its commit history and code review threads are also records of engineering work. Internal playbooks can be trade secrets and operational knowledge at once. Customer lists are often sold as an asset but carry privacy and contract limits that a plain IP schedule ignores.
| Asset | Usually handled as | Watch for |
|---|---|---|
| Patents, trademarks, domain | IP sale | Recorded assignments and upcoming renewals |
| Product source code | IP sale | Open-source licenses and customer-owned code |
| Commit history, pull requests, code reviews | Either, decided explicitly | Whether the IP buyer needs them to maintain the code |
| Support tickets and escalations | Records license | Customer confidential details inside tickets |
| CRM activity and deal notes | Records license | Pricing and contact data tied to individuals |
| Internal wiki and playbooks | Either, decided explicitly | Trade secret status and client material |
| Customer list | Asset sale | Privacy policy promises and contract limits |
Why the order of the two deals matters#
The order matters because whichever deal closes first can limit the other. Asset purchase agreements commonly define purchased assets broadly, with phrases such as all books and records, all data and all intellectual property, and a buyer who acquires the codebase under that definition may also acquire the Zendesk archive and the Jira project history.
The reverse also happens. An exclusive data license signed before the IP sale can encumber the assets an IP buyer expects to receive clean, and a buyer who discovers it late may lower the offer or walk away. A non-exclusive license is easier to disclose and schedule, but the buyer still needs to know about it.
A workable rule: settle the definition of purchased assets first, then either exclude named record sets from the sale or have the agreement reserve the seller's right to license de-identified copies. The drafting points below are where that rule is won or lost.
- Purchased assets: list the IP by registration, repository and domain rather than relying on catch-all phrases such as all books and records.
- Excluded assets: name each retained record set by system and date range, for example help desk tickets from launch to closing and the internal chat workspace, never a vague category such as historical data.
- Reserved right: where a record set must go to the buyer, ask for a retained copy and a stated right to license de-identified versions, with any consent conditions written out.
- Seller confidentiality covenant: check whether it covers all business information or only the purchased assets, since a broad covenant can block a later license.
- Disclosure schedule: list any existing or planned data license so the seller's representations stay accurate.
- Transition copies: agree which records the buyer receives only as copies, such as open bugs or active customer tickets, as opposed to owning them outright.
Can records be licensed if they reveal the IP you sold?#
Records that reveal sold IP may need the IP buyer's consent before they are licensed, depending on what the purchase agreement transferred and what confidentiality promises the seller gave. Code review threads quote source code, engineering tickets describe architecture, and support escalations can expose roadmap decisions. Once the code and its trade secrets belong to someone else, licensing those records could disclose the buyer's property.
There are three common ways to handle the overlap. Exclude repositories and engineering records tied to the sold product; negotiate a consent in the purchase agreement that lets the seller license prepared engineering records under confidentiality terms; or license only records that do not expose protected design, such as support conversations about configuration and billing. Counsel should confirm which approach fits the agreement as signed.
Running both deals: a sequencing checklist#
Running an IP sale and a records license in parallel works when one person owns a single inventory and both deal teams work from it. That person is often the founder, a wind-down officer or the assignee in an assignment for the benefit of creditors.
- Build one inventory that lists every system, registration, repository and archive with its owner and date range.
- Split the inventory into an IP schedule and a records schedule, and flag gray-zone items for an explicit decision.
- Pull customer contracts, privacy policy versions and NDAs before either schedule is shared with a buyer.
- Decide exclusivity early: a non-exclusive records license keeps later options open and is easier to disclose.
- Agree the purchased-asset definition, excluded assets and any reserved license right before the purchase agreement is signed.
- Keep admin access and verified exports for retained records until the license review is finished.
- Document who signs for the seller at each stage, especially if the company will be dissolved.
Illustrative: a closing scheduling software company splits its assets#
Illustrative: a fictional software company that sold scheduling tools to commercial cleaning contractors decides to wind down after a funding round falls through. It employed more than 50 people at its peak. Its assets include a registered trademark, the domain, a product codebase in GitHub, several years of Zendesk tickets, Jira projects and a HubSpot CRM.
A competitor offers to buy the trademark, domain and codebase. The founder's counsel narrows the draft agreement so purchased assets cover the code, its repositories and the customer-facing help center, while historical Zendesk tickets, internal Slack channels and the Jira backlog for retired features stay with the company. The buyer asks for a copy of open bugs, which the company provides.
With the IP sale closed, the company reviews what it kept. Tickets that quote code from the sold product are excluded, customer names and contact details are removed from the rest, and a non-exclusive license for the support-to-resolution history is assessed. The buyer is told about the planned license in writing, so no one is surprised later.
How SourceX approaches a shutdown with an IP sale underway#
SourceX's role in a shutdown with an IP sale underway is the records license, not the sale of patents, trademarks or product ownership. The Rights step of the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery) starts with the asset purchase agreement, so any record set the buyer acquired, or that reveals sold IP, is identified before preparation begins.
For records that proceed, the SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization, including who signed for the seller after the sale. Nothing is shared during the initial fit check, which collects metadata such as system names and date ranges.
Frequently asked questions
Does selling the trademark and domain affect our right to license records?
Usually not directly. A trademark or domain sale transfers the brand, not the history of support tickets or project records. The risk comes from broad drafting: if the agreement also transfers all books, records and data, the archive goes with it. Read the definition of purchased assets before signing, and list any retained record sets by name.
Can the IP buyer stop us from licensing records later?
The buyer can if the agreement gives it the records, an exclusive right to them, or a confidentiality claim over what they reveal. A non-compete or non-disclosure covenant in the purchase agreement can also restrict the seller. Disclose any planned license during negotiation and get permission in writing rather than relying on silence.
Is licensing operational records the same as selling customer data?
No. A records license grants use of prepared copies of how the company worked, with personal and confidential details removed, while ownership stays with the company. Selling a customer list transfers the list itself. Both can still be limited by privacy policy promises and customer contracts, so each needs its own review.
Who signs a records license after the company is dissolved?
Whoever holds authority over the retained assets. That may be the board or a designated wind-down officer before dissolution is final, an assignee in an assignment for the benefit of creditors, or a trustee in bankruptcy. State law on dissolved entities varies, so counsel should confirm authority before any agreement is signed.
Should trade secrets ever be included in a records license?
Generally no. Licensing records that disclose a trade secret can weaken its protection unless strict confidentiality terms apply, and if the trade secret was sold, it now belongs to the buyer. Most records packages exclude pricing models, formulas and similar material by default and focus on workflows, decisions and outcomes.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.