Wind-downs and transitions
Insolvency professionals' guide to AI-era data assets
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Insolvency data assets in the AI era are operational records, such as support conversations, engineering histories, CRM activity and job records, that AI developers license to train and test models. For trustees, receivers and assignees, the first rule is preservation: keep admin access and key subscriptions alive until records are inventoried and rights are reviewed.
Key takeaways
- AI developers value records that show real work from request to outcome, which differs from the customer lists that dominated older data sales.
- Value is lost fastest in the first weeks, through lapsed subscriptions, disabled admin accounts and automatic deletion rules.
- A metadata-only fit check can tell a fiduciary whether an estate's records merit further work before any file moves.
- Privacy promises, customer contracts and employee expectations still apply, and court or creditor approval may be required.
- A non-exclusive license may produce proceeds while leaving the estate free to license or sell the same records later.
What counts as an AI-era data asset in an estate?#
An AI-era data asset is a company's record of how work was actually done: the support conversation and the fix that followed, the engineering issue and its code review, the dispatch note and the completed job, the nonconformance report and its corrective action. AI developers license such records, after personal and confidential details are removed, to train and evaluate models on realistic business tasks.
Older insolvency practice treated data mainly as customer lists, mailing lists and subscriber files sold for marketing reach. Those still exist and still carry heavy privacy limits. The newer category differs in who wants it, what makes it valuable and how it is usually transacted.
| Feature | Traditional data asset | AI-era data asset |
|---|---|---|
| Typical content | Customer lists, contact files, subscriber data | Tickets, issues, code reviews, CRM activity, job and quality records |
| Who wants it | Competitors and marketers | AI developers and model builders |
| What drives value | Reach to the people in the list | Context, linkage from request to outcome, domain expertise |
| Main legal question | Can personal data move to a new owner? | Can prepared copies be used without breaching privacy or contract promises? |
| Usual structure | Outright sale, with the business or alone | License of prepared copies, often non-exclusive |
Why should fiduciaries look at records differently now?#
Fiduciaries should look at records differently because an archive that once looked like a storage cost may now support a license. A debtor's years of help desk history, Jira projects or field service records can matter to AI developers if the records are detailed, connected and cleared for use, and the duty to maximize recoveries makes that worth checking before systems are shut down.
The check should be quick and realistic. Typical fit is a company with 50 or more full-time employees at its peak, several years of operating history and records in connected systems. Small estates, archives that are mostly personal data and records that belong to clients rarely justify the work, and an early fit check says so before money is spent.
A workflow from appointment to license#
The workflow from appointment to license runs in the same order for trustees, receivers and assignees, although the approvals differ by route. Preservation comes before valuation, and valuation comes before any marketing of the records.
- Access: identify systems from bank and card statements, obtain admin credentials and stop automatic cancellation of critical subscriptions.
- Preserve: pause deletion rules, export core systems and verify the exports.
- Inventory by metadata: system, record families, date ranges, approximate volumes and known restrictions.
- Fit check: test whether the record families match what AI developers license, without moving files.
- Rights triage: read privacy policy versions, customer contracts, NDAs and employee notices.
- Structure: choose between a sale and a license, and between exclusive and non-exclusive terms.
- Approval: obtain court, creditor or lender approval where the process requires it.
- Prepare and deliver: remove personal and confidential details, document provenance and hand over under the agreed terms.
Who signs and who approves in each route?#
Who signs a data license depends on the insolvency route: a trustee, a debtor in possession, a receiver or an assignee, each acting under a different source of authority. The approvals that follow differ too, so map them before a buyer is approached rather than after terms are agreed.
Whatever the route, read the secured lender's security agreement. A lien on general intangibles or on substantially all assets may reach the records and any license proceeds, so lender consent or a release is often part of the plan. The comparison below is general and varies by court, state and order.
| Route | Who signs | Approvals to plan for | Authority document to keep |
|---|---|---|---|
| Chapter 7 bankruptcy | The trustee | Notice and court approval for transactions outside the ordinary course; added privacy review where consumer data conflicts with the privacy policy | Trustee appointment and the approval order |
| Chapter 11 bankruptcy | The debtor in possession, or a trustee if one is appointed | Notice and court approval outside the ordinary course; input from any creditors' committee | The approval order |
| State receivership | The receiver | Whatever the appointment order requires, which often includes court approval of asset sales | The receivership order and any approval order |
| Assignment for the benefit of creditors | The assignee | Varies by state; some ABCs run with little or no court involvement | The assignment agreement and any court filing |
What destroys data value in the first weeks?#
Data value is usually destroyed by ordinary administrative events rather than by any decision. Unpaid subscriptions lapse, admin accounts belong to people who were let go, and deletion rules keep running. Each threat has an early warning sign a fiduciary can watch for.
| Threat | Early sign | Protective step |
|---|---|---|
| Subscription lapses for nonpayment | Failed payment notices in an admin inbox | Pay or negotiate a short extension for core systems |
| Admin account disabled | Only a terminated employee holds the owner role | Request a vendor-verified ownership transfer to the fiduciary |
| Automatic deletion rules | Retention settings purge old messages or tickets | Pause the rules and document the change |
| Vendor deletion after termination | Terms promise deletion once the account closes | Export before any notice of termination is given |
| Loss of context | No one left can explain the systems | Retain a former employee under a consulting agreement |
Rights and privacy questions to answer before any deal#
Rights and privacy questions decide what part of an estate's records can be licensed at all. Control of the servers or accounts does not settle whether third parties' information can be used, so a fiduciary needs answers to a short set of questions, assessed with counsel for the specific estate.
The answers usually split the archive. Consumer personal information collected under a restrictive privacy policy draws added scrutiny in bankruptcy and is often left out entirely. Business-to-business operational records, prepared so that individuals and customers cannot be identified, often raise narrower questions, but that conclusion is reached deal by deal and recorded in writing for the court or creditors.
- What did each version of the privacy policy promise, and to whom?
- Do customer contracts restrict use of their data or require deletion at termination?
- Which records contain other companies' confidential information under NDAs?
- What were employees told about monitoring and the use of workplace communications?
- Could laws such as the CCPA, other state privacy laws or the GDPR apply to any of the records?
- Does the sale or license need court approval, and will a privacy review be part of it?
Illustrative: a receiver and a contract manufacturer's quality records#
Illustrative: a fictional contract manufacturer of machined industrial components, with a peak headcount above 50 full-time staff, is placed in a state court receivership after a lender dispute. Its Epicor ERP, a hosted quality management system and a maintenance tool are paid on a company card that is about to be cancelled.
The receiver moves billing to the receivership account, takes over admin roles and engages the former quality manager as a consultant to explain the systems. A metadata inventory shows years of nonconformance reports linked to corrective actions, supplier exceptions and machine maintenance histories, alongside customer-owned drawings and specifications held under customer agreements.
The customer drawings and any part numbers tied to them are excluded, and a check confirms none of the work was export-controlled. The machines and the customer contracts are sold to a competitor whose purchase agreement covers equipment and open orders only. The receiver asks the court to approve a non-exclusive license of the de-identified quality and maintenance history, with the lender's consent attached.
How SourceX works with trustees, receivers and assignees#
SourceX treats the fiduciary as the supplier's authorized signer and runs the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Nothing is shared during the initial assessment, and the fiduciary approves each step before anything moves.
Each package is documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization, including the court order or assignment that gives the fiduciary authority, so the record can be shown to a court, creditors or a buyer. SourceX's dataset rights are set out in the signed supplier agreement, and it never hosts multi-terabyte datasets; large archives stay in the estate's storage or ship on encrypted drives.
Frequently asked questions
Is a license better than a sale for an estate's records?
Often, but not always. A non-exclusive license leaves the estate holding the records, so it can license them again or sell them later, while a sale ends the estate's involvement in one transaction. Tight estate timelines, buyer preferences and court requirements can favor either, so compare both with counsel before marketing the records.
Can former employees help after the company has closed?
Yes, and they are often essential. A former support lead, engineer or operations manager can explain which systems matter, where history was migrated and what fields mean. Engage them under a written agreement with confidentiality terms, and limit their access to what the task requires.
What if the records include consumer personal information?
Consumer personal information usually carries the heaviest limits. Privacy policy promises, state privacy laws and bankruptcy procedures may restrict any transfer, and regulators have objected to past sales of customer data. Most AI-era licenses exclude such data or rely on thorough de-identification reviewed with privacy counsel.
How is value estimated when there is no market price?
Value is known only once a buyer engages with a specific, prepared package. Before that, fiduciaries can rate records qualitatively on drivers such as uniqueness, domain expertise, human-generated signal, scale, recency, data cleanliness, rights and AI utility, then weigh preparation cost and privacy burden against them. The SourceX Enterprise Data Value Framework uses those drivers.
Is it worth paying to keep subscriptions running?
Usually for core systems and for a short, defined period. A few more months of a help desk, ERP or quality system can protect history that cannot be rebuilt, but it is still an estate expense. Record why it was incurred, tie the end date to the inventory and fit check, and cancel promptly if the records do not qualify.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.