> 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/merge-and-split-asset-groups.md).

# Merge and split asset groups

Combine groups into one, or divide a group's assets into new groups. These actions are available on the web for groups on the same property with the same asset group type.

> **Where to find it:** Open an asset group and use the **⋮** menu beside **Edit** in the Asset Group header. **Merge Asset Group** appears only when the property has more than one group of the same type.

## Merge groups

1. Choose **Merge Asset Group** from the **⋮** menu. The group you opened appears on the left.
2. Choose another group under **Merge into** on the right. The selected group always survives; all assets in the current group move into it.
3. Check the warning for the current group's description and any differing recurring services that will be deleted.
4. Choose **Merge … into …** to finish. Essential opens the surviving group.

The surviving group's schedules stay unchanged. All other participating groups' schedules are deleted. Assets and their completion history move into the surviving group. Reports move there too, with submitted answers and their original group description preserved.

The other groups leave the active group list. Their files, custom fields, and timeline remain available through their history pages. An unfinished bulk import for a merged group opens its history page; start a new import from the surviving group. Future open visits that explicitly refer to those groups are updated to refer to the survivor.

## Split a group

Your role needs permission to create multiple asset groups.

1. Choose **Split Asset Group** from the **⋮** menu.
2. Select the assets to move — search to narrow the list — and add an optional description for the new group.
3. Choose **Split … into …** — for example, "Split 3 assets into Roof units". Use the confirmation link to open the new group.

Each split creates one new group. To divide a group several ways, run **Split Asset Group** again on the remaining assets.

The new group receives an independent copy of the original recurring service schedules, including filters, settings, recurrence anchors, and completion holds. Existing tasks and outreach batches are not copied. The copied schedules participate in normal scheduling afterward.

Reports and the original schedules stay with the original group. Unselected assets stay there too. Moving every asset leaves the original group empty and available.

## What stays with each asset

Assets retain their attributes and service completion history. Submitted report answers remain unchanged. Both operations record timeline entries on all participating groups.

If another user changes a group before you confirm, Essential asks you to check the selection again. Resulting groups must respect the asset type's per-group limits.

## Related guides

* [Transfer assets between groups](/field-operations/assets/transfer-assets-between-groups.md)
* [What an asset group page shows](/field-operations/assets/what-an-asset-group-page-shows.md)
* [Per-group asset limits](/field-operations/assets/why-cant-i-add-more-asset-items-per-group-limits.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/merge-and-split-asset-groups.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.