> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/scenarios/advanced-actions/merging.md).

# Scenario Merging

Scenario Merging lets you consolidate changes from one scenario (source) into another (destination). Use it when multiple teams have worked on separate scenarios that need to be combined.

**Best for** — Independent teams working on non-overlapping parts of the org. The less overlap between scenarios, the smoother the merge.

## How to Merge

1. Open the destination scenario
2. Go to Toolbar > **Data Management** > **Merge Scenario**

<figure><img src="/files/P5VLLPK5u7g5JySOKYV6" alt=""><figcaption></figcaption></figure>

3. Select the source scenario from the dropdown

<figure><img src="/files/9QuyOBMuOM1AIBW0w8sT" alt=""><figcaption></figcaption></figure>

4. **Select Records** — choose All or a filtered subset
5. **Select Fields** — choose All fields or specific attributes (e.g., salary only)
6. Review the summary (records, fields, destination backup info)
7. **Conflict Review** — see conflicts and resolve (details below)

<figure><img src="/files/lrTXkOgXAr71K0sdEJ3l" alt=""><figcaption></figcaption></figure>

8. Click **Merge**

A backup of the destination scenario is automatically created before merging.

## No Conflicts (Independent Teams)

If the two scenarios modified completely different positions (e.g., one owns Engineering, the other owns Sales), no conflicts appear. Select **Merge All Fields to Destination** and click **Merge**. The merged changes appear as separate org branches — use **Make Root** on each top node if they should remain independent.

## With Conflicts (Overlapping Changes)

Conflicts occur when both scenarios modified the same position (different managers, different salaries, one closed while the other edited).

**Current resolution** — All-or-nothing. "Merge All Fields to Destination" makes the source win for all conflicts. If you want the destination to keep its values, cancel and coordinate manually.

Use the **Show only conflicts** filter to review what you'd be overwriting before deciding.

## When Not to Use Merge

* Scenarios with significant overlap — coordinate in a single shared scenario instead
* Final approved scenarios — don't merge into them; create a new scenario
* Scenarios built on different Main Org baselines

## Troubleshooting

<table><thead><tr><th width="263.3515625">Problem</th><th>Solution</th></tr></thead><tbody><tr><td>Duplicate positions after merge</td><td>Both scenarios created the same new position — delete one duplicate</td></tr><tr><td>Broken hierarchy after merge</td><td>Click the orange broken hierarchy icon > reassign managers to reconnect</td></tr><tr><td>Can't see merged changes</td><td>Clear all filters; confirm <strong>Show After</strong> mode is active</td></tr><tr><td>Merged wrong scenario</td><td>Restore from the automatic backup created before the merge</td></tr></tbody></table>

## Related Articles

* [Scenario Comparisons](/scenarios/comparisons.md) — Compare without merging
* [Scenario Refresh](/scenarios/advanced-actions/scenario-refresh.md) — Update scenario with Main Org changes
* [Bulk Operations](/scenarios/using-scenarios-basics/bulk-operations.md) — Make the same change across multiple positions


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agentnoon.com/scenarios/advanced-actions/merging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.