Restructuring a holding is always stressful for the business. Owners most often see only the tip of the iceberg: changing the nameplate and signing resolutions. In practice, however, most problems arise not in the legal domain, but at the seams between access management, HR records and data integrity.
When a holding changes its legal entity (for example, carving an asset out into a new operating company), a triple process kicks off: staff transfer (under labour law), migration of the IT landscape and re-execution of contracts. Left to run on its own, lawyers and IT specialists work in parallel, and this leads to collapse: employees lose access on day one, while databases "crash" because of account conflicts.
The key decision is to form a "lawyer + IT architect" tandem as early as the planning stage. Below we break down how this works on each front.
1. The legal front: not just orders and notices
The classic lawyer's mistake in restructuring is to think only about documents. But when transferring staff to a new legal entity, three IT dependencies must be taken into account.
If the system of record (CRM/ERP) migrates to new servers or a different cloud, you need to obtain consent from employees and counterparties again, or execute an addendum to the agreement.
The qualified electronic signature of the old entity's director is invalid for the new one. This affects regulatory filings, access to government information systems and trading platforms.
If the accountant logged in to the old company's online banking, after the entity change the access is reset to zero. Synchronisation with IT is needed: when the certificates are reissued.
2. Staff transfer: the digital twin of termination
Transferring employees to a new legal entity through termination (even a "transfer-type" one) generates a global failure in the IDP (Identity Provider). Picture this: 50 people sign termination requests on Friday, and on Monday they start at the new company.
What the IT architect does
- Creates "transit" accounts or sets up a mass change of user accounts.
- Migrates session histories so that corporate messengers don't drop.
- Aligns the date for resetting access to the old domain to 2 hours before the onboarding is signed.
What the lawyer does
- Includes a clause on changing the corporate user account in the transfer notices (issued in advance under labour law if the entity changes at the employer's initiative).
- Executes an addendum on transferring the employee's data (personnel file, social security and tax identifiers) - without this the IT architect has no right to copy the profile into the new database.
The risk of a gap. If IT migrates the data on the 25th, but the lawyer signs the deeds on the 1st of the following month, then for 6 days the employee is working "outside the system." The "lawyer + IT" tandem introduces a single "approval changelog."
3. Data migration: contracts, registers, e-signatures and legacy systems
This is the most expensive stage. When the legal entity changes, data does not "flow over" automatically - it has to be transferred to the new tax and registration identifiers.
The task pool for the tandem
- ERP databases. The lawyer confirms that old delivery notes and invoices remain valid under tax regulations. The IT architect replicates them while preserving numbering, or flags them as "Archive: Entity-1."
- CRM. The "counterparty legal entity" field has to be replaced in bulk. Manual entry is a mistake. Automation via API plus the lawyer's sign-off that this does not change the jurisdiction of the deals.
- Cloud drives (M365, Google Drive). Changing folder ownership. If this is not done, the former director of the old entity retains rights to the trade secrets of the new one. The lawyer records this in the asset handover deed.
The main stop factor. A system written 10 years ago is tied to the old domain via a security certificate. The IT architect intercepts the traffic through a reverse proxy, while the lawyer checks whether this breaches the terms of the developer's licence agreement.
4. The synchronisation formula: a RACI matrix for the lawyer and the IT architect
To avoid chaos, a responsibility matrix is drawn up at the start of the project. It establishes who is responsible for the outcome (R), who approves it (A), who is consulted (C) and who is informed (I) on each task.
| Task | Lawyer | IT architect |
|---|---|---|
| Transfer notices (labour law) | R / A | C |
| Personal data consents and addenda | R / A | C |
| Changing and resetting user accounts | C | R / A |
| ERP database migration with preserved numbering | C | R |
| Bulk entity replacement in CRM (API) | A | R |
| Changing cloud folder ownership | A | R |
| Reissuing the e-signature for the new entity | R | C |
| Software licences and letters to the vendor | R | C |
| Approval changelog (single schedule) | A | A |
Double-run migration. To avoid downtime on "day zero," the old and new domains run in sync for 2-3 days: the IT architect configures traffic routing, the lawyer prepares bilateral service acceptance deeds for that period.
Turnkey holding restructuring
Changing the legal entity, transferring staff and migrating data is a process where mistakes at the seam between law and IT cost millions. G-Invest supports such projects end to end: a restructuring roadmap, a joint audit by lawyers and IT architects, a lawful scheme for transferring employees while preserving their digital profiles, and data migration without loss of history in compliance with GDPR and data protection rules.
Frequently asked questions
What are the risks when migrating ERP databases during an entity change?
The main risk is a "break" in the numbering of primary documents and the loss of settlement history with counterparties. It is solved by migration through a dedicated data transfer tool and a legal succession deed.
Who is responsible for employees' personal data when the operator changes?
The new legal entity becomes the new personal data controller. The lawyer is obliged to notify the data protection authority within the statutory deadline. The IT architect ensures encryption when transferring personal data sets between the old and the new entity (in line with GDPR).
What to do with the director's electronic signature during restructuring?
The e-signature is tied to the registration number. When the entity changes, the e-signature is revoked. Solution: ahead of the transition, issue an e-signature for the new entity, with the right to delegate to staff of the old one - this is a task for the tandem of the lawyer and the system administrator (IT).
How to avoid business downtime on "day zero"?
Organise a "parallel launch": for 2-3 days the old and new domains run in sync. The IT architect configures traffic routing, the lawyer prepares bilateral service acceptance deeds for that period. This is called "double-run migration."
Does changing the legal entity affect software licences?
Yes. Without re-executing the licence agreement, the new entity becomes a pirate. The "lawyer + IT" tandem: the lawyer writes to the vendor about the reorganisation, the IT architect applies re-hosting rights.