GoHighLevel custom fields store information about one contact or opportunity (a birthday, a service of interest, a quote number), custom values are account-level placeholders for text that is the same everywhere (your business name, a booking link), and tags are labels on a contact that workflows can add, remove and check. The rule that keeps an account tidy: a field for data that differs per person, a custom value for something that is the same in every message, a tag for a state a workflow should react to. Fields are created one at a time under Settings, Custom Fields, with Contact or Opportunity as the object, and that object cannot be changed later. This page lists every field type HighLevel documents, the folders, the decision table between the three tools, a naming convention, how fields drive workflows, the documented limits, how import mapping works and a cleanup method. HighLevel facts were checked at help.gohighlevel.com on November 2, 2026; titles and dates are in the Sources section.
What is the difference between custom fields, custom values and tags in GoHighLevel?
A custom field holds data about one contact or opportunity, a custom value holds one piece of information reused across many messages and pages, and a tag is a label on a contact used to group contacts and trigger workflows.
| Tool | Holds | Scope | Where you create it | Merge tag or reference | Example |
|---|---|---|---|---|---|
| Custom field (contact) | Data unique to one person | One contact | Settings, Custom Fields, Fields tab, object Contact | {{contact.field_key}} | Preferred service, birthday, insurance provider |
| Custom field (opportunity) | Data unique to one deal, which can differ between two deals for the same contact | One opportunity | Settings, Custom Fields, object Opportunity | Opportunity merge fields | Quote number, job address, roof size |
| Custom value | Information that is the same everywhere it is used | Whole sub-account | Settings, Custom Values | {{custom_values.key}} (key generated from the name, for example custom_values.my_custom_value) | Booking link, business hours, office address |
| Tag | A label, present or absent | One contact, but the same tag name is shared across contacts | Typed on a contact, in a bulk action, or by the Add Contact Tag workflow action | Filter: Has tag / Doesn't have tag | source-facebook, status-customer, no-show |
HighLevel's own definition, from the merge fields overview (modified September 1, 2026): custom fields are "user-defined data points unique to each contact or opportunity", custom values are "reusable placeholders for information that stays the same". Editing a custom value updates it everywhere it is used; editing a field changes one record.
| Custom field | Custom value | Tag | |
|---|---|---|---|
| Differs per contact | ✓ | ✕ | ✓ |
| Change once, updates every message | ✕ | ✓ | ✕ |
| Can trigger a workflow | ◐ | ✕ | ✓ |
| Can be bulk uploaded | ✕ | ✕ | ◐ |
Source: HighLevel merge fields and custom variables overview, read October 18, 2026. Fields and values cannot be bulk-created; tags can be added in bulk actions
Which custom field types does GoHighLevel offer?
HighLevel documents text (single line, multi line, text list), number, monetary, phone, email, URL, dropdown (single and multiple), radio, checkbox group, date picker, file upload and signature for contacts, with Date and Time, User and Rich Text added for opportunities.
| Field type | Use it for | Rules from the help center |
|---|---|---|
| Single line text | Short free text: nickname, referral name | Fine for display, poor for filtering: typos make every filter miss |
| Multi line text | Notes, intake answers | Not for anything you will branch on |
| Text list | Several short values | Listed under text inputs in the custom fields article |
| Number | Headcount, square feet, score | Use with the Math Operation action and numeric If/Else conditions |
| Monetary | Quote, budget, deposit | Currency formatted; pair with opportunity value rather than duplicate it |
| Phone and Email | A second number or address | Keep the standard phone and email fields as the ones automations send to |
| URL | Portfolio, property listing, document link | Clickable on the record |
| Dropdown (single) | Any category you will filter or branch on: service, location, plan | Our default for categories; the If/Else action matches on the option |
| Dropdown (multiple) | Several services of interest | HighLevel says 50 or more options are fine and there is no practical option limit |
| Radio | One of a few visible choices on a form | Same data as a dropdown, different form display |
| Checkbox group | Consents, add-ons | Multiple values on one field |
| Date picker | Birthday, policy renewal, last visit | Drives date-based triggers and Wait until date; an empty date stalls the step |
| File upload | Photos, documents, signed forms | Set a file restriction (maximum 250 MB per file) and single or multiple files; an older HighLevel article says file upload and signature fields cannot be filtered |
| Signature | Signed consent on a form | Same filtering limit as file upload |
| Date and Time, User, Rich Text (opportunity only) | Install date and time, assigned estimator, formatted scope notes | Described in HighLevel's expanded opportunity field types article; Date and Time can be date only, time only or both, with date restrictions |
Two structural rules: a field's object (Contact or Opportunity) cannot be changed after creation, so a field built on the wrong object has to be recreated, and only contact fields appear in forms and contact workflows. Custom Objects (for example properties, vehicles or pets linked to a contact) are a separate feature with their own fields and their own documented record limits; use them when one contact owns several things that each need their own data.
Folders
Folders are created under Settings, Custom Fields, Folders tab, and they appear as sections on the contact or opportunity record, which is how a 40-field account stays readable. HighLevel's examples are General Information, Qualification Details, Property Information, Appointment Preferences and Service Details. Custom values have their own folders under Settings, Custom Values, Folders tab: a value sits in exactly one folder, folders cannot be nested, and the Bulk Actions menu moves several values at once.
When should you use a field, a custom value or a tag?
Use a field when the answer differs per person and you will report or branch on it, a custom value when the text is identical in every message, and a tag when a workflow needs a yes/no state such as "booked" or "source-google".
| You want to | Use | Why not the others |
|---|---|---|
| Remember which service someone asked about | Dropdown custom field | A tag per service multiplies fast; a custom value is the same for everyone |
| Put your booking link in forty messages and change it once | Custom value | A field would hold the same text 10,000 times |
| React when a lead came from Facebook | Tag set by the Facebook lead trigger, or the standard source field | Tags are what the Contact Tag trigger and the Has Tag filter read |
| Report revenue by source | Opportunity source plus opportunity value | The Lead Source Report reads the source field, not tags |
| Stop sending to people who already booked | Tag "booked" added by the appointment trigger, or an appointment condition in If/Else | A field works too, but a tag is faster to check and remove |
| Store a quote that differs per job for the same customer | Opportunity custom field | A contact field would be overwritten by the second job |
| Change the office hours in every reminder before a holiday | Custom value, edited once or by the Update Custom Values action | Nothing else updates every template at once |
| Hold a date that drives a renewal reminder | Date picker field | Tags have no date; custom values are not per person |
| Mark a contact as a no-show for recovery | Tag, removed when they rebook | A state that a workflow adds and removes is the textbook tag |
How do custom fields drive workflows?
A field is written by a form, an import, the Update Contact Field action or an AI action, and read by If/Else conditions, trigger filters, Smart List filters and merge fields in messages, so one dropdown can route, personalize and report at the same time.
- Write the field at entry. Map the form question to the field in the form builder. For webhooks and integrations the field key must match exactly; a key that matches nothing is silently ignored and the field stays blank.
- Branch on it with If/Else. Add the If/Else action, choose Contact Details, pick the field and the operator. Dropdown fields match on the option; the If/Else action can also compare dynamic values from earlier steps. Add a final branch for "empty" because an unmapped field is blank, not an error.
- Update it from a workflow. The Update Contact Field action changes one or several existing fields using a fixed value or a dynamic value from an earlier step; it does not create fields. It can clear custom fields but not standard fields.
- Change account-wide text from a workflow. The Update Custom Values action edits a custom value, for example switching a "current promotion" line used in twenty templates.
- Trigger on a change. The Contact Changed trigger fires when a field changes; the Contact Tag trigger fires when a tag is added or removed. Both pair with Opportunity triggers from pipeline setup.
- Personalize messages. Insert {{contact.field_key}} in SMS and email. Empty merge fields are replaced with blank text and HighLevel does not support fallback values, so write sentences that still read correctly when the field is empty, or branch before sending.
- Segment and report. Smart Lists filter on fields and tags; the lead routing workflow branches on the location or service field to pick the pool.
If a branch is not taken when it should be, the field is usually empty or holds a near-match ("Roofing " with a trailing space). Check the contact record first, then the execution log; our workflows not triggering guide covers the rest.
Which limits does HighLevel document?
HighLevel states no strict limit on the number of custom fields or custom values, but bulk creation is not supported, fallback values for empty fields do not exist, a field's object cannot be changed, and file uploads are capped at 250 MB per file.
| Item | Documented position (checked November 2, 2026) | What it means for your build |
|---|---|---|
| Number of custom fields or values | "No strict limit", with advice to manage them carefully | The real limit is what your team can explain; see the cleanup method |
| Bulk creation | Not supported; each field and value is added individually | Plan the list before building; copying between sub-accounts is done through snapshots |
| Object change | Contact and Opportunity fields cannot be switched after creation | Decide the object before you click Save |
| Dropdown options | 50 or more options are fine; "no practical limit" | Long lists are allowed, but a form with 50 options loses leads |
| Fallback values | Not supported; empty merge fields render blank | Branch before sending, or write copy that survives a blank |
| File upload | Maximum 250 MB per file, single or multiple files per field | Fine for photos and PDFs |
| Filtering | An older opportunity-fields article says file upload and signature cannot be filtered | Keep a dropdown or checkbox beside them if you need to filter "has signed" |
| Tags | Case sensitive ("Facebook" and "facebook" are two tags); the mobile app bulk action handles up to 500 contacts and 10 tags at a time | Lower-case every tag name |
| Custom value folders | One folder per value, no nesting | Prefix names instead of relying on deep folders |
A naming convention that keeps the account clean
Use lower-case names with a type prefix for tags, a folder-style prefix for custom values, and short specific names for fields so every item reads the same way in a filter list.
- Fields: short and specific with one meaning each, for example "service_interest", "property_type", "renewal_date". Never "notes2" or "field_old". Use a dropdown for anything you will filter on. The key is generated from the name and shown in the field list; keep the name stable, because integrations map by key.
- Custom values: prefix by area so the list sorts itself: "company.booking_link", "company.hours", "offer.current_promo". Put each in a matching folder. Changing a value's name later does not change its key, so the merge tags in templates keep working.
- Tags: prefix by type, lower case, hyphenated: "source-facebook", "status-customer", "stage-booked", "ops-no-show". Decide the full list before the first workflow.
- Folders: one per subject (Intake, Qualification, Service details, Billing), matching the sections a rep reads on the record.
- Write it down. A one-page list of every field, value and tag with its meaning and the workflow that writes it. It is part of the handover document in our process, and the account-wide version of this scheme is in GoHighLevel business operations structure.
How does import mapping work?
Under Contacts, Import, you upload a CSV of up to 50 MB, match each column to a contact field, create a new custom field for any unmatched column or choose "Don't import data in unmatched columns", and set lists and consent on the details step.
Rules that save a re-import:
- Create dropdown fields before the import and make the CSV values match the options exactly; an import into a dropdown with a non-matching value gives you a field you cannot filter.
- Use UTF-8 encoding and YYYY-MM-DD dates, and strip line breaks and emoji from cells; HighLevel's migration guides recommend the same.
- Unmatched columns are either new custom fields or skipped. Letting the importer create fields from column headers is how accounts end up with "Column 14" as a field name; map to fields you named first.
- Check the deduplication preference before importing; HighLevel has a separate "Allow Duplicate Contacts" setting that decides whether matching emails or phones merge or duplicate.
- Platform importers (for example the HubSpot importer) map custom fields by internal key, and a key collision with an existing field causes errors; align the keys first. Our HubSpot to GoHighLevel migration guide covers that path.
- Test with 20 rows, open 5 records, then run the full file.
Common custom field and tag mistakes
| Mistake | Result | Fix |
|---|---|---|
| A custom field used for text that never changes | Thousands of identical values to maintain | Move it to a custom value and update the templates |
| Free-text field for a category | Typos break every filter and If/Else branch | Recreate as a dropdown, migrate values with a bulk action or workflow |
| Tags that mean the same thing | Workflows miss some contacts | Pick one spelling, bulk add it, bulk remove the rest |
| Field built on the wrong object | Cannot appear in forms (opportunity field) or differs per deal (contact field) | Recreate on the right object; the object cannot be switched |
| Date field left empty | Date-based workflow stalls or sends at the wrong time | Branch on "is empty" before the Wait |
| Merge field with no value | "Hi , your appointment" in the message | No fallback exists; branch or rewrite the sentence |
| Tags used as a to-do list | Nobody removes them, so they never mean anything | Use tasks or pipeline stages for work; tags for states |
| Capitalised and lower-case versions of a tag | Two tags, half the contacts in each | Tags are case sensitive; standardize on lower case |
| Integration sends the wrong key | Field silently stays blank | Copy the key from the field list, not the display name |
How do you clean up an account's fields and tags?
Export the lists, mark each item as keep, merge or delete, consolidate tags with bulk add and remove, recreate free-text categories as dropdowns, move constant text to custom values, then delete what is left and write the one-page dictionary.
- Inventory. List every field (Settings, Custom Fields), value (Settings, Custom Values) and tag (the tag filter in Contacts). Note which workflow, form or integration writes each one. Anything with no writer is a candidate for deletion.
- Decide. Keep, merge or delete, in a spreadsheet. HighLevel's ideas board still has an open request to show where a custom value is used, so for values search your templates and workflows by key before deleting.
- Merge tags. Build a Smart List for the old tag, bulk add the new tag, bulk remove the old one. Tag removals cannot be undone directly, so do the add first.
- Fix categories. Create the dropdown field, run a workflow or bulk action that copies the old free text into the right option, then retire the old field.
- Move constants. Create the custom value, replace the text in templates with its merge tag, delete the field.
- Delete carefully. Deleting a field removes its data from records and breaks any workflow that references it, so export first and delete after the workflows are updated.
- Document. Write the dictionary and put the folder structure in place so the next person does not start the mess again.
If you want this built
Field, value and tag design is part of every GoHighLevel CRM implementation we do, and cleanup of an existing account is a common first job on a support plan or after the free account audit. Fixes are quoted as one fixed price, in writing within 24 hours of the call; book the free 30-minute call at contact our GoHighLevel team.
Sources
- HighLevel help: "Overview of Merge Fields and Custom Variables" (modified September 1, 2026; read November 2, 2026)
- HighLevel help: "How to Create and Use Custom Fields" (modified September 1, 2026; read November 2, 2026)
- HighLevel help: "Creating and Managing Custom Fields for Better Data Organization" (modified September 1, 2026; read November 2, 2026)
- HighLevel help: "How to Use Custom Fields for Opportunities in HighLevel" and "Expanded Custom Field Types for Opportunities in HighLevel" (read November 2, 2026)
- HighLevel help: "Adding Files To Contacts using a Custom Field" (read November 2, 2026)
- HighLevel help: "Create, Organize and Configure Settings for Custom Values" (modified July 25, 2025; read November 2, 2026)
- HighLevel help: "Workflow Action - Update Contact Field" and "Workflow Action - Update Custom Values" (read November 2, 2026)
- HighLevel help: "Using If/Else Workflow Action to Automate Decision-Making" (read November 2, 2026)
- HighLevel help: "Getting Started - Import Existing Contacts" (modified March 24, 2026; read November 2, 2026) and "Import HubSpot Data into HighLevel" (read November 2, 2026)
- HighLevel help: "Bulk Add and Remove Tags from Contacts", "Removing Contact Tags From Multiple Contacts" and "Getting Started With Smart Lists" (read November 2, 2026)
- HighLevel ideas board: "Find Where Custom Values Are Being Used Throughout Sub-Account" (read November 2, 2026)
Frequently asked questions about GoHighLevel custom fields
What is the difference between a custom field and a custom value in GoHighLevel?
A custom field holds data for one contact or opportunity, such as a birthday or quote number, and each record has its own value. A custom value is one account-level placeholder, such as a booking link, and changing it updates every template, workflow and page that uses it. HighLevel's merge fields overview (September 1, 2026) uses the same split.
What custom field types does GoHighLevel have?
For contacts: single line, multi line and list text, number, monetary, phone, email, URL, single and multiple dropdown, radio, checkbox group, date picker, file upload and signature. Opportunity fields add Date and Time, User and Rich Text. HighLevel's article says "and more", so check the type picker in your account.
Where do I create custom fields and custom values?
Custom fields: Settings, Custom Fields, Fields tab, Add Field, choose Contact or Opportunity as the object, then the type. Folders are on the Folders tab of the same screen. Custom values: Settings, Custom Values, New Custom Value, with their own Folders tab. Both are created one at a time.
Is there a limit on custom fields in GoHighLevel?
HighLevel says there is no strict limit on the number of custom fields or custom values, only advice to manage them carefully (checked November 2, 2026). The documented constraints are no bulk creation, no fallback values for empty fields, no object change after creation and a 250 MB cap per uploaded file.
Can I bulk upload custom fields?
No. HighLevel states that bulk creation or upload of custom fields and custom values is not supported; each is added individually. The contact importer can create a field from an unmatched CSV column, and snapshots copy fields between sub-accounts, but there is no CSV of field definitions.
How do I change a custom field from a workflow?
Use the Update Contact Field action. It updates one or several existing fields with a fixed value or a dynamic value from an earlier step, and it can clear custom fields but not standard fields. To change a custom value from a workflow, use the Update Custom Values action.
How do I use a custom field in an If/Else condition?
Add the If/Else action, choose Contact Details, select the field and an operator such as "is" or "contains". Dropdowns match on the option. Add a final branch for an empty field, because a field that was never written is blank and the contact otherwise falls through to the wrong path.
Should I use tags or custom fields to segment contacts?
Use a field for data you will filter or report on in detail (service, location, plan), and a tag for a state a workflow adds and removes (booked, no-show, customer). Tags are case sensitive and multiply quickly, so keep them to states and sources and put categories in dropdown fields.
How do I map a CSV to custom fields on import?
Go to Contacts, Import, upload the CSV (up to 50 MB), then match each column to a contact field. Unmatched columns can become new custom fields or be skipped with "Don't import data in unmatched columns". Create dropdown fields first so the CSV values match their options, and test with 20 rows.
Can you clean up my account's fields and tags?
Yes. The inventory, merge and dictionary steps above are a standard job on our support plans, and the free account audit tells you how much of it you need.