Guides
Selling customer data in insolvency: value, permissibility, process
How insolvency administrators realise a customer database in an asset deal, which data may be transferred without consent and how the value of a customer base can be estimated reliably.
For many acquirers, the customer base is the real reason for taking over an insolvent company or parts of it. Machines can be bought new; established customer relationships cannot. At the same time, customer databases consist almost entirely of personal data, and selling them is no ordinary purchase agreement in data protection terms. Anyone who wants to sell customer data in insolvency must therefore answer two questions at once: what is the database worth, and under what conditions may it be transferred? This guide shows how to classify the customer database as an asset in an asset deal, which case groups data protection practice distinguishes, what happens to marketing consents and what a reliable valuation looks like.
The customer database as an asset of the estate
A customer database is not a physical object but a body of information. Nevertheless, as part of the business, it belongs to the insolvency estate and is subject to the administrator's power of administration and disposal under § 80 InsO (German Insolvency Code). Its economic value arises from the possibility of continuing existing business relationships or approaching former customers again.
In a share deal, the question hardly arises: the legal entity remains the same, and the data stays with the same controller. In insolvency proceedings, however, the asset deal within a transferring restructuring predominates. Here the controller changes. In data protection terms, every transmission to the acquirer is a processing operation that requires its own legal basis. The basics of the administrator's role as controller are explained in the guide GDPR and insolvency administrators.
Consent of the creditors' bodies
Under § 160(2) no. 1 InsO, the sale of the company or of a business is a particularly significant legal act that requires the consent of the creditors' committee or the creditors' meeting. If only the customer database is sold on its own, it must be examined in the individual case whether it is of comparable significance for the proceedings. Irrespective of this, the data protection assessment belongs in the documents submitted to the creditors' bodies.
Legal basis for the transfer: Art. 6(1)(f) GDPR
Obtaining consent from every single customer is practically impossible with larger databases. The transmission is therefore regularly based on legitimate interests under Art. 6(1)(f) GDPR. The legitimate interest is obvious: creditors benefit from a higher purchase price, the acquirer wants to continue the business relationships, and customers too often have an interest in warranty, spare parts supply or service continuing.
These interests must be weighed against the interests of the customers. The decisive question is whether they could reasonably expect that their data would pass to a new owner when the business was sold. The closer and more recent the business relationship and the less sensitive the data, the more likely the balancing is to come out in favour of the transfer.
The case groups of data protection practice
The German Data Protection Conference (Datenschutzkonferenz) of the federal and state authorities has described case groups for the asset deal, which practice follows. In simplified form, they can be summarised as follows:
- Customers with current contracts: if the contract passes to the acquirer, the data needed to perform the contract can be transferred with it. Under civil law, the assumption of the contract itself generally requires the customer's consent, so the customer is involved in any case.
- Existing customers without a current contract but with a recent business relationship: here, a transfer on the basis of an opt-out approach is considered permissible. The customers are informed in advance and given a reasonable period to object to the transmission.
- Customers whose last contact was long ago: for old records, according to this approach, the interest of the data subjects prevails. They should not be transferred, but remain with the estate and are erased once the retention obligations have expired.
- Outstanding receivables: if receivables against customers are sold as well, the transmission of the data needed for them is generally permissible on the basis of legitimate interests.
- Particularly sensitive data and bank data: health data and other data under Art. 9 GDPR, as well as bank details, are, according to the prevailing view, transferred only with express consent.
The specific limits, in particular how long ago a business relationship may have ended and what objection period is reasonable, should be determined and documented in the individual case. Where there is uncertainty, consultation with the competent supervisory authority may be advisable.
Divide the customer base into case groups before the sale. Treating all records uniformly is almost always either too generous or gives away value.
Marketing consents and newsletter lists
Stricter standards apply to marketing data. Consent under Art. 6(1)(a) GDPR is given to a specific controller. According to the prevailing view, it does not automatically pass to an acquirer. In addition, there are the unfair competition requirements of § 7 UWG (German Act against Unfair Competition) for advertising by email, telephone and messenger, which require prior express consent or the narrow conditions of the existing-customer exception.
In practice, this means:
- Consents whose wording already expressly provides for disclosure to legal successors are an argument in favour of the transfer. Whether this holds depends on the specific wording and on transparency.
- If there is no such clause, the acquirer should not send marketing to the recipients after the takeover without new consent. What is possible is a one-off, neutrally worded notice from the administrator about the change of ownership, combined with the opportunity to give new consent.
- Evidence of consents, such as double opt-in logs with timestamps, forms part of the purchased assets. Without it, a mailing list is practically worthless for marketing purposes.
- Unsubscribes and suppression lists must be handed over too, so that the acquirer does not contact people again who have objected.
Professional secrecy and sensitive sectors
Particular caution is required if the debtor is bound by professional secrecy or operated in a sensitive sector. Medical practices, care services, pharmacies, tax advisory and law firms are subject to a duty of confidentiality in addition to data protection. The unauthorised disclosure of third-party secrets is a criminal offence under § 203 StGB (German Criminal Code). Patient files or client records can therefore not be sold like an ordinary customer database. In these cases, the consent of the data subjects is generally required, and until then the files are kept separately.
Even outside professional secrecy, there are data sets that are particularly sensitive: data on children, data on payment defaults, credit information or movement profiles from apps. Here, the balancing under Art. 6(1)(f) GDPR should be documented with particular care.
Process: selling customer data in insolvency, step by step
An orderly process protects the administrator against liability risks and the acquirer against a database it may later not be allowed to use. The following sequence has proven itself:
- Preserve the database: before any processing, create a complete insolvency data preservation of the CRM, the online shop and the merchandise management system. It documents the initial state and protects against accidental loss.
- Analyse the database: number of records, date of last contact, existing contracts, outstanding receivables, consents, sensitive fields. Data preparation and research delivers this analysis from the raw data.
- Form case groups: assign each record to a group and determine its legal treatment.
- Data minimisation: transfer only the fields the acquirer needs for the purpose. Bank details, free-text note fields and internal ratings are as a rule held back.
- Inform and enable objection: write to customers in the opt-out group, inform them about the acquirer, purpose and deadline, and record objections reliably.
- Draft the purchase agreement: limit warranties on data quality, set out the acquirer's obligations as the new controller and make provision for assuming the information obligations under Art. 13 and 14 GDPR.
- Hand over and log: handover in a secure format, checksum, handover record with scope and cut-off date.
- Deal with the remainder: archive data not transferred with the estate where retention obligations exist, and otherwise erase it.
Due diligence before the purchase
Prospective buyers want to examine the database before buying. Aggregated key figures are generally sufficient for this: number of active customers, revenue distribution, regional distribution, repeat purchase rate, share of records with consent. Individual personal data should not be released before the purchase agreement is concluded. If a sample is unavoidable, it should be pseudonymised and protected by a confidentiality agreement.
Valuation: what is the customer base worth?
There is no market price for customer data as there is for machines. The valuation is an estimate that should be based on traceable criteria. The most important factors include:
- Recency: records with recent purchasing activity are worth considerably more than old holdings, which may not be transferred anyway.
- Transferable share: only the part that can legally pass according to the case group analysis feeds into the value. Objections reduce it subsequently.
- Data quality: duplicates, incorrect addresses and incomplete fields reduce its usefulness.
- Customer value: average revenue, contribution margin and repeat purchase rate per customer.
- Dependence on the business operations: without brand, domain, product range and service, a customer base quickly loses value. A stand-alone sale therefore usually achieves less than a package.
- Legal risks: uncertainties regarding consents or sensitive data lead to discounts or to indemnity demands from the acquirer.
The customer database is often realised not on its own but together with the domain, online shop and trademark rights. The guide domains in insolvency provides guidance on handling domains. If the software system in which the data resides is to be sold as well, the questions raised in the guide software licences in insolvency must also be considered.
An example from practice
A mail-order retailer of garden supplies files for insolvency. A competitor is interested in the brand, domain and customer base. Analysis of the shop system shows a large number of customer accounts, only some of which have placed orders in recent years. Consents with logs exist for the newsletter, but their wording does not provide for disclosure. After notification and an objection period, the administrator transfers the active customer accounts without payment data. Old records remain with the estate. Newsletter recipients are informed once that the shop is being continued under a new owner, together with the opportunity to sign up again there. The purchase price reflects the transferable share, not the total number of records.
Typical mistakes when administrators sell customer data in insolvency
Many problems arise not from the legal position but from time pressure. The following mistakes are encountered again and again in practice:
- Export without preservation: the acquirer receives a file, but the original state is not documented. In later disputes about scope and quality, the evidence is then missing.
- Entire database instead of a selection: the complete database content is handed over, including old records, payment data and internal notes.
- Objections not implemented: customers object within the deadline, yet their records still end up with the acquirer because the list was not reconciled with the export.
- Shutdown before handover: hosting or the shop system is terminated before the data has been fully exported.
- No separation in a mixed system: the customer data sits in the same database as accounting and personnel data and is copied unfiltered.
Anyone wishing to sell customer data in insolvency should use these points as a checklist before every handover. They can be avoided with manageable effort if the technical implementation is planned early.
Liability and documentation
A sale that infringes the GDPR entails risks for everyone involved. The supervisory authority can impose fines under Art. 83 GDPR, data subjects can claim damages under Art. 82 GDPR, and in a dispute the acquirer can assert warranty claims unless these have been effectively limited by contract. Whether this gives rise to personal liability on the part of the administrator is assessed under § 60 InsO and depends on the circumstances.
The best protection is documentation that makes the decision traceable: analysis of the database, case groups formed, balancing under Art. 6(1)(f) GDPR, information letters, objections received, handover record and erasure evidence for the remaining data. This belongs in the case file.
How Beweisanker supports the sale of customer data
When you sell customer data in insolvency, you decide on the legal treatment. Beweisanker preserves the systems holding the customer base and prepares the data so that you can form case groups and quantify the transferable share. We separate the data sets according to your instructions, produce the export file for the acquirer with checksum and handover record, and archive or erase the remaining data traceably.
In the event of a business closure, we also take on the IT wind-down, so that servers and cloud accounts are only switched off once all required data has been preserved and handed over. To discuss a specific case, you can reach us via the Contact page.
Frequently asked questions
May the administrator sell customer data without the customers' consent?
In many cases yes, based on legitimate interests under Art. 6(1)(f) GDPR and an opt-out approach. For particularly sensitive data, bank data and data of professionals bound by secrecy, on the other hand, consent is regularly required.
How long should the objection period be?
The GDPR does not specify a fixed period. It must be long enough for customers realistically to notice the information and respond. The chosen period and its justification should be documented.
Can the acquirer use the newsletter list it has taken over straight away?
As a rule, not without further ado. According to the prevailing view, consents apply to the controller to whom they were given. New consent given to the acquirer is the safe route.
Who informs customers about the change of ownership?
It makes sense for the administrator to provide information about the planned transmission before the handover. The acquirer must in turn fulfil the information obligations under Art. 14 GDPR. Both can be combined in a joint letter.
What happens to customer data that is not sold?
It remains with the estate. Data subject to retention obligations, such as invoices, is archived. All other records are erased as soon as they are no longer needed for the proceedings.
This guide is for general information only and does not replace legal advice in an individual case.
Direct line
Urgent preservation?
Call us. We usually agree the scope and next steps during the first conversation.
- Response usually on the same working day
- Preservation on site or remotely
- Binding quotation in advance
Read more
More guides
Liquidating a GmbH: checklist for IT and data from the dissolution resolution to custody of the records
What managing directors and liquidators should do with accounts, cloud, accounting, servers, website, hardware and paper records in each phase of the liquidation, so that nothing is missing once the GmbH has been deleted.
Read article →Continuation of business operations: keeping IT running in insolvency
How insolvency administrators keep IT stable during the continuation of business operations: critical systems, service providers and estate liabilities, key personnel, data preservation and an emergency plan.
Read article →GDPR: insolvency administrators as data controllers
Why the insolvency administrator becomes the controller under data protection law, which legal bases they can rely on, and how to organise access requests, data processing and safeguards.
Read article →