Selling data before closing a company: a checklist.

The closing date sets the clock. It does not set the rights.

A company that decides to close has a limited window. Servers get shut off. Contracts lapse. Staff leave. The people who know where the data came from are often the first to go.

That pressure is real. It does not change what the company can license. Rights, authority, and deletion duties still decide what may be offered to a buyer.

If you want to sell company data before closing, the work is mostly sequencing. Decide who can authorize. Preserve evidence and systems. Separate what may be offered from what may not. Then approach buyers with a documented package.

Who can authorize a sale.

Start with authority. A buyer will ask who signed and on what basis.

In a solvent wind-down, the board usually remains in control. Check the articles, shareholder agreements, and any lender consents. A resolution should name the assets, the purpose, and the person who may sign.

In a formal insolvency process, authority may move. A liquidator, administrator, or similar office-holder may control the assets. Their duties run to creditors. They may need court or creditor approval for some transactions.

Confirm these points before outreach:

• Which entity owns the data, and is it the entity that is closing?
• Does the board still have power to sell, or has an office-holder taken control?
• Do lenders hold security over the data or the systems that hold it?
• Are any consents needed from shareholders, creditors, or a court?
• Who will sign, and where is the signed authority recorded?

Counsel should answer these. We do not.

Preserve systems before they are switched off.

Data is easiest to assess while the systems still run. Once hosting ends, a simple question can become a recovery project.

Before shutdown, list what must stay alive long enough for review and export:

• Production databases and their backups.
• File storage, archives, and legacy systems.
• Source control, schemas, and data dictionaries.
• Logs that show how records were collected.
• Hosting, cloud, and software accounts, with renewal dates.
• Administrator credentials and the people who hold them.

Ask the cloud and software vendors what happens at termination. Some delete data on a fixed schedule. Extending one account for a short period may cost less than losing the only copy of an archive.

Do not create new copies casually. Every copy is a deletion and security obligation. Make exports deliberately, record where they sit, and limit who can reach them.

Keep the people who hold the context.

Documentation rarely explains a data set fully. Engineers, analysts, support leads, and finance staff carry the rest.

Identify the few people who can explain:

• How the data was collected and under what terms.
• What each field means and which fields are unreliable.
• Which records came from customers, users, vendors, or third parties.
• What was changed, merged, or removed over time.

Ask counsel how to keep them available. A short consulting or retention arrangement, with confidentiality terms, is common. Before they leave, ask them to write down what they know. A two-page note is better than a memory.

Deletion duties come before any transfer.

A closing company often carries deletion obligations. Some come from privacy law. Some come from customer contracts. Others come from vendor terms or regulator guidance.

Some duties pull the other way. Tax, employment, and litigation rules may require retention of certain records.

Build a deletion and retention register. For each category, record:

• The source of the duty and its deadline.
• Whether the data must be deleted, retained, or returned.
• Who is responsible for carrying it out.
• How completion will be proved.

Do not delete anything until counsel confirms the register. Deleting too early can destroy evidence of rights. Deleting too late can breach a duty. A buyer will also want the register, because it shows which material is clean.

Customer data needs its own decision.

Customer data is the hardest category in a closing. It often contains personal information. It is usually covered by confidentiality terms and purpose limits.

Treat it as excluded until counsel says otherwise. Questions to put to counsel:

• Did the customer agreement permit disclosure or reuse of this data?
• Does the data include personal information, and what notice was given?
• Does the closing itself trigger notice or return duties?
• Can the data be aggregated or de-identified in a way that is documented and defensible?

Many companies will find that their strongest assets are not customer records. They are original content, internal documentation, or archives with clear ownership. Our pages on company shutdown data and acquired archives describe how we assess those categories.

The checklist, with timing.

Timing depends on the closing date and on how quickly inputs arrive. These stages show the order, not a promise of speed.

As soon as closure is under consideration

1. Confirm who holds authority to sell, and record it.
2. Name one internal owner for the data project.
3. Ask counsel to review lender security and customer contracts.
4. Stop scheduled deletions that are not legally required.

Before systems are shut down

5. List all systems, backups, and accounts, with end dates.
6. Extend or preserve the minimum needed for review.
7. Identify the people with context and agree how to keep them available.
8. Draft the deletion and retention register.

During rights review

9. Build an inventory by source, date range, format, and rights status.
10. Exclude customer and personal data unless counsel clears it.
11. Document provenance for each proposed subset.
12. Prepare a data dictionary and a limited sample approved for disclosure.

Before buyer contact

13. Approve the materials, recipients, and access conditions in writing.
14. Confirm that the signer’s authority covers the proposed license.
15. Agree how proceeds, retained rights, and deletion will be handled.

After a license is signed

16. Deliver only the approved scope.
17. Complete deletions on the register and keep proof.
18. Archive the agreement, the register, and the sample manifest.

If a step cannot be completed, the package should shrink. It should not be described more broadly than the evidence allows.

What can slip, and what to do about it.

Three problems appear often in a wind-down.

First, authority changes. An office-holder is appointed and the board can no longer sign. Pause outreach. Reconfirm who has control and restart from there.

Second, systems disappear early. A vendor terminates for non-payment. Raise it with the vendor immediately. Ask for an export or a short extension before the account is closed.

Third, staff leave before the context is written down. Hold short interviews now. Record the answers and attach them to the source register.

A buyer will test all of this. A package that states its limits clearly is easier to evaluate than one that implies completeness.

How we help.

We represent the seller. We do not represent buyers, and we do not act as your counsel.

In a closing, we help you:

• Turn the checklist above into dated tasks.
• Assemble the inventory, provenance summary, and sample manifest.
• Decide which categories are worth presenting to buyers and which should stay out.
• Run buyer outreach only after you approve the materials and recipients.
• Compare proposed terms for scope, exclusivity, and retained rights.

The working process shows each stage in order. More background is in our insights. Your counsel reviews every agreement. The authorized owner decides whether to proceed.

If your company is closing and holds data you believe has value, start with a confidential seller brief. Share the systems, approximate volumes, closing date, and who holds authority. We will tell you what looks feasible and what does not.