> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Duplicate or clone a table: which one you need
- URL: https://blog.jestor.com/duplicate-or-clone-a-table/
- Published: 2026-09-16T18:51:23.000Z
- Updated: 2026-09-16T18:51:23.000Z
- Author: Bruno Bannach

Choosing to **duplicate or clone a table** depends on one question: do you want the data as well? Duplicating copies the structure, the fields and the automations without the records. Cloning brings the records too. In **Jestor**, both are available, from different places.

## Why the distinction matters more than it appears

Copying a table with its records into a new client environment is a data exposure problem, not a convenience. The person who opens that copy sees everything the original held.

Copying without records is the safer default, and it is what people usually want when they say duplicate.

Where each one applies:

- A structure reused for a different client, without their predecessor's data
- An internal template rolled out to a similar process
- A test environment that needs real records to be meaningful
- A backup before a risky structural change

## Duplicate versus clone

| Aspect             | Duplicate           | Clone                  |
| ------------------ | ------------------- | ---------------------- |
| Fields             | Copied              | Copied                 |
| Automations        | Copied              | Copied                 |
| Records            | Not copied          | Copied                 |
| Typical use        | Reusing a structure | Testing with real data |
| Data exposure risk | None                | Requires care          |

## Step by step to copy a table

1. **Decide whether you need the records**, which determines the method.
2. **Use duplicate** to copy the structure and automations only.
3. **Use clone**, available in the table's options menu, when you need the records too.
4. **Rename the copy immediately**, so the two are never confused.
5. **Review the copied automations**, since they may point at the original table.
6. **Check permissions** on the copy before sharing it.

## Why reviewing copied automations matters

An automation copied along with a structure may still reference the original table, the original fields or an external destination. Running it unchecked can write to somewhere you did not intend. A quick review before enabling anything is the difference between a useful copy and a confusing incident.

- **Structure without data:** duplicate covers the common case
- **Records included:** clone when real data is genuinely needed
- **Automations carried over:** worth reviewing before enabling
- **Useful for agencies:** a proven structure reused per client

## Frequently Asked Questions

### Does duplicating a table copy the records?

No. Duplicating copies the structure and automations without the records. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### How do I copy a table with its data?

Use the clone option, available in the table's options menu.

### Should I check anything after copying?

Yes. Review the copied automations, since they may still reference the original.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.