Wind-downs and transitions
Chief restructuring officer checklist for overlooked intangible assets
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A chief restructuring officer should treat operating records, domains and admin accounts, contract rights, prepaid balances and claims as intangible assets to find and protect before any system is shut off. The working rule is preserve first, value second: one cancelled subscription can erase years of support tickets, job histories or order exceptions a licensee might have wanted.
Key takeaways
- Operating records in SaaS systems are the intangible most often lost, because cost-cutting cancels subscriptions before anyone exports the history.
- Domains, phone numbers and admin accounts control access to every other asset and should be secured early.
- Contract rights, prepaid balances, tax attributes, insurance policies and claims belong on the intangible list even when they are missing from the balance sheet.
- Each record family needs a rights screen for client ownership, vendor terms and personal data before it is offered to anyone.
- Qualitative value drivers, not book value, decide which records deserve preparation effort.
Which intangible assets do CROs most often overlook?#
Chief restructuring officers most often overlook the intangibles that live in software rather than on the balance sheet: operating records in SaaS systems, the domains and admin accounts that control access, and rights buried in vendor and customer agreements. Trademarks and patents usually make the first inventory; years of Zendesk tickets, dispatch records or warehouse exceptions usually do not.
These assets slip through because cost-cutting moves faster than the asset review. Finance cancels subscriptions to preserve cash, IT decommissions servers, and departing staff take the knowledge of where things live. Once a vendor purges a cancelled account, the history is gone whatever it was worth.
The overlooked intangibles checklist#
The overlooked intangibles checklist below is organized by where each asset sits, so every line can be assigned to the person who controls it. Work through it before approving cancellations, not after.
| Asset | Where to find it | First action |
|---|---|---|
| Support and service histories | Zendesk, Intercom, Freshdesk, field service systems | Confirm retention settings and export routes before cancellation |
| CRM and sales records | Salesforce, HubSpot, spreadsheets on shared drives | Freeze deletion and record the admin owner |
| Order, job and exception records | ERP, WMS, TMS and dispatch software | Identify archive tables and how far back history reaches |
| Engineering and product history | Jira, GitHub or GitLab, Confluence | Secure owner accounts and export repositories and issues |
| Domains, email and phone numbers | Registrar, Google Workspace or Microsoft 365, carrier accounts | Turn on auto-renew and move recovery to a monitored address |
| Software, cloud and app store accounts | Vendor portals, cloud consoles, developer accounts | Confirm who holds admin access and whether the account can be assigned |
| Trademarks and trade names | Registrations, website, packaging | Confirm the owning entity and renewal status |
| Customer and vendor contracts | Contract folders, procurement system | Flag assignment, change-of-control and confidentiality terms |
| Prepaid subscriptions, credits and deposits | Accounts payable records, vendor portals | Request refunds or apply credits before termination |
| Tax attributes and refunds | Tax returns, provision workpapers, open amended returns | Ask tax advisors before any ownership or asset change that could limit their use |
| Insurance policies and pending claims | Broker files, policy binders | Confirm tail coverage and notice requirements |
| Litigation and recovery claims | Counsel files, demand letters | Preserve evidence and calendar deadlines |
| Permits, licenses and certifications | Compliance files, state and local portals | Check which ones transfer to a buyer and which lapse at closing |
Preserve before you cut: sequencing system shutdowns#
Sequencing system shutdowns so that exports come before cancellations is one of the most valuable steps a CRO can take for intangible recovery. Each cancellation should pass a short gate: does this system hold records needed for legal holds, tax, claims or a possible sale or license?
The gate is cheap to run and expensive to skip. A system that fails it stays live, even at a reduced plan, until the export is done and verified.
- Pause auto-deletion and retention purges in every system that holds operating history.
- List every admin account, its owner and its recovery email or phone.
- Keep system admins and power users on through the export, because they know where history and attachments actually live.
- Export full history in native formats, including attachments, comments and linked records.
- Log what each export contains: system, date range, record counts reported by the tool and known gaps.
- Store exports in company-controlled, encrypted storage with access logging.
- Apply the retention and deletion schedule only after legal holds and asset decisions are settled.
Rights screens before any record is offered#
Rights screens decide whether a record family is an asset the company can transfer or license, or a liability it must protect. Owning the server does not mean owning every record on it.
Client deliverables, customer-uploaded files and customer code are often controlled by the client's contract. Vendor terms can limit how exported data is used. Employee and customer personal information brings privacy obligations that follow the records, and a privacy policy promise may restrict transfers. Note each restriction against the record family rather than writing off whole systems.
| Record family | Often licensable after preparation | Usually carved out |
|---|---|---|
| Support tickets | Internal troubleshooting notes and resolution steps | Customer attachments and personal details |
| CRM activity | Deal stages and internal notes on objections | Contact data and customer-confidential terms |
| Engineering records | Internal issues, code reviews and release notes | Customer-owned code and third-party licensed code |
| Operations records | Exceptions, root causes and corrective actions | Customer drawings and controlled technical data |
Contract rights and claims hiding in the files#
Contract rights and claims are intangibles that rarely appear on an asset register because they sit in agreements and correspondence rather than in the general ledger. Customer agreements may carry unbilled milestones, early termination fees or minimum purchase commitments. Vendor agreements may carry service credits, unused prepayments and refundable deposits that expire if nobody asks for them before termination.
Claims are easier to lose than to find. Warranty claims against equipment suppliers, insurance claims for prior incidents, overpaid taxes and potential actions against former insiders or counterparties all need a named owner and a deadline. Ask counsel and the controller for a joint list early, because some notice periods are short and the people who know the facts may be leaving.
Tax attributes such as net operating losses can matter to a plan or a buyer, and changes in ownership can limit their later use. Flag them to tax advisors before any equity or asset transaction is agreed, not after.
Data licensing rights belong on the same list. If the company has ever licensed records, the agreement may carry future payments, audit rights or restrictions that affect what the estate can do next.
How to rank intangibles without a price list#
Ranking intangibles in a restructuring works better with qualitative drivers than with a number, because operating records rarely have a market price until a buyer engages. The SourceX Enterprise Data Value Framework is one SourceX-developed method: it rates uniqueness, domain expertise, human-generated signal, scale, recency, data cleanliness, rights and AI utility as value drivers, treats exclusivity as raising price and reproducibility as reducing value, and counts preparation cost and privacy burden against net value.
For a CRO, the useful output is a short list: which record families to preserve at full fidelity, which to archive cheaply and which to delete on schedule. That list also helps the company's advisors explain why an apparently minor asset deserves a marketing process.
Illustrative: a 3PL restructuring finds its exception archive#
Illustrative: a fictional third-party logistics company with several warehouses enters an out-of-court restructuring. The CRO's first asset list covers leases, forklifts, receivables and a trademark. Finance has scheduled cancellation of the legacy WMS and the customer portal to cut costs.
The CRO pauses both cancellations and asks the operations lead what the systems hold. The WMS contains years of receiving discrepancies, mis-picks and their resolutions; EDI logs tie them to customer orders; Samsara telematics show routing exceptions. Exports are taken, customer pricing and contact data are flagged for exclusion, and the archive is added to the asset register as a candidate for a non-exclusive license. Lender counsel is told, because the loan documents cover general intangibles.
Where SourceX fits in a CRO's asset review#
SourceX fits a CRO's asset review after records are preserved and before any archive is marketed. The fit check uses metadata only, such as system names, years of history and record families, so a CRO can learn whether an archive is a licensing candidate without moving files.
If the records proceed, the SourceX five-step transaction runs Supply, Rights, Preparation, Approval and Delivery, with the company or its fiduciary approving each step and lender or court consents handled in the Approval step. Large archives stay in the company's own storage or ship on encrypted drives; SourceX does not host multi-terabyte datasets.
Frequently asked questions
Should the CRO or IT own the records inventory?
The CRO should own the decision and IT or operations should own the work. IT knows where records live and how to export them; the CRO decides which systems can be cancelled and which must be preserved for legal, tax or asset reasons.
Do lenders have a claim on operating records?
They may. Many security agreements cover general intangibles and proceeds, which can reach records and any license fee. Review the loan documents with counsel before marketing records, and keep the lender informed to avoid a dispute later.
What if a vendor has already purged a cancelled account?
Ask the vendor in writing whether any backup or archive remains and on what terms it can be retrieved. Then check other sources: local exports, email notifications, scheduled reports, data warehouse copies and integrations that synced records into other systems.
Are operating records worth anything in a liquidation?
They can be, but value depends on the record type, rights, condition and buyer demand at the time. Some archives attract interest and others do not. The cost of preserving them is often modest next to the cost of losing the option.
Does the checklist change in a formal bankruptcy?
The asset list is similar, but transfers outside the ordinary course need court approval, and assets must be disclosed in the schedules. Personal information may require extra privacy review before any sale or license.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.