Skip to content

Basics

Standard vs Custom Objects in Salesforce

Making choices for a clean data model.

Reading time
2 min
Published
Updated
All articles

What are objects in Salesforce?

Objects are the foundation of your data model in Salesforce: they determine how information is stored and organized. If you want to set up Salesforce well, you need to know the difference between standard and custom objects.

An object as a table

Imagine you have a customer database. Each customer is a record in the Account object. Fields like company name, address and phone number are the columns of this table.

Standard objects

Standard objects are objects that Salesforce has already set up for you and that support the most common business processes. These objects already contain fields and relationships that fit many organizations.

Commonly used standard objects

  • Account stands for the companies or organizations you have a relationship with, such as customers, suppliers or partners.
  • Contact is a person who belongs to an account. Every contact is linked to an account.
  • Lead is a potential customer or sales opportunity that hasn't been qualified yet.
  • Opportunity is the actual sales opportunity, which you use to track the sales cycle through Closed Won.
  • Case is a support ticket or customer question that you handle in Service Cloud.
  • Campaign is a marketing campaign or promotion that generates leads.

Start with the standard objects

Standard objects have three advantages:

  • Predefined structure: they already contain fields and relationships that fit many organizations.
  • Consistency and maintenance: Salesforce takes care of updates and maintenance.
  • Extensive documentation: there is plenty of documentation, because every Salesforce customer uses the same objects.

Custom objects

Not every process fits within the standard objects. That's why you can create custom objects. These are your own tables where you store data specific to your business, such as Project, Contract, Subscription or Training.

When should you use custom objects?

Only create custom objects when the standard objects don't meet your needs. Too many custom objects make your Salesforce environment complex and hard to maintain. If you already have too many, you can have the data model cleaned up.

Best practices for custom objects

1. Choose a clear name and API name

Use capital letters for each word (e.g., Project__c) and make it recognizable for users.

  • Good: Project__c, Training__c, Contract__c
  • Bad: proj, trng, cntrct

2. Choose the right type of relationship

Determine whether the object should have a master-detail relationship (strict hierarchy) or a lookup relationship (looser) with existing objects.

  • Master-detail: a Project always belongs to an Account and can't exist without one.
  • Lookup: a Training refers to an Account but can also exist without one.

3. Use record types

When a custom object serves multiple processes, you can set up a separate page layout and picklist values per type. A Project__c object could have these record types, for example:

  • Implementation
  • Maintenance
  • Training

4. Document your object

Describe the purpose of the object and the fields. This helps with maintenance and supports AI features, as well-filled description fields provide context for Einstein.

Example: offering trainings

Say you offer trainings to customers. You already have standard objects like Account and Contact, but you also want to record information about the trainings you deliver:

  1. Create a custom object Training__c with fields such as Training name, Date, Location and a lookup to Account.
  2. Add a related list to the Account so you see all trainings for that customer.
  3. Automate with Flow, for example with a record-triggered flow that automatically creates a task for the trainer when a new training is scheduled.

Standard where you can, custom where you must

If you know the difference between standard and custom objects, you have the basis of every Salesforce implementation in hand. Use existing objects where you can and add custom objects where you need them. That keeps your data model simple and lets it grow with your organization.

The article on fields, relationships and record types shows how to bring more structure to your Salesforce environment.

Want to know when you need custom objects?

We analyze your processes and determine together which objects you need for a scalable data model.

Schedule a data model session