> For the complete documentation index, see [llms.txt](https://easyedge.gitbook.io/easyedge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://easyedge.gitbook.io/easyedge/connect-to-assets/duplicate-assets.md).

# Duplicate Assets

The **Duplicate Asset** function allows you to quickly create a new Asset based on an existing one, without having to go through the entire configuration process again. This feature is particularly useful when adding multiple Assets of the same type.

***

## How to Duplicate an Asset

* The **Duplicate** option is available for all Assets in the system.
* To duplicate an Asset, open the **Actions** menu (⋮) and select **Duplicate**.

<figure><img src="https://3821385045-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDvVEo0tfCfsP8te90e3t%2Fuploads%2F3BKktYlAY1QRvWQsFjEm%2Fimage.png?alt=media&amp;token=9403c957-bf59-4aad-b184-520047873f95" alt=""><figcaption></figcaption></figure>

### Result of Duplication

* The duplicated Asset will keep the same **characteristics** as the copied Asset.
* If the original Asset is based on a **Custom configuration** or a **Library Asset Profile**, the duplicated Asset will maintain the same binding.
* The system automatically appends a suffix (e.g., “(1)”) to the duplicated Asset name. You can later rename it for clarity.

<figure><img src="https://3821385045-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDvVEo0tfCfsP8te90e3t%2Fuploads%2FeK0BSYPYVT1NLuhN8EmK%2Fimage.png?alt=media&amp;token=44e87a29-d1a1-4982-ab5b-d139fe4d6b47" alt=""><figcaption></figcaption></figure>

### Adjusting the Duplicated Asset

* After duplication, you should update the **Communication Settings** of the new Asset so that it can communicate with the correct physical device.
* The **Name** can also be updated to provide a better reference to the new Asset.
* By default, the duplicated Asset keeps the same **Data Fields and Tags** as the original. This means you don’t need to reprocess Data Fields after updating the communication settings or name.
  * Keep the current configuration if you want the duplicated Asset to have the same Tag structure as the copied one.
  * Only reprocess the Data Fields if you want to change the **Asset Modeling** or rebuild the Tag structure.

<figure><img src="https://3821385045-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDvVEo0tfCfsP8te90e3t%2Fuploads%2F0uSWYiaeYqH1cZ724aEi%2Fimage.png?alt=media&amp;token=faeff197-dd67-4e57-b8aa-d8aa597c822c" alt=""><figcaption></figcaption></figure>

***

## Notes

* In addition to using **Library Asset Profiles** to replicate Assets across multiple sites, the **Duplicate Asset** function simplifies the addition of identical Assets within the same system.
* Only the **Data Source** is duplicated. If the original Asset is already used in **Workflows** or **Data Streams**, these relations will **not** be duplicated. They must be configured separately.

{% hint style="info" %}
✅ This makes the process of scaling and managing Assets more efficient, while still ensuring flexibility for site-specific adjustments.
{% endhint %}