DonkeyHR

Migrating payroll to new software: a checklist

Move payroll by cleaning employee records, carrying forward balances, comparing a parallel run and approving a clear cut-over before using the new system.

DonkeyHR Team · 2026-10-27 · 6 min read

Move payroll by cleaning employee records, carrying forward opening balances and year-to-date figures, checking leave balances, and comparing a parallel run. Agree a cut-over date and get written sign-off before using the new system for a live payroll. Matching the overall total is not enough: check each employee’s pay, deductions and balances.

What should you decide before moving payroll?

Choose who will prepare the records, who will check them and who can approve the move. In a small business, an owner and an office manager may share these jobs. Make the responsibility clear even when the team is small.

Define what a successful move looks like. Employee records should be complete, balances should agree with the old records, and every difference in the parallel run should have an explanation.

Keep a readable copy of the old payroll records. Confirm how you will access payslips, registers and supporting documents after the move. Do not assume access will continue after an old subscription ends.

How do you clean employee data before importing it?

Start with a single employee list. Remove duplicate records and separate active employees from people who have left. Use a consistent employee identifier so similar names do not cause records to be mixed up.

Check names, joining details, employment status, salary components and deduction settings against approved records. Verify bank details through your normal confirmation process. Restrict access to payroll files because they contain personal and financial information.

Resolve unclear entries before importing them. A blank field might mean “not applicable”, “not collected” or “missing”. Those meanings should not be treated as interchangeable.

Map each old salary component to its destination in the new system. A familiar label does not prove that the calculation behaves the same way.

Which opening balances and year-to-date figures should you carry?

Opening balances are the amounts that need to continue from the old records. Depending on your payroll arrangements, these may include outstanding advances, recoveries and unpaid adjustments. Record what each balance means and which payroll period it relates to.

Keep these separate from year-to-date figures. Year-to-date figures describe earnings and deductions already processed during the financial year. They should not become fresh earnings or deductions merely because they have been imported.

A mid-year switch needs year-to-date earnings and tax so TDS stays right. Reconcile those figures employee by employee against the old payroll records. Include relevant declarations and adjustments already considered, and confirm how the new system uses them.

Do not assume a successful import means the tax calculation is correct. Review the resulting calculation as well. Rules can change during the labour-code transition, so check the current notification or official portal before changing statutory settings.

How should you move leave balances and pending requests?

Choose a clear point at which leave balances will be measured. Export balances after accounting for approved leave up to that point.

Check each leave type separately. An available balance, a pending request and an approved future absence are different records. Confirm how each will be handled after the move.

Review leave policies, approval responsibilities and regional holidays. Otherwise, a correct imported balance can become wrong when the next leave request is processed.

Tell employees where to submit requests during the changeover. Keep a record of requests received while the migration is being checked, then reconcile them before opening the new process to everyone.

How do you run a useful parallel comparison?

A parallel run means calculating the same payroll period in both systems using the same approved inputs. Keep attendance, leave, salary changes and adjustments identical. Changing the inputs halfway through makes the comparison difficult to trust.

Compare employee-level earnings, deductions and net pay. Also compare component totals, year-to-date figures and closing balances. If relevant, inspect exported payroll records to confirm that their contents agree with the reviewed calculation.

Classify differences before correcting them. A missing input needs a different fix from an incorrect component mapping or rounding setting. Record the cause, correction and result of the repeat comparison.

What does an illustrative comparison show?

Illustrative example: the old payroll total is Rs 4,12,000 and the new payroll total is Rs 4,12,000. The total difference is Rs 4,12,000 minus Rs 4,12,000, which is nil.

However, an employee’s net pay differs by Rs 500. Another employee-level difference offsets it, so the overall totals still match.

Investigation traces the Rs 500 difference to a rounding setting applied incorrectly during calculation. This is an invented migration error, not a statutory rounding rule or an acceptable tolerance. Correct the setting, investigate the offsetting difference separately, and repeat the comparison.

The lesson is simple: matching totals can hide incorrect individual payments.

When should you set the cut-over date and sign off?

Choose a cut-over date that gives you time to resolve differences before the next live payroll. State which period the old system will finish and which period the new system will begin.

Freeze the approved migration file. If a late change arrives, record it and update the affected records through a controlled process. Avoid quietly editing separate copies.

Prepare a sign-off note covering the records checked, unresolved items, responsible reviewer and approved cut-over. Any unresolved item that could change an employee’s pay should be resolved before approval.

Keep a fallback plan. State how payroll will be completed if the new calculation cannot be approved in time.

What should your migration checklist contain?

Use this checklist before approving the move:

  • Confirm the employee list is complete and duplicates are resolved.
  • Verify salary components, deduction settings and bank details.
  • Reconcile opening balances with supporting records.
  • Reconcile year-to-date earnings and tax for each employee.
  • Check leave balances, pending requests and regional holidays.
  • Run both calculations with the same approved inputs.
  • Explain and correct employee-level differences.
  • Inspect the contents of relevant payroll exports.
  • Record the cut-over, fallback process and written sign-off.
  • Confirm access to historical payroll records.

Common mistakes

Importing untidy records transfers old problems into a new system. Clean the source records first, and keep a note of corrections.

Entering year-to-date earnings as current-period pay can distort the new run. Confirm where historical figures belong and review the output.

Approving a parallel run because the grand total matches can conceal employee-level errors. Check individual results.

Letting both systems remain editable after cut-over creates competing records. Define where corrections will be recorded and who approves them.

FAQ

Can we move payroll during the financial year?

Yes, but carry forward and reconcile year-to-date earnings and tax. Check how those figures affect TDS in the new calculation before approving live payroll.

Should employees check their migrated details?

Employees can help confirm personal details and leave information through a secure process. The payroll reviewer remains responsible for reconciling earnings, deductions and balances against approved records.

Who should approve the migration?

Someone authorised to approve payroll should sign off after reviewing the reconciliation. The person preparing the import should provide evidence of the checks and explain any corrections.

How can software support the move?

DonkeyHR is an Indian payroll and HR product for small businesses, currently in beta, with payroll calculations for PF, ESI, professional tax and TDS, leave policies, and payroll register CSV exports. Check that the records and calculations needed for your move are supported before agreeing the cut-over.

Related reading