---
schema_version: "1"
id: 9ec7ed90d07dacb61b0fcb5ee88e34abe6465c4dcfacff345f240c1370fac59c
title: Deprecated Root Relationships
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_cab_deprecated_root_relationships.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_cab_deprecated_root_relationships.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9b793fda6df49975b69bc92c19f9176cc93d105ef8b02dfb1d659ece7b404cf8
description: A root relationship represents a 1:1 relationship between a contact record and a data extension that acts as a source for contact information in Contact Builder. A root relationship can only exist between the contact record and a single data extension. That contact record relates via the contact key or contact ID to the data extension. The data extension used as part of the root relationship can contain only one row per individual contact. Each row in a root relationship represents a contact, and you cannot link to multiple rows for a single contact in a root relationship.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Deprecated Root Relationships

A root relationship represents a 1:1 relationship between a contact record and a data extension that acts as a source for contact information in Contact Builder. A root relationship can only exist between the contact record and a single data extension. That contact record relates via the contact key or contact ID to the data extension. The data extension used as part of the root relationship can contain only one row per individual contact. Each row in a root relationship represents a contact, and you cannot link to multiple rows for a single contact in a root relationship.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_contact_data-264-0-0-production-enus/0e4d875c-8c8c-4be4-8f13-c8278eafbbf9/images/icon_note.png)

Note

Populations replaced the root relationship functionality within Data Designer. You can only remove root relationships using Data Designer. Your existing root relationships remain in place until you actively remove the relationship. However, you must create root-type relationships using populations in Data Designer.

Root relationships create a single master record for contact information. Enabling several root relationships within an account can disrupt data relationships, especially for multiple primary key values. Ensure that you use only the Contact Key value as a primary key in root relationships. Limit the number of data extensions with root relationships to the contact record. Each root data extension must contain channel addresses, such as email addresses or mobile numbers. Prioritize channel addresses within Contacts Configuration.

For example, you could use a root relationship where the contact record does not represent the database of record. Use information imported from a CRM system into a data extension as the primary source of contact information.

You cannot link any root data extension to an attribute set.