Company records as a creditor recovery asset: what trustees should know

Why can company records add to creditor recovery?#

Company records can add to creditor recovery because AI developers license operational histories that show how real work was done. Support conversations, CRM histories, engineering issues and code reviews, job and dispatch records, and quality logs from an operating business are hard to find in public sources, and a closed company may hold years of them.

These records rarely appear as a separate line on a schedule of assets. They sit inside software subscriptions, email accounts and file shares, which are often the first costs a distressed company cuts. A trustee who treats them as an asset early keeps the option open; one who treats them as an IT cleanup task usually loses it.

Not every estate holds records worth licensing. The question is answered case by case, and it should be asked before access is gone.

Step one: preserve before access disappears#

Preservation means keeping admin access, exports and the subscriptions that hold records alive long enough to assess them. Many SaaS vendors restrict or delete customer data after an account is cancelled or goes unpaid, on schedules set in their own terms, so check each vendor's documentation and contract before any cancellation is approved.

Preservation also serves other duties. Records may be needed for claims analysis, litigation or tax filings, so the work is rarely wasted even if no license follows.

• 1Identify every system of record: help desk, CRM, ERP, code hosting, project management, email, chat and file storage.
• 2Recover admin credentials from departing staff and move them under the estate's control.
• 3Pause automatic cancellations and deletion jobs where the cost is justified.
• 4Take full exports of systems that will be shut down and store them encrypted under estate control.
• 5Document what was preserved, when and by whom, for later chain-of-custody questions.

Step two: inventory what the estate holds#

An inventory describes record families, systems, accessible history and approximate volume without moving any files. It answers the questions a buyer asks first: what kind of work the records show, whether they link requests to decisions and outcomes, and how far back they can still be exported.

Note what is missing as well. A past migration that dropped older history, or a system that was never paid for beyond a free tier, changes what the estate can offer.

Step three: review the rights before marketing anything#

A rights review asks whether the estate may license each record family, and on what conditions. Possession of the files is not enough. Customer contracts may contain confidentiality and data-use clauses, privacy notices may limit how personal information is used or transferred, and vendor terms may restrict exports or reuse.

Personal information needs particular care. Under 11 U.S.C. §363(b)(1), if the debtor told individuals it would not transfer their personally identifiable information to unaffiliated parties, and that policy was in effect when the case began, the trustee may sell or lease that information only consistently with the policy, or after a consumer privacy ombudsman is appointed under §332 and the court approves the transaction after notice and a hearing. In the RadioShack case, state attorneys general objected to the sale of customer data, and the Delaware bankruptcy court approved a sale in May 2015 only after a settlement narrowed the categories and age of customer data transferred. State privacy laws may also apply, and which rules apply is assessed deal by deal with counsel.

Exclusions are normal. Employee files, customer-owned deliverables, health or financial details and material under strict confidentiality clauses are often carved out, leaving the operating records that describe how the work was done. Reporting on the 2026 Spirit Airlines data sale, for example, says it excluded passenger profiles, loyalty records and privileged legal materials, with a third party stripping personally identifiable information before the buyer received anything.

Step four: approval and the shape of the deal#

Approval for a records transaction depends on the proceeding. A license or sale outside the ordinary course in bankruptcy generally needs court approval after notice to creditors; a receiver acts within the receivership order; an assignee for the benefit of creditors acts under state law and the assignment agreement. This is general information, not legal advice, and counsel confirms the path in each case.

Deal shape matters as much as approval. A non-exclusive license lets the estate license the same records to more than one buyer, but payments spread over time can conflict with closing the case. A paid-up license at signing often fits an estate better, and the license should state who handles obligations such as deletion requests once the company no longer exists.

Mistakes that cost estates their records#

The mistakes that cost estates their records are mostly about timing and authority. They tend to happen early in a case, when cost control and records value pull in opposite directions and nobody has yet been asked who owns the question.

• 1Cancelling every subscription in one sweep to stop costs, before exports are taken.
• 2Leaving admin access with a former employee, or letting someone take an export home.
• 3Marketing records before the rights review, then shrinking the scope in front of buyers.
• 4Signing a license whose payments outlast the case without a plan for collecting them.
• 5Defaulting to an exclusive license when non-exclusive terms could serve several buyers.

Illustrative: a receiver preserves a software company's history#

Illustrative: a fictional receiver is appointed over a vertical software company that served property managers. The company's Zendesk, Jira and GitHub accounts are on card billing, and the card is about to be cancelled along with the rest of the operating accounts.

The receiver keeps those three subscriptions running, takes full exports and moves admin access to the receivership. A metadata inventory shows years of support tickets linked to engineering issues and code changes. Counsel reviews the customer terms, which allow use of support data in de-identified form but restrict customer-uploaded documents.

The receiver seeks court approval for a non-exclusive, paid-up license of the de-identified tickets, issues and code reviews, with customer documents excluded. The remaining subscriptions are then closed on schedule.

How SourceX works with trustees and receivers#

SourceX works with trustees, receivers and wind-down officers through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The first step is a metadata-only fit check, so nothing leaves the estate's control while the opportunity is being assessed.

For each package that proceeds, the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization, giving the court, creditors and the buyer one documented account of what was approved. Large archives stay in the estate's storage or ship on encrypted drives.