All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Duplicate a unit or folder, with or without its records

Copy the structure of a unit or a folder, with its fields, groups, views and permissions, in one step, and choose whether to copy the records too.

6 min

This feature may not be turned on for your account yet. Contact support to turn it on.

Before you start · for owners
The permission to create units
  • You need: The permission to create units

Steps

1
Open the unit’s or folder’s menu and choose Duplicate.
2
Leave New name empty to keep the original’s name, or type a new one. You can choose a Folder for the copy.
3
Under Records, choose Structure only, or the option that copies the records too.
The window shows how many records will be copied, and whether that’s over the limit.
4
Decide whether the fields are shared with the original (Share with the original, the default) or independent (Give the copy its own).
5
Press Duplicate.
The copy appears, with a list of warnings for anything that wasn’t copied.

What’s copied?

Part
Copied?
Fields, their settings and their order
Yes
Groups and their conditions
Yes
Saved views, Kanban boards, filters, totals and column layout
Yes, and they point to the copy’s fields
The team’s default view
Yes
Role levels
Yes, copied from the original
The duplicate rule
Yes
Relations
Only between two units copied together
Records
Only if you choose to
Members’ personal default views
No

Shared or independent fields

By default, the copy shares the same field definitions as the original, so an option you add once shows in both units. The records stay separate. See Share a field across several units, or copy it to them.

These are always copied as independent fields: system fields, the serial number (each unit has its own counter), and every field that points to another one, such as lookup, rollup, calculation and catalog fields.

Relations

Duplicating a single unit doesn’t create any relation, because a relation needs two sides. Duplicate the whole folder so the relations between its units are rebuilt. Lookup and rollup fields that depend on a relation that wasn’t copied show in the warnings.

Copying records

Only the records you can see are copied. They keep their original creation date, and their files are copied as new files. The copy’s duplicate rule may refuse some rows, and those show in the warnings.

Unit names and field labels don’t change. If the original unit is deactivated, the copy is deactivated too.

If something goes wrong

What you see
Why
What to do
The copy has no relations
You duplicated a single unit.
Duplicate the whole folder, or add the relation by hand: see Link units with relations.
The number of records is over the limit
You can see more than 2,000 records.
Copy the structure only, then import the records.
A lookup or rollup field shows in the warnings
Its relation wasn’t copied.
Create the relation, then add the field again.

A real example

Shield Security Co.
The situation

The company opened a Jeddah branch and wants the same system as in Riyadh.

What they did
  1. They duplicated the whole “Operations” folder, without records.
  2. They kept the fields shared, so the status options stay the same in both branches.
The result

The Jeddah branch was ready in minutes, with its contracts and visits linked just as in Riyadh.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Up to 25 units and 500 fields in one duplicate.
Up to 2,000 records in one duplicate. For a folder, the limit counts all its units together.
Copying records is optional, and off by default.
For more than 2,000 records, use import.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.