Service · Virtualisation
Virtualising legacy systems in insolvency: keep using ERP and accounting
The old hardware is being realised, but the data in the ERP system will be needed for years to come. Beweisanker migrates legacy systems to a virtual environment in which merchandise management, financial accounting and industry software remain as usable as before the insolvency.
- Independent of the original hardware
- Operable like the original
- Basis for GoBD data access
- ERP server (Windows Server 2012)running
- SQL database, merchandise managementrunning
- Financial accounting (client)running
- Licence server & dongle emulationchecked
- Tax audit data access (Z1)set up
5 users · loggedUses
What the administration needs the virtualised legacy system for
Debt collection
Open item lists, delivery notes and dunning history remain retrievable, so that receivables can be evidenced and collected.
Analyses & reports
Balance sheets, trial balances or inventory valuations can be generated with the software's original functions.
Tax data access
For a tax audit, the system must be available in machine-analysable form and, depending on the circumstances, also for direct access.
The problem: data without an operational system is barely usable
Merchandise management, ERP and financial accounting store their data in proprietary databases. Without the matching software, neither an open item list nor an account sheet can be meaningfully generated from them. At the same time, the software often runs on old hardware that belongs to the estate and is to be realised, or on rented servers whose contracts are ending.
Under § 155 InsO (German Insolvency Code), bookkeeping obligations continue, and records must remain readable and analysable throughout the statutory periods. A mere database export meets this requirement only to a limited extent. The solution is to virtualise the legacy system: it keeps running, just no longer on the original hardware.
How we virtualise legacy systems
The basis is a complete preservation of the system as a 1:1 image. From this, we create a virtual machine that behaves like the original computer.
Physical-to-Virtual (P2V)
In a P2V migration, a physical server or workstation is converted into a virtual machine. Drivers and system settings are adjusted so that the operating system starts in the new environment. Databases, program versions and client structures remain unchanged.
Open virtualisation platform
We rely on Proxmox VE and KVM, i.e. established open-source technology. This avoids dependence on individual vendors and licensing models, which matters when a system has to be operated for many years. Systems already virtualised on other platforms can generally be taken over and converted.
Typical legacy systems
- ERP and merchandise management systems with their own database
- Financial accounting and payroll, such as locally installed DATEV data or other accounting software
- Industry software for trades, retail, construction, logistics or healthcare
- Document management and archive systems
- Older Windows servers with specialist applications for which updates are no longer released
Licensing questions should be clarified early. Whether software may continue to be used after virtualisation depends on the vendor's licence terms and must be examined in the individual case. We document existing licence keys, dongles and maintenance contracts as early as the preservation stage.
Secure operation of outdated systems
Legacy systems often no longer receive security updates. We therefore operate them isolated at network level: the virtual machine has no unprotected internet access, and access takes place via secured browser access or an encrypted connection. Every login is logged. Before any changes, we create snapshots, so that the system can be reset to the preserved initial state at any time.
With merchandise management and ERP in particular, it is important that the system does not continue working unnoticed after virtualisation. Automatic jobs such as dunning runs, order proposals, interfaces to banks or online shops and email dispatch are therefore deactivated before the system is first started. The data thus remains as it was at the time of preservation, and no unwanted postings or messages to customers and suppliers are generated.
Where possible, we integrate hardware dongles required by some industry software by passing them through to the virtual machine. Where this does not work, we look for alternatives with you, such as an export route via the vendor.
Access models
We provide the virtualised environment in the way that suits your law firm:
- Cloud in Germany: operation on open-source infrastructure in German data centres, access via browser
- Locally at the law firm: provision on a dedicated computer or server, offline on request
- With or without administration: we take care of maintenance and user management, or you operate the environment yourself
- Access for third parties: logged access for tax advisers, tax auditors or experts
Tax data access
Under § 147(6) AO (German Fiscal Code), the tax authorities can access tax-relevant data directly (Z1), indirectly (Z2) or through the provision of data media (Z3). A virtualised legacy system enables all three forms. The requirements that apply after a system change are explained in our guide on tax data access. For long-term operation throughout the retention periods, see Archiving and retention obligations.
Direct line
Preservation urgent?
Call us. We usually clarify scope and next steps in the very first conversation.
- Response usually on the same working day
- Preservation on site or remotely
- Binding quote in advance
Process
From image to operable system
Preservation
1:1 image of the server or workstation with checksum log.
Conversion
P2V migration to a virtual machine on Proxmox VE or KVM.
Function test
We check start-up, database, login and key analyses together with you.
Provision
Isolated, logged access according to the chosen access model.
Frequently asked questions
Virtualising legacy systems
Can the old server hardware be sold after virtualisation?
Yes, once preservation and the function test are complete. Before the sale, the storage media should be erased using recognised methods.
Does virtualisation also work with very old software?
In most cases yes, including operating systems no longer supported by the vendor. Hardware dongles or special cards can be difficult; we check these in advance.
May we continue to use the software after virtualisation?
This depends on the vendor's licence terms and must be examined legally in the individual case. We compile the necessary information on licences and contracts.
Who can access the virtualised system?
Only the persons you authorise, such as your team, the tax adviser or the tax auditors. Every access is logged and can be restricted to individual functions.
How long can a virtualised system be operated?
As long as necessary, including for the entire retention period. We adjust operation when less access is needed as the proceedings progress, thereby reducing running costs.
Further reading
Related services
Insolvency data preservation
Complete 1:1 preservation of servers, clients, email and databases with SHA-256 log.
Data preparation & research
Full-text search and email research for insolvency avoidance, liability and expert reports.
Archiving & retention
Long-term archiving – audit-proof on WORM storage (Object Lock) – throughout the commercial and tax-law retention periods.
From the Guides
In-depth articles
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.
Read article →DATEV data in insolvency: preserving the accounts and keeping them usable
Where the debtor's DATEV data resides, how you obtain accounting and payroll data, and how exports and virtualisation keep the accounts usable over the long term.
Read article →Tax data access (Z1, Z2, Z3) after business closure
How insolvency administrators ensure the tax authorities' data access under § 147(6) AO even after business closure. With an explanation of Z1, Z2 and Z3 and virtualisation as the solution.
Read article →Every day counts.
Contact us as soon as proceedings are on the horizon. Together we will clarify 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