What Happens to Employees in a European Acquisition

Under TUPE and its EU equivalents, when a business or part of a business changes hands, most employees assigned to that part of the business transfer automatically to the buyer on their existing terms and conditions, continuity of employment intact, rather than being rehired fresh or left with the seller. This applies whether the deal is structured as an asset purchase or in some cases a service contract changing hands, not just a straightforward share sale, which surprises buyers who assumed employment questions were purely a matter of who they chose to make offers to.

A buyer generally can't use the transfer itself as grounds for a dismissal, and generally can't unilaterally worsen an employee's terms and conditions purely because of the transfer, though there are exceptions and nuances that vary by jurisdiction and situation. This is the piece that catches buyers most often: an integration plan that assumes you can quietly harmonize a transferred employee's terms down to match your existing team's terms is often not legally straightforward, and needs a proper local-law review before it's built into the deal model.

Both seller and buyer typically have an obligation to inform, and in some cases consult, affected employee representatives about the transfer before it happens, on a timeline that needs to be built into deal planning, not treated as a post-closing afterthought. Skipping or rushing this step is a common, avoidable source of post-deal disputes, and it needs lead time that a fast-moving deal timeline doesn't always naturally accommodate.

Because terms and conditions carry over, a buyer needs to actually understand what they're inheriting, not just headcount and salary, but accrued benefits, pension obligations, and any collective agreements that come with the transferred employees. Due diligence on the workforce should get the same rigor as financial and IP due diligence, since employment terms you didn't know you were inheriting can materially change the deal's real economics after closing.

Workforce due diligence for a transfer should cover at least these items:

• The existing terms and conditions of every transferring employee, including continuity of employment, since these carry over to the buyer intact.
• Accrued benefits owed to the transferring employees, not just headcount and salary, so the deal price reflects what is actually being inherited.
• Pension obligations that come with the transferred workforce, reviewed with the same rigor as financial and intellectual property diligence.
• Any collective agreements that apply to the transferring employees, since they travel with the business and shape what changes are possible after closing.

Because you generally can't immediately harmonize terms or make transfer-driven changes without proper process, build your integration timeline around a realistic path (often involving a genuine business reason unrelated to the transfer, proper consultation, and time) rather than assuming day-one alignment with your existing team's structure and terms. Rushing this is where a technically compliant transfer still turns into a workforce relations problem.

A common pattern is the deal team negotiating the acquisition with a cost model that assumes quick post-closing savings from harmonized headcount and terms, while the people actually responsible for integration only learn about the transfer constraints after signing, when it's too late to adjust the deal price or timeline for what's actually achievable. Loop in whoever will own workforce integration during deal structuring, not after, so the deal model reflects what's realistically possible under the transfer rules.

Employees who transfer under these rules didn't choose the acquisition, and uncertainty about their job during a deal process is genuinely stressful, independent of the legal protections in place. Clear, honest, and timely communication about what is and isn't changing, even when full details aren't available yet, tends to reduce both the anxiety and the flight risk of people you actually want to retain through the transition.

Most transfer frameworks give an employee some right to object to transferring, though the consequences of objecting vary by jurisdiction and can affect their entitlement to notice or severance depending on how the objection is handled. This is a genuinely technical area worth a specific legal read for any deal where you expect meaningful employee resistance to the transfer, rather than assuming an objection simply means the employee stays with the seller cleanly.