meetergomeetergo Help

Custom Fields

Add custom data fields to deals and configure required fields per pipeline stage

Updated on January 12, 2026

Custom fields let you capture additional information on deals beyond the standard fields. Create fields for budgets, decision dates, competitor information, or any data your sales process requires. You can also require certain fields before deals can advance to specific stages.

Understanding Custom Fields

Custom fields extend deal records with:

  • Additional data points you need to track
  • Structured information (not just notes)
  • Stage-specific requirements
  • Consistent data across all deals

Custom Field Types

meetergo CRM supports various field types:

TypeDescriptionExample Use
TextSingle-line textProduct SKU, reference number
TextareaMulti-line textDetailed requirements, special instructions
NumberNumeric valuesQuantity, user count, score
CurrencyMonetary amountBudget, discount amount
DateDate pickerDecision date, contract end date
CheckboxYes/No toggle"Legal approved", "References checked"
SelectSingle choice dropdownIndustry, source, priority tier
MultiselectMultiple choice checkboxesFeatures needed, departments involved

Creating Custom Fields

Access Field Settings

  1. Navigate to CRM settings
  2. Find Custom Fields section
  3. Click Add Field

Configure the Field

SettingDescription
NameField label shown to users
TypeData type (text, number, etc.)
RequiredWhether field must be filled
OptionsFor select/multiselect: available choices
Default ValuePre-filled value for new deals

Example: Industry Field

Name: Industry
Type: Select
Options:
- Technology
- Healthcare
- Finance
- Manufacturing
- Retail
- Other
Required: No

Example: Budget Field

Name: Budget
Type: Currency
Required: No
Default: (empty)

Using Custom Fields on Deals

Viewing Custom Fields

On the deal detail page:

  1. Open a deal
  2. Go to the Overview tab
  3. Scroll to the Custom Fields section
  4. View all custom field values

Editing Custom Fields

  1. Click on the custom field you want to edit
  2. Enter or select the value
  3. Changes save automatically

Or use the Edit button to edit multiple fields at once.

Inline Editing

Most custom fields support inline editing:

  1. Click the field value
  2. Make changes
  3. Click away or press Enter to save

Required Fields Per Stage

Ensure critical information is captured by requiring fields at specific pipeline stages.

How It Works

  1. Define which custom fields are required for each stage
  2. When moving a deal to that stage:
    • If required fields are filled → Deal moves normally
    • If required fields are missing → Dialog prompts to complete them

Example: Proposal Stage Requirements

Before entering "Proposal" stage, require:

  • Budget: Must know the budget range
  • Decision Maker: Must identify the key decision maker
  • Timeline: Must know expected decision date

Configuring Stage Requirements

  1. Go to Pipeline Settings
  2. Select a stage
  3. Find Required Custom Fields
  4. Select which fields must be filled for this stage
  5. Save

The Required Fields Dialog

When moving a deal to a stage with missing required fields:

  1. A dialog appears listing unfilled required fields
  2. Fill in the missing information
  3. Click Save & Move
  4. The deal advances to the new stage

If you cancel, the deal stays in its current stage.

Best Practices

Field Design

Keep it focused:

  • Only create fields you'll actually use
  • Remove unused fields over time
  • Consolidate similar fields

Use appropriate types:

  • Number for quantities (not text)
  • Date for dates (not text)
  • Select for fixed options (not text)

Clear naming:

  • Descriptive labels
  • Consistent terminology
  • Avoid abbreviations

Stage Requirements

Be strategic:

  • Don't require everything everywhere
  • Focus on stage-critical information
  • Too many requirements slow down reps

Match your process:

  • Discovery: Qualification info
  • Proposal: Budget, timeline
  • Negotiation: Decision maker, competition

Start simple:

  • Begin with few requirements
  • Add more based on need
  • Monitor impact on deal velocity

Common Custom Fields

FieldTypeStage Recommended
BudgetCurrencyDiscovery/Proposal
Decision DateDateProposal
CompetitionSelectDiscovery
Source/Lead OriginSelectAny
Pain PointsTextareaDiscovery
Next StepTextAll stages
Probability OverrideNumberLate stages
Contract LengthNumberNegotiation
Implementation NeedsMultiselectProposal

Editing Field Configuration

Changing Field Settings

  1. Go to Custom Fields settings
  2. Find the field to edit
  3. Click Edit
  4. Modify settings
  5. Save

Deleting Fields

  1. Go to Custom Fields settings
  2. Find the field
  3. Click Delete
  4. Confirm

Custom Fields in Workflows

Custom fields can be used in:

  • Stage requirements: Enforce data collection
  • Filtering: Find deals by field values
  • Reporting: Analyze deals by field data
  • Activity log: Track field changes

Field Visibility

All custom fields are visible to users with CRM access. Consider:

  • Using clear labels for team-wide understanding
  • Documenting field purposes if not obvious
  • Maintaining consistent data entry standards

FAQ

How many custom fields can I create?

Check your plan limits. Most plans support numerous custom fields, but practical limits exist for usability.

Can I reorder custom fields?

Field order can typically be configured in settings. Drag and drop to arrange.

Are custom fields searchable?

Basic search may not include custom fields. Use filters or export for detailed analysis.

Can I make a field required globally?

Set the field as required in field settings. For stage-specific requirements, configure in pipeline settings.

What happens to data if I change field type?

Data may be lost or converted. Text to number drops non-numeric values. Always backup critical data first.

Can I import custom field data?

Depends on import capabilities. Check if CSV import supports mapping to custom fields.

Can different pipelines have different custom fields?

Custom fields are typically account-wide. Use stage requirements to make fields relevant to specific pipelines.

Can I create conditional fields?

Showing/hiding fields based on other values may have limited support. Check current capabilities.

Custom Field Patterns

Qualification Scoring

Fields:
- Budget Fit (Select: Strong, Medium, Weak)
- Authority Confirmed (Checkbox)
- Need Identified (Checkbox)
- Timeline Defined (Checkbox)

Use: Quick BANT qualification view

Competitor Tracking

Fields:
- Primary Competitor (Select: list of competitors)
- Competitive Position (Select: Ahead, Even, Behind)
- Competitor Price (Currency)

Use: Win/loss analysis

Implementation Planning

Fields:
- Implementation Type (Select: Standard, Custom, Enterprise)
- Estimated Hours (Number)
- Technical Contact (Text)
- Go-Live Target (Date)

Use: Resource planning

Was this article helpful?

Let us know if this article answered your questions.