# Records of a Dormant Subsidiary or Retired Product: Options

> A dormant subsidiary or retired product still holds records that can be licensed. Who owns them, which contracts still bind and what to do first.

Canonical: https://origindatapartners.com/guides/dormant-subsidiary-retired-product-data
By: Origin Data Partners
Status: Published
Published: 2026-11-15
Updated: 2026-11-15
Sources checked: 2026-11-15

## Quick answer

Yes, in most cases the records can still be licensed, by whichever entity owns them today. After a merger or a share purchase that is the surviving or acquired company. After an asset purchase it is whoever the purchase agreement names. The old customer contracts and privacy promises still apply. Decide before the system is switched off or the entity is dissolved, because either can put the records out of reach.

## Key points

- The form of the deal decides who owns the records: share purchase, merger or asset purchase.
- A dormant entity can sign a licence, but in the UK the income ends its dormant status.
- Customer contracts of a retired product outlive the product.
- Property left in a UK company when it is dissolved passes to the Crown. Move or license records first.

## Who owns the data of a company you acquired?

It depends on how the deal was done. In a share purchase the acquired company still owns its records and you own the company. In a merger the records pass to the surviving company by law. In an asset purchase you own only what the agreement lists.

Delaware's merger statute shows the second case. After a merger, "all property, rights, privileges, powers and franchises, and all and every other interest shall be thereafter as effectually the property of the surviving or resulting corporation as they were of the several and respective constituent corporations" ([Delaware General Corporation Law, section 259](https://delcode.delaware.gov/title8/c001/sc09/)). Records and the rights in them move with everything else. So do the obligations attached to them.

An asset purchase is different. Data, databases and "books and records" are often listed, but excluded assets and excluded contracts are listed too. Read the schedules before assuming a record set came across. The [guide to company data in an asset sale](https://origindatapartners.com/guides/asset-sale-company-data) covers the wording.

| How the business was acquired | Who owns the records now | What to check |
| --- | --- | --- |
| Share purchase: you bought the company | The acquired company, which is now your subsidiary | Its own contracts and privacy notices. Nothing changed for its customers |
| Merger into your company | The surviving company | The contracts that came with the records, and any that barred assignment or change of control |
| Asset purchase | Whoever the agreement names, asset by asset | The schedules of acquired and excluded assets, and the data clause |
| Carve-out of a division | Split between seller and buyer by the sale agreement | Who holds shared systems, and what the transition services agreement lets each side use |


## Can a dormant subsidiary license its old records?

Yes. A dormant company still exists and still owns its property, so it can sign a licence through its directors. The catch is that licence income is activity, and activity can end the dormant status the group relies on for simple filings.

In the UK, a company "is called dormant by Companies House if it's had no 'significant' transactions in the financial year" ([GOV.UK](https://www.gov.uk/dormant-company/dormant-for-companies-house)). A licence fee paid into the company is a significant transaction. The next accounts would be non-dormant accounts.

Groups usually pick one of two routes. Either the subsidiary signs and accepts a year of full accounts, or the records are first transferred to an active group company, which then signs. A transfer inside a group has tax and contract consequences of its own, so the finance and legal teams should choose the route together.


## What survives in a retired system, and what can a buyer use?

More than the database. A retired product or a decommissioned internal system leaves several layers behind, and the ones that explain the work are worth more than the raw tables.

| Layer | Usually survives switch-off? | Why a buyer cares |
| --- | --- | --- |
| Production database | Only if a final export or backup was kept | The record of what happened: orders, cases, jobs, tickets |
| Attachments and file store | Often lost first, because storage is billed separately | Drawings, photos, reports and documents that the rows point to |
| Audit and change history | Rarely exported unless someone asks | Shows who changed what and why, which is the reasoning a model lacks |
| Source code and configuration | Yes, in the repository | Explains the data model and the business rules |
| Support desk and bug tracker for the product | Yes, if the tools are still paid for | Problem, diagnosis and fix, linked |
| Runbooks, specifications and training material | Scattered across shared drives | How the work was meant to be done |
| Backups in a vendor format | Yes, but may need the old software to restore | Usable only if someone can still read them |

The data dictionary matters as much as the data. Once the last engineer who knows the schema leaves, column names such as STATUS_CD_2 are guesses.


## Do customer contracts of a retired product still restrict the data?

Yes. Ending a product does not end the promises made while it ran. Confidentiality clauses normally survive termination, and data processing terms usually require customer content to be returned or deleted when the service ends.

Privacy law also follows the records. In Europe personal data must be "collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes", and "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed" ([GDPR, Article 5](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng)). In California, to sell covers "making available" a consumer's personal information "to a third party for monetary or other valuable consideration" ([Cal. Civ. Code 1798.140](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=CIV&sectionNum=1798.140)).

What the company usually can license is its own operating record of the product: tickets, bug history, code, internal documents and de-identified operational data. The [guide to NDAs and customer contracts](https://origindatapartners.com/guides/nda-customer-contract-data-licensing) explains how to sort the two, and the [de-identification guide](https://origindatapartners.com/guides/de-identify-company-data-before-licensing) covers the personal data.


## Should you license the records before decommissioning the system?

Decide before, even if the licence comes later. The decision costs little while the system is running and a great deal once it is off. At the least, export and inventory the records before the switch-off date.

There is no standard timetable, and we have no sourced figure to give you. A licence does not have to be signed before decommissioning. What has to happen first is the part only a running system allows.

- Run a full export in an open format (CSV, JSON, Parquet or SQL dump), with attachments and audit history.
- Write down the schema: tables, keys, code values and what each status means.
- Count the records by type and by year.
- Record which customers and contracts each record set relates to.
- Keep the exports somewhere with an owner, a retention date and access control.

The [guide to exporting company records before closing](https://origindatapartners.com/guides/export-company-records-before-closing) lists export routes for common systems.


## Does licensing old records affect striking the entity off?

It can, in two ways. Trading shortly before an application can make the company ineligible for voluntary strike-off, and anything the company still owns at dissolution is lost to it. Deal with the records before the entity goes.

In the UK, a company can apply to be struck off only if it "has not traded or sold off any stock in the last 3 months" ([GOV.UK](https://www.gov.uk/strike-off-your-company-from-companies-register)). The same guidance says of business assets: "Anything that's left will go to the Crown" ([GOV.UK](https://www.gov.uk/strike-off-your-company-from-companies-register/close-down-your-company)). The statute behind it provides that when a company is dissolved, "all property and rights whatsoever vested in or held on trust for the company immediately before its dissolution" are "deemed to be bona vacantia" ([Companies Act 2006, section 1012](https://www.legislation.gov.uk/ukpga/2006/46/section/1012)). That includes databases, copyright and contract rights.

Delaware gives more time. A dissolved corporation is "continued, for the term of 3 years from such expiration or dissolution" for purposes that include enabling it "to dispose of and convey" its property ([Delaware General Corporation Law, section 278](https://delcode.delaware.gov/title8/c001/sc10/)).

This page is general information, not legal advice. The rules differ by country and state, so ask the adviser handling the closure. The guides to [closing a UK limited company](https://origindatapartners.com/guides/close-a-limited-company-uk) and [dissolving a US corporation](https://origindatapartners.com/guides/dissolve-a-corporation) set out the steps.


## What does it cost to keep the records versus license them?

Keeping is not free and licensing is not either. The useful comparison is line by line, with your own figures. A non-exclusive licence does not remove the records, so the two are not alternatives: most companies that license also keep.

| Cost of keeping a retired system | Cost of licensing its records |
| --- | --- |
| Hosting or archive storage, every year | One export and the staff time to check it |
| The legacy software licence needed to read the data | De-identification of personal and customer data |
| A person who still understands the system | Legal review of ownership and old contracts |
| Retention, legal hold and deletion duties | Security review of how the buyer stores the data |
| Exposure if the archive is breached | Management time on terms |


## Example: one-page inventory for a retired product

A fictional industrial software company retired a scheduling product it had acquired six years earlier. The legal entity that sold it is now a dormant subsidiary. The figures are invented to show the method.

| Record set | Volume | Owner today | Restrictions | Decision |
| --- | --- | --- | --- | --- |
| Support tickets and resolutions | 84,000 tickets, 2011 to 2023 | The subsidiary | Customer names and contact details | In, after de-identification |
| Bug tracker and release notes | 19,000 issues | The subsidiary | None found | In |
| Source code and build history | 1 repository, 12 years | The subsidiary. Two contractors signed assignments | Open-source licences to list | In, after a licence and secrets scan |
| Customer schedule data | 2.1 TB | The customers. Held under the service contract | Return or delete at termination | Out. Deleted on the contract terms |
| Implementation project files | 310 projects | The subsidiary, with customer confidential material mixed in | Confidentiality clauses survive | In for 190 projects after contract review |
| Backups in the old vendor format | 40 tapes | The subsidiary | Cannot be read without the old software | Out, unless restored |

Fictional example. The group chose to transfer the four "in" record sets to its active parent before licensing, so the subsidiary could stay dormant and be struck off later.


## Common mistakes with acquired and retired records

Most of them happen quietly, on someone else's project plan.

- Assuming an asset purchase brought every record across without reading the schedules.
- Switching off the system before a full export, then finding the backups need the old software.
- Losing the schema knowledge when the last engineer leaves.
- Treating a retired product's customer contracts as dead.
- Letting a dormant entity be struck off while it still owns the records and the copyright.
- Signing a licence in a dormant UK company without telling the people who file its dormant accounts.
- Leaving shared systems out of a carve-out agreement, so neither side is sure it may license the history.
- Paying to store duplicate systems for years because nobody was asked to decide.


## A retired product's records as a data asset

A product that ran for ten years leaves a complete, closed record of real work: every problem customers raised, every fix, every release. Complete histories of that kind are what AI developers ask companies for, and a retired product has one advantage over a live one. Nothing in it is still changing.

Origin works with buyers and helps a company describe what a dormant entity or retired system holds, find out what it could be worth and decide whether to go further. Nothing is exported at the start. If the group is selling or closing the entity instead, read the [guide to licensing data when selling a business](https://origindatapartners.com/guides/license-company-data-when-selling-business). Origin Data Partners is an independent data partner that helps companies get their data bought. A buyer may pay Origin when a deal closes.

Does your company hold records like these? [See what your data is worth](https://origindatapartners.com/check-fit).


## Questions and answers

### Can you sell company data after a merger or acquisition?

Usually yes, if the deal gave you the records and the contracts attached to them allow it. After a merger the surviving company owns them. After a share purchase the acquired company still does. After an asset purchase, check the schedules. Customer contracts and privacy promises carry over.

### Who owns data after an acquisition?

In a share purchase, the acquired company, now your subsidiary. In a merger, the surviving company: under Delaware section 259 all property of the merged companies becomes the property of the survivor. In an asset purchase, whoever the agreement names for each asset.

### What should you do with data from a decommissioned system?

Before switch-off, export it in an open format with attachments and audit history, write down the schema, count the records and note which contracts apply. Then decide what to delete, what to keep for retention duties and what could be licensed.

### Can records of a discontinued product line be licensed for AI training?

Often, for the company's own records: support tickets, bug history, code and internal documents, once personal data is removed. Customer content held under the service contract normally has to be returned or deleted and is not the company's to license.

### Does licensing data end a UK company's dormant status?

Yes, in practice. Companies House treats a company as dormant only if it had no significant transactions in the financial year. A licence fee is a significant transaction, so the next accounts would be non-dormant.

### What happens to company records when a dormant subsidiary is struck off?

In the UK, property and rights the company still holds at dissolution are deemed bona vacantia and belong to the Crown under section 1012 of the Companies Act 2006. Transfer or license the records before applying.

### Who can license shared data after a carve-out?

Whoever the sale agreement says. In a carve-out, systems and history are often shared for a period under a transition services agreement. If the agreement is silent on licensing, neither side should assume it has the right. Agree it in writing.

## Sources

- [Delaware General Corporation Law, subchapter IX (section 259: effect of merger)](https://delcode.delaware.gov/title8/c001/sc09/)
- [Delaware General Corporation Law, subchapter X (sections 271 and 278: sale of assets, winding up)](https://delcode.delaware.gov/title8/c001/sc10/)
- [GOV.UK: Dormant companies and associations, dormant for Companies House](https://www.gov.uk/dormant-company/dormant-for-companies-house)
- [GOV.UK: Strike off your limited company from the Companies Register](https://www.gov.uk/strike-off-your-company-from-companies-register)
- [GOV.UK: Strike off your limited company, close down your company](https://www.gov.uk/strike-off-your-company-from-companies-register/close-down-your-company)
- [Companies Act 2006, section 1012: property of dissolved company to be bona vacantia](https://www.legislation.gov.uk/ukpga/2006/46/section/1012)
- [Regulation (EU) 2016/679 (GDPR): Articles 5 and 28, Recital 26](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng)
- [California Civil Code section 1798.140: definitions (sell, service provider)](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=CIV&sectionNum=1798.140)

## Related reading

- [Asset sale vs stock sale: tax, liabilities and your data](https://origindatapartners.com/guides/asset-sale-company-data)
- [Selling your business or practice: can you license its data separately?](https://origindatapartners.com/guides/license-company-data-when-selling-business)
- [Cancel Google Workspace or delete Slack? Export data first](https://origindatapartners.com/guides/export-company-records-before-closing)
- [Stop deleting it: which business records to keep so you can license them later](https://origindatapartners.com/guides/keep-company-data-sellable)
- [Does an NDA or Customer Contract Block Licensing Your Data?](https://origindatapartners.com/guides/nda-customer-contract-data-licensing)
- [Dark Data Monetization: Turning Unused Records Into Income](https://origindatapartners.com/guides/dark-data-monetization)
