When I first started teaching people Salesforce, I noticed something. The ones who struggled with reports, with automation, with Apex, almost always had the same hidden gap. They had never really understood the data model. They were trying to build the roof before anyone had poured the foundation. So before you write a single formula or flow, let me give you the one mental picture that makes the rest of Salesforce click.
Think spreadsheets first
You already understand the core idea, even if you do not know it yet. Picture a spreadsheet.
- The whole spreadsheet, the thing with a name at the top, is an object.
- Each row in it is a record.
- Each column is a field.
That is it. An object called Account is just a table of companies. Each row is one company, one record. Each column, like Phone, Website, or Industry, is a field holding one piece of information.
Salesforce ships with many ready-made objects (Account, Contact, Opportunity, Case) and lets you build your own. If you want the deeper story on when to reuse the built-in ones versus building your own, read Standard vs Custom Objects. For now, just hold the spreadsheet picture.
Fields are typed, and that matters
In a plain spreadsheet, a cell will accept anything you type. A phone number, a typo, a smiley face. Salesforce fields are stricter, and that strictness is a feature. A Date field only accepts dates. A Number field only accepts numbers. A Checkbox is true or false. This is what keeps the data clean enough to actually trust. We will not go deep on field types here, but keep in mind that the column is not just a label, it has rules baked in.
The real magic: relationships
If Salesforce stopped at objects and fields, it would be a fancy collection of disconnected spreadsheets. The thing that turns it into a system is relationships. A relationship connects records in one object to records in another.
Here is the everyday example. A company (an Account) has several people who work there (Contacts). Instead of retyping the company name on every contact, you link each Contact to its Account. Now they are connected. Open the Account and you can see all its Contacts. Open a Contact and you can see which company it belongs to.
The data model is the skeleton of everything in Salesforce. Reports, automation, security, and code all walk along the bones of your relationships. Get the skeleton right and the whole body moves well.
There are two relationship types a beginner needs to know.
Lookup relationships
A lookup is a loose connection. It says “this record is related to that one,” but the two can live independent lives. A Contact has a lookup to its Account. If you delete the Account, Salesforce does not automatically destroy the Contact. The link is helpful but not binding. Most relationships you meet day to day are lookups.
Master-detail relationships
A master-detail is a tight, dependent connection. The child record (the detail) cannot exist without its parent (the master). Delete the parent and the children go with it. The child also inherits some of the parent’s behavior, including who is allowed to see it. A classic example is a line item that only makes sense as part of its parent record. If the parent is gone, the line item is meaningless, so it should go too.
The quick way to feel the difference: a lookup is two adults who are friends, and a master-detail is a parent and a young child. One can leave without the other being harmed. The other cannot.
The backbone every Salesforce org shares
Almost every Salesforce implementation, no matter the industry, leans on the same core trio.
- Account is the organization you do business with.
- Contact is a person, usually linked to an Account.
- Opportunity is a potential deal, linked to the Account it might come from.
Account to Contact, Account to Opportunity. Learn this backbone and you will recognize it everywhere, because most other objects hang off of it in one way or another. When you later explore something as advanced as Quote-to-Cash, you will find quotes and orders quietly bolted onto this same Account spine.
Why this is worth slowing down for
I once watched a student try to build a report that crossed three objects, and it kept coming out empty. The problem was not the report tool. The records simply were not linked, so there was nothing to cross. The moment we fixed the relationships, the report filled in instantly. Nothing else changed.
This is the lesson I want you to carry. When something in Salesforce behaves strangely, your first question should often be: how are these records connected, and are they connected at all? A surprising amount of confusion dissolves the moment you look at the relationships instead of the symptom.
It reminds me a little of tuning a stringed instrument. You can have perfect technique, but if the strings are not in the right relationship to one another, every note sounds wrong. The connections come first. The music comes after.
Your next step
You now hold the picture that everything else is built on: objects are tables, records are rows, fields are columns, and relationships are what turn the whole thing into a living system.
To zoom back out, revisit What Salesforce Actually Is. When you are ready to decide what to build yourself, continue with Standard vs Custom Objects. And the full path lives in Foundations.