Import Builder/Guides/CSV Date Formatting
CSV Formatting

Why Excel Is Changing Your Dates in CSV (3 Fix Methods)

Dates are one of the most common causes of CSV import problems. Learn which format to use, why Excel changes dates when it opens a CSV, and three ways to stop it.

Dates are more complicated than they look

A CSV file stores dates as text. Unlike databases or Excel files where dates have a specific data type, a CSV just sees "2026-08-07" as a string. This means every system that reads the CSV needs to interpret the text and parse it into an actual date. If they interpret differently, chaos ensues.

Regional differences

03/04/2026 could mean March 4th (US) or April 3rd (EU) depending on regional settings. The same date gets interpreted completely differently.

Excel auto-formatting

Excel converts anything that looks like a date into one of its own dates, shown in your computer's regional format. Save the file as CSV and that format is what gets written.

CSV has no date type

CSV files contain text values only. There's no way to mark a value as a date. Your system has to guess or follow documented conventions.

System-to-system mismatches

QuickBooks might export dates as MM/DD/YYYY, Salesforce as YYYY-MM-DD, and your CRM as DD/MM/YYYY. Combining data from multiple sources creates chaos.

Real-world example of date problems:

Your CSV contains: 02/03/2026

US System:

Feb 3, 2026

EU System:

Mar 2, 2026

ISO System:

Invalid date

Why Excel changes CSV dates and how to prevent it

Excel tries to automatically detect dates and numbers when opening CSV files. This "helpful" auto-formatting causes more problems than it solves. When you double-click a CSV file to open it in Excel, it runs its date detection and may silently change your data.

How Excel changes dates:

Regional interpretation

Input: 04/05/2026

US Excel: April 5, 2026 | UK Excel: May 4, 2026. Same data, different dates!

Format conversion

Input: 2026-08-07

Excel turns it into a date and shows it in your regional format, such as 07/08/2026 in the UK. Save the file as CSV and that's what gets written.

Invalid date detection

Input: 32/13/2026

Excel can't read it as a date, so it stays as text while the real dates around it are converted. The mix is easy to miss.

Two-digit years

Input: 08/07/26

By default Excel reads 00 to 29 as 2000 to 2029, and 30 to 99 as 1930 to 1999, so 08/07/45 becomes 1945.

3 ways to stop Excel changing dates:

✓

1. Import the CSV instead of double-clicking it

On the Data tab, choose From Text/CSV, pick the file and click Transform Data. Select each date column, change its type to Text, then Close & Load. The dates stay exactly as they are in the file. (The older Text Import Wizard does the same: turn it on under File, Options, Data, Show legacy data import wizards.)

✓

2. Format the column as Text before typing or pasting dates

Select the column, choose Format Cells, then Text. Anything typed or pasted afterwards is kept as written. Formatting it afterwards doesn't undo a conversion that's already happened.

✓

3. Set the date format before saving

A CSV is saved with dates as they're displayed. If Excel has already converted them, select the column, choose Format Cells, then Custom, and type the format the import needs, such as yyyy-mm-dd. Save as CSV and check the file in a text editor.

Human-readable dates for manual data entry

When people type dates by hand, month names avoid day and month mix-ups. Few import tools accept them, though, so convert the column to the import's format before saving (method 3 above).

Month names reduce ambiguity in manual entry

7 Aug 2026
31 Dec 2026
15 Jan 2026

This format is easier for humans to read because the month is clearly identified. There's no way to confuse August 7th with July 8th.

When to use human-readable vs. machine-readable dates

Machine-readable (YYYY-MM-DD)

In the file you import, unless the system asks for another format.

Human-readable (7 Aug 2026)

In sheets people read and type into. Convert before you save the CSV.

Best practice

Collect dates in a form that only accepts the format you need, so there's nothing to convert.

CSV date best practices

Use the format the import asks for

Check the system's import help first. Where you have a choice, use YYYY-MM-DD (ISO 8601).

Don't leave the format to chance

If the import needs MM/DD/YYYY or DD/MM/YYYY, say so next to the column, and check a few dates with a day above 12 after importing.

Use month names only for people, not imports

7 Aug 2026 is clear to read, but convert it to the import's format before saving the CSV.

Validate dates before importing

Check that dates are in the correct format and represent valid dates (no Feb 30th).

Keep date formats consistent across columns

Every date column must use the same format. No mixing YYYY-MM-DD with MM/DD/YYYY in the same file.

Always include full 4-digit years

Use 2026, never 26. Two-digit years are ambiguous and cause Y2K-like issues.

Pad months and days with leading zeros

Use 2026-08-07, not 2026-8-7. Consistent formatting helps parsing.

Include time if the system needs it

Use ISO 8601 format: 2026-08-07T14:30:00Z (if times matter). Otherwise stick to dates only.

Don't open/edit CSV files in Excel unnecessarily

If you need to, import it through Data, From Text/CSV, with date columns set to Text. To just look at it, use a text editor.

Document your date format

Include a note in your template or spec, such as 'All dates in YYYY-MM-DD format'.

Key takeaway

Use the format your import asks for, and YYYY-MM-DD when you have the choice. Then stop Excel converting dates on the way: import the CSV with date columns as Text, or set the date format before you save.

Import cleaner CSV data

Build guided CSV workflows that validate and transform data before it reaches your application.

Start building free