Subsidiary-to-EOR Migration: What Actually Breaks When You Switch

When you migrate employees from your own legal subsidiary to an Employer of Record, the four things most likely to break are payroll continuity (gaps or duplicate pay runs), benefits enrolment (old plans terminate before new ones activate), employment contract continuity (a new contract can look like termination + rehire under local law, triggering severance obligations), and IP/invention assignment (work product needs to be re-assigned to the new legal employer). None of these are guaranteed to break — but all four need an explicit handoff plan, because no authority manages the transition for you.

This is the practical list of failure points, drawn from how these migrations actually go wrong, plus what to check before you set a cutover date.

---

1. Why Companies Migrate from a Subsidiary to an EOR

Before the “what breaks” list, it helps to be clear on why teams make this move — because the reason usually determines which risks matter most:

• Winding down a market but keeping a handful of employees employed there

• Cost of maintaining the entity (filings, local director, audit, dormant-company compliance) no longer justifies a shrinking headcount

• Reducing compliance exposure by handing local employment law risk to a specialist instead of carrying it in-house

• M&A or restructuring where the legal entity is being sold, merged, or dissolved but the people aren’t

Whatever the driver, the migration itself is a legal employer change — the people, role, and pay may stay the same, but who is legally responsible for them changes. That’s where the breakage happens.

---

2. Payroll Continuity: The Most Visible Failure Point

This is the one employees notice immediately if it goes wrong.

What breaks: A gap between the subsidiary’s final pay run and the EOR’s first pay run — or, less commonly, a duplicate payment — because the two payroll systems aren’t run by the same provider and don’t share a payroll calendar by default.

What to check:

• Align the EOR’s first pay cycle to start exactly where the subsidiary’s last one ends — no overlap, no gap

• Confirm year-to-date payroll figures (tax withheld, statutory contributions paid, leave accrued) are transferred to the EOR so tax filings and payslips stay accurate for the full year, not reset to zero mid-year

• Decide who runs the final subsidiary payroll and who runs the first EOR payroll, and get both dates in writing before you tell employees anything

If you’re consolidating from multiple providers or entities, this is also the moment to plan a clean cutover rather than running parallel systems for months — AgileHRO’s global payroll service migrates payroll in under 4 weeks with zero missed pay runs as a stated guarantee.

---

3. Benefits Enrolment: The Coverage Gap Nobody Notices Until Someone Needs It

What breaks: The subsidiary’s group health insurance, life insurance, or pension/retirement plan terminates on the entity’s last active day — but the EOR’s equivalent benefits don’t always activate on the same day, especially if enrolment requires a waiting period or open-enrolment window.

What to check:

• Get the exact termination date of every subsidiary benefit in writing from the insurer/provider, not just HR’s assumption

• Confirm the EOR’s benefits start date in writing, and push for same-day or next-day activation, not “within 30 days”

• For any benefit with a waiting period (some life or disability cover), ask whether the EOR can waive it for migrating employees — this is a common, reasonable ask and most EORs will accommodate it

• Flag the gap explicitly to employees if one is unavoidable — silence here is what turns a logistics issue into a trust issue

---

4. Employment Contract Continuity: The Legal Risk Most Teams Miss

This is the breakage with real financial and legal consequences, not just operational friction.

What breaks: In many jurisdictions, ending employment with the subsidiary and starting employment with the EOR is, legally, a termination followed by a new hire — even if the employee’s day-to-day work doesn’t change at all. That can trigger:

• Statutory severance or notice pay obligations on the subsidiary side

• Loss of accrued tenure-based benefits (seniority pay, long-service leave, certain termination protections) unless explicitly carried over

• A break in continuous service that affects probation periods, pension vesting, or local labour law protections tied to length of service

What to check:

• Get local legal advice in each country on whether the transfer can be structured as a “transfer of employment” (continuity preserved) rather than a termination and rehire — some jurisdictions have specific mechanisms for this (similar in spirit to TUPE-style transfers in the EU/UK), others don’t

• If continuity can’t be preserved, budget for severance/notice pay as a real cost of the migration, not an afterthought

• Get the new EOR contract to explicitly recognise prior tenure where the law and the EOR’s policies allow it, so seniority-based entitlements aren’t reset to zero

This is the single biggest reason to run a subsidiary-to-EOR migration with a partner who has in-country legal specialists reviewing the transfer per jurisdiction, rather than applying one global template. AgileHRO’s Employer of Record service explicitly states migrations are handled with zero missed pay runs and locally-vetted contracts — worth confirming the same rigour applies to the continuity question before signing.

---

5. IP and Invention Assignment: The One Everyone Forgets

What breaks: Most employment contracts include an IP assignment clause that assigns work product to “the Company” as defined in that specific contract. When the legal employer changes from your subsidiary to an EOR, the old IP assignment clause technically only covers work created under the old entity — not work created going forward under the new one, and in some cases not even retroactively.

What to check:

• Confirm the new EOR contract includes an IP assignment clause that flows IP rights through to your company (the client), not just to the EOR as the nominal legal employer — this is standard in proper EOR agreements but worth verifying explicitly, not assuming

• For any IP created in the gap between contracts (however short), get written confirmation of which contract governs it

• If the employee’s role is IP-sensitive (engineering, product, design), this is worth a specific line item in the migration checklist, not folded into general contract review

---

6. Migration Checklist: Subsidiary to EOR

Area	What to confirm before cutover
Payroll	Last subsidiary pay date and first EOR pay date are back-to-back, with no gap or overlap; YTD figures transferred
Benefits	Exact termination and activation dates for every benefit, in writing, with waiting periods waived where possible
Employment continuity	Local legal review of whether transfer can preserve continuity; severance budgeted if not
IP assignment	New contract’s IP clause confirmed to flow rights to your company, not just the EOR
Tax	Final subsidiary tax filings and withholding handled; EOR registered and withholding correctly from day one
Communication	Employees told what changes (legal employer) and what doesn’t (manager, role, pay) — ideally before, not during, cutover

---

FAQ

Does switching from a subsidiary to an EOR count as a termination under local law? It depends on the jurisdiction. In many countries it’s legally a termination and new hire unless structured specifically as a transfer of employment, which can trigger severance obligations. Get local legal advice per country before assuming continuity.

Will employees lose their tenure or seniority when migrating to an EOR? Only if the new contract doesn’t explicitly recognise prior service. This is negotiable with most EOR providers and should be confirmed in writing before migration.

How long does a subsidiary-to-EOR payroll migration take? A clean migration can be done with zero missed pay runs in under a month when planned with an aligned cutover date — the risk isn’t the timeline, it’s an unplanned gap between the old and new payroll calendars.

Who owns IP created during the transition period? Whichever contract is legally in force on the date the work is created. This is why confirming exact contract start/end dates — not just target dates — matters for IP-sensitive roles.

---

Planning a subsidiary wind-down or EOR migration? Talk to an AgileHRO global employment specialist about a country-by-country continuity review before you set a cutover date.