Import from Ento
Bring your people and leave history from Ento into Rotaleave with an Employees CSV and optional Leave CSV — previewed before anything is written.
Updated 11 July 2026
Ento has announced it is closing down — export your data while you still can. Rotaleave imports Ento data from CSVs, admin-only, from Settings → Import / Migrate, the People page’s Import / Migrate button, or during onboarding on the Your people step — set Source to Ento (CSV).
Build the exports in Ento
Ento has no single fixed export (and no self-serve API), so you build export templates:
- Log in to Ento as an admin.
- Go to Settings → Export templates.
- Build (or run) an Employees export — required. Ento itself only insists on Employee ID and First name, but add Email too: Rotaleave logins need one, and rows without an email are blocked with an error. Locations, Team, Access Level, Status and Start Date are optional but worth including.
- Optionally build a Leave export with Employee ID, Leave Category, Start Date, End Date, Status, Half Day and RequestId — add it if you have leave history to bring.
- Download both as CSV.
What comes across
| Column | Becomes in Rotaleave |
|---|---|
| Employee ID | links leave rows to the right person in this import (and flags duplicates) |
| identifies the person (must be unique) | |
| First name / Surname | Name |
| Locations | Department |
| Team | Team |
| Access Level | Role |
| Status | Active/archived |
| Start Date (employees file) | Start date |
| Leave Category | Leave type (created if missing) |
| Start Date / End Date (leave file) | Leave dates |
| Half Day | Half-day/day-part |
| RequestId | used to keep re-runs safe |
Any column Rotaleave doesn’t recognise is listed as a warning — never dropped silently — so you can fix the export and run it again. Remaining balances are never imported; enter opening adjustments after migrating.
Preview, then import
- Upload the Employees CSV (and the Leave CSV if you have one).
- Click Preview — nothing is written yet. You get Created / Updated / Skipped counts per entity plus warnings for anything the importer didn’t recognise.
- If any rows have real errors, the import is blocked with the list: “Fix these rows and re-upload — nothing has been imported.” Fix the CSV and preview again.
- Click Import and look for “Import complete.”
Safe to re-run
Re-running is safe by design: people are matched by email and leave records by request id, so corrected files update rather than duplicate. Iterate until the preview is clean.
Just have a spreadsheet?
If your data isn’t from Ento at all, use the Staff CSV import on the same page — download the Rotaleave template, fill it in (including Mon–Sun working patterns) and run the same Preview → Import flow. Details in Invite your team.