> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pentaho-data-mastering/configuring-merge-rules/adding-a-merge-rule/adding-merge-rules-in-bulk.md).

# Adding merge rules in bulk

You can add multiple merge rules at one time to control how matched data is merged to create Master Records. To create multiple merge rules at one time, import a JSON file that contains all the information for the merge rules.

Perform the following steps to create multiple merge rules at one time:

1. On the left navigation menu, click **Master Data**. The **Master Data** page opens.
2. In the **Merge Rules** card, click **Merge Rules**.

   The Merge Rules page opens.
3. Click **Add Merge Rule** > **Import Merge Rule(s)**.

   The Import Merge Rule(s) dialog box opens.
4. Browse to and select the JSON file that contains the merge rules information to import.

   **Tip:** You can drag and drop the JSON file into the Import Merge Rule(s) dialog box.
5. Click **Continue**.

   A confirmation message is shown in the top-right corner of the page and the merge rules are added to the merge rule table.


---

# 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.pentaho.com/pentaho-data-mastering/configuring-merge-rules/adding-a-merge-rule/adding-merge-rules-in-bulk.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.