Payroll Migration Services When Changing Provider in India

Changing payroll provider in India is a change of operator, not a change of employer. The TAN, the PF establishment code, the ESIC code and the state professional tax enrolments stay with your company, but the people who file against them change. Payroll migration when changing provider therefore succeeds or fails on three things: clean year-to-date data, unbroken statutory filings and a cutover date that does not split a TDS quarter. This guide sets out the sequence, the evidence to collect at each step and the 2026 rule changes your new system has to handle.

How do you migrate payroll when changing provider in India?

Move in six steps: clean the employee master, load year-to-date salary and TDS, move statutory logins into the company’s name, run at least one parallel cycle with zero unexplained variance, cut over at the start of a quarter where possible, and keep the outgoing provider on filings until the last return for its period is acknowledged. The company remains the employer and deductor throughout.

How is payroll migration when changing provider different from a first-time payroll set-up?

Payroll migration moves payroll from one provider or system to another, whereas outsourcing is the model you run. A provider change moves operations, not legal identity. Every registration, every employee identifier and every tax history already exists and must carry over intact. A first-time set-up creates those records; a migration has to prove the new system reproduces them to the rupee. That is why a provider change fails on continuity, not on configuration.

Table 1: What stays with the company and what moves at migration

Item	Held by	Changes at migration?	Evidence to collect
TAN and TRACES login	Company as deductor	No. Access and users change	Current user list, registered email and mobile
PF establishment code and EPFO Unified Portal login	Company as employer	No. Access, authorised signatory and DSC or e-Sign may change	Last 12 ECR acknowledgements, DSC registration status
ESIC employer code and portal login	Company as employer	No. Access changes	Last 12 challans, insured person list
Professional tax enrolment and returns	Company, state by state	No. Access changes	Enrolment certificates, last return acknowledgements
UAN and ESIC insured person numbers	Employee	No	Master list with numbers matched to PAN and Aadhaar
Salary structure and CTC	Company and employee contract	Should not change in the migration month	Signed structures, latest revision letters

What changes if the outgoing provider is an Employer of Record?

If the outgoing provider is an Employer of Record, the legal employer changes, so employees move to a new contract and some registrations and records change with it. The pattern is that identifiers tied to the individual carry across, and anything tied to the employer is rebuilt.

Table 2: What carries across when the legal employer changes

Item	Position on an Employer of Record switch
PAN and PF universal account number	Carry across; they belong to the employee
PF balance	Moves by an online transfer claim; the outgoing employer must first record the date of exit on the EPFO portal
ESIC insured person number	Carries across; contributions follow the new employer
Employment contract	New contract with the new employer
Professional tax and Shops and Establishments registration	The new employer’s registrations apply, state by state
Gratuity and continuity of service	Depends on how the change is structured; get both providers’ positions in writing before cutover
Tax for the year	Two employers in one tax year; the employee declares previous employer salary and tax deducted on Form 122 (section 392(4)(a), Income-tax Act, 2025; Rule 204, Income-tax Rules, 2026), and each employer issues its own Form 130

The rest of this guide covers the more common case, where the provider acts for your company as employer. For the choice between running payroll yourself and outsourcing it, see our comparison of payroll outsourcing vs in house payroll in India.

When is changing payroll provider worth the disruption?

Treat payroll migration when changing provider as a response to evidence: change provider when missed filings, rework or blind spots make the current arrangement costly, not because a rival quoted less. A migration carries one or two cycles of double work, so the trigger should be a pattern, not a single bad month.

Table 3: Patterns that justify a move, and what to check

Pattern	What to check in the current arrangement
A filing missed or corrected more than once in a year	Acknowledgements for every ECR, ESI challan, TDS deposit and Form 138 in the last four quarters
Scope stops at PF and ESI	Whether professional tax, Labour Welfare Fund and Shops and Establishments registrations, TDS reconciliation and Form 130 support are in writing
System not updated for 2026 rules	Wage definition, Forms 138 and 130, the ₹25,000 PF ceiling and the split-month September workings
Logins, data or signatory held in the vendor’s name	Registered email and mobile on each portal, and the DSC or e-Sign holder
Notices answered by you, not the provider	Open EPFO, ESIC or income tax notices, and who prepared each reply
No written service levels or liability terms	Response times, filing deadlines and responsibility for processing errors in the contract

Before you sign with the incoming provider, ask for these in writing:

• Its migration plan for your cutover quarter, and the person it proposes as filer of record for each return.
• How it will show zero variance in the parallel run.
• Which states it can file in for professional tax, Labour Welfare Fund and Shops and Establishments, and how it applies state minimum wage revisions from their effective dates.
• How it handles employees who joined from another employer during the year, which should involve collecting Form 122.
• Who bears the cost of errors during the transition.
• Its data security certification, access controls and breach notification process.

For the wider list of vendor questions, see our guide to payroll outsourcing for startups in India.

What data must move to the new payroll provider?

For payroll migration when changing provider, the new provider needs the employee master, the salary structure for each employee, year-to-date earnings and deductions, the tax computation base, and statutory identifiers. The tax computation base is the part most often missed. Salary TDS under section 392 of the Income-tax Act, 2025 is projected over the full year, so the projection is only right if earlier months, perquisites and declarations are loaded.

Most migrations carry six data sets. The table below shows what each is needed for and the defect Treelife sees most often.

Table 4: Data sets to load and the defects that break them

Data set	Needed for	Most common defect
Employee master (PAN, Aadhaar, UAN, ESIC number, bank account, state of work)	Every statutory file	PAN or UAN mismatches that reject the first ECR or Form 138 line
Salary structure by employee	Gross, PF base, ESI eligibility, professional tax slab	Old structure loaded after a revision, so the PF wage base is wrong
Year-to-date earnings, deductions and net pay by month	Tax projection, Form 130 totals, bonus and gratuity accruals	Only net pay loaded, not component-wise earnings
Tax computation base (tax deducted to date, perquisites, previous employer income on Form 122, declared regime, Form 124 declarations)	Correct monthly TDS for the rest of the year	Declarations reset to blank, so TDS jumps in the first live month
Loans, advances, reimbursements and arrears in progress	Recoveries and payouts	Recovery schedules lost, so a loan stops being deducted
Leave balances, pending full and final settlements, notice-period cases	Exit pay and leave encashment	Exits during the migration month processed in the old system and missed in the new

Payroll also depends on feeds and outputs outside the year-to-date file. Confirm before the first parallel cycle how attendance, leave, reimbursements and variable pay reach the new provider, that the bank payment file is in a format your bank accepts, and how payroll journals map to your ledgers.

Before the file goes across, run five checks on it:

• Match every PAN to the name on the Income Tax portal and every UAN to the EPFO member record.
• Reconcile year-to-date gross and TDS per employee to the last filed Form 138 statement and to the books.
• Confirm each employee’s tax regime choice and attach the latest Form 124 declaration (the declaration that replaced Form 12BB under the 2026 Rules).
• Flag ESOP perquisites already taxed or deferred, because the TDS projection depends on them.
• Freeze structure revisions and appraisal changes until the first live cycle is closed.

For the controls that keep TDS and payroll registers aligned after the move, see our note on virtual CFO payroll and TDS compliance.

Which cutover date works best, and how long does a payroll migration take?

For payroll migration when changing provider, the cleanest cutover is the first wage month of a quarter: April, July, October or January. Go live on the first day of a wage month, because a mid-month cutover splits one payroll period across two providers. The quarterly salary TDS statement and the quarter’s TDS deposits then sit wholly with one provider. A mid-quarter cutover is possible but needs one named party to file the full quarter’s Form 138, which needs the other provider’s data.

Form 138 is the quarterly statement of salary TDS under section 397(3)(b) of the Income-tax Act, 2025, read with Rule 219 of the Income-tax Rules, 2026. It is due on 31/07, 31/10, 31/01 and 31/05 (Income Tax Department guidance on Form 138). Form 130, the annual certificate that replaced Form 16, is generated from the processed statements and is due by 15/06 (Income Tax Department, Form 130 FAQs). A certificate cannot be generated for a quarter whose statement was not filed, so a gap in Form 138 ownership shows up months later as a gap in every employee’s certificate.

Table 5: Cutover options and their effect on filings

Cutover point	Effect on Form 138	Parallel run	Verdict
First wage month of a quarter (April, July, October, January)	One provider per quarter	One to two cycles in the preceding quarter	Best
Second or third month of a quarter	Statement must cover months from both providers	Parallel run inside the same quarter	Workable with a written filer agreement
March or April boundary	Year-end Form 138 for Q4 and Form 130 for the year fall on one side or the other	Close the year in the old system	Avoid unless the old provider closes the year
Month with an appraisal, bonus or structure revision	Variance is hard to explain	Parallel run produces noise	Avoid

As of 13/11/2026, the next clean cutover is the January 2027 wage month, which starts the last quarter of FY 2026-27. A cutover for the December wage month is possible but is mid-quarter and needs a named Form 138 filer for October to December. The length of a migration is set by dependencies, not by a fixed number of weeks. Each parallel cycle is one full wage month, so two parallel cycles cannot finish sooner than two wage months after data and access are ready. The sequence:

• Before notice: audit the current scope, collect the logins and the last 12 months of filing evidence, and read the notice and exit clauses.
• Data and access: cleanse the employee master, build the year-to-date file, move the logins and the authorised signatory into the company’s name.
• Parallel cycles: one or two wage months, each reconciled to the old system.
• Sign-off against written acceptance criteria, set out in the parallel run section below.
• First live cycle and first statutory filings, with the outgoing provider kept on filings until its last return is acknowledged.

Cost has three lines you can ask each provider to quote separately: a one-time migration or onboarding fee, the double processing cost of the parallel cycle, and any exit or data-export fee in the outgoing contract. Provider pricing varies by headcount and states, so ask for all three in writing before you give notice.

What does the full payroll migration checklist look like?

Use the checklist below as the working tracker. It is ordered by dependency, not by date, so adapt the timing to your notice period, your states and the quarter you are cutting over in.

Table 6: Payroll migration checklist, ordered by dependency

Phase	Action	Owner
Assess	Read the outgoing contract: notice, fees, data return, cooperation, non-solicit	Company
Assess	Audit filings, registrations and open notices for the periods the outgoing provider handled	Company and incoming provider
Select	Get the filer of record, state coverage and security terms in writing	Company
Plan	Fix cutover on the first day of a wage month, preferably the start of a quarter	Company
Access	Move portal logins, contact details and authorised signatory into the company’s name	Company
Data	Build and validate the year-to-date file, including the tax computation base	Both providers
Test	Run parallel cycle one and reconcile on the seven items	Both providers
Test	Run a second cycle if states, ESI-borderline employees or a recent structure change justify it	Both providers
Sign-off	Confirm the written acceptance criteria are met	Company
Communicate	Tell employees what changes and where past payslips will sit	Company
Cutover	Run the first live cycle, statutory files and payments	Incoming provider
Close	File the last returns, return the data pack and erase copies	Outgoing provider
Verify	Tie the first quarter’s Form 138 to the registers and TDS challans	Company and incoming provider
Verify	Check the annual tax statement and Form 130 data once the quarter closes	Company

The exit and return-pack terms belong in the contract, and the payroll outsourcing scope of services sets out what each should contain. The two verification rows are the ones teams skip, and a contribution that failed to post or a quarter whose Form 138 does not match the registers is cheaper to fix early than after Form 130 is issued.

How do you keep PF, ESI, professional tax and TDS filings unbroken during the switch?

In a payroll migration when changing provider, name one filer for every return and every wage month before cutover, move the portal logins into the company’s name, and keep the outgoing provider on filings until its last acknowledged return. Every statutory identity belongs to the employer, so the filing sequence can continue only if the new provider has working access on the first filing date.

Who holds the statutory logins today?

Check this in week one. On the EPFO Unified Portal, key actions such as KYC approval and transfer claim attestation need the authorised signatory’s registered DSC or Aadhaar-based e-Sign, and the registration must be redone when the signatory changes (EPFO e-Sign guidance). The EPF Scheme, 2026 notified on 29/06/2026 (G.S.R. 525(E)) now defines the authorised signatory in the Scheme itself. If the outgoing provider registered the logins under its own email, mobile number or employee DSC, one-time passwords go to the provider, not to you. Move the registered contact details to a company-owned email and a mobile number held by a named company officer, and add the new provider as a user, before notice expires.

Who files the quarter that straddles the switch?

One party must file the whole quarter’s Form 138 for the TAN, and any later change goes as a correction to that original statement. If cutover falls mid-quarter, agree in writing which provider files, what data the other provider hands over, and by what date. If the statement is filed from partial data, TRACES will generate certificates from it, and the gap reaches your employees.

What does the wage month rule mean for ECR and ESI?

Each return follows the wage month, not the date you signed the contract. If a wage month is processed by the outgoing provider, that provider’s file is the file for that month’s ECR and ESI challan. Do not split a wage month between two providers. The PF ECR is due within fifteen days of the close of the wage month and the ESI challan by the 15th of the following month, as set out in Treelife’s guides to PF ECR filing and ESI challan filing.

What should you audit in the outgoing provider’s work before you leave?

The switch is the cheapest time to find gaps, because they belong to the company as employer, not to the provider. Check five things for the periods the outgoing provider handled: the PF wage base against the Labour Codes wage definition, ESI coverage against the wage ceilings, professional tax, Labour Welfare Fund and Shops and Establishments registrations in every state where you have staff (each is a state-level regime), state minimum wage revisions applied from their effective dates, the status of TDS deposits and statements on TRACES, and any open notice. Fix anything found in the company’s name, with the new provider’s help, rather than inherit it unseen. Two regularisation windows are open at the time of writing: the ESIC New Amnesty Scheme, 2025 for specified pending cases, extended to 31/12/2026, and the EPFO VISHWAS, 2026 and AMNESTY, 2026 provisions, open to 28/12/2026 and extendable by six months. The EPFO Employees’ Enrolment Campaign, 2026 closed on 31/10/2026.

Table 7: Filing ownership across the switch

Filing	Due date	Last pre-cutover month filed by	First post-cutover month filed by	Proof to retain
PF ECR and challan	15th of next month	Outgoing provider	Incoming provider	ECR acknowledgement, challan receipt
ESI contribution challan	15th of next month	Outgoing provider	Incoming provider	Challan receipt
Professional tax (each state)	State schedule	Outgoing provider	Incoming provider	State return and payment acknowledgement
Salary TDS deposit	7th of next month; March deductions by 30/04 (Rule 218, Income-tax Rules, 2026)	Outgoing provider	Incoming provider	Challan with BSR code
Form 138	31/07, 31/10, 31/01, 31/05	Provider that holds the quarter	Same provider for the whole quarter	Filing acknowledgement
Form 130	15/06	Company, via TRACES, from processed statements	Same	Certificates downloaded and issued

For the state-by-state view of professional tax enrolments, see professional tax registration for multi-state payroll. The monthly PF and ESI mechanics sit in our notes on PF ECR filing and ESI returns and challan filing.

What if the migration falls around the financial year end?

A cutover on the April wage month works only if the outgoing provider stays on the year-end filings. TDS deducted in March is deposited by 30/04 (Rule 218, Income-tax Rules, 2026). The Q4 Form 138, which carries the annual annexure data, is due on 31/05, and Form 130 is generated from the processed statements and is due by 15/06 (Income Tax Department guidance on Forms 138 and 130). The outgoing provider therefore has live work until mid-June even though payroll has moved. Keep it on the March deposit and the Q4 statement in writing, and have the incoming provider collect the new tax year’s Form 124 declarations as part of the April run. A cutover that moves the year-end close itself, meaning the March payroll or the Q4 statement, is the riskiest option. Settle that position with your tax and regulatory advisory team before notice is served.

How long should the parallel run be, and what must reconcile?

In payroll migration when changing provider, run one full cycle at minimum and two when you have staff in several states, many ESI-borderline employees or any structure change in the last six months. The test is not that the new system works, but that its output equals the old system’s output for every employee, with every difference explained and signed off. Go live only at zero unexplained variance.

This is consistent with the one-cycle minimum in our scope guide. The second cycle is for the cases that carry more risk.

Write the acceptance criteria before the first parallel cycle, so go-live is a test result, not a judgement:

• Zero unexplained variance, employee by employee, on the seven items below.
• Every statutory file for the parallel month generated by the new provider and matched to the old provider’s file.
• Every portal login tested by the incoming provider, including the EPFO, ESIC, TRACES and state professional tax portals.
• Bank payment file accepted by the bank in a test.
• A named person at the company who signs off, and a named person at each provider.
• Approvers and HR trained on the new portal, approval flow and employee self-service before cutover.

Reconcile these seven items employee by employee:

• Gross pay, by component
• Net pay, matched to the bank payment file
• PF wage base, ceiling and employee and employer contributions
• ESI wages, eligibility and contributions
• Professional tax by state
• Salary TDS for the month and cumulative to date
• Year-to-date totals against the last filed Form 138 and the annual tax statement on the Income Tax portal

The Labour Codes require wages to be paid on a fixed schedule, with monthly wages due before the expiry of the seventh day of the following month under section 17 of the Code on Wages, 2019. That date is a hard constraint on how long a failed parallel run can be extended, so decide the fallback early: if the new system is not at zero variance by the pay cut-off, the old provider processes that month.

Tell employees before the first live cycle what will change. Net pay date, bank account and salary structure stay the same. The portal, payslip layout, declaration flow and helpdesk contact change. Also tell them where past payslips will sit, because the outgoing provider’s portal will not stay available for ever. Do not change the salary structure in the first live cycle, because a variance you cannot explain is a variance you cannot defend. Employers must give a wage slip on or before wage payment (section 50(3), Code on Wages, 2019), so payslips cannot wait for the new system to settle. For payslip content, see monthly payslip generation services in India.

Cover five points in one message from the company, not from either provider:

• Net pay date, bank account and salary structure do not change.
• The portal, payslip layout, declaration flow and helpdesk contact do change.
• Where past payslips and the Form 130 for earlier months can be found.
• What employees who joined this year need to declare, such as previous employer income on Form 122.
• Who to ask, and who at the company is accountable for each answer.

What should you monitor after go-live?

Treat the first live cycle and the first quarter as part of the migration. After the first live cycle, match the bank file to net pay, the ECR and ESI challan to the register, and the TDS challan to the deducted amount. After the first quarter, tie Form 138 to the payroll registers for all three months and to the TDS challans. Check the annual tax statement on the Income Tax portal for the quarter, and keep the sign-off and reconciliations in one evidence file.

What changed in 2026 that the new payroll system must handle?

Seven changes decide your test cases: the Labour Codes wage definition, the Income-tax Act, 2025 forms, the EPF Scheme, 2026, the ₹25,000 PF wage ceiling, the ESI transition date of 20/11/2026, the legacy regularisation windows and, for data handling, the Digital Personal Data Protection Act, 2023. A new provider that is still configured for the old rules will pass a parallel run against an old system that is also wrong.

Table 8: 2026 changes and the migration test for each

Change	Date	Test in the new system
Four Labour Codes in force; Central Rules notified	Codes 21/11/2025; Central Rules 08/05/2026	Wage definition applies to PF, ESI and gratuity bases; excluded components capped at 50% of remuneration (Code on Wages, 2019)
Income-tax Act, 2025 and Income-tax Rules, 2026	01/04/2026	Salary TDS under section 392; Form 138 replaces Form 24Q; Form 130 replaces Form 16; Form 124 replaces Form 12BB
Employees’ Provident Funds Scheme, 2026	Notified 29/06/2026, G.S.R. 525(E); the 1952 Scheme is preserved for one year from 21/11/2025 under section 164(2)(b) of the Code on Social Security, 2020	ECR format and authorised signatory records, checked again after 20/11/2026
EPF wage ceiling raised from ₹15,000 to ₹25,000	17/09/2026, S.O. 5109(E)	Ceiling in the new system; employees between ₹15,000 and ₹25,000 now in scope; EPS limit of ₹2,083 a month. The ESI wage ceiling stays at ₹21,000, with no revision notified as at 19/10/2026
ESI transition under the Code on Social Security, 2020	Old rules and regulations continue to 20/11/2026	Re-test wage file and challan after 20/11/2026 against whatever final regulations are notified; the 2026 draft was still unfinalised as of 11/11/2026
Legacy regularisation windows	ESIC amnesty to 31/12/2026; EPFO VISHWAS and AMNESTY 2026 to 28/12/2026	Use the audit findings before the windows close
Digital Personal Data Protection Rules, 2025	Notified 13/11/2025; core obligations from 13/05/2027	Data processor contract, access controls, retention and erasure of employee data

Three points matter for a migration run in November or December 2026. First, the PF ceiling moved to ₹25,000 from 17/09/2026, so the new system must carry the split-month September workings and the wider coverage band. Second, the ESI transition date of 20/11/2026 falls one week after this article’s date; Treelife’s ESI guide found no final notification of the ESI (General) Regulations, 2026 as of 11/11/2026, and we found no extension, so check the ESIC portal before relying on any wage file format. Third, section 8(2) of the Digital Personal Data Protection Act, 2023 allows a data processor only under a valid contract, so put the new contract in place before the first data file moves and require erasure under the outgoing one after the return pack is accepted.

What should the exit from the outgoing provider look like?

Payroll migration when changing provider ends with the exit: give notice in line with the contract, secure the data return in writing, and keep the outgoing provider on filings until the last acknowledged return for its period. Do not let fee disputes delay the return pack, because the employer owns the payroll data and statutory logins, and a provider holding them back is holding the company’s compliance record.

Before you serve notice, read the outgoing contract for six things: the notice period and how it must be served, any termination fee or minimum term, data return and deletion, the provider’s duty to cooperate with a successor, any non-solicit or exclusivity term, and who bears liability for errors in its period. The return-pack clause governs what you can demand; our scope guide lists the contents. For a migration, add these requests: the last 12 months of filing acknowledgements, the Form 138 data and acknowledgements for every quarter in the tax year, state registration and return records for professional tax, Labour Welfare Fund and Shops and Establishments, the payslip archive for the whole engagement, and written confirmation of which logins sit under the provider’s contact details.

Notices for the period the outgoing provider handled are addressed to the company as employer or deductor. Get a written list of every open notice and query, and agree in the exit terms who prepares the reply for each. Take legal support on any non-solicit or exclusivity term before you serve notice, because enforceability depends on the contract.

If the provider will not cooperate, serve a written notice under the contract demanding the data by a stated date, and rebuild most of the record from sources the company controls:

• TRACES: filed Form 138 statements, deduction details and Form 130 history
• EPFO portal: ECR history and member passbooks by UAN
• ESIC portal: contribution history and insured person list
• State portals: professional tax returns and payment history
• Company records: bank payment files, last payslips and the general ledger payroll postings

Move only the data the incoming provider needs, and keep a record of what moved, when and to whom. The outgoing provider’s data must then be deleted. Ask for a certificate of erasure once you have confirmed the return pack. Where payroll postings feed the books, tie the last cycle to the ledger before you close the old system; for the finance-side handover logic, see our guide on outsourced CFO transition in India.

Common mistakes that cost time and money in payroll migration when changing provider

Most failures in payroll migration when changing provider repeat the same five patterns. Each is preventable with one document.

Cutting over mid-quarter without a named Form 138 filer. Fix it by agreeing in writing who files the quarter and by when the other provider hands over its data. A late Form 138 attracts a fee under section 427 of the Income-tax Act, 2025 (as substituted by the Finance Act, 2026), at ₹200 for every day of delay, capped at the tax deductible and payable before the delayed statement is filed (section 427(1) and (2)).

Leaving logins under the vendor’s email and mobile. Fix it in week one by moving contact details to company-owned ones and re-registering the DSC or e-Sign of the company’s authorised signatory on the EPFO portal.

Loading year-to-date net pay without the tax computation base. Fix it by loading tax deducted to date, perquisites, previous employer income, regime choice and Form 124 declarations. Otherwise TDS in the first live month is wrong, and a correction means a revised statement.

Combining the cutover with a structure change or Labour Code restructuring. Fix it by splitting them: migrate first at the same structure, then change the structure from the second live cycle.

Ending the old contract before the last return is acknowledged. Fix it by keeping a one-quarter filing tail in the exit terms. Late PF deposits attract interest and damages, and late ESI contributions attract interest, so a missed first filing costs money as well as credibility.

Conclusion: the cutover to pick

Cut over in the January 2027 wage month if one parallel cycle, on December wages, is enough for your headcount and states. That keeps the last quarter of FY 2026-27 with one provider and lets you test the ESI position after 20/11/2026. If you need two parallel cycles, move the cutover to the April 2027 wage month and keep the outgoing provider on the Q4 statement and the year-end close. Payroll migration when changing provider is a continuity exercise: the registrations stay with you, so the work is moving access, data and filing ownership without a gap.

FAQs on payroll migration when changing provider in India

Q: Does the TDS projection restart when we change payroll provider?
A: No. TDS is computed for the employer and the employee across the full year, not per provider. The new provider must load tax deducted to date, perquisites, regime choice and declarations, so section 392 of the Income-tax Act, 2025 projects correctly. A reset shows up as a TDS spike or shortfall in the first live month.

Q: What does a payroll migration cost?
A: Cost has three lines: a one-time migration fee, the double cost of the parallel cycle and any exit fee in the old contract. Ask each provider to quote the three separately and compare over 12 months, not only the monthly rate.

Q: How long does a payroll migration take?
A: It depends on the number of parallel cycles, because each one is a full wage month. One cycle means at least one wage month of testing after data and access are ready, and two cycles mean two. Add the notice period in the outgoing contract and the first live cycle. A quarter-start cutover reduces risk more than it saves time.

Q: Which documents does the new provider need?
A: The employee master, current salary structures, year-to-date payroll by component, the tax computation base, Form 122 and Form 124 declarations, the last Form 138 acknowledgements, ECR and ESI challans for 12 months, and portal access. Ask the outgoing provider for the full return pack in writing.

Q: Is any FEMA step needed when an Indian subsidiary changes payroll provider?
A: Not for the change itself. FEMA matters only if employees are paid in foreign currency or the foreign parent pays the new provider across borders, in which case the usual remittance rules apply to that payment.

Q: How should founder-directors on payroll be handled?
A: Treat them like any other employee for TDS, PF and professional tax, and load their year-to-date remuneration and perquisites in the same file. Keep the board or shareholder approval for remuneration on file, because the new provider will not see it in payroll data.

Q: Does DPIIT startup recognition change the migration?
A: No. Recognition does not change payroll filings. Flag any ESOP perquisite whose tax is deferred for an eligible employee, so TDS does not run on a figure that is not currently taxable.

Q: What if the migration fails mid-way?
A: Keep the outgoing provider’s contract and access live until the first post-cutover month is filed. If the new system is not at zero variance at the pay cut-off, process that month in the old system, because wages are due before the seventh day of the next month (section 17, Code on Wages, 2019).

Q: What will investors or acquirers ask about a payroll provider change?
A: They ask for proof of continuity: filing acknowledgements for every month, the Form 138 acknowledgements for every quarter, and evidence that no month was processed twice or missed. Keep one evidence pack with each parallel cycle’s sign-off and the written filer agreement.

Q: What happens to employees who exit during the migration month?
A: Process the full and final settlement in the system that processed their last wage month, and carry the final figures into the year-to-date file. Wages for an employee who resigns or is removed are due within two working days (section 17(2), Code on Wages, 2019), so do not hold these for the cutover. Exits that fall between the data freeze and go-live are the most common source of duplicated or missed payouts, so list them separately.

Q: How should ESOP holders and NRI employees be handled?
A: ESOP perquisites and exercise events must be in the tax computation base, because they change the TDS projection. Carry residential status across for NRI or non-resident employees, since it changes the TDS treatment.

Q: Who issues Form 130 after a provider change?
A: The company, as deductor, from the TRACES-generated certificate for all months in the year, whichever provider processed them. TRACES builds the certificate from processed Form 138 statements for the TAN, so a filing gap leaves a gap in the certificate (Income Tax Department, Form 130 FAQs).

Q: Can the outgoing provider keep our data after exit?
A: It should not. Section 8(2) of the Digital Personal Data Protection Act, 2023 requires a valid contract for processing, and the contract should require return and erasure on exit. Substantive obligations under the Digital Personal Data Protection Rules, 2025 apply from 13/05/2027, so build the clause now rather than at renewal.

Q: What if the outgoing provider refuses to cooperate?
A: Serve a written notice under the contract demanding the data and logins by a stated date. The payroll data and the statutory registrations belong to the company as employer. Meanwhile, rebuild what you can from TRACES, the EPFO and ESIC portals, state portals, bank files and payslips, so the new provider can start from records you control.

Q: Can the switch be used to fix gaps left by the previous provider?
A: Yes, and it is the cheapest time to do it. Audit the PF wage base, ESI coverage, state registrations, TRACES status and open notices for the periods the outgoing provider handled. These obligations sit with the company, so fix anything found in the company’s name before an authority raises it.

---

Regulatory references

• Income-tax Act, 2025, section 392 (salary TDS), section 395(4)(b) (Form 130), section 397(3)(b) (quarterly statement), section 427 (late filing fee)
• Income-tax Rules, 2026, Rule 218 (TDS deposit) and Rule 219 (quarterly statements); Forms 124, 130, 138 and 168
• Code on Wages, 2019, section 2(y) (wages) and section 17 (payment of wages); Code on Wages (Central) Rules, 2026, notified 08/05/2026
• Code on Social Security, 2020, section 164(2)(b), the one-year transition to 20/11/2026 for the EPF Scheme, 1952 and for rules and regulations under the repealed ESI Act
• Finance Act, 2026, section 96, substituting sections 427 and 428 of the Income-tax Act, 2025 with effect from 01/04/2026
• Employees’ Provident Funds Scheme, 2026, G.S.R. 525(E), dated 29/06/2026
• Draft Employees’ State Insurance (General) Regulations, 2026 (no final notification found as of 11/11/2026)