Migrate to ASHR.work
There is no built connector from any of these systems into ASHR.work — the path is the same self-serve CSV import wizard for all five, with a dry run before anything is written. Pick where you are moving from for the specifics.
Migrate from Keka
Teams moving off Keka usually want their employee records, leave balances and holiday calendar carried across first, with the rest following once the basics are confirmed.
See the guideMigrate from Zoho People
If Zoho People is one part of a wider Zoho stack you are simplifying away from, exporting your HR data as CSV is the fastest way to get it into ASHR.work without waiting on a point-to-point integration.
See the guideMigrate from greytHR
Moving off greytHR typically starts with the employee list and leave balances, then salary structures and the org chart once payroll admins have reviewed a dry run.
See the guideMigrate from Darwinbox
Darwinbox deployments are often large and modular — bringing records across kind by kind, with a dry run before each commit, keeps a Darwinbox migration reviewable instead of one big irreversible cutover.
See the guideMigrate from BambooHR
BambooHR exports its data as CSV natively, which maps directly onto the same column-by-column dry run every import in ASHR.work goes through.
See the guideThe bulk CSV import wizard (Admin → Import data) is the same for every system above — employees, leave balances, holidays, assets, salary structures and the org chart import today, with a dry run before anything writes. Payroll history, performance review history and attendance records have no importer yet.
Move your team to ASHR.work
Start free, invite your team, then import your data from Admin > Import data.