Migrate from Keka to ASHR.work

What you can bring in today

The same self-serve bulk CSV import wizard every ASHR.work workspace has — Admin → Import data — imports these record kinds today, whichever system they are coming from:

• Employees

  Name, department, designation, manager and an optional bulk sign-in invite.

• Leave balances

  Each employee’s allocated and carried-forward balance, per leave type and year.

• Holidays

  Your holiday calendar — date, name, type and description.

• Assets

  Company assets — tag, category, assignment, purchase date and condition.

• Salary structures

  Each employee’s pay mode, annual CTC or monthly stipend, effective from a given date.

• Org chart

  Reporting lines — who manages whom.

How it works

There is no built connector from Keka to ASHR.work — the path below is the same one every migration takes, whichever system you are moving from.

1. 1

   Export your data

   Most HR systems offer a CSV or Excel export somewhere under Reports or Settings → Export. Export each record kind you want to bring across — employees, leave balances, holidays, and so on.

2. 2

   Download a template and map your columns

   Admin → Import data has a Download template button for each kind, generated straight from what the importer actually validates, so it never drifts out of date. Line your export up against it.

3. 3

   Preview a dry run

   Upload your CSV and every row is validated before anything is written — you get a list of what would change, row by row, and any issue that would block it.

4. 4

   Commit, safely

   Only once you confirm does anything get written, through the same rules a hand-entered record follows. Re-uploading a corrected file later updates the same rows instead of duplicating them.