Salesforce’s standard objects – Account, Contact, Lead, Opportunity, Case – cover most sales and service workflows. But real businesses have data that does not fit neatly into these standard categories: project milestones, equipment installations, loan applications, property listings, certifications, event registrations. Custom Objects let Salesforce administrators create new database tables – with their own fields, relationships, page layouts, validation rules, and reports – to extend Salesforce for any business use case. This guide covers how to create Custom Objects, how to design their relationships to other objects, and the governance considerations for keeping a Salesforce org clean as custom objects multiply.
That extra clarity matters when the team has to maintain the model later.
It also helps to explain the decision in plain language so the setup does not feel abstract.
The best guide is the one that makes customization feel deliberate.
A useful explanation should help the reader see where custom objects fit in the data model.
That means the guide should focus on practical design decisions rather than platform jargon.
For many teams, the value is in creating a system that matches real operations more closely.
It should also show how custom objects affect relationships, fields, and reporting.
A good guide should explain what custom objects are for and why they matter when standard objects are not enough.
That makes them a core part of data modelling in Salesforce.
Salesforce Custom Objects are useful because not every business process fits cleanly into standard CRM objects. Custom objects let teams model data around their own workflow instead of forcing everything into a generic structure.
What Is a Salesforce Custom Object?
A Custom Object in Salesforce is a database table that administrators create to store data that doesn’t fit in standard objects. Custom Objects work exactly like standard objects – they can have custom fields, relationships to other objects (standard or custom), page layouts, triggers, record types, validation rules, Flows, reports, and dashboards. The difference is that you define the schema: you choose the fields, the name, and the relationships.
Examples of common Custom Objects across industries:
- Financial Services: Loan Application, Policy, Claim, Financial Account, Investment Portfolio
- Healthcare: Patient, Appointment, Prescription, Care Plan, Medical Device
- Manufacturing: Equipment, Service Contract, Work Order (pre-built in FSL but customisable), Bill of Materials
- Real Estate: Property, Listing, Showing, Lease, Inspection
- Technology/SaaS: Subscription, License, Feature Request, Implementation Project, Customer Success Plan
- Professional Services: Project, Deliverable, Timesheet, Engagement, Statement of Work
Creating a Custom Object: Step-by-Step
- Go to Setup ? Object Manager ? Create ? Custom Object
- Provide the Label (singular and plural) and Object Name – the API name (auto-generated from the label, ending in
__c) - Choose the Record Name field format: Text (for a human-readable name) or Auto Number (for system-generated identifiers like “PROJ-00001”)
- Select optional features: Allow Reports, Allow Activities, Track Field History, Search
- Configure Sharing Settings: Public Read/Write, Public Read Only, or Private (controlled by sharing rules and role hierarchy)
- Save – the Custom Object now exists in the org with its standard system fields (Created Date, Last Modified By, Owner, etc.)
After creating the object, you build the Custom Fields, create the Relationships to other objects, configure Page Layouts, set up Record Types if needed, and build Reports and Dashboards.
Custom Object Relationships
Relationships define how Custom Objects connect to other data in Salesforce. There are three types:
Lookup Relationship
A Lookup is a loosely coupled relationship – it links one object’s record to another but does not require the linked record to exist. The child record is independent of the parent: deleting the parent does not delete the child. Use a Lookup when: the related record is optional, the child object makes sense to exist independently, or you need to relate to the same object type (a self-referential relationship, e.g., an Account’s parent Account).
Example: A Project object with a Lookup to Account. If the Account is deleted, the Project remains (with the lookup field blank).
Master-Detail Relationship
A Master-Detail is a tightly coupled relationship – the child (Detail) record is owned by the parent (Master). Deleting the Master deletes all Detail records. The Detail record’s sharing and security are inherited from the Master. Master-Detail relationships enable Roll-Up Summary fields on the Master – aggregate calculations (COUNT, SUM, MIN, MAX) of the child records. Use Master-Detail when: the child record cannot exist without the parent, and you need Roll-Up Summaries on the parent.
Example: A Contract Line Item object with a Master-Detail to Contract. If the Contract is deleted, all Line Items are deleted. The Contract record shows a Roll-Up Summary field with the total contract value summed from all Line Items.
Many-to-Many (Junction Object)
Salesforce does not natively support many-to-many relationships – but they can be built with a Junction Object: a Custom Object with two Master-Detail relationships to the two parent objects. Example: a Course Registration object with a Master-Detail to Contact (the student) and a Master-Detail to Course – allowing many contacts to register for many courses, with the Registration object holding the specific data about each enrolment (date, completion status, grade).
Custom Fields on Custom Objects
Custom Objects support all the same field types as standard objects: Text, Number, Currency, Date, Date/Time, Picklist, Multi-Select Picklist, Checkbox, URL, Email, Phone, Lookup, Formula, Roll-Up Summary, Geolocation, Long Text Area, and Rich Text Area. Field selection should follow the principle of minimum necessary data – only add fields that will be populated, reported on, and used for decision-making. Fields that nobody fills in and nobody reports on add noise without value.
Page Layouts and Record Types
Page Layouts on Custom Objects control what fields, related lists, and buttons are visible on the record page – the same as standard objects. When different groups of users need to see different information on the same custom object (e.g., sales reps see the customer-facing fields, finance sees the billing fields), Record Types allow different page layouts to be assigned to the same object based on the record’s type – enabling a single custom object to serve multiple use cases without duplicating the object schema.
Governance: Keeping Custom Objects Under Control
One of the most common Salesforce technical debt problems is an uncontrolled proliferation of Custom Objects – each administrator or consultant solving a specific problem by creating a new object, without considering how it relates to existing objects or how it will be maintained long-term. Governance best practices:
- Object proposal process: require a brief business case and design review before creating any new Custom Object – document the purpose, the fields, the relationships, and the reporting requirements
- Naming conventions: define consistent naming for API names (e.g., all objects in the “Customer Success” namespace start with “CS_”) to make the org navigable as it grows
- Ownership: every Custom Object should have an assigned business owner (not just a technical owner) who is responsible for keeping its data current and relevant
- Annual audit: review all Custom Objects annually – objects with fewer than 100 records and no recent activity may be candidates for archival or deletion
- Salesforce limits: a Salesforce Enterprise org supports up to 2,000 Custom Objects. In practice, most orgs hit governance quality problems long before the limit – but it is a hard ceiling to be aware of in large, complex implementations
When to Use Custom Objects vs Alternative Approaches
Custom Objects are the right solution for storing distinct, relational business data. They are not always the right answer:
- Use Custom Fields on existing objects: if the data you need to track is an attribute of an existing record type (an extra field on the Opportunity, a property of the Account), a Custom Field on the standard object is simpler than creating a new object
- Use Custom Metadata Types: for configuration data that drives business logic (rate tables, routing rules, threshold values), Custom Metadata Types are more appropriate than Custom Objects – they are deployable across environments (sandbox to production) and cacheable
- Use Salesforce CMS or Experience Cloud: for content management or community use cases, these native Salesforce tools may solve the problem without requiring a Custom Object data model
Salesforce Custom Object Architecture: Designing for Scale
How many custom objects can Salesforce have?
Up to 400 in Enterprise Edition, 800 in Unlimited Edition. Most orgs hit maintainability limits well before schema limits.
When to use a custom object vs a custom field?
Use a custom field when data belongs to an existing concept. Create a custom object when you need a new entity with its own records, list views, and relationships.
Can custom objects relate to standard objects?
Yes. You can create lookup or master-detail relationships from custom objects to standard objects like Account, Contact, or Opportunity.
Do custom objects affect Salesforce storage?
Yes. Each record consumes approximately 2 KB of data storage. Monitor usage in Setup > Storage Usage, especially for high-volume objects.
Are custom objects available in Salesforce mobile?
Yes, if you add them to the Mobile Navigation menu in Setup. Configure compact layouts to optimize how records display on smaller screens.
Problem: Custom Object Schema Sprawl Becoming Unmanageable
Organizations with 50+ custom objects face admin paralysis. Fix: Maintain an object data dictionary documenting each object purpose, owner, record volume, key fields, and relationships. Run quarterly audits using Object Manager to identify objects with zero records or no assigned permissions.
Problem: Deep Relationship Chains Breaking Governor Limits
Lookup chains of 5+ levels hit Apex and report governor limits. Fix: Limit lookup chains to 3 levels. Use master-detail only when the child record truly cannot exist without the parent. For complex hierarchies, consider Platform Events or External Objects to flatten data access patterns.
Problem: Custom Object Permissions Not Reaching New Users
New custom objects require explicit permission grants that admins frequently forget. Fix: Create a permission set checklist for every new custom object deployment. Use permission set groups to bundle all custom object permissions into role-based packages applied automatically on user onboarding.
The best custom-object setup is the one that matches the business process cleanly. If the model is vague, the CRM becomes harder to maintain.