Manage CRM fields and tags

Fields store facts; tags express reusable classification

Open Settings → CRM fields & tags. Custom fields belong to Contact, Company, or Deal records and have a data type. Tags are lightweight workspace labels used in segmentation and automation. Do not use a tag when a typed, reportable fact is required, and do not create a custom field for a short-lived campaign label.

Create a custom field

1. Select New custom field.
2. Choose the CRM object: Contact, Company, or Deal.
3. Enter a durable display name.
4. Choose the field type that matches future reporting and imports.
5. For a dropdown, add at least one stable option and order options deliberately.
6. Mark the field required only when every new and edited record can supply a truthful value.
7. Save and test it on a controlled record.
8. Update import mappings, saved views, automations, and team procedures that should use it.

Field

Object

Purpose

Determines whether the field appears on contacts, companies, or deals; it is a schema boundary, not a display filter.

Accepted values

Contact, Company, Deal

Edit or archive a field

Changing a field's name or dropdown options can alter how operators interpret existing values. Before editing, search imports, automations, conditions, list logic, and reports that reference it. Use the impact preview before archival. Archiving is safer than pretending an old concept means something new; archived fields can be restored through the supported lifecycle.

Do not recreate an archived field with the same label unless you intentionally want a different field identity.

Create and retire tags

1. Expand Advanced → Tags.
2. Select New Tag, enter a unique operational name, and choose a color that supports recognition without carrying meaning by color alone.
3. Test the tag in a contact workflow and any intended automation.
4. Before deleting, search lists, filters, campaigns, automations, and team procedures that depend on it.
5. Confirm deletion only after a replacement or migration is complete.

Data-quality review

Quarterly, search for duplicate labels, overlapping dropdown values, required fields with low completion, tags with no clear owner, and archived definitions still referenced in workflows. Prefer one canonical definition with documented allowed values.

Recovery

If a field change causes errors, stop dependent imports or automations, restore the field if supported, and compare identifiers rather than labels. For a deleted tag, do not bulk-apply a guessed replacement. Preserve object, field/tag ID, old and new definition, change time, affected automation/import IDs, and redacted example records.