Issues with Uploading Large Datasets to Clay: Need Assistance

Michiel de Vor · 2025-05-07 14:15:41.209997+00

Hey! I have a database with 320k rows that I want to upload to clay. I want to enrich these rows with domains. Currently I am trying to upload the list but it is not imported for 100%. It only gives me 36k rows when I upload the file. I saw that there is a row limit of 50k - is that correct? I also just tried to upload a file with 40k rows but now i only get 1300 rows back in clay. What to do ?

Issues with Uploading Large Datasets to Clay: Need Assistance | Clay

2 comments

· Sorted by Oldest

Channeled
APP
·
·
The current row upload limit in Clay is 50,000 rows per table. For your large files (320k or 40k rows), you'll need to split them into smaller chunks of 50,000 rows or less. To successfully import without losing data: 1. Ensure your CSV is UTF-8 encoded with comma-separated values. 2. Remove any "created at" or "updated at" columns. 3. Keep column count to 72 or fewer. 4. Use short file names. 5. If issues persist, try uploading your data to a public Google Sheet, then download as CSV and re-upload. To import: 1. Go to your Clay workbook 2. Click "Actions" > "Import From CSV" 3. Select your file 4. Choose to import to a new or current table 5. Complete the import process If you still encounter problems after following these steps, request human assistance by clicking on "Talk to a person" for further support.
Source: Import CSV [Clay 101] - Clay University
Daniel Kupka (Clay)
·
·
Hey Michiel, thanks for reaching out and sorry for the delay here. Yes, the current limit is 50k rows per table. I recommend breaking your database into smaller segments—each with 50k rows or fewer—and uploading them as separate tables. When uploading CSVs to Clay, you should ensure the following: ** The CSV file should not include "created at" or "updated at" columns. ** The CSV upload feature supports a maximum of 72 columns and 50,000 rows. Ensure your file is within these limits. ** Use UTF-8 encoded CSV files with comma-separated values for the most reliable results. ** If you encounter issues, try uploading your data to a public Google Sheet, then download it again as a CSV and attempt the upload once more. * Make sure the CSV file name is short. These steps help address common issues such as incorrect column separators and hidden formatting problems that can prevent successful uploads. If the issue still persists after going the above points, please share the CSV and I'm happy to dive in deeper :) If there's anything else I can assist you with, please let me know! 😊 Have a great Thursday, Daniel

Channeled
APP
·
·
The current row upload limit in Clay is 50,000 rows per table. For your large files (320k or 40k rows), you'll need to split them into smaller chunks of 50,000 rows or less. To successfully import without losing data: 1. Ensure your CSV is UTF-8 encoded with comma-separated values. 2. Remove any "created at" or "updated at" columns. 3. Keep column count to 72 or fewer. 4. Use short file names. 5. If issues persist, try uploading your data to a public Google Sheet, then download as CSV and re-upload. To import: 1. Go to your Clay workbook 2. Click "Actions" > "Import From CSV" 3. Select your file 4. Choose to import to a new or current table 5. Complete the import process If you still encounter problems after following these steps, request human assistance by clicking on "Talk to a person" for further support.
Source: Import CSV [Clay 101] - Clay University
Daniel Kupka (Clay)
·
·
Hey Michiel, thanks for reaching out and sorry for the delay here. Yes, the current limit is 50k rows per table. I recommend breaking your database into smaller segments—each with 50k rows or fewer—and uploading them as separate tables. When uploading CSVs to Clay, you should ensure the following: ** The CSV file should not include "created at" or "updated at" columns. ** The CSV upload feature supports a maximum of 72 columns and 50,000 rows. Ensure your file is within these limits. ** Use UTF-8 encoded CSV files with comma-separated values for the most reliable results. ** If you encounter issues, try uploading your data to a public Google Sheet, then download it again as a CSV and attempt the upload once more. * Make sure the CSV file name is short. These steps help address common issues such as incorrect column separators and hidden formatting problems that can prevent successful uploads. If the issue still persists after going the above points, please share the CSV and I'm happy to dive in deeper :) If there's anything else I can assist you with, please let me know! 😊 Have a great Thursday, Daniel