Every table has 50k row limit? I have 500k+ Accounts
Yes, each table has a 50,000-row limit on paid plans. For your 500k+ accounts, you have several options:
Split into multiple tables - Divide your data into smaller, manageable tables based on logical criteria.
Enterprise Plan with Passthrough Tables - This bypasses the 50k limit by handling rows on a rolling basis, automatically deleting older rows while retaining a set number (default 100).
Exclusion system - Create a central exclusion table to filter entities without duplicating rows across tables.
The Enterprise Plan's Passthrough Tables feature is likely your best solution for handling 500k+ accounts seamlessly.
Did that answer your question?
What is Pass through, I don't want to delete any rows. I want to keep it for all 500k Accounts so that I can enrich
Passthrough Tables automatically delete rows after processing - they're designed for continuous data flow where you enrich data then send it elsewhere. The feature processes incoming data, enriches it, forwards it to a destination, then deletes the original entries to make room for new data. [1]
Since you want to keep all 500k accounts without deletion, Passthrough Tables won't work for your needs. For permanent storage of all records, consider Bulk Enrichment instead - it can handle millions of rows from your CRM, enrich them, and export back to systems like Salesforce without the rolling deletion. [2]
Alternatively, split your data into multiple 50k-row tables to stay within standard limits.
Was that helpful?
If you still need help with managing your 500k accounts or understanding enrichment options, I’m here to assist. Would you like to provide more details about what you’re trying to achieve so we can explore the best solution together?
I understand we can enrich millions of rows in Clay by brining it from Salesforce but I don't seem to find this option.
From there, select Salesforce as your source type, authenticate your account, choose your Salesforce object and list view, then add enrichments as normal.
Did that answer your question?
Ok so we can't control how many rows we want to enrich here. First work on limited set of data and than add more.
Additionally, you can use Sandbox Mode for safer experimentation - enable it in your table settings to create a locked copy using selected test rows, then publish successful configurations to your original table. [3]
This lets you validate logic, columns, and integrations on a smaller subset before committing resources to enriching millions of rows.
Did that answer your question?
Yes this makes sense.
Thanks for the help
You're welcome. If you have any more questions or need further assistance, feel free to ask. I'm here to help.
