Processing
Row by rowEvery row is created individually, so one bad row never blocks the rest — failures return with their reasons.
- ProcessingPer row
- OutputRow errors
- Re-runSafe
Load an existing workforce from a spreadsheet in one pass, with per-row results reported back and salary details importable alongside the employee records.
Every row is created individually, so one bad row never blocks the rest — failures return with their reasons.
Every view stays structured and reviewable — nothing hides behind a tab.
Every row is created individually, so one bad row never blocks the rest — failures return with their reasons.
Personal, job and contact fields load in a single pass, with departments, designations and employment types matched by code.
Salary details import alongside employees so the first payroll run is not blocked.
Import is gated behind its own permission rather than granted to every administrator.
Load an existing workforce from a spreadsheet in one pass, with per-row results reported back and salary details importable alongside the employee records.
Map your existing columns to employee fields — codes, departments, designations, joining dates and contact details — with a sample CSV to download.
Each row is processed individually: valid rows land, failures come back as a per-row list to fix and re-run.
Employee records and their salary details can both be loaded, so payroll is usable immediately after migration.
Move from spreadsheets or another HR system without re-keying every employee.
Problems are reported per row, so the sheet can be corrected and re-run.
The import permission is separate, so bulk data entry is not implied by general employee access.
Historical payroll can be back-filled separately when reporting continuity matters.
Rows already imported are skipped by national ID, so running the same sheet twice never duplicates people.
Every imported employee gets their onboarding pipeline spawned automatically.
Load an existing workforce from a spreadsheet in one pass, with per-row results reported back and salary details importable alongside the employee records.
No. Rows are processed one at a time — valid rows are created, failures come back as a per-row list to fix, and re-running skips anyone already imported.
Yes. Employee records and salary rows are separate imports run as part of the same migration.
Only roles holding the dedicated import permission, which is separate from ordinary employee management.
Map your current workflow to the right HRM setup, permissions and rollout plan.