Custom Objects

Formula Fields are very useful at extending capabilities and allowing users to quickly create automatic calculations rather than manually entering results. A formula field is a custom field that automatically calculates values based on a formula expression. Formula fields are read-only, meaning users can't directly edit the value. Instead, the value is calculated based on the formula and the values in the source fields. This is not a new concept, since most CRM systems such as Salesforce, Zoho, Hubspot, freshworks, vtiger, salesloft, MS Dynamics, and Sugar all have the ability to create formula fields. If you are familiar with Excel, than you know how handy formula fields are as they allow us to create simple or even more complex formulas based on data from a record and from its related records if needed. Some examples of use cases that come to mind are: Dynamic Payment Calculations for Appointments or Services For example, if each appointment hour costs $150 Formula: ( {{appointment.only_end_time}} - {{appointment.only_start_time}} ) * 150 Lead scoring based on Engagement and Attribution Formula: IF( {{contact.attributionSource.utmSource}} = "google", 10, 5 ) + ( {{ contact.email _open_count}} * 2 ) Visualize Lead Temperature (using IMAGE and CASE) Formula: CASE( {{contact.rating}}, "Hot", IMAGE("/img/samples/light_Red_fire.gif", "Hot"), "Warm", IMAGE("/img/samples/light_Yellow.gif", "Warm"), "Cold", IMAGE("/img/samples/light_Blue_snowflake.gif", "Cold"), IMAGE("/img/samples/light_grey.gif", "No Rating")) Add 30 Days to an Enrollment Date Formula: ( {{contact.enrollment_date}} + 30 ) The ideal situation would be whenever your are creating a custom field and you choose the Formula Field Type, it would allow you to open a formula editor where you could construct the formula and insert other fields, operators, and functions. Here are some Operators that should be included: Math Operators (+, - , *, /, ^ ) Logic Operators ( =, <, >, <=, >=) Logic Functions ( AND, OR, IF, CASE, ISBLANK, ISNEW, NOT, IS) TEXT Functions ( FIND, CONTAINS, HYPERLINK, IMAGE, INCLUDES)

At minimum, role permissions so certain objects can be restricted to admin. Ideally, user permissions to control object visibility by user.

It would be great if pages & funnels could access Custom Objects and display them on the page, probably as a gallery. In our case, we're going to be showing properties. We'll have a featured image that we'd want to be displayed in a gallery, with some basic information from the custom object. Then the user can click that item to see the full details about that custom object (property).

Problem Statement Currently, when viewing custom objects associated with a contact (in the contact's detail view), only the primary display field is shown. This makes it extremely difficult to get useful information at a glance without having to click into each individual custom object record. For example, I use custom objects to track insurance policies for my clients. When I look at a contact's associated policies, I only see the policy number. I cannot see critical information like: Policy type (Auto, Home, Life, etc.) Premium amount Coverage limits Carrier/Insurance company Expiration date Status This forces me to click into each policy individually just to see basic details, which is time-consuming and inefficient when managing multiple policies per client. Requested Feature Add the ability to customize which custom object fields are displayed in the contact association panel, similar to how Opportunity cards can be customized. Ideally, this would allow users to: Select 3-7 custom fields to display on each custom object card in the association view Choose the layout/format of how these fields appear Apply these display settings at the custom object schema level (so all instances show the same fields) Use Cases This feature would benefit many industries and use cases: Insurance agencies tracking multiple policies per client Real estate tracking properties, showings, and listings Legal firms tracking cases and documents Healthcare tracking treatments, appointments, or prescriptions Financial services tracking accounts, investments, or loans Any business using custom objects to track multiple related records per contact Impact This enhancement would make custom objects significantly more practical and user-friendly, reducing clicks and improving workflow efficiency. Right now, opportunities have better display customization than custom objects, which limits the usefulness of the custom objects feature for many users. Comparison to Current Features Opportunity cards already have this functionality and can display multiple custom fields. Bringing this same capability to custom objects would create feature parity and make both tools equally powerful for different use cases.

It would be very helpful if Custom Object workflows could directly update Contact fields using values stored in Custom Object fields. Currently, while workflows can be triggered from Custom Objects, there is no way to map Custom Object field values to Contact fields within the same workflow. This limitation makes it difficult to keep Contact records synchronized with related Custom Object data and requires unnecessary workarounds or external integrations. Adding support for mapping Custom Object fields to Contact fields would simplify workflow automation, reduce manual processes, and enable more powerful use cases where Custom Objects store information that should also be reflected on the associated Contact record.

Hey team 👋 First of all — Custom Objects + Associations are a game-changer. They unlock a deeper CRM that goes beyond “single contact per record.” I love using associations to support real-world relationships like: Husband ↔ Wife Parent ↔ Child Member ↔ Coach Resident ↔ Carer Student ↔ Teacher This gives huge value to verticals like dance studios, gyms, schools, childcare, aged care, and medical practices where contacts naturally exist in relationship groups. 🚨 But the 1,000 association limit is a major blocker In the current setup, a standard family structure quickly consumes these associations: Example: Parent ↔ Child 2 parents + 1 child = 2 associations 2 parents + 2 kids = 4 associations 2 parents + 3 kids = 6 associations That means: Family size Associations used Business hits limit at… 1 child 2 500 families 2 children 4 250 families 3 children 6 166 families For many of my clients, 250–600 family relationships is TINY. A busy dance school or gym easily handles 1,500–4,000 family/member relationships. 🏁 Result: We can’t confidently sell this feature Ethically, I must tell customers upfront about the cap. But doing so kills confidence and potentially drives them to other CRMs that support scalable relationship mapping. GHL’s own documentation states: “The association limit is set to prevent performance issues and can’t be changed.” I totally understand the intent — performance matters. But as it stands, the limit forces us to cap who we can sell GHL to. This is business-limiting for us and for you. ✅ Proposal Please raise the association limit to something practical: ➡️ Minimum viable expansion: 20,000 associations per sub-account This would allow: Larger revenue-generating studios and gyms Multi-branch operators Verticals with natural multi-contact households More impactful automation and personalization Even better: ✔ Tiered limits based on plan level ✔ Ability to request increase via support ✔ Optimizations that allow scaling without performance issues 💡 Why this matters for GHL long-term Drives more mid-market adoption Makes GHL truly competitive with vertical CRMs Unlocks more automation and AI use cases Prevents need for external databases/workarounds Increases customer retention (ours & yours) ❤️ In short You built an AMAZING feature — but the current limit makes it impossible to deploy at scale in the industries that need it most. Please consider raising (or allowing paid expansion of) association limits so GHL can continue to scale with real-world business needs. Thanks for considering this — happy to provide further examples or testing support. 🙏

The Problem: CO records are still. single endless column. Records with 30-50+ fields mean constant scrolling to find one value - a real cost on a live call, when a rep needs a field now, not after 3 scrolls. It pushes teams toward post-call corrections and error-prone workaround automations to capture what was missed. This isn't a new ask - it's a gap. You already built and shipped this exact framework for Contacts in Labs (April 2026): panel layouts, drag-and-drop fields reordering, show/hide fields, assignable views per user or team. Custom Objects never got it. This requires is simply: apply the same framework you already validated with 100 beta customers and zero reported bugs to Custom Object records. What we're asking for: • Bring the Contact Page Customization framework (panels, reorderable modules, show/hide fields, assignable views) to Custom Object record detail pages. A 3-column layout alone would surface roughly 3x the fields in the same scroll depth as today's single column. • Section/panel grouping also matters beyond speed: keeping related fields (financials, contact info, status, etc.) visually distinct rather than blurred into one long list makes records easier to scan and navigate for anyone who relies on visual structure to find information quickly - a real accessibility gain, not just a convenience one. • Interrim step if the full framework takes longer: 1-click access to pinned "key fields" folder at the top of the record, with an equally fast click back to the full field list. What this is NOT asking for: Not a change to list view (which already has customizable, sortable columns) - this is specifically the sing-record detail page, which List View doesn't touch. Not a request for a new UI system - it's reusing the panel/module framework that already exists for Contacts. Why now: Custom Objects has had steady investment this year - List view, workflow actions for associated records, unique field enforcement, native form support. The record detail page I the one piece of that experience still stuck in v1.

If you are not familiar with the term Kanban, it is the setup we have for Opportunities. View picture. Add custom statuses like we have in Opportunities for Stages to the Kanban view.

Currently there are only 2 triggers in High Level for custom object. When an Object is created and when an Object is changed. We need more triggers like when a contact is associated with an object (filter by association label). Also we could use more actions in workflows for custom object. Like being able to change a contact's association label automatically when they meet certain conditions.

Currently, once a custom field is created and assigned to a specific object group (Contact, Opportunity, or Business/Company), it cannot be moved to a different object group.Please add the ability to move (or reassign) an existing custom field from one object type/group to another (e.g., from Contact → Opportunity, Opportunity → Business, etc.). Why this is needed: Business requirements often evolve. A field that was originally created under Contacts may later need to live on Opportunities or the Business/Company object. Right now the only workaround is to create a duplicate field, update all forms/workflows/automations, and migrate data — which is time-consuming and error-prone. This feature would give much more flexibility when refining CRM structure without losing existing data or having to rebuild everything. Ideal behavior would include a simple “Move to…” option when editing a field, with clear confirmation about any data implications. Thank you for considering this improvement!