Detailed Description:

Overview

Currently, all opportunity custom fields in GoHighLevel are global across all pipelines. This creates inefficiencies when managing multiple pipelines (e.g., Purchase, Refinance, Realtor Partner), as users must either:

Overload a single set of fields for all pipeline types

Manually ignore irrelevant fields

Or attempt workarounds using naming conventions or conditional logic

This leads to cluttered UI, slower workflows, and increased user error.

Requested Feature

Introduce pipeline-specific opportunity custom fields, where fields are assigned directly to a specific pipeline and only appear when that pipeline is active.

Core Functionality Requirements

Field-to-Pipeline Assignment

When creating or editing an opportunity custom field, allow selection of:

Specific pipeline(s) the field belongs to

Or a global option (visible across all pipelines)

Dynamic Field Visibility

When a user switches pipelines:

Only fields assigned to that pipeline should display

All unrelated fields should be automatically hidden

Pipeline-Level Field Groups (Optional but Ideal)

Ability to group fields per pipeline for cleaner organization

Example:

Purchase Pipeline → Borrower Info, Property Info

Refinance Pipeline → Current Loan, Cash-Out Details

Automation Compatibility

Fields should still be accessible in:

Workflows

Triggers

Conditions

Even if they are pipeline-specific

Backward Compatibility

Existing custom fields remain global by default

Users can optionally assign them to pipelines later

Use Case Example

Purchase Pipeline Fields:

Purchase Price

Property Type

Occupancy Type

Refinance Pipeline Fields:

Current Loan Balance

Interest Rate

Cash-Out Amount

Expected Behavior:

When in Purchase Pipeline → Only purchase-related fields appear

When switching to Refinance Pipeline → Purchase fields disappear, refinance fields appear automatically

No duplication. No hiding. No clutter.

Business Impact

Cleaner UI = Faster loan structuring

Reduces human error from irrelevant fields

Improves scalability for multi-product loan officers

Aligns CRM behavior with real-world mortgage workflows

Critical for high-volume users managing multiple loan types

Current Problem Summary

Right now, the system forces:

One-size-fits-all field structure across all pipelines

Manual mental filtering by the user

Inefficient data entry and poor UX

Expected Outcome

A modular, pipeline-driven field system where:

Each pipeline behaves like its own structured workspace

Fields dynamically adapt without manual intervention

CRM becomes faster, cleaner, and scalable for top producers