Contact Custom Fields
Use custom fields to store contact data that is specific to your business.
Custom fields let your workspace track contact details that are not part of the standard CRM fields.
Plan custom fields before importing or bulk editing contacts. A clean field structure makes filters, table views, reports, and automation easier to trust.
When to Use Custom Fields
Use a custom field when the data is structured and needs to be filtered, reported on, imported, or bulk edited. Examples include:
- Lead source.
- Region.
- Industry.
- Customer tier.
- Renewal month.
- Onboarding stage.
- Preferred service.
- Consent or qualification flags.
Use notes or comments instead when the information is unstructured context.
Do not create a custom field for information that belongs in a standard field, account, deal, ticket, task, or note. Put data where the team will naturally look for it later.
Choose the Right Kind of Field
Choose a list-style field when users should pick from fixed answers, such as lead source, region, or customer tier. Choose a text field when the answer is open-ended, such as a short note or external reference.
Use consistent option names. For example, choose either Referral or
Referred, not both. Inconsistent options make filtering and imports harder.
For yes/no information, use a structured option or checkbox-style field instead
of free text. Values such as yes, Yes, Y, and confirmed are hard to
filter consistently after import.
Use Custom Fields in Contacts
After a custom field is configured for contacts, users can:
- Add the value while creating a contact, or update it later.
- Show the custom field as a column in the contacts table.
- Filter contacts by the custom field.
- Bulk edit the field for selected contacts when needed.
Add important custom fields to saved table views when the team needs to review them often. If the field is hidden from the table, teammates may forget to keep it updated.
Maintain Custom Fields
Review fields after imports, campaign changes, and process changes. Archive or rename fields carefully because teammates may depend on them in filters, views, forms, imports, and workflows.
Before changing options on a list field, check whether existing contacts already use those values.
If a field is used by forms or workflows, update those mappings before removing or renaming the field. Otherwise new submissions may still arrive, but the data may stop landing where the team expects.
Importing Custom Fields
If a CSV file has a column that does not match a standard contact field, create the custom field before importing. Then map the CSV column to that field during the import.
Run a small import first when a custom field is important. Confirm the values appear in the contact detail page, table columns, and filters before importing the full file.
Normalize source values before upload. For list-style fields, make sure the CSV uses the same option names already configured in Agiled.
Field Planning Checklist
Before adding a contact custom field, decide:
- who owns the field
- whether the value should be required on forms
- whether imports will populate it
- whether users need it as a table column
- whether workflows or reports will depend on it
- how old or unused values will be cleaned up
Troubleshooting
If a custom field does not appear on a contact, confirm the field is configured for contacts and that the page was refreshed after field setup.
If imported values look inconsistent, clean the source CSV and normalize option names before reimporting or bulk editing.
If a filter returns fewer contacts than expected, check blank values, spelling, and whether the field is stored as text or fixed options.