---
slug: data-import-errors
title: Data Import Errors
section: Reference
description: Resolve file import failures, connector import failures, and common parsing issues.
listed: false
---
# Data Import Errors

**Use this page when a file import fails, a Connector import fails, or data loads but looks wrong (dates or numbers parsed as text, shifted columns, and similar issues).**

If you are blocked, the fastest path is usually: **fix the shape, re-import, then validate with a small sample.**

## File imports

### Bad delimiter or shifted columns

**Symptoms**: columns look shifted, values spill into the next column, or rows look misaligned.

Try this:

1. **Confirm** the file is actually CSV vs TSV.
2. **Check** for quoted fields (commas inside quotes can break simple parsers).
3. **Re-import** with an explicit delimiter setting if one is available.

### Wrong types (numbers as text, dates not parsed)

**Symptoms**: dates sort incorrectly, numbers behave like strings, or Charts and Pivot Tables do not recognise metrics.

Try this:

1. **Re-import** and set type overrides if available.
2. **Check** locale and format (for example, `DD/MM/YYYY` vs `MM/DD/YYYY`).
3. **Confirm** header rows are detected correctly.

### Very large files

Try this:

1. **Validate** with a small sample first, so you know parsing is correct.
2. **Pre-filter** columns and rows upstream if possible.
3. **Prefer Parquet or Arrow** for very large datasets when you can.

## Connector imports

Try this in order:

1. **Validate** the connection first (host, port, auth, TLS).
2. **Start small**: run a simple query like `SELECT 1` or pull a small table.
3. **Confirm** the selected schema and table exist, and permissions are granted.

## Next steps

If you have an error message, include it when contacting support.

## Related pages

- [Importing Data](/docs/data-import)
- [Connection Problems](/docs/connection-problems)
- [Performance Issues](/docs/performance-issues)
- [Connectors](/docs/connectors)