Guides

Checklist: IT preservation in the first 72 hours after the insolvency petition

What preliminary administrators, court-appointed experts and insolvency administrators should do for IT preservation in the first 72 hours after the insolvency petition. With priorities, typical mistakes and a checklist.

After the insolvency petition, the question of whether the debtor's data will be preserved in full is decided within a few days. Servers are still running, access still exists, employees with knowledge of the systems can still be reached. At the same time, hosting contracts are being terminated, licences blocked and computers sold. This checklist shows what preliminary administrators, court-appointed experts and insolvency administrators should do for IT preservation in the first 72 hours and which mistakes can be avoided.

Why the first days are decisive

Under § 36(2) no. 1 InsO (German Insolvency Code), the business books form part of the insolvency estate. Under § 155 InsO, the bookkeeping and accounting obligations under commercial and tax law continue to apply; in opened proceedings, the administrator fulfils them in respect of the estate. Even the preliminary administrator under § 22 InsO has the task of securing and preserving the debtor's assets. Data is today a central part of these assets: it forms the basis for collecting receivables, for examining avoidance claims under §§ 129 et seq. InsO and for fulfilling tax obligations.

Unlike inventory, data often disappears unnoticed. A terminated cloud contract, an overwritten laptop or a switched-off server is enough for accounting and correspondence to be irretrievably lost.

Rule of thumb: anything that is not preserved, or at least protected from alteration, in the first 72 hours is at risk thereafter. Preservation comes before analysis.

Step 1: IT inventory

Before anything can be preserved, it must be clear what exists in the first place. The inventory should be quick and pragmatic, not perfect. The following questions are important:

  • Systems: which servers, workstations, laptops, NAS systems and external data carriers are there? Which specialist applications run on them, such as financial accounting, merchandise management, payroll or CRM?
  • Locations: where is the hardware? Are there branches, warehouses, home-office devices or an external data centre?
  • Cloud services: are Microsoft 365, Google Workspace, DATEV cloud solutions, online shops or industry software used as software-as-a-service?
  • Service providers: which IT service providers, systems houses, hosting providers or tax advisers have access or hold data?
  • Access credentials: where are passwords documented? Is there a password manager, a list held by the service provider or only the knowledge of individual people?
  • Admin accounts: who holds administrator rights for servers, domain, firewall and cloud tenants? Are there global administrators in Microsoft 365?

Under § 97 InsO, the debtor and its corporate representatives are obliged to provide information and cooperate. In practice, this obligation also covers information on the IT landscape and on access. It is advisable to record the information provided in writing.

Step 2: Immediate measures

In parallel with the inventory, a number of measures should be implemented without delay.

Secure access credentials

Have the access credentials to all central systems handed over and keep them separately and protected. Particularly important are administrator accounts for the domain, the cloud tenants, the hosting provider and domain management. Whoever controls the domain also controls e-mail and many cloud logins. Check whether an additional administrator account can be set up for the administration instead of working permanently with employees' personal accounts.

Block access by former employees

Employees who have left or been released from their duties should no longer have access to systems. Block their accounts rather than deleting them. With cloud services such as Microsoft 365, deletion can result in the associated mailbox and OneDrive storage being permanently removed after a period. Remote maintenance access by external service providers should likewise be reviewed and restricted where necessary.

Check terminations of hosting and licences

Clarify which contracts have already been terminated or could be blocked because of payment arrears. With cloud services, expiry or termination is typically followed by a transition period of a few weeks to months, after which the data is permanently deleted. The exact periods depend on the provider and contract. Until the data has been preserved, contracts that hold data should not be ended. More on this on our page on preserving Microsoft 365 and cloud services.

Do not delete data

Expressly instruct the debtor, employees and service providers not to delete any data, not to reset any devices and not to dispose of or sell any hardware. This also applies to apparently old computers and data carriers. A short written instruction creates clarity and documents your approach.

Step 3: Set priorities

Not everything can be preserved at the same time. The following order has proven effective:

  1. Cloud accounts and e-mail. They are most at risk of blocking and deletion and can often be preserved remotely straight away.
  2. Financial accounting, payroll and merchandise management. This data is central to collecting receivables, reviewing avoidance claims and tax obligations. Not only the data holdings should be preserved but, wherever possible, the working system.
  3. File servers and NAS. Contracts, correspondence, project documents and personnel files are frequently on central shares.
  4. Workstations and laptops. Locally stored files and mailbox archives are often forgotten, especially on mobile devices.
  5. Mobile devices and other data carriers. USB hard drives, backup tapes and smartphones can contain relevant data.

For each preservation, it should be recorded when, by whom and to what extent it was carried out. Checksums such as SHA-256 make it possible later to prove that the images are unaltered. How we go about this is described on the Insolvency data preservation page.

Typical mistakes

In practice, some mistakes recur that can be avoided with little effort:

  • Taking only an export of the accounts. A PDF or CSV export does not replace the system. The original system is often needed for later analyses and for data access by the tax authorities.
  • Realising hardware too early. If a computer is sold before it has been preserved, the data is lost. Before realisation, the data must be preserved and then verifiably erased.
  • Deleting user accounts instead of blocking them. In cloud environments in particular, this can trigger the loss of mailboxes.
  • Relying on existing backups. The debtor's existing backups are often incomplete, outdated or encrypted without the key being known.
  • No documentation. Without a log, it is hardly possible later to prove which state was preserved and whether it is unaltered.
  • Overlooking data protection. Preserved data also contains personal information. It must be appropriately protected, for example by encryption and restricted access under Art. 32 GDPR.

The checklist for the first 72 hours

  1. Have contacts named at the debtor and at the IT service provider.
  2. Request an overview of servers, clients, NAS, data carriers and locations.
  3. Record all cloud services and software-as-a-service applications in use.
  4. Take over access credentials for domain, cloud tenants, hosting provider and domain management.
  5. Identify administrator accounts and have a dedicated account set up for the administration.
  6. Block, do not delete, the accounts of departed employees and unneeded remote access.
  7. Check pending terminations, payment arrears and threatened blocking of hosting and licences.
  8. Issue a written instruction: no deletion, no resetting, no disposal of hardware.
  9. Preserve cloud accounts and e-mail mailboxes as a priority.
  10. Preserve financial accounting, payroll and merchandise management as a working system.
  11. Preserve file servers, NAS and workstations.
  12. Log each preservation with time, scope and checksum.
  13. Store preserved data encrypted and with restricted access.
  14. Plan further use: virtualisation of the legacy system, research and archiving.

If you need support with implementation, we carry out the preservation on site or remotely. You will find an overview of how we work together on the page for insolvency administrators and under Process.

Frequently asked questions

Does the preliminary administrator already have to preserve the IT?

Under § 22 InsO, the preliminary administrator has the task of securing and preserving the debtor's assets. As the business books form part of the estate, there is much to be said for initiating data preservation as early as possible. The specific scope depends on the court's order.

Is it enough to take over the debtor's existing backups?

Often not. Existing backups are frequently incomplete, outdated or cannot be restored without the original software. They should be checked, but as a rule do not replace a separate, documented preservation.

What needs particular attention with Microsoft 365?

Accounts should not be deleted and contracts not ended before mailboxes, OneDrive and SharePoint have been preserved. After expiry or termination there is only a limited transition period, after which the data is permanently deleted.

How can it be proven that preserved data is unaltered?

By means of cryptographic checksums such as SHA-256, which are calculated during preservation and logged together with time and scope. A later recalculation shows whether the holdings have been altered.

Note: this article is for general information only and does not replace legal advice in an individual case. The provisions in force at the time and the circumstances of the specific proceedings are decisive.

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