Export your data
What this achieves
Section titled “What this achieves”Export produces a file of your records in a format another system or a spreadsheet can read. The export runs as a job rather than an instant download, so a large export does not depend on you keeping a tab open.
Required role: Administrator.
- Go to Integrations → Export.
- Choose the Entity.
- Choose the Format.
- Select Start Export.
- Watch the job appear in Export History and follow its counters.
- Select Download when the job completes.
Format
Section titled “Format”| Option | Description |
|---|---|
| CSV | Plain comma-separated text. Widest compatibility. |
| Excel (XLSX) | A spreadsheet workbook. |
| JSON | Structured data, for another system to consume rather than a person to read. |
Choose CSV or Excel for anything a person will open, and JSON where the file feeds another system. A JSON export handed to somebody expecting a spreadsheet is a support request.
The job and its counters
Section titled “The job and its counters”An export runs as a job and reports Total, Processed, Successful, and Failed as it goes. The history table shows the Entity, Format, Status, Records, and Date of each export.
The download action is only available once the job completes. Where a job is still running, the interface says the download is available once it completes; where a job failed, it says no file was generated.
Exported files leave your access controls behind
Section titled “Exported files leave your access controls behind”This is worth saying plainly. Everything inside Humavera is subject to roles and permissions. A spreadsheet of employee records is subject to whatever the person who downloaded it does with it.
Decide who may run exports, of what, and where the files are allowed to go. That is a policy decision rather than a product setting — the export button does not know what a file is for.
Example: an export of HC Corp’s employee records emailed to a consultant is a copy of the directory outside every control Humavera applies to it, including for people who later leave.
Export what the task needs. An export of one department for one purpose is a smaller thing to lose than an export of everything because it was one click fewer.
What happens next
Section titled “What happens next”The file is available from the export history. Where the export feeds another system regularly, a connector on a schedule is the more durable path than a person remembering to run this each month — a scheduled sync does not stop because somebody was on leave.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved