Data Recovery for Deleted Rows in Database Mapping

Matthew H. · 2025-07-26 09:45:27.736911+00

Hi I have recently been working on on a table and whilst mapping some details from one table to another, a large portion of row data has been deleted which has affected 6,800 rows. It seems that most of the columns data has been deleted. Is there a way to retrieve this?

Data Recovery for Deleted Rows in Database Mapping | Clay

9 comments

· Sorted by Oldest

Clay
APP
·
·
Unfortunately, we cannot recover deleted row data after the initial undo window passes. When deleting rows, a brief confirmation alert appears in the bottom-right corner for a few seconds with an "Undo" option - we're unable to recover data after that point. Clay doesn't track row history or deletions, so if data is overwritten or deleted, there's no way to recover previous data directly from within the platform. The best option is to re-import or manually update the data. If you need further help, request human assistance by clicking on "Talk to a person."
Matthew H.
·
·
i did not manually delete the data. it just disappeared.
Matthew H.
·
·
https://app.clay.com/workspaces/395159/workbooks/wb_0szsnr7BGeyZwKgdYix/tables/t_0szsrmjEWvTEnrovTgo/views/gv_0szsrmjn3ZcD479UxjN
Matthew H.
·
·
without making any changes, the remainder of the data in the other rows that were present have disappeared
Bo (.
·
·
Hi Matthew, This can happen if the rows had dependencies on formulas or enrichments that were retriggered. When auto-update is on, any changes to formulas or linked data can cause the rows to rerun. If the data is outdated or no longer available from the source, it may disappear when rerun. Was the deleted data coming from a formula or enrichment that could have been retriggered? That’s usually the cause in cases like this. Let me know if you have more questions.
Hasnain R.
·
·
Yeah, that can happen if a bulk update or mapping step overwrites existing data. Here’s what to do: Go to your table and click the clock icon (top right) this opens the Table History. From there you can restore a previous version before the data was deleted. Clay autosaves versions, so unless it was disabled (rare), you should be able to recover everything from just before the mapping change.
Matthew H.
·
·
thanks for the help. The deleted rows had no dependencies on formulas or enrichments, they were imported from a CSV, but the ones that were deleted were the columns that i had mapped new data to (from another table). Once the new data was mapped, the original data started to disappear sporadically. I guess you cannot map new data from another table that already has data from another source.
Clay
APP
·
·
Hi Matthew! Thank you for flagging this - you’re absolutely right.
When you map data from one table to existing columns (especially ones that already contain data from a CSV or another source), Clay currently treats that as an overwrite rather than a merge. If you want to prevent this you can use a Merge column. To prevent that, use Write to Other Table instead. It gives you more control over how data is inserted and won’t overwrite existing values unless explicitly set to.
Let me know if there is anything else I can help with, otherwise I'll go ahead and close out the ticket for now. Feel free to reach back out if there are other questions!
Matthew H.
·
·
Many thanks. Makes sense!

Clay
APP
·
·
Unfortunately, we cannot recover deleted row data after the initial undo window passes. When deleting rows, a brief confirmation alert appears in the bottom-right corner for a few seconds with an "Undo" option - we're unable to recover data after that point. Clay doesn't track row history or deletions, so if data is overwritten or deleted, there's no way to recover previous data directly from within the platform. The best option is to re-import or manually update the data. If you need further help, request human assistance by clicking on "Talk to a person."
Matthew H.
·
·
i did not manually delete the data. it just disappeared.
Matthew H.
·
·
https://app.clay.com/workspaces/395159/workbooks/wb_0szsnr7BGeyZwKgdYix/tables/t_0szsrmjEWvTEnrovTgo/views/gv_0szsrmjn3ZcD479UxjN
Matthew H.
·
·
without making any changes, the remainder of the data in the other rows that were present have disappeared
Bo (.
·
·
Hi Matthew, This can happen if the rows had dependencies on formulas or enrichments that were retriggered. When auto-update is on, any changes to formulas or linked data can cause the rows to rerun. If the data is outdated or no longer available from the source, it may disappear when rerun. Was the deleted data coming from a formula or enrichment that could have been retriggered? That’s usually the cause in cases like this. Let me know if you have more questions.
Hasnain R.
·
·
Yeah, that can happen if a bulk update or mapping step overwrites existing data. Here’s what to do: Go to your table and click the clock icon (top right) this opens the Table History. From there you can restore a previous version before the data was deleted. Clay autosaves versions, so unless it was disabled (rare), you should be able to recover everything from just before the mapping change.
Matthew H.
·
·
thanks for the help. The deleted rows had no dependencies on formulas or enrichments, they were imported from a CSV, but the ones that were deleted were the columns that i had mapped new data to (from another table). Once the new data was mapped, the original data started to disappear sporadically. I guess you cannot map new data from another table that already has data from another source.
Clay
APP
·
·
Hi Matthew! Thank you for flagging this - you’re absolutely right.
When you map data from one table to existing columns (especially ones that already contain data from a CSV or another source), Clay currently treats that as an overwrite rather than a merge. If you want to prevent this you can use a Merge column. To prevent that, use Write to Other Table instead. It gives you more control over how data is inserted and won’t overwrite existing values unless explicitly set to.
Let me know if there is anything else I can help with, otherwise I'll go ahead and close out the ticket for now. Feel free to reach back out if there are other questions!
Matthew H.
·
·
Many thanks. Makes sense!