Guides

Software licences in insolvency: continue using, transfer, terminate

How insolvency administrators deal with perpetual licences, subscriptions, SaaS and OEM licences: continued use, transfer in an asset deal, resale and termination of unused contracts.

Hardly any company works without licensed software. Financial accounting, ERP, CAD, office suites and specialist applications run on the basis of licence agreements that have often grown over years and are scarcely documented. In insolvency, three questions arise: may the software continue to be used to analyse data and continue business operations? Can licences be transferred to a buyer or sold? And which contracts should be terminated to relieve the insolvency estate? This article provides a structured overview of software licences in insolvency.

Types of licence and why the distinction matters

How a licence is to be handled in insolvency depends above all on its contractual design. In practice, four basic forms are encountered:

  • Purchased or perpetual licence: the right of use is granted for an unlimited period in return for a one-off payment. Separate maintenance or update contracts are frequently added.
  • Rental and subscription: the software is used for a specific period in return for recurring fees. When payment stops, the right of use generally ends as well.
  • Software as a Service (SaaS): the application runs at the provider, and the company accesses it via the internet. Besides the right of use, the main issue here is access to the data stored at the provider.
  • OEM licences: the licence is acquired together with hardware, for example a pre-installed operating system. It is frequently tied to the device.

For every piece of software, distinguish between the right of use and maintenance. A terminated maintenance contract does not automatically mean that the right of use lapses.

The administrator’s right of election under § 103 InsO

If a mutual contract has not been fully performed by either party at the time the proceedings are opened, the insolvency administrator may choose under § 103 InsO (German Insolvency Code) whether to perform the contract and demand performance from the counterparty or to refuse performance. For software contracts, it is therefore decisive whether they have already been fully performed.

For a perpetual licence that has been paid in full, a widely held view frequently assumes that the contract has been performed. There would then be no scope for the right of election, and the right of use would remain in place. However, this classification is not certain in every case. It depends on the contractual design, for instance on whether ongoing obligations of the licensor were agreed. There is no express statutory insolvency protection for licences in Germany.

For rental and subscription contracts and for SaaS, the situation is different because both parties perform on an ongoing basis. Here the right of election or, depending on the classification, the special rules for continuing obligations come into consideration. In practice, the following points must be examined:

  1. Which performance do both parties still owe?
  2. Does the contract contain termination rights for the event of insolvency, and are these effective?
  3. Are the software or the data still needed for the administration?
  4. What costs arise on continuation, and what costs on termination?

The assessment in the individual case requires a legal review. Technically, however, before any refusal or termination it should be ensured that the data are fully preserved and readable without the software.

Reselling used software

Licences no longer needed can generate realisation proceeds. On the principle of exhaustion, the Court of Justice of the European Union has ruled that the manufacturer’s distribution right in a copy of a program is exhausted under certain conditions once it has made that copy available for permanent use in return for a fee. This can also apply to downloaded software. The first acquirer must then render its own copy unusable.

For realisation in insolvency, this means:

  • In principle, only licences granted permanently come into consideration, not subscriptions or SaaS.
  • Volume licences cannot simply be split up at will. The details are disputed and depend on the licence model.
  • It should be possible to evidence the origin and the chain of rights without gaps.
  • The deletion of the installations at the seller should be documented, for example as part of data erasure and hardware remarketing.

Transfer in a transferring restructuring and asset deal

If the business is sold by way of a transferring restructuring, the buyer generally wishes to continue using the software deployed. Whether the licences can be transferred along with it depends on the respective licence agreement. Many agreements contain consent requirements under which a transfer is permissible only with the manufacturer’s approval. For subscriptions and SaaS, a contract assumption without the provider’s cooperation is regularly not possible.

When preparing an asset deal, the following is recommended:

  • Review the licence agreements early for transfer and consent clauses.
  • Contact the manufacturers in good time, as consents take time.
  • Set out clearly in the purchase agreement which licences pass over, which must be newly concluded and who bears the risk of consent being refused.
  • Consider the data held in the software separately. Even if the licence passes over, the insolvency estate must still be able to meet its own retention obligations.

Virtualising legacy systems: what applies to the licences?

After business closure, accounting and ERP data often have to remain readable for years. A proven solution is to transfer the legacy system to a virtual environment so that the original hardware can be realised. Beweisanker describes the approach on the page Virtualisation of legacy systems.

In terms of licensing law, this raises its own questions:

  • Windows Server: with OEM licences, the binding to the original hardware must be observed. Whether a transfer to virtual hardware is permissible depends on the licence terms. A new licence for the virtualisation environment may be required.
  • ERP and specialist applications: some programs check hardware characteristics or require online activation with the manufacturer. If the manufacturer itself is no longer in the market or the maintenance contract has ended, reactivation can become difficult.
  • Database licences: if databases are licensed per processor core, the allocation of virtual resources can affect the licence costs.
  • Read-only operation: some manufacturers offer discounted archive or read-access licences. It is worth asking.

Clarify the licensing question before virtualisation, not afterwards. It is important that activation data, licence keys and installation media are secured before the original hardware is realised.

Licence audits and cost reduction

Software manufacturers occasionally carry out licence audits. In insolvency this is particularly delicate if the licensing position is unclear. Back-claims from the period before the opening are in principle insolvency claims, whereas under-licensing during the ongoing proceedings can burden the insolvency estate. A complete licence inventory is the best defence.

At the same time, the inventory offers an opportunity to cut costs. Frequently found are:

  • Subscriptions for former employees that continue to be billed.
  • Duplicate licences after earlier system changes.
  • Maintenance contracts for software that is no longer used.
  • Cloud subscriptions with unneeded add-on modules.

Cancel unused subscriptions promptly, but only after the data stored there have been fully preserved. This applies in particular to cloud services whose content is deleted after the contract ends. Guidance on this is provided on the page on preserving Microsoft 365 and cloud services.

Approach: creating a licence inventory and securing evidence

A structured approach creates clarity for all decisions on continued use, transfer and termination.

  1. Record the software: list all programs installed on servers and workstations and all cloud services in use.
  2. Assign the licence type: for each product, record whether it is a perpetual licence, a subscription, SaaS or an OEM licence.
  3. Secure the evidence: gather invoices, licence certificates, licence keys and contract documents and store them in a protected location.
  4. Secure manufacturer portals: take over and document access to licensing portals and customer accounts, as these often hold the only evidence.
  5. Assess requirements: decide which software is needed for administration, continuation or sale.
  6. Implement measures: continue, transfer, realise or terminate contracts and record the decisions.

The licence documents are among the data that should be preserved before any shutdown. They form part of a complete insolvency data preservation and are needed later during the IT wind-down in insolvency proceedings for an orderly termination.

How Beweisanker supports you

Beweisanker creates the technical inventory of the software, preserves licence evidence and data and prepares legacy systems for long-term read-only operation. The legal assessment of the contracts remains with you and your advisers; we provide the technical basis for it. Feel free to contact us via the contact form.

Frequently asked questions

May the insolvency administrator continue to use purchased software?

For a licence granted permanently and paid in full, a widely held view frequently assumes that the contract has been performed and the right of use continues. However, the specific contractual terms are decisive.

Can a software manufacturer terminate the contract because of the insolvency?

Many contracts contain termination clauses for the event of insolvency. Whether such clauses are effective is legally disputed and should be examined in the individual case.

Can licences simply be transferred along with the business in a sale?

Not always. Many licence agreements require the manufacturer’s consent. For subscriptions and SaaS, a transfer without the provider’s cooperation is regularly not possible.

What should be considered before cancelling a software subscription?

Before cancellation, all data stored at the provider should be exported in full and preserved in a readable format. These data are frequently deleted after the contract ends.

This article is for general information only and does not replace legal advice in the 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 →

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.

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 →

Every day counts.

Talk to us as soon as proceedings are on the horizon. Together we establish which systems are affected and what needs to be preserved first.

Operating nationwide (Germany) · on site at short notice in Baden-Württemberg and German-speaking Switzerland