> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/ropa/merge.md).

# Merge processing activities

Learn how to merge duplicate or similar processing activities into a single one.

## Introduction

Merging processing activities lets you **combine several processing activities into a single one**, while keeping the information you choose and the items linked to them. It is particularly useful to **consolidate your record of processing activities**, remove duplicates and keep your documentation consistent.

One of the processing activities is kept as the **reference version**: you choose, field by field, the values to carry over from the others, then the others are deleted.

Merging requires write access to the record of processing activities. When task management, risk management or questionnaires are enabled in your workspace, you also need write access to these modules, so that the linked items can be moved to the reference version.

## Start a merge

You can start a merge from three places:

* **From the list, for several processing activities**: select the processing activities to merge (fewer than 30), click **Select a batch action**, then **Merge**. The comparison opens directly.
* **From the list, for one processing activity**: open the action menu at the end of its row and click **Merge**.
* **From a processing activity**: click the arrow next to the **Save changes** button, then **Merge**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-8190f1917a317822d47d2f0564ebeb1bf30465b1%2Fropa-merge-1.png?alt=media" alt="Merge entry in the action menu of a processing activity"><figcaption><p>The Merge entry of the action menu of a processing activity</p></figcaption></figure>

When you start from a single processing activity, the **Merging tool** window first asks you to choose the processing activities to merge it with: select them in **Select the objects you want to merge your data with**, then click **Next**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-96bff662141a6840b49e90135bc27c3566acaf9f%2Fropa-merge-2.png?alt=media" alt="Selection of the processing activities to merge"><figcaption><p>Select the processing activities to merge with</p></figcaption></figure>

## Choose the values to keep

The **Merging tool** window compares the processing activities side by side, one column per processing activity.

1. Tick, in the header of its column, the processing activity to keep: it becomes the **Reference version**. It keeps its identifier and its history. The other columns show the **Keep selected fields** badge: these processing activities are deleted once the merge is confirmed, and only the fields you select in them are carried over to the reference version.
2. For each field holding a single value, select the column whose value you want to keep.
3. For each field holding a list (purposes, datasets, recipients, security measures, etc.), tick the items to keep, whichever processing activity they come from: they are combined in the reference version.
4. Click **Merge**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-88ed8c645d68d90ef028cdc7407021d1348cb6a7%2Fropa-merge-3.png?alt=media" alt="Merging tool window comparing two processing activities"><figcaption><p>The Merging tool window</p></figcaption></figure>

To make the comparison easier:

* each field whose value differs from one processing activity to another is marked **Different**, and a counter shows the number of rows concerned;
* the table only shows the rows that differ; turn on **View all fields** to display all the comparable fields. Hidden identical fields keep the value of the reference version;
* the **Select all** button, under a column header, keeps the values of that column on all the rows that differ; **Undo selection** reverts it. An empty value never replaces a filled-in value.

The **Linked objects kept** section shows how many risk assessments, tasks and questionnaire responses are linked to the merged processing activities. They are automatically attached to the reference version, so nothing linked to the deleted processing activities is lost.

Once the merge is done, a message confirms it with a **Show item** link to open the reference version.

{% hint style="warning" %}
The processing activities other than the reference version are deleted when the merge is confirmed, and this cannot be undone. Check your choices before clicking **Merge**, and export the processing activities beforehand if you want to keep a copy of their content.
{% endhint %}

## Find duplicates automatically

To identify processing activities that are likely duplicates, click the arrow next to the **Create data processing** button, then **Data quality tool**. The detected duplicates are listed with a confidence score, and you can merge them from there.

{% content-ref url="/pages/bqGHctCxup4ShzpNv2Ax" %}
[Merging elements](https://doc.dastra.eu/en/features/general/merge.md)
{% endcontent-ref %}

## Typical use cases

| Case                              | Example                                                                        | Benefit                                           |
| --------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------- |
| **Consolidation**                 | Two processing activities "HR management" and "Staff management"               | Avoid duplicates and simplify maintenance         |
| **Reorganization**                | Similar processing activities created in several organizational units          | Keep a single, up-to-date processing activity     |
| **Harmonization across entities** | Equivalent processing activities documented separately by several subsidiaries | Make governance and global reporting easier       |
| **Record cleanup**                | Duplicates created during an initial import                                    | Improve the clarity and reliability of the record |

## Good practices

1. **Check compatibility**: only merge processing activities with identical or very close purposes.
2. **Keep the legal analysis consistent**: avoid merging processing activities that rely on different legal bases.
3. **Document your decision**: explain the reasons for the merge in an internal discussion on the reference version.

{% hint style="success" %}
Merging processing activities helps you keep a clean, up-to-date record while reducing the administrative workload, and you keep control over every value carried over.
{% endhint %}


---

# 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://doc.dastra.eu/en/features/ropa/merge.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.
