How to Export Candidates to CSV Without Breaking Your Data

How to Export Candidates to CSV Without Breaking Your Data

To export candidates to CSV, open the candidate list in your ATS or candidate database, filter it to the people you need, choose the columns, and use the export or download option. The file that comes out is only useful if it is clean: one header row, one candidate per row, UTF-8 encoding and one value per cell. This guide covers the steps, the fields worth including, the mistakes that corrupt files, and what to look for in any system you may import into later.

TL;DR

• Filter first, then export. A targeted file (one role, one pool, one date range) is easier to check and safer to share than your whole database.
• Choose fields on purpose: contact details, role, skills, location, source, status and dates cover most uses. Leave out anything the recipient does not need.
• Keep the file machine-readable: one header row, commas as separators, UTF-8 encoding, one value per cell.
• Open the file in a spreadsheet carefully. Dates, accents and leading zeros are the usual casualties.
• If your candidates live in a shared inbox as email attachments, build the database first, then export from it.

Table of Contents

• What a candidate CSV export is for
• Step by step: exporting candidates from a database or ATS
• Choosing which candidates and fields to export
• How to format the file so another system can read it
• Importing a CSV into an ATS or candidate database
• What to check when you evaluate an ATS or database for CSV features
• When your candidates are in a shared inbox, not a database
• Perspective: why the export is only as good as the intake
• From inbox to clean CSV with RecrutFlo
• A pre-flight checklist before you send any candidate file
• FAQ
• Sources

What a candidate CSV export is for

A CSV (comma-separated values) file is plain text with one record per line. Every spreadsheet, ATS, CRM and mailing tool can read it, which is why it is the default format for moving candidate data around.

Recruiters export candidates for a handful of recurring reasons:

• Reporting. Counting applicants by role, source or month for a hiring manager or a client.
• Sharing a shortlist. Sending a filtered set of profiles to a client or a colleague who does not have system access.
• Migration. Moving from one tool to another, or from a folder of spreadsheets into a proper database.
• Backup. Keeping an offline copy of your talent pool.
• Outreach. Feeding a segment of past candidates into an email or messaging tool, where your consent and data protection obligations allow it.

Each purpose needs a different slice of data. Decide the purpose before you click export, because it determines the filters, the columns and who may receive the file.

Step by step: exporting candidates from a database or ATS

The button names differ between systems (Export, Download, Save to CSV, Reports), but the sequence is nearly always the same.

1. Open the candidate list. Use the main candidates view or a saved search, not an individual profile.
2. Filter to the group you need. Narrow by role, skill, language, location, status or date added. A job-specific export is far easier to verify than a full dump.
3. Select records. Tick individual candidates or use a select-all option for the filtered result. Check the count shown against what you expect. Many systems cap how many records you can export at once, so a count that is lower than expected is a signal to check the limit.
4. Choose the columns. If the system lets you pick fields, select only what the file’s purpose requires. If it does not, plan to delete columns afterward.
5. Run the export and save the file with a clear name. Include the purpose and date, for example warehouse-supervisors-2026-11.csv. Avoid spaces and unusual symbols in file names, since they cause problems with uploads (we wrote about which symbols break uploads).
6. Check the file before you use it. Open it in a plain text editor first to see the real structure, then in a spreadsheet to read it comfortably.

If you cannot find an export option at all, look in reports or settings. Some systems restrict export to admin roles, which is a sensible control for personal data.

Choosing which candidates and fields to export

Start from the question the file answers

A file for a hiring manager needs name, current role, key skills, location and availability. A file for a migration needs everything you can get, including internal IDs, status and notes. A file for a mailing needs name, email and the consent or source information. Three purposes, three different files.

A practical field list

Keep personal data to the minimum

Candidate files are personal data. Export what the purpose requires and no more, store the file somewhere access-controlled, and delete it when the job is done. If you operate under rules such as the GDPR for candidates in the EU, or state privacy laws in the US, check with your legal or privacy lead before sharing a file outside your organization.

How to format the file so another system can read it

A download button does not guarantee a usable file. The UK government’s guidance on using the CSV file format is a good checklist because it is written for interchange between systems. Its main points translate directly to candidate data:

• One header row at the top, with a clear name for each column.
• One subject per file. Candidates in one file, job openings in another. Do not mix them.
• Consistent data types in each column: all dates in the same format, all numbers as numbers.
• Commas as separators, and values containing commas wrapped in quotation marks.
• UTF-8 encoding, so names such as José, Zoë or Małgorzata survive.
• One value per cell. If a candidate has five skills, decide on a single, consistent way to list them rather than adding columns that exist for only some rows.

The same guidance also tells you to check that spreadsheet software has not changed dates, characters or leading zeros. That is where most candidate files go wrong.

The three classic spreadsheet accidents

Leading zeros disappear. A phone number or postal code such as 07911 becomes 7911 once a spreadsheet treats it as a number. Import the column as text instead of double-clicking the file.

Dates flip. 03/04/2026 means March 4 in the US and April 3 in much of the world. Ask for ISO format (2026-04-03) when you can, because it reads the same everywhere.

Accents turn into symbols. This is an encoding issue. If names look garbled, re-open the file using the import function and choose UTF-8 as the encoding.

A practical habit: never edit and re-save the original export. Keep it untouched, and work on a copy.

Importing a CSV into an ATS or candidate database

Exports are often the first half of a move. The second half is import, and it fails for predictable reasons.

1. Download the import template if the target system provides one, and match your column headers to it. If there is no template, ask what columns it accepts.
2. Map the columns. Most systems show a mapping screen where you pair each header in your file with a field in the system. Check the email and name mapping first.
3. Handle required fields. Records missing a required field, often email or name, are typically rejected. Fill or remove them before upload.
4. Test with a small batch. Import 10 to 20 rows, open the resulting profiles and check that skills, dates and special characters came through.
5. Deal with duplicates. Decide in advance whether the import should skip, merge or overwrite records that already exist. Email address is the usual matching key.
6. Import the full file only after the test batch looks right, and keep the source file as your audit record.

What to check when you evaluate an ATS or database for CSV features

If you are choosing a tool partly on how well it handles data in and out, compare on these points:

• Export scope. Can you export a filtered list, or only everything? Are there record limits per export?
• Column control. Can you choose which fields leave the system?
• Complete data. Does the export include structured fields such as skills, languages and location, or only name and email?
• Import mapping. Is there a mapping screen, a template, and a clear error report for rejected rows?
• Duplicate handling. Does the system detect duplicates on import and on an ongoing basis?
• Permissions and audit. Who may export, and is there a record of it? Exports are the most common way personal data leaves a system.
• Pricing clarity. Is export included in your plan, and are the plan limits published?

These questions matter more than any feature list, because they decide whether your data stays portable.

When your candidates are in a shared inbox, not a database

Many small teams have no candidate database to export from. Applications arrive as email attachments in a shared mailbox, and the “database” is a folder of PDFs and a half-maintained spreadsheet. Exporting to CSV from there means typing names, emails and skills into cells by hand.

The fix is to structure the data once, at the point of arrival. We cover the approach in how to turn the CVs in your recruitment inbox into a searchable candidate database, and the search side in how to search candidate CVs from your email inbox. Agencies with large volumes will find more in our piece on agency CV management. Once every CV is a profile with consistent fields, a CSV export becomes a two-minute task instead of an afternoon of copy and paste.

Data quality at the source decides export quality at the end. Our guide to candidate data quality lists the dimensions worth checking before you trust any file.

Perspective: why the export is only as good as the intake

We built RecrutFlo around a simple observation: teams do not struggle with the export button, they struggle with what sits behind it. When CVs arrive in a shared inbox, the real work is turning attachments into rows that mean something.

That is why our approach starts at the mailbox. RecrutFlo connects to your existing inbox, identifies CV attachments, extracts contact details, experience, skills, languages, location, salary expectations and availability, and organizes them into searchable candidate profiles. We flag duplicates, so the same person does not appear three times in your file. When you need the data elsewhere, CSV export is there.

We also think small teams should not need an implementation project to get here. Our setup is designed to work without an onboarding call, you keep control over what is automated, and workspace isolation, an audit trail and team access control are part of the product, because candidate data deserves care.

Marco

From inbox to clean CSV with RecrutFlo

If your CVs arrive by email, RecrutFlo is designed to do the structuring for you. It connects to Microsoft 365, Outlook and IMAP mailboxes (Gmail is coming), parses PDF, DOC and DOCX CVs, and builds a searchable database you can filter by skills, experience, languages, location and role, then export to CSV. The How it works page shows the flow.

You can start on the Free plan and move up when volume grows. Starter is €19 per month, Professional is €49 per month and Business is €149 per month. If you need extra capacity, additional processing runs are a one-off €9 for 100, €29 for 500 or €49 for 1,000. Full details are on the pricing page, or start from recrutflo.com.

A pre-flight checklist before you send any candidate file

Run through this each time:

• The file contains only the candidates and columns the recipient needs.
• The header row is present, with one clear name per column.
• Encoding is UTF-8 and special characters display correctly.
• Phone numbers and postal codes still have their leading zeros.
• Dates use one format, ideally 2026-11-06 style.
• No cell contains more than one value, unless a documented delimiter is used for skills.
• Duplicates have been removed or merged.
• The file is stored or sent through an access-controlled channel, and there is a plan to delete it.

A minute on this list saves the recipient hours, and protects the people whose data is in the file.

FAQ

How do I export candidates to CSV from my ATS?

Open your candidate list, filter it to the group you need, select the records and choose the export or download option. Pick the columns if the system allows it. Open the result in a text editor first to confirm it looks right before using it in a spreadsheet.

Why do names and phone numbers look wrong when I open the CSV in a spreadsheet?

Spreadsheets guess at data types and encoding when you double-click a file. Garbled accents usually mean the file was read with the wrong encoding, and missing leading zeros mean a text column was treated as a number. Use the spreadsheet’s import function, set the encoding to UTF-8 and mark those columns as text.

What fields should a candidate CSV include?

For most uses: name, email, phone, location, role, skills, languages, source, status and date added. Add salary expectation and availability when the file supports shortlisting. Leave out anything the recipient does not need, since candidate files contain personal data.

Can I export candidates from a shared email inbox?

Not directly, because emails and attachments are not structured records. You first need the CV details pulled into candidate profiles, either by hand or with software that reads CV attachments. RecrutFlo is designed for this: it builds profiles from the CVs in your inbox, which you can then export to CSV.

How do I avoid duplicates when importing a CSV?

Decide beforehand whether the import should skip, merge or overwrite existing records, with email address as the usual matching key. Import a small test batch first and check the profiles. Clean the file for duplicate rows before upload if the target system does not detect them.

Sources

• Using CSV file format, GOV.UK

Recommended

• How to Turn the CVs in Your Recruitment Inbox into a Searchable Candidate Database
• How to Parse PDF Resumes into Structured Candidate Data
• Candidate Data Quality: 5 Dimensions for a Recruiter Inbox Pilot
• CV File Names: The Symbols That Can Break Uploads