How to Fix Notion Import CSV Not Showing All Columns or Data
In this tutorial, you'll learn about How to Fix Notion Import CSV Not Showing All Columns or Data. We cover key concepts, practical examples, and best practices.
Notion imports CSV files by mapping columns to database properties. When imported data is missing columns, has wrong data types, or skips rows, the CSV header row is missing, delimiters are inconsistent, or the data format does not match Notion's expected types.
The Problem
You import a CSV file (File > Import) and the resulting database has fewer columns than the CSV. Or some columns have "Unrecognized" data or empty values.
Wrong approach — manually re-entering all the data from the CSV.
The Fix
Check the CSV file format before importing:
1. Open the CSV in a text editor (not Excel)
2. Verify the first row contains column headers
3. Headers should be simple text: "Name", "Price", "Date"
4. Avoid special characters in headers
Use the column mapping dialog during import:
1. During import, Notion shows detected columns and their types
2. For each column, select:
- "Map to property" → choose an existing or new property
- "Don't import" → skip the column
3. Verify the detected "Type" matches your data (Text, Number, Date, Select)
For date columns that import as text:
1. Ensure dates are in ISO format: 2026-01-15 or 2026-01-15T10:30:00
2. Regional formats (01/15/2026) may be parsed as text
3. Convert dates in the CSV before importing
4. Use a consistent date format throughout the file
Expected output:
All CSV columns map correctly to database properties
Data types are correctly inferred (Number, Date, Text)
All rows import without data loss
Prevention Tips
- Clean CSV data before importing: remove empty rows, standardize dates, remove extra commas
- Keep CSV headers simple and unique — avoid duplicates
- Test import with 5-10 rows first before importing the full file
- Use "Text" type for properties that should not be auto-typed (ZIP codes, IDs)
- After import, check the "Unrecognized" property group for unmapped data
Common Mistakes with import csv
- Mixing let bindings with <- bindings in do notation, producing type errors
- Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
- Non-exhaustive pattern matches that compile with warnings then crash at runtime
These mistakes appear frequently in real-world NOTION code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.
Practice Exercise
Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.
This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.
FAQ
Related: DodaTech's CSV Import Validator analyzes your CSV file for common issues — missing headers, inconsistent delimiters, date format mismatches — before you import into Notion. Use with DodaZIP for data preparation.
Built by the developers of DodaTech
Doda Browser, DodaZIP & Durga Antivirus Pro