> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/assets/move-an-asset-group-to-another-property.md).

# Move an asset group to another property

Move a whole asset group to a different property, including a property owned by another customer.

> **Where to find it:** On the web, open an asset group, open the **⋮** menu beside the group heading, and choose **Move to Another Property**.

1. Search for the **Destination property** by customer, property name, or address.
2. Select the destination and review the move details.
3. Choose **Move Asset Group**.

The group keeps its assets, attributes, files, service completion history, and recurring service settings. Existing jobs and inspection reports retain their original property. The group and both properties record the move in their timelines.

Automation settings stay unchanged. Recurring-service outreach uses the destination customer's contacts and property contact roles. If the destination property, customer, or group is inactive, it stays inactive and outreach remains subject to that status.

If the group is selected for an open visit, remove it from that visit's expected assets before moving it. Historical visits stay with their original property.

If the destination already has a group of the same type, including an inactive group, you need the **Create Multiple Asset Groups** permission to move another group there.

## Related guides

* [Transfer individual assets between groups](/field-operations/assets/transfer-assets-between-groups.md)
* [Merge and split asset groups](/field-operations/assets/merge-and-split-asset-groups.md)
* [Set or change an asset group's automation](/field-operations/assets/set-or-change-an-asset-groups-automation-automation-setup.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.withessential.com/field-operations/assets/move-an-asset-group-to-another-property.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.