{"id":488,"date":"2026-05-08T09:00:00","date_gmt":"2026-05-08T03:30:00","guid":{"rendered":"https:\/\/swapnilzambare.com\/blog\/standard-vs-custom-objects-salesforce\/"},"modified":"2026-10-04T02:18:48","modified_gmt":"2026-10-03T20:48:48","slug":"standard-vs-custom-objects-salesforce","status":"publish","type":"post","link":"https:\/\/swapnilzambare.com\/blog\/standard-vs-custom-objects-salesforce\/","title":{"rendered":"Standard vs Custom Objects in Salesforce: A Beginner Guide"},"content":{"rendered":"\n

Standard vs Custom Objects is one of the first design choices every Salesforce admin makes. In our Salesforce data model guide<\/a>, you learned that objects are like tables that store your data. Now we go one step further and ask a practical question. Should you use an object Salesforce already gives you, or build your own?<\/p>\n\n\n\n

In this post, you will learn what standard and custom objects are, how to spot them by their API names, and how to decide between them. Then you will build a real custom object in your Developer Edition org<\/a>. Get this choice right, and your org stays clean for years.<\/p>\n\n\n\n

What are Standard vs Custom Objects?<\/h2>\n\n\n\n

A standard object is an object that Salesforce creates for you in every org. Account, Contact, Lead, Opportunity and Case are common examples. They come with ready-made fields, page layouts and features.<\/p>\n\n\n\n

A custom object is an object that you create for your own business needs. For example, a school might create a Course object, and a car dealer might create a Vehicle object. Salesforce adds “__c” to the end of every custom object’s API name, like Course__c.<\/p>\n\n\n\n

Here is a simple analogy. Standard objects are like the folders that come with a new office cabinet: Customers, Contacts and Deals. Custom objects are the extra folders you label yourself, because your business has something unique to track.<\/p>\n\n\n\n

Why the Standard vs Custom Objects Choice Matters<\/h2>\n\n\n\n

Picking the wrong object causes pain later. If you build a custom “Customer” object when Account already exists, you lose many built-in features. Reports, integrations and apps from AppExchange all expect customers to live in Account.<\/p>\n\n\n\n

On the other hand, forcing unrelated data into a standard object is just as bad. Storing training courses as Opportunities, for example, mixes sales numbers with class schedules. So the goal is simple: use standard objects when they fit, and custom objects when they do not.<\/p>\n\n\n\n

How to Spot Standard vs Custom Objects by API Name<\/h2>\n\n\n\n

Every object and field has two names. The label is the friendly name users see, like “Course”. The API name is the name that code, formulas and integrations use, like “Course__c”. Also, an API name never has spaces.<\/p>\n\n\n\n

\"Standard<\/a>
Standard vs Custom Objects compared, with examples and API name patterns for each.<\/figcaption><\/figure>\n\n\n\n

The suffix at the end of an API name tells you what kind of item it is. Below is a table of the ones you will meet most often.<\/p>\n\n\n\n

Suffix<\/th>Meaning<\/th>Example<\/th><\/tr><\/thead>
No suffix<\/td>Standard object or standard field<\/td>Account, Industry<\/td><\/tr>
__c<\/td>Custom object or custom field<\/td>Course__c, Fee__c<\/td><\/tr>
__r<\/td>Custom relationship, used in queries<\/td>Teacher__r.Name<\/td><\/tr>
__mdt<\/td>Custom metadata type<\/td>Discount_Setting__mdt<\/td><\/tr>
__e<\/td>Platform event<\/td>Order_Update__e<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Also notice that you can add custom fields to standard objects. For example, a field called “GST Number” on Account gets the API name GST_Number__c. So a standard object can still hold your own custom data.<\/p>\n\n\n\n

Types of Objects in Salesforce<\/h2>\n\n\n\n

Standard objects<\/h3>\n\n\n\n

These are built for common business processes. Lead, Account, Contact and Opportunity support the sales cycle. Case supports customer service, and Campaign supports marketing.<\/p>\n\n\n\n

Many standard objects include special features. For example, Leads can be converted into Accounts, Contacts and Opportunities with one click. Opportunities have stages, probabilities and forecasting. You would need a lot of custom work to rebuild these.<\/p>\n\n\n\n

Custom objects<\/h3>\n\n\n\n

These store data that is unique to your business. Common examples include Property for real estate, Student for education, and Project for consulting firms.<\/p>\n\n\n\n

When you create a custom object, Salesforce gives it standard system fields automatically. These include Name, Owner, Created By and Last Modified By. Then you add your own custom fields on top.<\/p>\n\n\n\n

Rename a standard object instead of rebuilding it<\/h3>\n\n\n\n

Sometimes a standard object fits, but your team uses a different word. For example, a school may call its customers “Parents” instead of Accounts. In that case, you do not need a new object. Go to Setup, type “Rename Tabs and Labels” in Quick Find, and change the label of Account to Parent.<\/p>\n\n\n\n

The API name stays Account, so reports, apps and integrations keep working. Only the words users see on screen change. This is a quick win that many beginners miss.<\/p>\n\n\n\n

Other object types<\/h3>\n\n\n\n

As you grow, you will also meet external objects, which show data stored outside Salesforce, and big objects for very large data volumes. These are advanced topics. For now, focus on standard and custom objects.<\/p>\n\n\n\n

Standard vs Custom Objects: Side-by-Side Comparison<\/h2>\n\n\n\n

The table below sums up the main differences.<\/p>\n\n\n\n

Feature<\/th>Standard object<\/th>Custom object<\/th><\/tr><\/thead>
Who creates it<\/td>Salesforce<\/td>You, the admin<\/td><\/tr>
API name<\/td>No suffix, like Account<\/td>Ends in __c, like Course__c<\/td><\/tr>
Can you delete it?<\/td>No<\/td>Yes, and restore within 15 days<\/td><\/tr>
Built-in features<\/td>Many, like lead conversion<\/td>Only the basics you add<\/td><\/tr>
Rename the label<\/td>Yes, with Rename Tabs and Labels<\/td>Yes, any time<\/td><\/tr>
Best for<\/td>Common processes like sales and service<\/td>Data unique to your business<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

When should you use which? First, check if a standard object already fits the business concept. If it does, use it and add custom fields. If no standard object matches the real meaning of the data, create a custom object.<\/p>\n\n\n\n

Standard vs Custom Objects in Practice: Build a Course Object<\/h2>\n\n\n\n

Bright Path Tutors wants to track the courses it sells. No standard object fits, so let’s create a custom object called Course.<\/p>\n\n\n\n

Step 1: Create the object<\/h3>\n\n\n\n
    \n
  1. Go to Setup and click the Object Manager tab.<\/li>\n\n
  2. Click Create, then Custom Object.<\/li>\n\n
  3. Fill the fields as shown in the table below.<\/li>\n\n
  4. Tick Launch New Custom Tab Wizard after saving this custom object, then click Save.<\/li>\n<\/ol>\n\n\n\n
    Field<\/th>Value<\/th><\/tr><\/thead>
    Label<\/td>Course<\/td><\/tr>
    Plural Label<\/td>Courses<\/td><\/tr>
    Object Name<\/td>Course (API name becomes Course__c)<\/td><\/tr>
    Record Name<\/td>Course Name, Data Type Text<\/td><\/tr>
    Allow Reports<\/td>Ticked<\/td><\/tr>
    Track Field History<\/td>Ticked<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Step 2: Create the tab<\/h3>\n\n\n\n

    The tab wizard opens next. Pick any Tab Style, such as Books, and click Next. Keep the default profile settings, click Next, then Save. Now a Courses tab appears in the App Launcher.<\/p>\n\n\n\n

    Step 3: Add two custom fields<\/h3>\n\n\n\n
      \n
    1. In Object Manager, open Course, then Fields and Relationships, and click New.<\/li>\n\n
    2. Pick Currency, click Next, enter “Fee” as the Field Label and click Next, Next, Save and New.<\/li>\n\n
    3. Pick Number, enter “Duration in Weeks” as the Field Label, and click Next, Next, Save.<\/li>\n<\/ol>\n\n\n\n

      Now create two Course records from the Courses tab, such as “Spoken English” with a fee of 4999 and “Basic Maths” with a fee of 2999.<\/p>\n\n\n\n

      Step 4: See how developers read your object<\/h3>\n\n\n\n

      You do not need to write code as an admin. However, it helps to see how developers use your API names. Here is a SOQL query, the language used to read Salesforce data.<\/p>\n\n\n\n

      SELECT Name, Fee__c, Duration_in_Weeks__c\nFROM Course__c\nORDER BY Fee__c DESC<\/code><\/pre>\n\n\n\n
      Notice the “__c” on the object and both custom fields, while Name is a standard field with no suffix. You can run this in the Developer Console under the Query Editor tab. The result looks like this.<\/p>\n\n\n\n
      Name             Fee__c    Duration_in_Weeks__c\nSpoken English   4999      8\nBasic Maths      2999      6<\/code><\/pre>\n\n\n\n
      Compare it with a query on a standard object. Here, every field is standard, so there is no suffix at all.<\/p>\n\n\n\n
      SELECT Name, Industry, Phone\nFROM Account\nWHERE Industry = 'Education'<\/code><\/pre>\n\n\n\n
      We will learn SOQL properly later in this series. For now, just remember that API names are what code sees.<\/p>\n\n\n\n
      \"Standard<\/a>
      The Course custom object with its fields and API names, next to the standard Account object.<\/figcaption><\/figure>\n\n\n\n
      Common Mistakes with Standard vs Custom Objects<\/h2>\n\n\n\n