How to clone a package

Cloning creates an independent copy of a package and all its contents. This is useful for creating variants, backups, or starting a new model based on an existing one.

Clone a package

1. Right-click the package you want to clone in the Explorer
2. Select Clone Package
3. A copy appears in the Explorer with “(Copy)” appended to the name
4. Rename it as needed with F2

Cloning runs in batches on the server, so large packages clone too. A progress toast — Cloning “<name>” — shows how far it has got.

What’s cloned

The clone is a deep copy — everything in the package tree is duplicated:

• The package and all nested sub-packages
• All elements and relationships
• All diagrams (including node positions, edge waypoints, and formatting)
• All catalogs (including column configuration)
• View links on its diagrams. A link to a view inside the package points to the copy of that view; a link to a view outside the package still points to the original
• All property values

The cloned elements are independent — changes to the clone don’t affect the original, and vice versa.

What’s not cloned

• External references (imports, classifier links) point to the same M2 types — they’re shared, not duplicated
• The clone is created in the same project as the original

Owned elements

Owned (nested) elements always live in their owner’s package. Cloning or moving an element takes everything it owns with it. An element that owns more than 2,000 nested elements can’t be cloned or moved on its own — clone or move its package instead.

Tips

• Clone an M1 model package to create an alternative scenario (e.g., “Current State” vs “Target State”)
• Clone an M2 metamodel to create a variant without modifying the original
• After cloning, rename the package and its key elements to avoid confusion