> For the complete documentation index, see [llms.txt](https://kb.bravegen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bravegen.com/carbon/core-concepts/reporting-entities/managing-entities/moving-and-merging-entities.md).

# Moving & Merging Entities

Reorganise your entity hierarchy by moving, merging, or splitting entities.

Use these actions to fix up your [entity](/carbon/core-concepts/reporting-entities.md) hierarchy after it's been created — for example, reorganising entities that Task Review placed directly below the root entity, combining two entities that turned out to be the same thing under different supplier identifiers, or correcting an entity that was merged by mistake.

{% hint style="warning" %}
Moving and merging entities can trigger a base year recalculation. Make sure any change is intentional before applying it, especially on entities with existing reported history.
{% endhint %}

## Moving an entity

Move a single entity by updating its **Parent** field on the entity's [Entity Details](/carbon/core-concepts/reporting-entities/managing-entities/entity-details.md) view. To move several entities at once, select them on the **Entities** table (Settings -> Entities) and apply the **Move To** bulk action.

Entities can't be moved by dragging and dropping them within the hierarchy.

## Merging entities

Merging combines two entities into one, reassigning all historical activity, sources, and inventory items from the merged entity onto the entity you merge into.

The primary place this happens is during [Task Review](/carbon/core-concepts/data-collection/tasks/task-reviews.md): when the system surfaces an Entity Identifier it doesn't recognise, map it to an existing entity instead of creating a new one, and the two are merged.

You can also merge an existing entity into another directly, from the three-dot actions menu on the **Entities** table (Settings -> Entities), by selecting **Merge** on the entity you want to merge away, then choosing the destination entity.

When entity B is merged into entity A, B's identifier is added to A as an **Alias** — see [Entity Details](/carbon/core-concepts/reporting-entities/managing-entities/entity-details.md). Data stays bound to the identifier or alias rather than to the entity record itself, which is what makes it possible to split a merge back apart later.

{% hint style="info" %}
There are currently no restrictions on what can be merged — any entity can be merged into any other, regardless of Entity Type or where each sits in the hierarchy.
{% endhint %}

## Splitting a merged entity

To reverse a merge, remove the alias from the destination entity's **Aliases** field on its [Entity Details](/carbon/core-concepts/reporting-entities/managing-entities/entity-details.md) view. This detaches that identifier — along with every source and inventory item recorded against it — back into its own separate entity.

## Locking the Entities table

A toggle at the top of the **Entities** table locks the hierarchy, blocking moving, merging, and splitting from that table. This lock is applied manually rather than automatically — turning it on only restricts changes made from the Entities table itself; the same actions remain available from each entity's [Entity Details](/carbon/core-concepts/reporting-entities/managing-entities/entity-details.md) view.