# Conceptual, logical and physical models for Omnistudio

*Omnistudio Consultant Study Guide · Best Fit Solutions · Last updated October 27, 2026 · https://www.certifyforce.com/study-guide/omnistudio-consultant/best-fit-solutions/conceptual-logical-and-physical-models-for-omnistudio*

How to move an Omnistudio solution from business concepts to a logical entity model and then to physical objects: virtual entities for external data, logical versus physical optionality, consolidating entities with record types, master-detail versus lookup, standard versus custom objects, account data skew, and the objects that store Omnistudio components.

- Certification: Salesforce Omnistudio Consultant
- Exam section: Best Fit Solutions
- Study guide: https://www.certifyforce.com/study-guide/omnistudio-consultant

**Official exam objective:**

> Guide in the creation of a Conceptual Model, Logical Model, and Physical Model to support the business solution, including recommending optimal object design (standard vs. custom) to support Omnistudio artifacts.

## What the exam expects

- Explain what conceptual, logical and physical models each show, and walk an Omnistudio solution from one to the next.
- Model data that stays outside Salesforce as a virtual entity reached through an Integration Procedure or Salesforce Connect.
- Read a Salesforce ERD: logical versus physical optionality, master-detail versus lookup, record-type subtypes.
- Recommend consolidating similar entities into one object with record types, and decide standard versus custom objects from out-of-the-box features and licenses.
- Keep child records per account below the data skew threshold.
- Name the standard objects that store Omnistudio components on the Standard Runtime.

Key terms: **logical model** (business entities and relationships, no physical detail); **physical model** (objects, fields and relationship types in the org); **virtual entity** (in the logical model, not stored as an object); **record type** (subtype of one object); **master-detail** (required parent with cascade delete and inherited visibility); **data skew** (more than 10,000 child records on one parent).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Logical model | Business entities and relationships, no physical considerations | [Enterprise Data Architecture](https://developer.salesforce.com/blogs/developer-relations/2014/11/enterprise-data-architecture) |
| Virtual entity | No border in an ERD; data via external APIs or Salesforce Connect | [Data Model Notation](https://architect.salesforce.com/docs/architect/reference-diagrams/guide/data-model-notation) |
| Record-type subtype | Dashed border in an ERD | [Data Model Notation](https://architect.salesforce.com/docs/architect/reference-diagrams/guide/data-model-notation) |
| Master-detail | Cascade delete; detail visibility follows the parent | [Data Model Notation](https://architect.salesforce.com/docs/architect/reference-diagrams/guide/data-model-notation) |
| Contact to Account | Physically optional, logically required (ignoring private contacts) | [Data Model Notation](https://architect.salesforce.com/docs/architect/reference-diagrams/guide/data-model-notation) |
| Data skew threshold | More than 10,000 child records on one parent | [Design Your Data Model](https://trailhead.salesforce.com/content/learn/modules/large-data-volumes/design-your-data-model) |
| Platform license | Custom apps and core objects; no opportunities, leads, campaigns or forecasts | [Standard User Licenses](https://help.salesforce.com/s/articleView?id=sf.users_license_types_available.htm&language=en_US&type=5) |
| Omnistudio component objects | Omni Process, Omni Data Transformation, Omni UI Card | [Omnistudio Naming Conventions](https://help.salesforce.com/s/articleView?id=sf.os_omnistudio_naming_conventions.htm&language=en_US&type=5) |

## Check yourself

- Why might an architect consolidate three similar logical entities into one object?
- When should an entity be drawn as a virtual entity?
- Which two considerations decide between a standard and a custom object?
- Which Standard Runtime object stores both Omniscripts and Integration Procedures?

## Sources

- [Salesforce Data Model Diagrams (Data Model Notation)](https://architect.salesforce.com/docs/architect/reference-diagrams/guide/data-model-notation)
- [Designing Enterprise Data Architecture on the Salesforce1 Platform](https://developer.salesforce.com/blogs/developer-relations/2014/11/enterprise-data-architecture)
- [Design Your Data Model (Large Data Volumes)](https://trailhead.salesforce.com/content/learn/modules/large-data-volumes/design-your-data-model)
- [Standard User Licenses](https://help.salesforce.com/s/articleView?id=sf.users_license_types_available.htm&language=en_US&type=5)
- [Omnistudio Naming Conventions](https://help.salesforce.com/s/articleView?id=sf.os_omnistudio_naming_conventions.htm&language=en_US&type=5)
- [Omnistudio](https://help.salesforce.com/s/articleView?id=sf.os_omnistudio.htm&language=en_US&type=5)
- [Migrate From Managed Package Runtime to the Omnistudio Standard Runtime](https://developer.salesforce.com/blogs/2026/08/migrate-from-managed-package-runtime-to-the-omnistudio-standard-runtime)
- [Omnistudio Best Practices and Developer Tools Overview](https://trailhead.salesforce.com/content/learn/modules/omnistudio-development-essentials/dive-into-best-practices-technologies-and-developer-tools)
- [Business Rules Engine](https://help.salesforce.com/s/articleView?language=en_US&id=ind.business_rules_engine.htm&type=5)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 7 linked practice questions, and unlimited timed mock exams are included with the Omnistudio Consultant pack (USD $19): https://www.certifyforce.com/practice-exams