Import problems

Most import problems have one of these causes. This article routes you to the fix; for the full import flow see "Create a list and import a file" and "File import details."

Columns look wrong, or characters are garbled#

ListPlus detects your file's delimiter and character encoding automatically — see "File import details" for exactly how. If a value ended up in the wrong column, or accented characters show as odd symbols, the most common cause is a source file that isn't cleanly formatted; re-export it as CSV or Excel from the original tool and import again. If the type is wrong (for example an email column detected as plain text), fix it in List Settings → Schema — see "How column type detection works."

No header row detected#

ListPlus expects a header row and skips any preamble rows above the data table automatically. If your first row looks like data rather than column names, ListPlus treats the whole file as headerless and names the columns _1, _2, and so on — add a proper header row to your source file and re-import, or rename the columns after import.

Google Sheets link won't import#

The sheet must be shared as "Anyone with the link can view." Otherwise you'll see an error asking you to make the file publicly accessible, or a Google Sheets Import dialog with Download as CSV and Download as Excel buttons — download the file and select it on the New List page. You can also connect your Google account instead (Pro) — see "Connecting a CRM, spreadsheet or other app."

File too large#

Every import format is capped at 100 MB; a larger file shows "File too large. Maximum size is 100MB." Split the file or remove unneeded columns and try again.

Only some rows were imported#

If your import is larger than your plan's remaining record capacity, ListPlus imports what fits and shows "Importing X of Y rows due to your plan's record limit." — see "What is the record limit?" for the exact numbers and how to free up space or upgrade.

Related topics: create-list-and-import-file · import-file-details · column-detection · record-limit · not-enough-credits · contact-support.

FAQ#

Why did my columns come out wrong after importing?#

Delimiter and encoding are detected automatically, so this is usually either a wrong detected column type (fix it in List Settings → Schema) or a source file that isn't cleanly formatted (re-export it as CSV or Excel and re-import). See "How column type detection works" for fixing types.

My imported text shows strange characters instead of accents#

Re-save the file as UTF-8 in the original tool and import again — see "File import details" for how encoding is detected.

ListPlus named my columns "_1", "_2" instead of using my headers#

This happens when ListPlus decides your first row looks like data rather than column names, so it treats the file as headerless. Add a real header row to your source file and re-import, or just rename the generated columns after import.

Why won't my Google Sheets link import?#

The sheet must be shared as "Anyone with the link can view." Otherwise you'll see an error asking you to make the file publicly accessible, or a Google Sheets Import dialog with Download as CSV and Download as Excel buttons — download the file and select it on the New List page. You can also connect your Google account instead (Pro).

I get "File too large" when I try to import#

You'll see "File too large. Maximum size is 100MB." — see "File import details" for the size limit per format.

My import only brought in some of my rows#

Your plan's record limit was reached partway through the file, so ListPlus imported as many rows as still fit and shows "Importing X of Y rows due to your plan's record limit." Delete unneeded records or lists to free up space, or upgrade your plan — see "What is the record limit?"

Do I need to clean up my file before importing?#

No — delimiter and encoding are detected automatically; see "File import details" for what's automatic and how to skip a column.

None of this fixed my import — what now?#

Contact support with the file (or a small sample that reproduces the problem) and what you expected to see — see "Contact support" for how to reach us.