Quick Answer
Monday.com CSV imports fail for five predictable reasons: row and column limits exceeded, status label values that don't match board options exactly, inconsistent date formats, a file size above 10MB, or board automations firing on imported items.
The fix: Validate your CSV structure before import — check row count, column count, status values, and date formats against your board configuration.
Why it happens: Monday.com maps CSV columns to board columns by header name, and maps values to dropdown options by exact string match. A single extra space or different capitalization causes silent failures.
Identify Your Exact Problem in 5 Seconds
Monday.com will tell you your import succeeded even when half your data is wrong. Match what you see to the root cause:
| What you see after import | Root cause | Jump to |
|---|---|---|
| Correct row count but Status columns are blank | Label mismatch — not a file problem | Fix 2 |
| Dates showing as numbers | Date format wrong | Fix 3 |
| Fewer rows than expected (no error shown) | Silent skip — status/dropdown mismatch | Fix 2 |
| "There was a problem uploading" | Row/column limit or file size | Fix 1 |
| Names in Assigned To imported as plain text | People column can't map from CSV | Fix 4 |
| Status changed itself after import | Board automation fired | Fix 5 |
| Only first tab of Excel file imported | Multi-tab file behavior | Fix 4 |
If your row count looks right but values are blank: you have a mapping problem, not a file problem. That distinction saves hours.
What Monday.com's Error Messages Actually Mean
"There was a problem uploading, please contact support." — File structure issue or size limit exceeded. Start by checking your row count (8,000 max for existing boards) and file size (10MB max).
"Please reduce the file size." — Your file exceeds monday.com's import limits. For existing boards: 100 columns and 8,000 rows. For CRM boards: 50 columns and 8,000 rows.
Items silently not imported (no error shown, lower-than-expected count) — Status or label values in your CSV don't match the options configured on your board. The import completes but skips non-matching rows.
"You've reached your upload limit for the time being." — You've hit the 100-file-per-account-per-hour rate limit. Wait and retry.
Import succeeds but all items show the wrong status — Board automations fired during import and changed status values. Disable automations before importing.
Fast Fix (90 Seconds)
If your monday.com import just failed, try this first:
- Check your row count — Open your CSV in a text editor and count rows. Existing board limit: 8,000 rows. CRM board limit: 8,000 rows.
- Check your file size — Must be 10MB or less. Compress or split if larger.
- Check your column count — Existing boards: 100 columns max. CRM boards: 50 columns max.
- Match your status values exactly — Go to your board, click a Status column, and copy the exact label text (including capitalization and spacing) into your CSV.
- Disable automations — Before importing, temporarily turn off any board automations that trigger on status changes.
If the import still fails or items are being silently skipped, continue below.
TL;DR: Monday.com CSV imports fail most often because status label values in your file don't exactly match board options, or the file exceeds platform limits. Validate your CSV before uploading — check row count, status values, date formats, and file size. Run your file through SplitForge Data Validator to catch mismatches before monday.com does.
Your project migration is due Friday. You've exported 3,000 rows from your old tool, cleaned the data, and opened monday.com's import wizard. You drag the CSV in, watch the progress bar, and see the success message — 3,000 items imported. But when you open the board, half the Status columns are blank. The Due Date column is showing numbers instead of dates. And your Assigned To column mapped to a plain text field instead of People.
Monday.com's import completed without errors. But your data is wrong.
Each error type was reproduced using monday.com's CSV import wizard, March 2026.
| Error / Symptom | Root Cause | Fix |
|---|---|---|
| "There was a problem uploading" | Row/column limit or file size exceeded | Check: 8,000 rows, 100 columns, 10MB |
| Status columns blank after import | Label values don't match board options exactly | Copy exact label text from board into CSV |
| Date column shows numbers | Date format wrong or inconsistent | Standardize all dates to YYYY-MM-DD |
| Items silently skipped (correct count, wrong data) | Status/dropdown mismatch — silent drop | Run validator before import |
| Wrong status after import | Board automations fired on import | Disable automations before uploading |
| Only first 100 columns imported | Column limit hit | Reduce to 100 columns, split file |
| Multi-tab file partially imported | Only first tab imports | Separate each tab into its own CSV |
| "You've reached your upload limit" | 100 files/account/hour rate limit | Wait 1 hour and retry |
| "Please reduce the file size" | File exceeds 10MB | Split file or compress data |
| Names in Assigned To show as plain text | People column can't be populated from CSV | Import as text, assign manually after |
| Email column rejected | Invalid email format in CSV values | Validate email format before import |
| Timeline column shows wrong dates | Start/end date format inconsistency | Both dates must be YYYY-MM-DD |
| Subitem rows not appearing | Subitems import as regular items | Convert to subitems manually post-import |
| Dependency column blank | Dependency references item names, not IDs | Add dependencies manually after import |
| CRM board only shows 50 columns | CRM board column limit (not 100) | Strip unused columns; CRM cap is 50 |
How Monday.com Compares to Other Import Systems
| Platform | Strict on data types? | Updates existing rows? | Deduplicates? | Safe date format | Max rows |
|---|---|---|---|---|---|
| monday.com | Yes on labels/status | No — append only | No | YYYY-MM-DD | 8,000 |
| PostgreSQL COPY | Yes — errors immediately | N/A (append only) | No | YYYY-MM-DD | Server limits |
| Google Sheets | No — silent coercion | Yes (paste over) | No | YYYY-MM-DD safest | 10M cells |
| Notion | Partial — silent drop | No — append only | No | YYYY-MM-DD safest | ~50K rows practical |
| NetSuite | Yes on references | Yes (Update mode) | No | Account date format | Import Assistant limits |
Monday.com is one of the strictest platforms for label/status values — but unlike PostgreSQL, it never throws an error. It silently drops non-matching values. That combination makes it the most likely to produce a "successful" import with wrong data.
Table of Contents
- Identify Your Exact Problem in 5 Seconds
- How Monday.com Compares to Other Import Systems
- Why Monday.com CSV Imports Fail
- Fix 1: Row, Column, and File Size Limits
- Fix 2: Status and Label Value Mismatch
- Fix 3: Date Format Errors
- Fix 4: Column Type Mapping Failures
- Fix 5: Board Automation Interference
- Common Scenarios
- Additional Resources
- FAQ
This guide is for: Project managers migrating data into monday.com, ops teams building new boards, CRM admins importing contact lists.
Why Monday.com CSV Imports Fail
Monday.com CSV imports fail for five structural reasons, not random ones. Understanding which reason applies to your file tells you exactly where to look.
The platform maps CSV columns to board columns by exact header name match. It maps dropdown and status values by exact string comparison — case-sensitive, space-sensitive, punctuation-sensitive. Any mismatch causes the value to be dropped silently, with no error in the import summary.
The most dangerous failure mode is the silent one: monday.com reports a successful import at the correct row count, but silently drops values that don't match board options. Your row count looks right but your data is wrong.
Fix 1: Row, Column, and File Size Limits
Monday.com enforces strict import limits that vary by board type. Exceeding any of these limits causes the upload to fail.
Limits for importing to an existing board:
- 100 columns maximum
- 8,000 rows maximum
- 10MB file size maximum
Limits for CRM board imports:
- 50 columns maximum
- 8,000 rows maximum
- 10MB file size maximum
Additional constraint: 100 file uploads per account per hour. If you're doing batch migrations, space them out.
If your file exceeds these limits:
- Split large CSVs — Use SplitForge CSV Splitter to divide files into batches of 7,500 rows (leaving a buffer below the 8,000 limit).
- Remove unnecessary columns — Every column in your CSV that isn't mapped adds to your column count. Strip unused columns before import.
- Check actual file size — Open your file manager and check the
.csvfile size, not the source spreadsheet. CSV files compress significantly compared to Excel.
Fix 2: Status and Label Value Mismatch
This is the most commonly missed error in monday.com imports. Status, dropdown, and label columns only import correctly when CSV values match board options exactly — character for character.
What "exactly" means:
In Progress≠in progress(capitalization)Done≠Done(trailing space)On Hold≠On-Hold(hyphen vs space)
When a value doesn't match, monday.com doesn't throw an error. It silently imports the row with that field left blank.
The silent failure trap — what this looks like in practice:
| Your CSV value | Board option | Import result |
|---|---|---|
in progress | In Progress | Field blank (no error) |
Done (trailing space) | Done | Field blank (no error) |
On-Hold | On Hold | Field blank (no error) |
In Progress | In Progress | Correct |
Monday.com reports a successful import regardless. You only discover the problem when you open the board and see empty status columns. This is the most commonly missed failure mode in monday.com imports.
How to fix it:
- Export your board's current status options — On your monday.com board, click any Status column header → Settings → Copy all label names exactly as shown.
- Open your CSV in a text editor — Use Notepad++ or VS Code (not Excel, which may auto-format).
- Find and replace non-matching values — Replace every variation in your CSV with the exact board label text.
- Validate before importing — Run your CSV through SplitForge Data Validator to catch column value mismatches against a reference set.
Preventive approach: Before building a large migration file, do a test import with 5–10 rows containing all your status values. Confirm every status maps correctly before running the full import.
Fix 3: Date Format Errors
Monday.com's date importer expects consistent date formats across the entire column. Mixed formats cause the column to fail silently or import as text.
Recommended format: Use YYYY-MM-DD (ISO 8601) for all date values. This format is unambiguous across all account locales — it's the safest choice whether your account is US, EU, or Asia-Pacific. Monday.com recognizes it regardless of regional settings.
Why not MM/DD/YYYY? Ambiguous on international accounts. 05/03/2026 reads as May 3 in the US but March 5 in Europe. YYYY-MM-DD has no ambiguity.
How to fix inconsistent dates:
- Open your CSV in a spreadsheet editor — Sort by the date column to bring inconsistencies together.
- Identify all date format variants — Look for written-out months (
March 15), slashes vs dashes, 2-digit vs 4-digit years. - Standardize to YYYY-MM-DD — Use find-replace or a formula (
TEXT(A1,"YYYY-MM-DD")) to convert all dates. - Export as CSV — Save as CSV (not XLSX) before importing.
Fix 4: Column Type Mapping Failures
Monday.com supports a defined set of column types for CSV import: Numbers, Text, Date, Email, Dropdown, Timeline, and Phone. Any CSV column that doesn't map correctly is imported as plain Text — no error shown.
What a broken mapping looks like:
| CSV column | Mapped as | Result | Should be |
|---|---|---|---|
Assigned To | Text | Names import as plain text strings | People (manual after import) |
Due Date | Text | Dates import as "2026-03-15" strings | Date |
Priority (with values like "High") | Text | Works — but no color/label logic | Dropdown (map manually) |
Email | Text | Imports but email features won't work | Email column |
The broken → fixed mapping example:
CSV column: Assigned To
Mapped as: Text ← what monday.com guesses by default
Result: "John Smith" appears in a plain text field, not as a
linked team member. Assignment features won't work.
Fix: Click the dropdown on the mapping screen → select
"People" column. Import as text first if the user
doesn't exist yet, then assign manually.
Columns that can't be imported via CSV:
- People/Assigned To — Import as text, assign manually after.
- Formula columns — Cannot be imported. Add manually after.
- Files/Attachments — Not supported in CSV import.
- Subitems — Import as regular items; convert to subitems manually.
- Dependencies — Cannot be imported. Set dependencies manually.
How to fix column mapping during import:
- On the mapping screen, review each CSV column header against the suggested board column.
- Click the dropdown next to any mis-mapped column to select the correct board column type.
- Click "Don't import column" for formula, attachment, and dependency columns.
- Unmatched columns become Text — Rename or remove these after import.
Multi-tab Excel files: Only the first tab imports. Export each tab separately as its own CSV.
Dropdown / Status / Label Import Rules
Reference this before building any import file that includes Status, Dropdown, or Label columns.
| Rule | Detail |
|---|---|
| Case-sensitive? | Yes — Done ≠ done |
| Space-sensitive? | Yes — Done (trailing space) ≠ Done |
| Multiple values allowed? | No for Status/Label. Yes for multi-select Dropdown (comma-separated) |
| New options created on import? | No — unrecognized values are dropped silently |
| How to find exact option text | Board column header → Settings → view all labels |
| Safe test approach | Import 5 rows with all your status values first |
| What "success" looks like | All status columns populated (not blank) after import |
Fix 5: Board Automation Interference
Monday.com automations run on imported items the same way they run on manually created items. If you have a "When status changes to Done → send email" automation, every imported row with Done in the Status column triggers that automation.
Common automation problems during import:
- Status changes automatically after import (automation triggered)
- Team members receive notification emails for thousands of imported items
- Items move between boards or groups automatically
Fix:
- Go to your board → Click the Automations icon (lightning bolt, top right).
- Turn off all automations before starting your import.
- Import your CSV.
- Verify data is correct.
- Re-enable automations.
This takes 2 minutes and prevents hundreds of unwanted notifications.
Common Scenarios
Migrating from Asana or Trello
Asana and Trello exports use different status terminology than monday.com. Asana uses Complete / Incomplete. Trello uses Done / In Progress / Backlog. Neither matches monday.com's default labels.
Before importing: export your monday.com status options, then build a find-replace map from your old tool's terminology to monday.com's exact labels. Run that substitution on your CSV before uploading.
Importing CRM Contact Lists
CRM imports to monday.com CRM boards have a stricter 50-column limit. Large contact exports from Salesforce or HubSpot often include 80–120 columns. Strip any column you don't need in monday.com before importing — this is faster than remapping 100 columns in the wizard.
The privacy consideration: monday.com processes your contact data on their servers when you upload. For contact files containing email addresses, phone numbers, or deal values, validate and clean your CSV locally first using SplitForge Data Validator before uploading.
Recurring Imports from External Sources
Monday.com doesn't have a native scheduled CSV import. Each import adds new rows — it doesn't update existing ones. Importing the same CSV twice creates duplicates. If you need recurring imports, use monday.com's API or a third-party integration rather than manual CSV uploads.
Additional Resources
Official Monday.com Documentation:
- Import from Excel/CSV to monday.com — Official import limits, column types, and step-by-step wizard guide
- Import from Excel to monday CRM — CRM-specific limits and field mapping
CSV Standards:
- RFC 4180: CSV Format Specification — Official CSV structure standard
- Unicode UTF-8 Standard — Character encoding reference for international data
Related Guides:
- MDN File API — How browsers handle file reads (relevant for local validation)
For a complete breakdown of CSV import errors across all platforms, see our CSV import errors complete guide.