Wind-downs and transitions
What records are worth assessing before you delete them at shutdown?
By SourceX Editorial · Updated
Short answer
The business records most worth assessing before deletion at shutdown are the ones that show work being done and resolved: support tickets with outcomes, code reviews and issue histories, job and project records, decision threads, and quality or exception logs. Personal files, client-owned material and isolated documents rank lowest. Assess first, because deletion cannot be reversed.
Key takeaways
- Records that connect a request to a decision and an outcome rank highest for AI developers.
- Years of consistent history in one system outrank a larger archive scattered across tools and migrations.
- Payroll, HR, medical, payment and client-owned records are set aside from licensing, though many must still be kept.
- A metadata inventory is enough to rank records; nothing needs to be exported to decide what to assess.
The ranked checklist#
The ranked checklist orders common record types by how often they hold licensing value, with the reason and the caution that usually applies. Priority is a starting point, and a company's own systems and contracts can move any row up or down.
Notice what the top rows share. Each one records a person facing a real problem, making a judgment and producing a result that the system captured.
| Priority | Record type | Typical systems | Why it may have value | Main caution |
|---|---|---|---|---|
| Highest | Support tickets with resolutions | Zendesk, Intercom, Freshdesk, Salesforce Service Cloud | Real problems, steps taken and outcomes | Customer personal details in free text |
| Highest | Code reviews, issues and fixes | GitHub, GitLab, Jira, Linear | Expert reasoning linked to changes and results | Customer code and secrets in repositories |
| Highest | Job, project and dispatch records | ServiceTitan, Procore, Deltek, ERP job modules | Complete workflows from request to completion | Residential customer data and client deliverables |
| High | Quality and exception logs | QMS, ERP, WMS, TMS | Problems, root causes and corrective actions | Customer-owned designs and specifications |
| High | Internal decision threads | Slack, Teams, email | How people reasoned through real decisions | Employee messages, NDA-bound material and privilege |
| Medium | Process docs and playbooks | Confluence, Notion, SharePoint | Codified expertise and procedures | Less useful when not linked to outcomes |
| Medium | CRM activity histories | Salesforce, HubSpot | Sales and account decisions over time | Contact details and customer confidentiality |
| Low | Isolated files and exports | Shared drives and desktops | Rarely useful without context | Unknown provenance |
What makes a record worth assessing#
A record is worth assessing when it shows a piece of real work from start to finish. AI developers building agents and assistants look for the reasoning between a request and its result, which is why a resolved ticket linked to an engineering fix outranks a polished policy document that nobody followed.
The checks below take minutes per system for someone who used it daily. Write the answers down; they become the first page of any later inventory.
- Linkage: the record connects a request to a decision and an outcome.
- Depth: several years of history in one consistent system, not split by a migration.
- Expertise: the work required judgment, not just data entry.
- Language: records are predominantly in English, unless a buyer has asked for others.
- Control: the company, not a client, controls the content.
Records to set aside#
Records to set aside are those whose content is mostly personal, regulated or owned by someone else. Setting them aside early keeps the assessment focused and keeps sensitive material out of every later step.
Setting a record aside does not mean deleting it. Many of these records must be kept for legal reasons; they simply do not belong in a licensing assessment.
- Payroll, benefits, HR and performance files.
- Health information and anything covered by medical privacy rules.
- Payment card data, bank details and customer financial records.
- Client deliverables, client-owned designs and customer code.
- Communications with lawyers that may be privileged.
- Board minutes, equity records and tax files, which belong in the retention schedule.
Assess, keep or delete: decision rules#
The decision rules come down to two questions for each record family: does a law or contract already say what must happen, and if not, could the records be licensed? Answer the first question before the second, because an obligation always outranks an opportunity.
| Situation | Decision |
|---|---|
| A law requires retention | Keep with a custodian; exclude from licensing |
| A contract requires return or deletion | Return or delete; exclude from licensing |
| Company-controlled, linked and several years deep | Preserve and assess |
| Company-controlled but isolated or thin | Delete under the schedule unless needed for another reason |
| Rights are unclear | Preserve until counsel reviews |
How to rank records without exporting them#
Ranking records takes a metadata inventory, not an export. For each system, list the record families, the years still accessible, approximate volumes, whether records link to each other, and any known restrictions.
Most of the answers come from the people who ran the systems. The support lead knows how far back tickets go, the engineering lead knows whether pull requests reference issues, and the controller knows what the accountant needs kept. Capture the answers before those people leave, because the inventory is the one part of the assessment that depends on them.
Keep the inventory free of record contents. Field names, date ranges and counts are enough to rank a system, and an inventory without personal data is far easier to share with advisors and potential licensing partners, though counsel should still confirm that system names and counts reveal nothing confidential.
Illustrative: a contract manufacturer ranks its archive#
Illustrative: a fictional precision contract manufacturer is closing after losing its largest customer. Its systems include an ERP with quotes, orders and routings, a QMS with nonconformance reports and corrective actions, a CMMS with maintenance work orders, and an engineering mailbox full of customer correspondence.
The owner's first instinct is to delete everything except tax records. A metadata inventory changes the plan. Nonconformance reports linked to root causes and corrective actions rank highest, and maintenance work orders with failure codes rank high. Customer drawings, specifications and the engineering mailbox are set aside because customers own or restrict them, and ERP quotes are set aside because they reveal customer pricing.
The quality and maintenance records are preserved for a licensing assessment, and everything else follows the retention schedule. The decision took one inventory meeting, not a data project.
How SourceX assesses shutdown records#
SourceX ranks records with the SourceX Enterprise Data Value Framework, a SourceX-developed methodology that weighs uniqueness, domain expertise, human-generated signal, scale, recency, data cleanliness, rights and AI utility, and counts preparation cost and privacy burden against net value. The assessment starts with metadata only, so a closing company can decide what to preserve before anything is shared.
Records that proceed move through the SourceX five-step transaction, from Supply and Rights through Preparation, Approval and Delivery, with the company approving each step and a SourceX Evidence Packet recording what was licensed and why.
Frequently asked questions
Are older records still worth assessing?
Often, yes. Older records can still show how real work was done, and long history adds depth. Records tied to retired products or obsolete tools may be less useful, so note what each period covers and let the assessment decide rather than deleting by age alone.
Does an archive need to be large to matter?
Volume helps, but consistency and linkage matter more. A modest archive of resolved tickets linked to fixes can be more useful than a much larger set of disconnected emails. Note approximate volumes in the inventory and let buyer requirements decide whether they are enough.
Should we keep backups of everything just in case?
Not indefinitely. Keeping everything raises storage cost and privacy exposure, and it may conflict with deletion obligations in customer contracts. Preserve record families that are legally required or that rank well in the assessment, and delete the rest under the retention schedule once decisions are made.
What about records from a business line we already sold?
Check the sale agreement first. Records tied to a sold business line may have transferred to the buyer, or the agreement may restrict how the seller uses them. Exclude them from the assessment until counsel confirms the company still controls them.
Who should run the assessment inside the company?
One person who knows the systems, usually the COO, CTO or an operations lead, working from the inventory, with counsel reviewing anything marked unclear. Founders often try to do it alone during the shutdown and run out of time, so assign it early and give it a deadline.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.