Skip to content

Spreadsheet to HRMS migration plan: a four-week approach

A four-week plan to move payroll and HR records from spreadsheets to an HRMS: data cleaning, imports, a parallel run and cut-over, with a weekly checklist.

Saralix Team6 min read
On this page

Moving from spreadsheets to an HRMS goes well when the data is clean and the old and new systems are compared before anyone depends on the new one. It goes badly when the import is treated as the whole project. This plan is four weeks long, assumes a company of 10 to 100 people, and builds a parallel run into the schedule.

Figures here reflect the rules as we understand them at the time of writing. Verify against the current rules and notifications before relying on them.

If you are still deciding whether to move, our comparison with spreadsheets lists what a sheet handles well and where it starts to strain.

Before you start: pick the right month

The cleanest cut-over is the first month of a quarter, or of the financial year, so that TDS and PF history carry in cleanly. Avoid the week of a statutory deadline. Start week 1 about five to six weeks before the first payroll you want to run in the new system. Assign one owner (usually HR or finance), one approver, and one person who knows the current sheet in detail.

Week 1: Inventory and clean the data

What to gather

  • The employee master sheet.
  • The latest salary register, plus the last two or three months for comparison.
  • Attendance and leave records for the current year.
  • Leave balances at the start of the year and now.
  • Statutory details: PAN, UAN, ESIC number, bank accounts, work state.
  • Tax declarations and previous-employer income for mid-year joiners.
  • Loans and advances outstanding.
  • Any reimbursements still pending.
  • The company’s registrations: PF, ESI, PT, TAN, GSTIN and CIN for letters.

Cleaning checklist

  • One row per employee, and one employee ID per person that never changes.
  • Names match PAN and bank records.
  • Dates in one format. Mixed formats are the most common cause of an import error.
  • No blank mandatory fields: joining date, department, work location, manager.
  • Duplicates removed. Check names, bank accounts and PAN.
  • Bank account numbers and IFSC verified with the employee for anyone who has had a payment bounce.
  • Exited employees separated from active ones. Keep their final settlement records, but do not load them as active.
  • Salary components named consistently (Basic, HRA, Conveyance, Special Allowance, and so on).
  • Reporting managers listed by ID, and no one reports to themselves.
  • The salary structure rule written down, with the PF treatment and the LOP divisor.

Cleaning is dull, and it is where most of the value sits. A migration is a good excuse to find the five employees whose PAN has been blank for two years.

Week 2: Configure and import

Configure first

Set up the company, branches, statutory registrations and payroll cycle. Create the salary templates and leave types. Load your own official holiday list for each state. Assign admins and roles, including who can prepare and who can approve payroll.

Import employees

Saralix imports employees from a CSV file, with a dry run first. The dry run shows what would be created or rejected, so you can fix the file and repeat before anything is saved. Run it, fix errors line by line, and only then run the real import. Export the result and compare row counts and a handful of records against the source.

Import attendance

Attendance can be bulk uploaded from a spreadsheet or a biometric software export, again with a dry run first. It accepts DD-MM-YYYY or ISO dates, 12 or 24 hour times, and P, A, HD, L and WFH codes. Days in an approved payroll month are locked, so load history before you approve any month. If you have biometric devices, they push punches to a keyed API, so check with your vendor how to connect them.

Opening balances

Enter leave opening balances, loans outstanding and any year-to-date figures you need for tax. Document where each number came from.

Week 3: Parallel run

Run last month’s payroll in the new system using last month’s inputs, and compare it with the old output. This is the step that earns trust.

Comparison table

Check Old sheet New system Difference Reason
Headcount paid
Total gross
Total PF (employee and employer)
Total ESI
Total PT by state
Total TDS
Total net pay
Five sample employees, line by line

Expect differences. Common reasons are rounding, a different LOP divisor, PT slabs not applied in the sheet, PF wages treated differently, or a sheet formula that has been wrong for months. For every difference, decide which side is right. If the sheet is wrong, you now know something about past payments, so discuss with your consultant what to do about it.

Also test the secondary flows:

  • A joiner, using the invite route, then HR verification.
  • A leave request through approval.
  • A bank file for a small test payment, with the format your bank uses.
  • A payslip PDF.
  • An employee login to the self-service portal.

Week 4: Cut-over

Cut-over checklist

  • Parallel run differences all explained.
  • Employees told what is changing, when, and what to do (set a password, check their details).
  • Self-service invitations sent.
  • Old sheet frozen as read-only, with a date in the filename.
  • Cut-off date announced for the first live payroll.
  • Maker and checker confirmed.
  • Statutory due dates entered in your calendar: TDS by the 7th, PF and ESI by the 15th.
  • A named person for questions during the first month.

Then run payroll as normal, but review exceptions more closely than usual. See how to run payroll in 7 steps for the sequence, and use the payroll month-end close checklist for the last days of the month.

After the first live month

  • Compare the new system’s totals to your books, and reconcile bank payments.
  • Collect questions from employees and add them to a short FAQ.
  • Review which sheets you still use, and retire them one by one.
  • Keep the old sheet for the retention period your consultant advises.
  • Revisit the setup in month three. Most teams find a rule or two they want to adjust.

Risks and how to reduce them

Risk Reduction
Bad data in, bad data out Week 1 cleaning, dry runs
Silent calculation differences Parallel run with a difference table
Employees confused Early communication, self-service demo
A statutory date missed during the switch Calendar reminders, avoid cut-over near a due date
Key person absent A backup who has done a dry run
Mid-year tax data missing Collect previous-employer income and year-to-date TDS first

How long it really takes

Four weeks is realistic for 10 to 100 people when one person can give it a few hours a day. A very clean sheet can go faster. Years of manual patches usually take longer, and the clean-up is a benefit in itself. If you want a sense of the effort, the payroll features and people features pages show what is set up.

Closing thought

The parallel run is the part people want to skip, and the part that pays for itself. If you are ready to try it, Saralix is free for up to 10 employees, so a small team can rehearse the import with real data before it commits to anything, and the pricing page explains what applies as you grow. You can also read about choosing an HRMS before you decide.

Free up to 10 employees

Run your first payroll free.

Attendance, leave, payroll and PF, ESI, PT and TDS compliance in one place. See the plans, or ask for a walkthrough.