Exporting Candidate Data to CSV and XLSX: What Belongs Where

Why format matters more than you think

A candidate's phone number exports as 2025551234 in CSV. Excel auto-interprets it as a number and strips the leading zero or adds scientific notation by the time you've opened it. You paste it into an offer-letter template, and the candidate gets a text to a wrong number. Or you export to-hire data, and 40% of phone numbers are corrupted before you hand it to HR.

This isn't a hypothetical. It happens every week to hiring teams that don't think about export format.

Format choice also affects compliance. CSV exposes the raw data, column by column. XLSX lets you add metadata, hide columns, and apply structure that reduces PII leakage. Both are fine; the choice depends on the downstream use case.

CSV: when it's right

Use CSV when:

• You're piping data into another tool (ATS, HRIS, offer-letter mail-merge, reporting platform). CSV is the lingua franca.
• You need one-time export for compliance or record-keeping. CSV is audit-trail friendly — it's human-readable, version-controllable, and requires no special software.
• Your data is tabular and doesn't need structure beyond columns. A list of finalists and their assessment scores.

CSV pitfalls to avoid:

• Phone numbers. Export as text by wrapping in quotes: "2025551234" not 2025551234. Or add a + prefix: +12025551234.
• Email addresses in mail-merge contexts. Test one in your merge template before bulk-applying it. Email parsing is fragile.
• Dates. Always export as YYYY-MM-DD. Never rely on locale defaults. Excel's interpretation of 01/02/2026 is a 50/50 coin flip between US and EU users.
• Names with commas. If a candidate's name is "Smith, John", CSV can mangle it. Wrap in quotes: "Smith, John".
• Encoding. Export as UTF-8, not ASCII or ISO-8859-1. Candidate data has international characters; don't lose them.

XLSX: when it's right

Use XLSX when:

• You're sharing candidate data with non-technical users (hiring manager, HR generalist) who'll view in Excel and shouldn't see backend schema.
• You need to add formatting, filtering, or column hiding. XLSX supports it; CSV doesn't.
• The data includes sensitive columns (internal notes, salary expectations, background-check status) that you want to hide-column rather than strip entirely.
• You're doing compliance reporting. XLSX lets you add a metadata sheet describing data retention, processing, and timestamps.

XLSX advantages:

• Column-level formatting. Phone numbers as text (no leading-zero loss), dates as date format (no ambiguity), currency with decimals.
• Filtering and sorting. The recipient can add an AutoFilter without corrupting the data.
• Metadata. Add a second sheet with export date, data-retention policy, and redaction notes.
• Signature-friendly. Hash the XLSX, email it with a note that the checksum is abc123..., and you've documented what you sent.

XLSX pitfalls:

• File size. An XLSX with 5,000 candidates × 20 columns is 2–3 MB; CSV is 500 KB. Matters for email.
• Shared access. If you email an XLSX and someone edits it locally, reconciling changes is a nightmare. CSV forces a single source of truth.
• Parsing. Some HRIS systems expect CSV and choke on XLSX. Test before committing to the format.

Compliance and PII: what to include and exclude

Always safe to include:

• Name, email, phone
• Job applied for, stage (Application, Screening, Interview, etc.)
• Application date, stage-change dates
• Assessment scores (if not directly identifying: "Coding score: 78/100" is fine; "passed regex assessment" is fine)

Requires consent or context:

• Salary expectations or offers
• Background check status (only if you have the candidate's consent to share with downstream HR)
• Interview feedback (never expose other panelists' names; aggregate or anonymize)
• Assessment content or responses (save for compliance audits, not routine export)

Never export:

• Internal recruiter notes of a personal or subjective nature ("seems disorganized")
• Diversity data (race, gender, age) — unless it's a required EEO report with proper anonymization
• Candidate communication history (emails, chats) — security and privacy risk

The rule: if the exported data is going to a person or system outside your org, strip anything you wouldn't text the candidate directly.

Common use cases and format recommendations

The technical reality: Excel loves to corrupt data

Excel will:

• Turn 0123456789 into 123456789 (leading zero loss).
• Turn 1E+10 into scientific notation.
• Turn 2026-01-02 into Jan 2 if it auto-formats as date.
• Lose trailing zeros in decimal fields (1.10 becomes 1.1).

Workarounds:

1. Format-as-text first. Before opening CSV in Excel, select all columns and set format to "Text". Then paste or open.
2. Use XLSX with cell formatting pre-applied. If you're generating XLSX, set phone columns to text format, date columns to date format, with explicit locale (US or ISO).
3. Add a README sheet. In XLSX, include a second sheet that documents which columns are text, which are dates, and why.

ClarityHire supports CSV export (with text-wrapped phone numbers by default) and XLSX export (with pre-formatted cells and a metadata sheet). Choose CSV for tool integrations, XLSX for human review and compliance archival.

Try data export on ClarityHire