How to Duplicate Workbooks with All Data Included

Ciaran E. · 2026-01-28T16:31:29.487Z

Is it possible to duplicate workbooks, with all data included? ie not just blank columns

How to Duplicate Workbooks with All Data Included | Clay

Clay Support
APP
·
·
Currently, duplicating a table in Clay only copies the table structure and sources—not the data itself. [1] [2] [3] There isn’t a way to duplicate workbooks or tables with all data included.
If you want to copy data, you’ll need to export your table as a CSV and then import it into a new table. [4] Duplicating workbooks as a whole (with all data) isn’t supported yet.
Clay Support
APP
·
·
Did that answer your question?
Ciaran E.
·
·
hmmm ok - and for columns with nested JSON, would I have to set each value as a column so it nicely exports to csv?
Nicolas B.
·
·
Clara N. you could also send the data to your newly duplicated table with "write to other table" enrichment
Clay Support
APP
·
·
Yes, for columns with nested JSON, you’ll need to create child columns for each value you want to export. Click into the cell with the nested JSON, open the Cell details panel, and use “Add as column” to extract specific keys or endpoints. This way, each value becomes its own column, making your CSV export clean and readable. [1] [2]
Clay Support
APP
·
·
Did that answer your question?
Ciaran E.
·
·
Thanks Nicolas B. - the issue remains as described above though, as I have some columns with dozens of nested data points
Clay Support
APP
·
·
I understand this can be frustrating with many nested data points. I’ll connect you to a human agent who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Nicolas B.
·
·
Clara N. fair enough, write to other table would require mapping which works but is tedious compared to if clay allowed you to simply duplicate the table with all the data. Their suggestion is probably best then
🙏1
Nicolas B.
·
·
Cheers
Quentin R.
·
·
Hope this helps 👌🏼
Ciaran E.
·
·
Thank you Quentin! So given that this is the table, and it must be duplicated rather than moved (it will serve a different purpose), is #3 the best option? Looking at say the third column on Get call details, would I have to send each nested item individually? There are probably 100 or more nested items in the table so want to avoid clicking buttons as much as possible 🙂 thanks a mil
Quentin R.
·
·
Then option 3 makes the most sense. Sending that many fields sounds to me like an edge case so not sure how it behave, but it's pretty risk free operations so you can test safely 😊 An alternative would be to use AI in this table to summarize, or other transformation, to only send what will be used in the next table.
Quentin R.
·
·
You could also lookup row from other table in the one you sent me, if you think it's more helpful.

18 comments