---
title: "Discussion on \"Master-Detail vs Lookup: Salesforce Relationship Decision\" | Hashnode"
description: "Discussion on \"Master-Detail vs Lookup: Salesforce Relationship Decision\". Two custom objects, one with a parent reference to the other. Master-detail or lookup? The choice is permanent for practical purposes and affects sharing, rollups, cascades, and migration paths. Five criteria decide it cleanly."
url: "https://hashnode.com/posts/master-detail-vs-lookup-salesforce-relationship-decision/6a53c39172b7c2ef215595e4"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Master-Detail vs Lookup: Salesforce Relationship Decision](https://sapotacorpvn.hashnode.dev/master-detail-vs-lookup-salesforce-relationship-decision?utm_source=hashnode&utm_medium=feed)

Two custom objects, one with a parent reference to the other. Master-detail or lookup? The choice is permanent for practical purposes and affects sharing, rollups, cascades, and migration paths. Five criteria decide it cleanly.

Jul 12 · 8 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#salesforce](https://hashnode.com/tag/salesforce)
-   [#data-model](https://hashnode.com/tag/data-model)
-   [#schema](https://hashnode.com/tag/schema)
-   [#apex-development](https://hashnode.com/tag/apex-development)
-   [#relationships](https://hashnode.com/tag/relationships)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.