CSV Candidate Import for Recruiters

Almost every recruiting team has candidate data in spreadsheets: event lists, agency submissions, exports from a previous system, a manager's personal shortlist. Getting it into a system is usually treated as a formality, and it usually goes wrong.

The failure is rarely upload. It is mapping: columns that do not match fields, names in one cell or two, dates in three formats, duplicates of people already in the system, and rows that fail silently.

The result is a database people stop trusting, which is worse than the spreadsheet, because at least the spreadsheet's flaws were visible.

Edvenity's import runs in four steps: choose the import type, upload the file, name the batch, then map and validate fields before anything is written.

Two details do most of the work. Every record is reported as created, updated, skipped, or failed, so a partial import is visible rather than silent. And naming the batch makes the intake findable months later, so a recruiter can filter to exactly that source instead of searching the whole database.

Resume archives import the same way, parsed into candidate profiles, with files tracked as linked or orphaned so unmatched documents surface as a fixable gap.

Imported candidates land in the searchable talent pool and can be invited into jobs directly.