5.1 The Salesforce Data Model & Standard Objects

The Salesforce Data Model & Standard Objects

Quick Summary: Salesforce structures business data using a relational database model where database tables correspond to Objects, rows correspond to individual Records, and columns correspond to Fields. Salesforce provides pre-built Standard Objects (such as Lead, Account, Contact, Opportunity, Case, and Campaign) that support core commercial operations and cannot be deleted. Administrators create Custom Objects (identified by the __c API suffix) to store organization-specific data. The Account object serves as the foundational anchor connecting contacts, sales opportunities, and support cases.

Understanding how Salesforce organizes, stores, and relates data is essential for mastering platform administration and business analysis. At its core, Salesforce is a powerful relational database wrapped in an intuitive, metadata-driven user interface. Instead of requiring structured query language (SQL) commands to manipulate tables and establish foreign keys, Salesforce provides declarative point-and-click tools that allow administrators and users to interact with a sophisticated relational data model.

---

Relational Database Concepts in Salesforce

To grasp how Salesforce manages enterprise information, consider how traditional relational database concepts translate into Salesforce terminology:

+-------------------------------------------------------------------------+
| Relational Database Concept   |  Salesforce Platform Equivalent         |
+-------------------------------+-----------------------------------------+
| Database Table                |  Object (e.g., Account, Contact)        |
| Table Row                     |  Record (e.g., Acme Corporation record) |
| Table Column                  |  Field (e.g., Phone Number, Annual Rev) |
| Unique Primary Key            |  Record ID (15- or 18-character string) |
| Foreign Key / Relationship    |  Lookup or Master-Detail Field          |
+-------------------------------------------------------------------------+

1. Objects as Database Tables

An Object is a database table that stores a specific category of information. For example, all information about customer organizations is stored in the Account object, while individual customer support inquiries are stored in the Case object.

2. Records as Table Rows

A Record is a single row within an object's database table. Each record represents an individual instance of that object. For example, a single company named "Acme Health Supplies" is stored as one record in the Account object.

Every record in Salesforce is assigned a globally unique system identifier known as the Record ID. Record IDs exist in two formats:

• 15-Character ID: A case-sensitive string generated by default in Classic URLs, standard reports, and legacy APIs.
• 18-Character ID: A case-insensitive string created by appending a 3-character checksum suffix to the 15-character ID, designed to prevent truncation errors in external third-party software (such as Microsoft Excel) that do not distinguish between uppercase and lowercase letters.

3. Fields as Table Columns

A Field represents a single column within an object's table. Fields define the specific data points collected on every record. Salesforce provides standard system fields automatically on every object—such as Id, CreatedDate, CreatedById, LastModifiedDate, and OwnerId—alongside business fields like Phone, Email, and Status.

---

Standard Objects vs. Custom Objects

Salesforce classifies database objects into two primary categories based on their origin and administrative lifecycle:

Exam Watchout: Standard objects cannot be deleted from a Salesforce organization. If a company does not use the Leads or Campaigns objects, the administrator can hide their tabs and remove user permissions, but the underlying standard object remains permanently within the platform schema.

---

The Six Core Standard CRM Objects

Salesforce delivers hundreds of standard objects, but six core objects form the backbone of customer relationship management across sales, marketing, and customer service operations:

+-------------------------------------------------------------------------+
|                    Marketing & Prospecting Phase                        |
|   [Campaign] ------------> Tracks Engagement on ----------> [Lead]      |
+-------------------------------------------------------------------------+
                                                                |         
                                                   Converts Into v        
+-------------------------------------------------------------------------+
|                    Customer Relationship Foundation                     |
|                               [Account]                                 |
|                                   |                                     |
|         +-------------------------+-------------------------+           |
|         |                         |                         |           |
|         v                         v                         v           |
|     [Contact]               [Opportunity]                [Case]         |
|  (Individual People)        (Deals & Sales)          (Support Tickets)  |
+-------------------------------------------------------------------------+

1. Lead (Lead)

A Lead is an unqualified prospect, potential customer inquiry, or raw contact. Leads represent people or organizations that have expressed preliminary interest in a company's products or services (for example, by stopping at a trade show booth, downloading an online whitepaper, or submitting a Web-to-Lead form). Because leads have not yet been evaluated for budget, purchasing authority, or legitimate business fit, they are held in a separate object to prevent unverified data from cluttering active customer accounts.

2. Account (Account)

An Account represents an organization, company, institution, or individual customer with whom a business has a commercial relationship. The Account object serves as the central anchor of the entire Salesforce data model. Almost every sales, service, and activity record links directly back to an Account.

Salesforce supports two distinct Account models:

• Business Accounts (B2B): Used when selling to other companies or organizations. Business Accounts track company-level attributes (annual revenue, industry, headquarters billing address) and serve as the parent record for multiple individual Contacts.
• Person Accounts (B2C): Used when selling directly to individual consumers (such as retail banking customers, patients in healthcare, or individual policyholders). A Person Account merges Account fields and Contact fields into a single unified record. Person Accounts must be enabled by an administrator and cannot be disabled once activated.

3. Contact (Contact)

A Contact represents an individual person associated with an Account. Contacts track direct communication coordinates (first name, last name, direct phone, mobile number, email address, job title, and mailing address). While a Contact typically belongs to a single parent Account, organizations can enable Contacts to Multiple Accounts to associate an individual with several organizations simultaneously while designating one primary Account.

4. Opportunity (Opportunity)

An Opportunity represents a qualified deal, pending sale, or potential revenue-generating transaction. Opportunities track sales progress through structured pipeline stages, expected financial amounts, close dates, win probabilities, and competitor involvement. Opportunities tie directly to a parent Account and can feature Opportunity Contact Roles to indicate key stakeholder involvement (such as Decision Maker, Evaluator, or Influencer).

5. Case (Case)

A Case represents a customer inquiry, support ticket, issue report, or feedback request. Cases are managed primarily within Service Cloud, tracking the lifecycle of customer problems from initial logging (via phone, email, web form, or chat) through diagnosis and final resolution. Cases link directly to an Account and Contact, providing service agents with full context regarding the customer's purchase history and past interactions.

6. Campaign (Campaign)

A Campaign represents an organized marketing program or promotional initiative designed to generate leads, build brand awareness, or drive product adoption. Examples include industry conferences, webinars, digital ad blitzes, direct mail mailers, and email newsletters. Campaigns track budgeted costs, actual expenditures, expected revenue, and member engagement. Both Leads and Contacts can be added to Campaigns as Campaign Members.

---

Standard Object Reference Matrix

The following matrix outlines the six core standard objects, their API representations, default fields, and key relational connections:

---

Standard Object Relationship Architecture

The interaction between standard objects reflects how a typical enterprise interacts with customers across the commercial lifecycle:

1. Marketing Engagement: Marketing teams launch a Campaign (e.g., an annual software summit). Prospects who register are recorded as Campaign Members, which point to Lead records.
2. Lead Qualification: Inside sales representatives review the Lead. Once the prospect expresses concrete interest and satisfies qualification criteria, the lead is converted into three interconnected records: a new or existing Account, a new or existing Contact, and an active Opportunity.
3. Deal Execution: Account executives manage the Opportunity, advancing it through sales stages until reaching Closed Won.
4. Ongoing Support: After the purchase, the customer contacts customer service with a question. A support agent logs a Case tied directly to the customer's Account and Contact records, giving the support agent immediate visibility into the client's past sales history.