---
title: "Consolidating and Merging Dataset Records"
slug: "consolidating-and-merging-dataset-records"
updated: 2026-08-11T18:02:11Z
published: 2026-08-11T18:02:11Z
canonical: "knowledge.technolutions.net/consolidating-and-merging-dataset-records"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Consolidating and Merging Dataset Records

[Consolidate Records](/v1/docs/consolidate-records-and-the-effects-of-main-vs-duplicate) is a powerful tool for identifying and consolidating duplicate records in the database. Using this tool requires exercising caution and an understanding of how Slate identifies duplicates and merges records.

This article covers the matching criteria used in the Consolidate Records tool to match a main [dataset record](/v1/docs/datasets-overview) to a duplicate dataset record.

> [!NOTE]
> **💡** Dataset records are only considered a match if both records are associated with the same dataset.

The following order of duplicate searches is employed on candidate dataset records:

1. **Name + Related Dataset:** Exact match on name and related dataset record. For example, two Organization Contacts named *John Doe* are associated with the same Organization.
2. **Username + Related Dataset:** Exact match on username and related dataset record.
3. **Name + Address:** Exact match on name, street address, and postal code.
4. **Custom Unique for Matching Fields:** Fields marked as containing [unique IDs](/v1/docs/unique-for-merging), such as Common App ID, SIS ID.