Skip to main content

Getting Started with Custom Objects in Stack

Custom objects in Stack are designed for businesses that need to manage relationships or processes beyond the standard CRM capabilities. This feature allows you to create tailored objects that fit your unique business needs, enabling you to define custom fields and set up associations with other CRM objects. Custom objects can also be integrated into various tools, such as workflows.

When Should You Consider Using Custom Objects?​

Custom objects are ideal in the following scenarios:

  • Unique Business Relationships or Processes: If your data doesn't fit neatly into existing objects like Contacts, Companies, or Opportunities, custom objects let you define your own structure to meet your specific needs.

  • Tracking Specialized Data: For example, managing event registrations, properties, inventory, or any other specialized information that requires a structured CRM approach can benefit from custom objects.

  • Extending CRM Functionality: By linking custom objects with standard CRM objects, you can build more complex relationships and workflows within your CRM system.

When to Stick with Standard CRM Objects​

While custom objects offer great flexibility, they may not always be necessary. Consider these points before creating a custom object:

  • Sufficiency of Standard CRM Objects: Many businesses can effectively manage their data using Contacts, Companies, and Opportunities. Custom objects should be considered only if these do not meet your requirements.

  • Access to Specific CRM Features: Some features, like sending bulk marketing emails, are only available with Contacts. Ensure that using a custom object won't restrict access to essential features.

  • Risk of Data Duplication: Be cautious of potential data overlap with standard objects, which can lead to inconsistencies and confusion.

Examples of When to Use or Not Use Custom Objects​

Use Case 1: Real Estate (Homes)​

A property management business might create a custom object for "Homes" to store and track specific property data, such as location, size, availability status, and maintenance records. This can be associated with other objects like Contacts (tenants, buyers).

Use Case 2: Pets & Veterinary Care​

A veterinary clinic could use a custom object for "Pets" to record each animal's medical history, linked to the owner's contact information. This helps manage appointments, treatments, and vaccination schedules within one system.

When Not to Use: Event Attendees​

If organizing an event and you need to send invitations, track responses, or send post-event surveys, using the Contacts object is likely more efficient. Creating a custom object for "Event Attendees" might limit your ability to send marketing emails and use automation features.

When Not to Use: Client Communications for Law Firms​

If your law firm already uses the Opportunities object to track cases and client interactions, creating a custom object for "Client Communications" might add unnecessary complexity. Instead, continue logging important details under existing objects to avoid overlap.

Additional Resources​

Explore these resources to further understand how to leverage custom objects in Stack for your business needs.