Duplicate a project
Clone an entire project, units, sheets, items, attachments, and column setup, as a starting point for a new build.
Duplicating clones an entire project. Use it when the next build will be very similar to a finished one, duplicate, then edit the few things that differ. For a more reusable starting point across many future builds, save as template instead.
Steps
Open the source project.
From the project menu (top-right), choose Duplicate project.
Type a name for the new project. Address, customer, and other identifying fields can be edited after creation.
Confirm. The new project appears in the project list within a few seconds.
What gets cloned
| Cloned | |
|---|---|
| Units (names, order) | Yes |
| Per-unit and per-project sheets | Yes |
| Items, attribute values, classifications, notes | Yes |
| Image attachments | Yes |
| Custom columns and column hide/show settings | Yes |
| Scope overrides | Yes |
| Decision-maker notes | Yes |
What does not clone
- Status, the new project starts in Draft, regardless of source.
- Completion timestamps on sheets, the new project's sheets start in editing state.
- Comments and audit log, those are anchored to the source items.
- Share links and exports, the new project gets its own.
Versus save-as-template
| Use duplicate when… | Use save-as-template when… |
|---|---|
| You need exactly one similar project right now. | You want to make this structure a reusable starting point. |
| The customer-facing data overlaps significantly (e.g. same architect's spec). | You want a clean, image-free starting point. |
| You want attachments to come with you. | You want each new project to start image-free. |
Performance
Like copying a unit, duplicating involves cloning every attachment in storage. Larger projects take longer, wait for the success toast before navigating.