Issue with Duplicating Rows During Table Column Import

Adi S. · 2026-01-10T16:52:26.213Z

Hello Team! I am trying to import different columns from different tables. These columns have the same rows (company), but when I send it, it is duplicating. Please check the screenshot attached. When I deduplicate, it deletes new columns or old columns. I want to keep the columns, but only match them to the existing Domain Normalized column, not create new duplicate rows. Every table has Domain Normalized column. It was created in Table 1, then I kept sending it to consecutive tables. When I send columns from two different tables of the same company, they create new rows. I tried sending one of the table's columns via Lookup, but it returned 0 records found. I checked 1000 times, and the name of the column is exactly the same. Please help ASAP. Please let me know if you need more information from me. Thanks.

Issue with Duplicating Rows During Table Column Import | Clay

Clay Support
APP
·
·
To avoid duplicates when importing columns from different tables, use the "Write to Other Table" integration and map your columns carefully. Make sure you match the "Domain Normalized" column as the key for merging—this ensures new data updates existing rows instead of creating duplicates. If you use "Send table data," always map to existing columns rather than creating new ones. This way, you keep all your columns and avoid row duplication. [1] [2] [3]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the duplicate rows issue, I’m here to assist. Would you like to provide more details about the tables or the process you’re using so we can continue troubleshooting?
Adi S.
·
·
It is redirecting me to export - send table data. This is what I have been doing.
Clay Support
APP
·
·
When you use "Send table data" and map columns, each row is sent as-is. If you send the same company (like "Domain Normalized") multiple times, it creates new rows instead of updating existing ones. To avoid duplicates, make sure you're mapping to existing columns in the destination table, not creating new ones. After sending, use the "Add to column" or "Map to existing column" options to update existing rows rather than adding new ones. This keeps your data aligned and prevents duplicates. [1] [2] [3]
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help with avoiding duplicate rows when sending table data, I’m here to assist. Would you like to share more details about the tables or the steps you’re taking so we can continue troubleshooting?
Adi S.
·
·
Ok, I am sending 3 columns from table 2, and 2 columns from table 4 to table 5. The Domain Normalized column was originally made in Table 1; it is being sent to every consecutive table. I refrained from sending "Domain Normalized" mulitple times to table 5 from different tables. But whenever anything is sent to table 5 from a different table, it automatically creates new rows. Even when i create columns in table 5 and map the sent columns to them it comes in new rows. Pls check the screenshots.
Clay Support
APP
·
·
When you send data from different tables to a destination table, each send creates a new row by default. To avoid duplicates and merge data into existing rows, make sure you map the sent columns to existing columns in the destination table, not create new ones. After sending, use the "Add to column" or "Map to existing column" options to update existing rows instead of adding new ones. This keeps your data aligned and prevents duplicates. If you’re still seeing duplicates, double-check that you’re not accidentally creating new rows instead of updating existing ones. [1] [2]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the duplicate rows issue, I’m here to assist. Would you like to provide more details about the tables or the steps you’re taking so we can continue troubleshooting?
Adi S.
·
·
OK, I go to Table 4, click "action", click "export", click "send table data", click on "destination", select Table 5 from the dropdown, select "send row" then select 3 rows, click save and run. It got sent in table 5 as new rows. At this point, I haven't clicked anything in the Table 5. Even when I map them to existing columns, they get entered in new rows.
Clay Support
APP
·
·
"Send table data" always creates new rows by design - it doesn't merge data into existing rows based on matching values like Domain Normalized. [1]
The mapping you're doing happens after the data is sent, not during the send process. When you map to existing columns using "Add to column" or "Map to existing column," you're just organizing the data that's already been created as new rows. [2]
To merge data without duplicates, use the "Write to Other Table" integration instead. This lets you map columns properly and can update existing rows rather than always creating new ones. [3]
Clay Support
APP
·
·
Did that answer your question?
Adi S.
·
·
No, "Write to Other table" feature is deprecated and takes me to send table data.

25 comments