How to Switch EOR Providers in India: A Migration Checklist

Changing EOR provider is one of those projects that looks like a procurement decision and turns out to be an operations problem. The commercial comparison takes a week. The migration takes a quarter, and almost all of the risk sits in the parts nobody scoped: statutory registrations, a tax year split across two employers, and entitlements that are measured against the employer rather than against the job.

India makes this sharper than most markets. Payroll is tied to registrations that belong to the legal employer, several of them state specific, and your provider is the legal employer. When it changes, most of that plumbing changes with it. Our How to Switch EOR Providers: The 2026 Transition Playbook covers the general sequencing, so this guide stays on what is specific to India.

It is written for the person who has to make the switch work: a People or Operations lead, a founder, or a finance owner with an India team on someone else's payroll. It assumes you have already decided to move, or are close to it.

One framing point before the detail. A switch does not have to be disruptive for employees, and in a well run migration most of them notice only a new payslip format and a new HR contact. The disruption comes from doing the steps in the wrong order.

Why do companies switch EOR providers in India?

In our experience the trigger is rarely price alone. It is usually a service failure that has become a pattern, or a change in what the company needs from India that the incumbent cannot serve.

The reasons we hear most often group into five:

• Payroll accuracy and timing: repeated errors in salary, statutory deductions or filings, which cost internal time to reconcile and damage trust with the team.
• Compliance confidence: an inability to answer specific questions about registrations, filings or state level obligations, or to produce evidence when asked.
• Responsiveness: slow answers on employee questions, which lands on your managers rather than on the provider.
• Depth in India specifically: a global provider running India through a local partner, where every question takes two hops and nobody owns the answer.
• Commercials and scale: pricing that no longer fits the headcount, or a renewal increase that is not matched by service.

Diagnosing which of these you have matters, because the first four are solved by changing provider and the fifth is sometimes solved by renegotiating. If you are unsure, write down the last five things that went wrong and see whether they share a cause.

If the commercial case is your main driver, benchmark it against Employer of Record Pricing in 2026: Real Cost Breakdown before you assume a switch will save money.

For a view of the market you are choosing from, see 10 Best EOR Service Providers for 2026.

What changes on an India switch, and what stays the same?

This is the table we wish every company had before starting. The pattern is that anything tied to the individual tends to carry across, and anything tied to the employer has to be rebuilt.

Two rows deserve emphasis because they are where migrations go wrong. Gratuity is genuinely uncertain and depends on how the change is structured, and the tax row is the one that surprises employees months later.

Note that a switch is not the same as an exit, even though some of the machinery overlaps. Where an employee actually leaves, the process in EOR Employee Offboarding in India: What Employers Must Know applies instead.

What should you check in your existing EOR agreement first?

Before you evaluate anyone new, read the contract you already have. Your exit terms set the calendar, and discovering a ninety day notice requirement after you have signed elsewhere means paying two providers for a quarter.

Work through these clauses specifically:

• Notice period for termination: how much, in what form, and whether it can only be served at particular points such as a renewal date.
• Termination fees or minimum terms: any early exit charge, committed headcount, or unexpired minimum period.
• Data return and deletion: what employee records you are entitled to receive, in what format, and what the provider will keep and for how long.
• Employee transition cooperation: whether the incumbent is obliged to cooperate with a successor, which is worth knowing before relations cool.
• Non solicit and exclusivity: any term that purports to restrict moving the employees, and whether it is enforceable where they sit.
• Outstanding liabilities: who funds accrued leave, gratuity provision and any pending statutory dues at the point of transfer.

Read the clauses rather than the summary you were given at signing, and if the exit terms are unclear, get that clarified in writing before you give notice. Do not serve notice until the incoming provider has a firm go live date.

Accrued leave is the liability most often left unallocated at this stage, and how it is valued depends on the pay structure described in Salary Structure in India: CTC Breakup Guide.

How should you evaluate the incoming India provider?

Selection is a topic in its own right, and How to Choose an Employer of Record: A 2026 Buyer's Guide covers the general criteria. What follows is only what is worth testing differently when the team is in India.

Ask the incoming provider these, and prefer specific answers over reassurance:

• Who is the legal employer: the provider itself through an Indian entity, or a local partner? Ask for the entity name, and understand that a partner model adds a hop to every question.
• Which registrations do you hold: provident fund establishment code, insurance registration, professional tax and establishment registration for the states your team sits in.
• How do you handle a mid year joiner from another employer: the answer should mention collecting previous employer salary details. If it does not, they have not thought about your migration.
• What is your position on continuous service: and will you put in writing what the new contract says about prior service?
• What does the employee actually experience: on contract, payslip, benefits enrolment and support, in the first sixty days.
• Who owns errors during transition: and what happens if the first payroll run is wrong.

The mid year joiner question is the single most useful screen in that list, because it separates providers who run India payroll from providers who resell it.

Do employees have to resign and sign new contracts?

They will normally need a new employment contract, because the legal employer is changing and a contract needs two parties. Whether that is structured as a resignation and rehire, a tripartite transfer, or a novation depends on the arrangement, and it is a question for Indian counsel rather than for a template.

What we would push back on is the assumption that resignation is the default. It is the simplest mechanism to administer and the most expensive for the employee, because a resignation and rehire treats the relationship as ending, which can affect service based entitlements. If a provider proposes it without discussing alternatives, ask why.

Three principles hold whichever route you take:

• No employee should be worse off in cash terms: salary, allowances and benefit value should be replicated, and any difference should be deliberate and explained.
• Prior service should be addressed explicitly in writing: whether or not it can be preserved, silence is the worst outcome because it creates a dispute later.
• Consent should be informed: the employee is being asked to contract with a different company, and they are entitled to understand what changes.

Communicate this yourself rather than delegating it entirely to either provider. The message that works is short: the employing company is changing, your role, pay and team are not, here is what you need to sign and why, and here is who to ask.

Benefit parity is the part employees check first, so confirm it against Employee Benefits in India: Employer Guide 2026 before contracts go out.

A poorly handled change is an attrition event, and the market context for that sits in Attrition Rate in India 2026: Trends & Industry Data.

What happens to provident fund, ESI, and professional tax?

These three behave differently, and the good news is that the one employees worry about most is the one that is genuinely safe.

Provident fund

The employee keeps their universal account number, which is designed to carry across employers. The new employer issues a new member ID under its own establishment code, and the employee files an online transfer claim to move the accumulated balance from the old account into the new one. Nothing is lost and no withdrawal is required.

Two operational points determine whether this goes smoothly. The outgoing employer must file the employee's date of exit in the EPFO system, because the transfer cannot proceed until it does. And the transfer is initiated by the employee rather than by either provider, so somebody needs to tell your team to do it and check that they have.

Employees' State Insurance

Where employees are covered, because their wages fall at or below the coverage ceiling and the establishment is covered, the insurance number follows the individual while contributions are made by whoever is the employer at the time. The incoming provider links the existing number to its own registration. Confirm there is no contribution gap across the cutover month, because a gap can affect benefit eligibility.

Professional tax and establishment registration

Both are state level and belong to the employer, so the incoming provider's registrations apply from go live. This is the part that most often delays a migration: if your team is spread across several states and the incoming provider is not registered in all of them, registration lead time becomes your critical path.

Ask for the state by state position early. The wider set of obligations is described in Payroll Compliance in India: A Guide for Foreign Companies.

Why does a mid year switch create a tax problem for your employees?

Because India's income tax year runs from 1 April to 31 March, and a switch part way through it means two employers have each withheld tax on part of the year's salary. Unless the second employer is told about the first, each computes tax as though its own salary were the employee's only income, and both apply the exemption and deduction thresholds in full.

The result is systematic under withholding. Neither employer has done anything wrong, but the employee discovers a shortfall when they file, sometimes with interest. It is the most common avoidable grievance following an EOR migration, and it is entirely preventable.

The fix is administrative. When an employee joins part way through the year, they declare their previous employer's salary and the tax already deducted to the new employer, which then computes withholding on the aggregate. Under the Income-tax Act, 2025, that declaration is made on Form No. 122, which replaces the earlier Forms 12B and 12BAA.

Two related changes are worth knowing, because they affect the paperwork your employees will receive:

• Salary withholding sits under section 392: of the Income-tax Act, 2025, which replaced the 1961 Act with effect from 1 April 2026.
• The annual TDS certificate is now Form No. 130: which replaces Form 16. An employee who switches mid year should expect one from each employer for that year.

So build three things into your migration plan: tell employees they will receive two certificates for the transition year, make sure the incoming provider collects the previous salary declaration from every employee rather than only from new hires, and ask the outgoing provider to confirm in writing that its filings for the part year are complete.

The mechanics of Indian salary withholding are set out in Payroll Tax in India: Employer Rates, TDS, and Deadlines.

What happens to gratuity and continuous service?

This is the entitlement most exposed by a switch, and it deserves a direct answer: it depends on how the change is structured, and you should get the treatment agreed in writing before cutover rather than discovering it afterwards.

The reason is structural. Gratuity under the Code on Social Security, 2020 vests after five years of continuous service, and continuous service is measured against the employer. On a provider switch the legal employer is exactly what changes. Two providers writing recognition of prior service into their contracts is a contractual arrangement between private parties, and a contract cannot by itself create statutory continuity where the law would not find it.

That does not mean tenure is always lost, and we are not going to assert a single answer for every case. It means the question is real, the answer is jurisdiction and structure specific, and the risk sits with the employee unless someone deals with it.

Practically, do three things. Ask both providers for their position in writing. Get Indian counsel to confirm it for your structure. And where continuity cannot be preserved, decide deliberately whether to compensate the employee for the reset rather than letting them absorb it silently.

We look at this question in more depth, including the provident fund and insurance angles, in Will My India Team Lose Tenure If I Switch EOR Providers?.

How should employee data move between two providers?

Deliberately, and with a record. You are moving payroll files, identity documents, bank details, nominations and employment records between two companies, and India now has a statutory framework covering exactly that.

The practical rules are short:

• Transfer only what the incoming provider needs: to employ, pay and file for the person. A full historical file is rarely necessary and expands everyone's exposure.
• Use a secure channel and record what moved: date, categories, recipient and purpose. This record is what lets you answer a question about it later.
• Agree what the outgoing provider keeps: it will have its own retention obligations as a former employer, so total deletion is not the right ask.
• Get the incoming provider's security position in writing: including access control, encryption and how long it keeps records after employment ends.
• Check who else touches the data: sub processors and payroll software vendors on both sides, since a migration is a good moment to find out.
• Tell your employees: not because a consent form is necessarily required, but because people notice when their payroll data moves and being told first is basic respect.

On the legal framing, India's Digital Personal Data Protection Act, 2023 and its Rules, 2025 are notified, with the substantive obligations phased to take effect eighteen months from the November 2025 notification. Both providers will be handling this data in their own right rather than purely on your instruction, which is why their security positions matter more than a clause you draft.

What the framework requires, and when, is set out in India's DPDP Act for Foreign Employers: A Practical Guide.

What does an India cutover plan look like?

We plan migrations by workstream rather than by calendar, because the workstreams have different lead times and the longest one sets your date. Registration lead time is usually the binding constraint, not notice period.

Workstream 1: Contract and commercials

Confirm exit terms with the incumbent, sign with the incoming provider, and fix a go live date that is the first day of a month. Mid month cutovers split a payroll period across two employers and create avoidable reconciliation work.

Workstream 2: Statutory readiness

Confirm the incoming provider holds provident fund, insurance, professional tax and establishment registrations for every state your team sits in. Where one is missing, get the expected date in writing, because this is the workstream that moves your go live.

Workstream 3: People

Communicate, then paper. Explain the change, issue new contracts, and give people time to read them. Do not compress this into the final week, and do not let the first communication come from a provider your team has never met.

Workstream 4: Payroll build and parallel run

Give the incoming provider a full salary and benefit build, then run at least one parallel calculation against the incumbent's last live run before go live. A parallel run is the only control that reliably catches a build error before it reaches an employee.

The security controls worth testing at the same time are set out in EOR Data Security: A Global Compliance & Protection Guide.

Workstream 5: Data and access

Transfer the employee records the incoming provider needs, on a recorded basis, and set up its systems and support routes for your team.

Workstream 6: Closeout

The outgoing provider issues final settlements where relevant, files exit dates with EPFO, completes its filings for the part year, and confirms all of this in writing. Then your team files provident fund transfer claims. Where a settlement is genuinely due, the components and deadlines are in Full and final settlement in India: 2026 compliance guide.

Sequence these so that statutory readiness starts first and the parallel run happens before, not after, the point of no return.

What is the full migration checklist, and what should you check after go live?

Use this as your working tracker. It is deliberately ordered by dependency rather than by date, so adapt the timings to your notice period and your states.

The four verification rows are the ones teams skip, and they are the cheapest insurance in the whole project. Do them at thirty and ninety days, because a contribution that failed to post is much easier to fix in the same tax year.

What are the most common mistakes on an India EOR migration?

These are the failures we see repeatedly, and each one is a planning gap rather than an unavoidable risk:

• Serving notice before the incoming provider is ready: which leaves you exposed if a registration takes longer than promised.
• Discovering a missing state registration late: the most common cause of a slipped go live date.
• Choosing a mid month go live date: which splits a payroll period and multiplies reconciliation work.
• Skipping the parallel run: and finding the build error in a live payslip instead of a spreadsheet.
• Not collecting previous salary declarations: which under withholds tax and produces a grievance at filing time.
• Letting employees hear it from a provider first: the fastest way to turn an administrative change into an attrition risk.
• Assuming resignation and rehire is the only route: without checking what it costs the employee in service based entitlements.
• Leaving gratuity treatment unwritten: which converts a known question into a later dispute.
• Forgetting the exit date filing: which quietly blocks every provident fund transfer.

If you address only three, address the state registrations, the parallel run and the tax declaration. Together they account for most of the damage we see.

If your problem turns out to be the model rather than the provider, Employer of Record vs Own Entity: Which Is Right for You? is the comparison to run instead.

Where can you verify these rules yourself?

The statutory points above come from primary sources, and these are the ones to read before you rely on any of it:

• EPFO guidance on the universal account number and transfer claims: including the requirement that the employer file the date of exit before a transfer can proceed.
• ESIC coverage and contribution pages: for the wage ceiling, the contribution rates and how coverage is notified by state.
• Code on Social Security, 2020: for gratuity entitlement and the five year continuous service condition in section 53.
• Income Tax Department pages on Form No. 122 and Form No. 130: for the previous employer declaration and the annual salary TDS certificate under the Income-tax Act, 2025.
• Your own state professional tax and establishment departments: because these are state specific and change independently of central law.
• Digital Personal Data Protection Act, 2023 and Rules, 2025: for the data transfer points and the phased commencement dates.

Where a rule is state specific, the central source will not answer your question, and the state department is the only reliable place to look. Build that into your timetable rather than treating it as a detail.

How does Wisemonk handle an India EOR migration?

Wisemonk is an India native Employer of Record that helps global companies hire, pay, and manage employees in India without setting up a local entity. We take on migrations as the incoming legal employer, which means the registrations, filings and payroll build are ours rather than a partner's.

Here is how we run an India migration:

• Migration planning: we map your states, confirm registration readiness, and set a go live date against the binding constraint rather than an optimistic one.
• Contracts and communication: new employment contracts issued with time to read them, and a communication plan that starts with you.
• Parallel payroll run: we reconcile against your outgoing provider's last live run before go live, not after.
• Statutory continuity: provident fund transfer support, insurance linkage, and a written position on prior service before you commit.
• Transition year tax: we collect previous employer salary declarations from every transferring employee so withholding is computed on the full year.
• Post migration checks: contribution posting, transfer completion and payslip reconciliation at thirty and ninety days.

We work with 300+ global clients, support over 2,000 employees, and process more than $20M in annual payroll, with a 4.8/5 rating on G2. EOR pricing starts from $99 per employee per month.

If you want the provider specific version of this process, How to Switch from Your Current Existing EOR to Wisemonk's EOR in 2026 sets out the steps on our side.

Nothing here is legal advice, and the right transfer mechanism for your team depends on your structure and your contracts. Take Indian counsel on the employment mechanics before you commit to a route.