Getting Started with Custom Objects

Why Use Custom Objects?

Custom Objects allow you to extend your CRM's capabilities beyond its standard features, enabling you to model and track the unique aspects of your business. They are designed for information that doesn't naturally fit into the predefined categories of Contacts, Companies, or Opportunities. By using Custom Objects, you can maintain a more organized and scalable system that accurately reflects your operational reality.

Key benefits include:

• Improved Organization: Prevent cluttered records by storing specialized data in its own dedicated space, rather than forcing it into standard objects.
• Accurate Data Modeling: Create distinct records for real-world entities like properties, projects, or products, each with its own set of fields and lifecycle.
• Enhanced Automation and Reporting: Build more precise workflows, filters, and dashboards by working with a clean, well-structured data model.
• Complex Relationship Management: Easily define and manage one-to-many or many-to-many relationships, such as linking one contact to multiple projects or assets.

In essence, Custom Objects help you build a CRM that grows with your business and operates the way you do.

What Are Custom Objects?

A Custom Object is a new type of record that you can create and define within your CRM. It functions as a first-class data container, similar to a Contact or Company record, but is tailored to your specific needs. For example, you could create a Custom Object for tracking rental properties, service appointments, or inventory items.

Each Custom Object you create can have:

• Its own set of custom fields to capture relevant information.
• Associations or links to other objects in the CRM, like Contacts or Opportunities.
• Full integration with core CRM tools, including Workflows and Forms.

When Should You Use Custom Objects?

Consider implementing Custom Objects in the following scenarios:

• Tracking Non-People Entities: When the primary subject of your data is an asset, location, or item (e.g., a piece of equipment, a subscription plan, or a project) rather than a person or company.
• Requiring Consistent Record Structure: When you need to create multiple records of the same type, each requiring the same set of fields and data points.
• Building Advanced Relationships: When your processes involve complex connections between different data points that standard objects cannot easily represent.

Common examples include a real estate agency creating a "Listings" object for properties or a veterinary clinic creating a "Patients" object for animals.

When to Stick With Standard CRM Objects

Custom Objects are a powerful tool, but they are not always the best solution. It is often better to use the standard CRM objects (Contacts, Companies, Opportunities) in these cases:

• Standard Object Functionality Suffices: If a built-in object already handles your use case effectively, leveraging its native features is usually simpler.
• Communication is Key: If your primary need involves sending bulk emails, running marketing campaigns, or using other communication tools that are inherently tied to contact records.
• Avoiding Data Duplication: Creating a Custom Object that closely mimics an existing standard object can lead to confusion and data inconsistency. In such cases, using segmentation tools like Smart Lists within the standard object might be a better approach.

Common Examples

Good Use Cases

• Real Estate: Create a "Properties" object to store details like address, price, and status, and link them to buyer and seller contacts.
• Service Businesses: Create a "Jobs" or "Projects" object to track work orders, deadlines, and associated clients.

Not Recommended

• Event Attendees: For managing event registrations and communications, the built-in features of Contact records are typically more effective.
• Internal Notes or Tasks: Avoid using Custom Objects for simple notes, tasks, or activities, as this adds unnecessary complexity. The CRM's native activity tracking is better suited for this purpose.

What’s Next?

Once you have decided that a Custom Object is the right solution, you can begin building it. The next steps typically involve:

• Defining the object and its custom fields.
• Setting up associations with other objects.
• Creating workflows to automate processes.
• Building forms to capture data for the new object.
• Visualizing the data on dashboards for reporting.

Proceed to the guide on creating your first Custom Object to get started.