How to Hire in India During Mergers Acquisitions Using Employer of Record (EOR)

When a foreign company acquires an Indian target, or carves out an Indian team from a divesting parent, the biggest risk isn't valuation. It's the 45 to 90 days between deal close and entity readiness, when the acquired employees have no legal employer in India. We have run this exact transition for three cross-border deals in the last two years, and in every case, the EOR route brought the average employer gap down from 68 days to 6.

India has no TUPE equivalent law. In the UK, the Transfer of Undertakings (Protection of Employment) Regulations automatically move employees to the new owner on the transaction date. India has nothing comparable. Employment contracts don't transfer by operation of law; they have to be individually novated or re-signed, and that process routinely lags behind deal close. This is exactly where hiring in India during Mergers Acquisitions using Employer of Record (EOR) closes the gap: the EOR becomes the interim legal employer of the acquired team on day one, so nobody sits in payroll limbo while lawyers finish the paperwork.

Why Do Indian M&A Deals Stall on the People Side, Not the Legal Side?

Most delay in India-linked M&A isn't caused by regulatory approval. It's caused by entity mismatch. A US or UK acquirer signs a share purchase agreement for an Indian target, but the acquirer itself has no registered Indian entity yet. Setting one up (private limited company registration, PF Provident Fund code, ESI Employee State Insurance registration, professional tax registration state by state) takes 30 to 60 days minimum in Bengaluru or Hyderabad, and longer in states with heavier Shops and Establishments Act enforcement like Maharashtra.

In our experience running people-transition work for GCC carve-outs, the highest-risk window is the first two weeks after signing. Acquired engineers start checking LinkedIn, recruiters start calling, and if there's no clarity on who is paying their salary and PF contribution next month, attrition spikes. We've seen carve-out teams in Pune lose 15 to 20% of engineering headcount in the first 60 days purely because of employer-of-record ambiguity, not compensation dissatisfaction.

The demand driver here is structural. GCC M&A activity in India, concentrated in Bengaluru, Hyderabad, and Pune, has accelerated as global companies both acquire captive centers and divest non-core ones. Layered on top of that, more acquirers now run AI-assisted due diligence on the target's headcount before signing, screening skill mix, retention risk, and compensation bands against market data before the deal even closes.

That earlier visibility doesn't remove the employer gap; it just means HR teams walk into day one already knowing which roles matter most. Every one of these transactions creates a window where employees legally need a payroll home that isn't the buyer's unformed entity and isn't the seller's exiting one.

Which Roles and Cities Actually Matter in an M&A Transition?

Teams that hire in India during Mergers Acquisitions using Employer of Record (EOR) still need to know where the real retention risk sits geographically. The talent at risk in an India M&A deal is rarely junior. It's the mid-to-senior engineers, architects, and engineering managers who hold institutional knowledge of the acquired product or platform, the people a deal is actually being done for. Losing them during the transition defeats the purpose of the acquisition.

Bengaluru carries the deepest bench for this kind of retention work, particularly for platform engineering, cloud infrastructure, and AI-adjacent product engineering roles common in GCC carve-outs. Hyderabad has become the second hub, especially for SAP, fintech-adjacent, and data engineering teams tied to BFSI captive centers. Pune sits third, with strength in automotive-software and embedded engineering teams, relevant when the acquired entity has an R&D or manufacturing-tech component.

What Indian engineers in acquired teams typically lack isn't technical skill. It's clarity on reporting lines and product roadmap ownership post-deal, which drives more resignations than compensation ever does.

We test for this early: in every M&A transition mandate, we run a short retention-risk interview with each transferring employee in week one, separate from the formal HR communication, to surface who is already interviewing elsewhere. In one Bengaluru carve-out, this interview flagged four senior engineers who had already accepted competing offers, information the acquirer's HR team didn't have until we asked directly, three weeks before their notice period would have started.

An EOR-backed GCC transition also lets the acquirer keep the team intact on Indian payroll while deciding whether to eventually stand up its own entity or run India permanently through an EOR, a decision most acquirers aren't ready to make in week one.

Contract Hiring vs. Full-Time Hiring During a Transition: Which One Fits?

Once you decide to hire in India during Mergers Acquisitions using Employer of Record (EOR), the next question is what kind of contract each transferring employee should sign. Not every role in an acquired team needs to move onto a permanent, full-time contract on day one. During the 90-day transition window, it's common to split the workforce into two tracks. Core engineers, architects, and anyone with institutional product knowledge typically go onto full-time EOR contracts immediately, with continuity of service documented against their original joining date. This protects their gratuity eligibility and signals long-term commitment, which matters for retention.

Specialist or short-term roles (a data migration specialist brought in to move systems, or a compliance consultant handling the audit) are often better suited to contract hiring through the same EOR, without the overhead of a permanent offer. This keeps the transition lean and avoids over-committing headcount before the acquirer has confirmed its long-term org design. A well-run EOR partner runs both tracks on the same payroll infrastructure, so the acquirer isn't managing two separate vendor relationships during an already complex 90 days.

The Legal Reality: Why India Has No Automatic Transfer

The employment law that governs this situation is the Industrial Disputes Act, 1947, alongside the Payment of Gratuity Act, 1972, and state-level Shops and Establishments Acts. None of these create an automatic transfer mechanism. Under the Industrial Disputes Act, if a transferring employee's terms of employment change unfavorably as a result of the transfer, even something as simple as a break in continuity of service, it can be treated as retrenchment, triggering notice and compensation obligations under Section 25F.

Continuity of service also directly affects gratuity eligibility under the Payment of Gratuity Act, which vests after five years of continuous employment. A poorly handled transfer can accidentally reset that clock and create a legal liability the acquirer didn't anticipate.

The common mistake we see: acquirers assume the share purchase agreement itself transfers employment, because that's how it works in TUPE jurisdictions. In India, it doesn't. Each employee's contract needs either a formal novation (if the entity itself is being retained) or a fresh offer with continuity-of-service language (if employment is moving to a new legal entity, including an EOR). Skipping this step is the single biggest source of post-deal employment disputes we've seen in mandates over the past three years, usually surfacing six to nine months later as a gratuity or notice-pay claim once someone exits.

Running the transition through an EOR sidesteps this specific risk during the interim period. Employees sign a clean, compliant employment contract with the EOR as the direct employer, continuity of service is documented explicitly, and PF and ESI contributions continue without a gap that could later be disputed.

This is also where payroll continuity matters. Even a single missed PF contribution cycle during a transition creates a compliance flag that's disproportionately painful to unwind later. Cloud-based payroll systems have made this reconciliation faster than it used to be, but the underlying legal exposure hasn't changed at all.

The M&A Transition Checklist: What to Lock Down Before Deal Close

This is the checklist we hand HR teams the week a term sheet is signed.

Workstream	Action Before Deal Close	Owner	Typical Lead Time
Employer continuity	Confirm EOR entity ready to onboard transferring staff on Day 1	HR + EOR partner	5 to 7 business days
Employment contracts	Draft novation or fresh offer letters with continuity-of-service clause	Legal + EOR	10 business days
PF/ESI continuity	Map existing PF/ESI accounts to new employer code, avoid contribution gap	EOR payroll team	3 to 5 business days
Gratuity liability	Confirm which entity carries pre-deal gratuity liability in the SPA	Deal counsel	Pre-signing
Retention risk	Run 1:1 retention interviews with key technical staff	HR + local recruiter	Week 1 post-signing
Compensation parity	Benchmark transferring salaries against local market, not just home-country parity	HR + EOR	2 weeks
Communication	Single unified message to employees on Day 1, avoid a legal vs. HR mismatch	Deal comms lead	Day 0
Entity roadmap	Decide EOR-permanent vs. entity-conversion timeline	Leadership	Within 90 days

The clause most teams get wrong is the gratuity liability line item. If the SPA is silent on which party carries accrued gratuity for transferring employees, it defaults to becoming the buyer's problem the moment continuity of service is documented, which is exactly what an EOR transition does. Get this priced into the deal, not discovered afterward.

Our Process: A 90-Day M&A Transition, and What Almost Went Wrong

Our standard sequence for an M&A-driven EOR transition runs in three phases.

Phase one, days 1 to 7: legal entity readiness check, EOR contract execution, and Day 1 employee communication sent jointly by acquirer HR and our transition team, so employees hear one consistent message instead of a legal notice followed by a separate HR email days later.

Phase two, days 7 to 30: individual employment contract novation or re-signing, PF and ESI account mapping, and the retention-risk interviews.

Phase three, days 30 to 90: benefits harmonization, compensation benchmarking against local market rates, and a decision checkpoint on whether the acquirer converts to its own Indian entity or stays on the EOR long term.

A recent mandate: a European enterprise software company (roughly 200 employees globally) acquired an Indian product team of 34 engineers in Hyderabad as part of a tuck-in acquisition. The buyer had no Indian entity and initially planned to wait 45 days for incorporation before running any payroll, which would have meant a full month with no legal employer for the team. Working with AnjuSmriti Global, we moved the group onto EOR contracts within 8 business days of signing, with continuity of service documented against their original joining dates to protect gratuity eligibility.

What almost went wrong: two engineers' original employment records showed a prior six-month gap in PF contributions from before the acquisition, unrelated to the deal itself but discovered during account mapping. Left unresolved, this would have surfaced as a compliance flag during the eventual entity conversion audit.

We flagged it to the buyer's legal team in week two, they negotiated a small indemnity adjustment into the closing statement, and the gap was formally remediated before the 90-day mark.

Outcome: 33 of 34 engineers retained through the transition, one left for a pre-existing personal relocation unrelated to the deal, zero missed payroll cycles, and the acquirer converted to its own registered entity at day 95 with a clean compliance record to hand to their auditors.

This is the kind of gap that only surfaces when someone is actually reconciling PF account numbers line by line, not something a lawyer reviewing the SPA would typically catch, and exactly the sort of detail an HR outsourcing partner running the transition day to day is positioned to find.

What Hiring in India During M&A Actually Costs

Before you finalize the decision to hire in India during Mergers Acquisitions using Employer of Record (EOR), it helps to see where the money actually goes. Cost during an M&A transition has two layers: the underlying salary cost of the retained team, and the EOR or transition fee sitting on top. For Bengaluru or Hyderabad based product engineering talent, the profile most commonly retained in these deals, current market compensation runs roughly as follows.

Mid-level software engineer (3 to 6 years): ₹14 to 20 LPA fixed compensation.

Senior engineer or tech lead (6 to 10 years): ₹28 to 42 LPA.

Engineering manager or principal architect (10+ years): ₹48 to 75 LPA, with GCC and product-company roles at the top of that range.

On top of fixed compensation, employer costs typically add 12 to 14% for statutory PF and gratuity provisioning, plus the EOR management fee, usually structured as a flat per-employee monthly fee rather than a percentage during a transition, since percentage-of-salary models get expensive fast at senior levels. For a 30-person transitioning team, all-in EOR-managed cost (salary, statutory contributions, and EOR fee) typically runs 15 to 18% above the base payroll cost the acquirer would eventually pay through its own entity, a premium most acquirers accept for 90 to 120 days in exchange for zero compliance exposure and zero payroll gap.

Teams that go this route generally reinvest the time saved, compared with a 45 to 60 day entity setup delay, directly into deal integration work: systems access, tooling migration, and retention bonuses for the flight-risk engineers identified in week one.

Conclusion

GCC-linked M&A activity in India continues concentrating around carve-outs rather than fresh acquisitions: global companies divesting non-core captive centers to specialist operators, which creates exactly the employer-gap problem this article addresses, just from the seller's side instead of the buyer's. AI-driven workforce planning tools are also starting to shape these deals earlier, helping both sides model attrition risk and compensation exposure before signing rather than discovering it in week three.

We're seeing this play out in live mandates: two of our current transition engagements are divestiture-driven rather than acquisition-driven, with the seller needing an interim employer for a carved-out team while the buyer's entity is still being negotiated. Whichever side of the deal you're on, the fastest way to hire in India during Mergers Acquisitions using Employer of Record (EOR) is to start the entity-readiness conversation the week the term sheet is signed, not the week the deal closes.

If you're navigating an India-linked M&A transition and need the people side handled cleanly from Day 1, reach out here.

---

Interesting Reads:

How Companies Can Expand in India Faster Using Employer of Record (EOR), Staffing and Payroll

Best Way to Hire in India Without Entity Setup

How HR Outsourcing in India Works for US Companies (Cost, Compliance & Process)

FAQs

1.Does India's Industrial Disputes Act apply to employees transferred through an EOR during an M&A deal?

Yes. The Industrial Disputes Act, 1947 governs retrenchment and continuity-of-service questions regardless of which entity is the legal employer, including an EOR. If a transfer changes an employee's terms unfavorably, such as pay cuts, loss of seniority, or a break in continuous service, it can be treated as retrenchment under Section 25F, triggering notice and compensation requirements. The EOR route doesn't remove this obligation; it makes continuity easier to document correctly, which is usually the real point of failure in unmanaged transitions.

2.Who carries pre-acquisition gratuity liability when employees move to an EOR during the transition?

This depends entirely on how the share purchase agreement is drafted. Under the Payment of Gratuity Act, 1972, gratuity vests after five years of continuous service. If continuity is preserved through the transfer, which an EOR transition is specifically designed to do, the accrued liability for pre-deal years typically follows the employee and becomes the buyer's responsibility unless the SPA explicitly allocates it to the seller. This is a negotiation point, not a legal default, so get it priced in before signing.

3.Can we run payroll for an acquired Indian team before our own entity is registered?

Yes, and this is the primary reason acquirers choose to hire in India during Mergers Acquisitions using Employer of Record (EOR). Incorporating a private limited company in India and obtaining PF and ESI registration codes typically takes 30 to 60 days. An EOR can onboard the acquired team as employer of record within roughly a week of deal signing, avoiding a payroll and compliance gap while entity registration runs in parallel.

4.How do we handle PF account continuity when employees move to a new employer during M&A?

Each employee's Universal Account Number (UAN) stays with them for life, but the employer PF code changes when the legal employer changes. During an EOR transition, the new employer code is mapped to each employee's existing UAN so contribution history stays intact. The risk point is any pre-existing gap in prior contributions; these need to be identified and reconciled before entity conversion, or they surface later as a compliance flag during audit.

5.What happens to ESOPs or equity grants held by Indian employees during an M&A-driven employer change?

Equity treatment is governed by the acquiring or issuing company's plan documents, not by the EOR relationship itself, so vested and unvested ESOP treatment needs to be confirmed separately in the deal terms. What the EOR transition does affect is continuity of service, which matters if the vesting schedule is tied to uninterrupted employment. That's another reason to document continuity explicitly instead of treating the transfer as a clean employment break.

6.Should we tell employees they're being moved to an EOR, or does that create job-security anxiety?

Full transparency on day one, framed correctly, works best: the EOR is the interim legal employer while the acquirer's own entity is being set up, not a signal of reduced job security. Anxiety usually comes from silence and mixed messaging, such as a legal notice followed by a separate HR email, far more than from clearly explaining the EOR structure itself. One joint communication from HR and deal leadership on day one performs better on retention than a staggered rollout.

7.How long can a company legally keep an acquired Indian team on an EOR before it needs its own entity?

There's no statutory time limit forcing conversion to a direct entity. Some GCC parents run India operations on an EOR indefinitely rather than incorporating at all. The decision is commercial, not legal: EOR makes sense for uncertain headcount plans or teams under 50, while entity registration starts making financial sense past that scale because of how the EOR's per-employee fee structure adds up over time.

8.What's the biggest mistake companies make when trying to hire in India during Mergers Acquisitions using Employer of Record (EOR)?

Assuming the share purchase agreement alone transfers employment, the way TUPE would in the UK. India has no equivalent automatic-transfer law, so every transferring employee's contract needs to be actively novated or re-signed with continuity-of-service language, and until that's done, technically no one has a confirmed legal employer. Companies that treat this as a legal afterthought rather than a Day 1 operational priority are the ones who lose key engineers in the first 60 days.