Shipped · August 23, 2026
Importing contacts works again
Excel files are recognized, imports no longer time out, and City, State, ZIP and County can finally be mapped. Here it is running on production.
Live in production · confirmed working
What the recording shows
| Moment | What you see |
|---|---|
| Upload | The drop zone reads “Supports .csv, .tsv, and Excel (.xlsx) files” — Excel is accepted now. |
| Mapping | City is auto-recognized (green check); State, ZIP code and County are offered as mapping targets. |
| Run | The import runs in the background instead of timing out — no “Server took too long.” |
| Done | “Import complete” with a count of what was created, updated and quarantined. |
If you still have the import screen open from before today, reload the tab — the old version may be cached in your browser.
What was reported
- Excel (.xlsx) files weren’t recognized on upload — only CSV showed up.
- Importing a file failed with “Server took too long,” so imports didn’t work at all.
- Columns like City had nowhere to map, and you couldn’t create City either because it’s a built-in field.
What was actually wrong
- Excel was filtered out. The upload only accepted CSV/TSV, so workbooks were ignored.
- The whole import ran in one web request. Every row was processed before the page responded, so any real-sized file ran past the time limit and gave up. Imports now run in the background and report progress.
- The mapping list was incomplete. It offered only the six identity fields plus your custom fields — the standard built-in fields (City, State, ZIP, County) were left out, so those columns couldn’t be mapped or created. They’re now in the list and recognized automatically.
About your earlier imports
A few imports had been stuck showing “processing” forever; their contacts had actually already been added, so they were marked complete. The ENDVBM import was re-run through the fixed tool, back-filling City and State onto 181 of those contacts that the old version had dropped — with no duplicates created.