Anis Mahmud Anik

GoHighLevel custom fields: contact vs opportunity fields

A contact card and a deal card side by side, each with its own set of custom fields.

Short answer

Use a contact custom field for facts about the person that stay true across deals, such as preferred language. Use an opportunity custom field for facts about one deal, such as the quoted package or budget. The object type is permanent once a field is created, and only contact fields appear in forms and contact workflows.

What is the difference between a contact field and an opportunity field?

A contact field attaches to a person. It shows up in contact records, forms, surveys, contact workflows, Smart Lists and email or SMS personalization. An opportunity field attaches to a single deal. It shows up in opportunity records, pipeline views, opportunity workflows and deal reporting.

The test is simple: if the same person can have two different answers at the same time, the field belongs on the opportunity. One owner can ask about a website build and a monthly retainer in the same quarter. Their email address is the same for both. The budget and start date are not.

QuestionContact fieldOpportunity field
What does it describe?The personOne deal
Can it differ between deals?NoYes
Available in forms?YesNo
Used in contact workflows?YesNo, only opportunity workflows
Typical examplePreferred languageQuoted package

Where do you create custom fields?

Go to Settings, then Custom Fields. Use the object selector to choose Contact or Opportunity, stay on the Fields tab and click Create field in the top right. Field types include Short Text, Long Text, drop-downs, date pickers, phone, email, radio selects, checkbox groups and URLs.

Opportunity fields have a few extra types, including monetary, signature, rich text and a user field. File upload is not yet available for opportunities.

Can you change a field from contact to opportunity later?

No. HighLevel states that once a field is created as a contact or opportunity field, it cannot be switched. To change the type you create a new field and move the data across. That makes the first decision the expensive one, so write the field map before you build.

Are opportunity custom fields available in every account?

Check before you plan around them. HighLevel’s guide to opportunity custom fields says the feature is currently accessible in Labs, so it is not generally available on the evidence of that page. If Opportunity is missing from the object selector, the feature is probably not switched on for your account yet.

Which fields belong on the contact?

Put a value on the contact when it should survive a new deal:

  • Preferred language or contact method
  • Business website or company type
  • General service interest
  • First-touch source, if you report on it per person
  • Details a form collects, because forms write to contact fields only

Which fields belong on the opportunity?

Put a value on the opportunity when it describes this deal only:

  • Package or service being quoted
  • Budget or expected value
  • Target start date
  • Reason the deal was won or lost
  • Proposal status

Lead source is the field that most often goes wrong. Decide which meaning you need. First-touch source suits the contact. Source of this particular deal suits the opportunity. Never use one field for both.

How do you plan fields before building workflows?

Write one line per field: purpose, object, field type, who fills it in, allowed values, and which forms, workflows or reports depend on it. Reuse a standard field when one exists. Use drop-downs or radio selects for anything a workflow will branch on, so “CRM setup” never becomes three spellings. Then test with a sample contact and a sample opportunity before any real lead sees it.

A tidy field map also feeds the other half of a clean CRM. See Tags vs custom fields vs Smart Lists for when a label is better than a field, and what to set up first in GoHighLevel for the order to build in.

Frequently asked questions

Can a form fill in an opportunity custom field?

Not directly. HighLevel documents that only contact fields appear in forms and contact workflows. Collect the answer on the contact. If you need it at deal level, check that the workflow action creating the opportunity can set the matching field before you rely on it.

Can one contact have several opportunities?

Yes. That is the reason deal-level facts live on the opportunity. Each deal keeps its own stage and its own field values.

Should every piece of information become a custom field?

No. Create a field when you need to filter, report, branch a workflow or collect it in a form. Use a note for one-off context.

What happens to a field I delete?

Check forms, workflows, Smart Lists and reports first. Anything that reads the field will lose its input.

If you want the field map done for you, see the services page or book a free 30-minute call.

Sources: HighLevel Help: How to use custom fields; HighLevel Help: How to use custom fields for opportunities. Checked against the Help Center on 29 October 2026.

Want this set up for you?

30 minutes, a clear next step.

Anis Mahmud Anik

HighLevel Certified Admin. I set up and automate GoHighLevel for founders and owners.