Home
Events
Groups
Members

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps
Gtm Career Advice
Member Spotlight

Community Guidelines

Powered by Tightknit

Issue with CSV Import: How to Resolve Column Name Conflicts

Sabrina Iskandar

·

·

Why did this error occur when I tried to import the csv into a new workbook? How to overcome this without doing something as tedious as renaming columns? You should've made it possible by default to import columns with similar names from other workbooks, since it is in a separate workbook

Loading attachments

Issue with CSV Import: How to Resolve Column Name Conflicts | Clay

3 comments

· Sorted by Oldest

Clay
APP
·
·
Common CSV import issues include mixed separators, formatting problems, or column naming conflicts. Quick fixes: - Remove commas, colons, and semicolons from your CSV data - Use UTF-8 encoding with comma-separated values - Upload to Google Sheets first, then re-download as CSV - Keep filename short Column mapping: During import, you can modify column names and delete unnecessary columns in the mapping step without manually renaming in your original file. If you need further help troubleshooting the specific error, request human assistance by clicking "Talk to a person."
Sources: Import CSV [Clay 101] - Clay University How to import your CSV into Clay | Documentation | Clay University
Clay
APP
·
·
Hello Sabrina! Thanks for reaching out! Taking a look now!
Clay
APP
·
·
Hey Sabrina! Thanks for reaching out. Looks like you already have data in the table you are adding CSV Import as a source. Do you mind sharing the table link URL and a screenshot of the CSV Import headers? I can get some additional context based on that and help troubleshoot this!