Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Migration guide

Migrate from sumHR to Apragya: Employee Records, Leave and Payroll Moved Cleanly

For HR teams at growing Indian companies on sumHR who want HR and payroll on the same record as projects, expenses and assets.

A nurse marking attendance on a biometric device with an HR officer beside her

Teams that migrate from sumHR are usually past the stage where HR alone is the goal. They want employees on the same record as timesheets, expense claims, assets and the finance entry for salaries.

sumHR is an Indian HR and payroll product aimed at small and mid-sized companies. If it covers your needs well, there is no pressing reason to move.

This guide covers what to export, the setup order, an illustrative example and the checks.

How to migrate from sumHR: the short answer

Export the employee master (codes, departments, managers, joining dates, documents list, bank and statutory numbers), leave types and balances, shift and holiday lists, and salary details. Check the vendor's current documentation for the exports your plan offers.

Set up leave types, shifts and holidays in Apragya first, then import employees and balances. If payroll moves too, load the year's earlier earnings and TDS.

Switch at a month start so attendance and payroll periods line up.

Before the switch, check three things: every employee has a manager (or leave requests have nowhere to go), leave balances total the same as the old closing report, and PAN, UAN and ESI numbers are present for everyone on payroll. Tell employees the date, and show them where to apply for leave and see payslips from that day.

  1. Choose a month start for the switch.
  2. Set up departments, leave types, shifts and holidays.
  3. Export and clean the employee master.
  4. Import employees with managers and statutory numbers.
  5. Load leave balances as at the switch date.
  6. Load payroll openings if payroll moves.
  7. Run one month in parallel, then switch.

An example: a hospital group in Nagpur

Take an illustrative group with 310 staff across two hospitals, rotating shifts and many leave types. It moved on 1 July.

The HR team's switch checklist

  • Departments and wardsSet up for both hospitals.Done
  • Shift patternsMorning, evening and night rotations.Done
  • Employee masterNine missing managers assigned.Checked
  • Leave balancesTotals agreed with the June closing.Matched
  • Biometric deviceseSSL devices connected.Ready
  • July payrollParallel run at month end.Pending
Assigning the nine missing managers kept leave approvals from getting stuck.

In the first week, leave requests reached the right ward in-charge because every employee had a manager. Attendance came from the biometric devices. July payroll matched in both systems apart from two night allowances, which were corrected before salaries went out.

An organisation tree of small figures with nine newly linked by blue ribbons
Nine employees gained a manager on import, so their leave requests reached the right ward in-charge.

How to move employee data to a new HRMS

Step 1 of 5

Set the rules

Departments, leave types, shifts and holidays.

  1. Set the rules: Departments, leave types, shifts and holidays.
  2. Import employees: With managers, documents and statutory numbers.
  3. Load leave: Balances per employee and type.
  4. Connect attendance: eSSL biometric devices or app check-in.
  5. Payroll openings: Earlier earnings and TDS if payroll moves.

HRMS switch checklist for India: what to verify

Check three things before the switch: every employee has a manager, leave balances match the old closing, and statutory numbers are present. Those three prevent most complaints in the first month.

sumHR and Apragya

FeaturesumHRApragya
HR and leaveSupportedSupported
Payroll complianceSupportedPF, ESI, PT, LWF and TDS
Projects and timesheetsCheck the vendorSame employee record
Expenses and assetsCheck the vendorSame employee record
AI agentsCheck the vendorOn records, with human review

Checked against public information on 16 September 2026.

What HR gains after the move

One employee record

Shared across apps.

Shifts

Rotations and overtime.

Self-service

Leave, attendance and payslips on the phone.

Documents

Stored on the employee record.

PII masking

Sensitive fields hidden by role.

Agents with review

AI flags unusual leave or attendance patterns.

See shifts, leaves, the sumHR alternative and Apragya vs sumHR.

Getting started

  1. Set up rules before importing people.
  2. Import employees and fix missing managers.
  3. Load and match leave balances.
  4. Connect attendance devices.
  5. Run payroll in parallel for one month.

Rules first, people second, balances third. That order avoids rework.

What it costs to start

INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus Payroll
2,000
AI Credits a month
Included on Starter
Free
Up to 3 users
CRM, HR and Vendor Onboarding

Moving from sumHR, answered

Can employee documents move?
Yes. Export them and attach them to each employee record.
Will leave history come across?
Balances move. Past leave records are usually kept as an export.
Can we move HR first and payroll later?
Yes. HR can move first; payroll follows at a later month start.
Do biometric devices work?
eSSL devices are supported for attendance.
What does it cost to start?
Payroll is available from the Starter plan, INR 3,999 a month for up to 10 users, which includes CRM and HR plus a choice of enterprise apps and 2,000 AI Credits a month. Pro, at INR 7,999 a month, covers 25 users and every enterprise app.

Start with your employee master

Import your employees and check managers and leave balances first.