What custom person account fields do and why you might need them

A custom person account field lets you store information about a contact that your CRM system doesn't have a built-in space for. Instead of cramming notes into a general text box or creating separate spreadsheets, you build a field that works like the standard ones — searchable, sortable, and visible on every contact record.

The most common reason to create one is to track something specific to how your business works. A real estate agent might add a "Preferred contact method" field. A nonprofit might add "Volunteer skills" or "Donation frequency". A service business might add "Equipment owned" or "Preferred appointment time". These fields save time because the information is always in the same place, formatted the same way, instead of buried in notes.

The exact steps depend on which CRM you use — Salesforce, HubSpot, Pipedrive, and others all work differently. But the underlying logic is the same: you define what the field is called, what type of information it holds, and who can see it.

Key Takeaways

  • Custom fields store information your CRM doesn't have a standard space for, and they work like built-in fields — searchable and visible on every record.
  • The steps to create one differ by CRM system, but most require you to access settings or administration, not the main contact view.
  • You choose the field type (text, number, dropdown list, date, checkbox) based on what kind of information you're storing.
  • Once created, a custom field appears on every contact record of that type, so plan the name and purpose before you build it.

How to create a custom field in Salesforce

In Salesforce, custom fields live in the object settings, not in the contact record itself. Start by clicking the gear icon in the top right corner and select "Setup". In the left sidebar, search for "Object Manager" and click it. Find "Account" or "Contact" depending on whether you're adding a field to company records or individual people.

Click the object name, then click "Fields & Relationships" in the left menu. Click "New" in the top right. Salesforce will ask you to choose a field type — "Text" for short entries, "Text Area" for longer notes, "Number" for quantities, "Picklist" for dropdown menus, "Checkbox" for yes/no, or "Date" for calendar entries. Pick the type that matches what you're storing.

Fill in the field label (the name people see) and the field name (what the system uses internally — Salesforce creates this automatically, but you can change it). Decide whether the field is required, whether it should be unique, and who can see it. Click "Save" at the bottom. The field now appears on every contact or account record of that type.

How to create a custom field in HubSpot

HubSpot calls custom fields "custom properties". Click the settings icon (gear) in the top right, then go to "Data Management" and click "Properties". Choose whether you're adding a property to Contacts, Companies, or Deals. Click "Create property" in the top right.

Name the property and choose its type: "Single-line text" for short entries, "Multi-line text" for longer notes, "Number" for quantities, "Dropdown select" for a list of options, "Checkbox" for yes/no, or "Date picker" for calendar entries. You can also set a description that explains what the property is for — this helps other people on your team understand when to use it.

HubSpot lets you decide whether the property is visible in the contact record, whether it shows in forms, and whether it's required. Once you save, the property appears on every contact record and can be used in workflows, reports, and filters.

How to create a custom field in Pipedrive

In Pipedrive, custom fields are called "custom fields" and live in the settings for each data type. Click the settings icon (gear) in the top right corner. Go to "Company settings" or "Personal settings" depending on your account type, then click "Fields and their visibility".

Choose the section where you want to add the field — Deals, Persons, Companies, or Activities. Click "Add custom field". Name it and choose the field type: "Text" for short entries, "Numeric" for numbers, "Select" for a dropdown, "Multiselect" for multiple checkboxes, "Date" for calendar entries, or "Phone" for phone numbers. Set whether the field is mandatory and who can see it.

Once saved, the field appears in that section for all records. You can reorder fields by dragging them, and you can hide fields you don't use often without deleting them.

Choosing the right field type for what you're tracking

The field type you choose affects how the information can be searched, sorted, and reported on. A "Text" field works for almost anything — names, descriptions, codes — but it's harder to filter or sort because the system doesn't know what the entries mean. A "Dropdown" or "Picklist" field is better when you have a fixed set of options, because you can filter by any option and see counts of how many records have each one.

Use "Number" for quantities, measurements, or IDs that you might add or compare. Use "Date" for anything time-based — contract renewal dates, last contact, preferred appointment times. Use "Checkbox" only for yes/no questions, because it takes up less space and is faster to fill in than a dropdown with two options. Use "Text Area" or "Multi-line text" only if you need to store paragraphs; for short notes, a regular text field is cleaner.

If you're unsure, start with "Text" — you can always change it later in most systems, though changing a field type may affect existing data. The key is to think about how you'll use the information: if you'll filter by it, use a dropdown. If you'll calculate with it, use a number. If you'll search for it, use text.

Planning field names and descriptions so your team uses them correctly

A field name that makes sense to you might confuse someone else on your team. "Pref contact" might mean preferred contact method, preferred contact time, or preferred contact person. Spend a minute writing a clear label and, if your CRM allows it, a description.

In Salesforce, the field label is what people see; the field name is what developers see. Make the label clear and human-readable. In HubSpot, add a description when you create the property — it shows up in the property settings and helps teammates understand when to use it. In Pipedrive, the field name is what shows on the record, so make it specific.

Also decide upfront whether the field is required. A required field slows down data entry if people don't always have the information, but it ensures the field is never left blank. Most teams make fields optional unless there's a strong reason otherwise.

Viewing and editing custom fields after you create them

Once a custom field exists, it appears on every record of that type. In Salesforce, you can edit the field settings by going back to Setup, Object Manager, the object name, and Fields & Relationships — click the field name to change its properties. In HubSpot, go to Settings, Data Management, Properties, and click the property name. In Pipedrive, go to Settings, Fields and their visibility, and click the field.

You can usually change the field label, description, and visibility without affecting existing data. Changing the field type is riskier — some systems warn you that data might be lost or reformatted. If you need to change a field type, test it on a copy of your data first, or contact your CRM's support team.

If you create a field and realize you don't need it, most systems let you hide it instead of deleting it. Hiding preserves the data in case you change your mind later, while deleting removes the data permanently.

Frequently Asked Questions

Can I change a custom field after I've created it?

Yes. You can change the label, description, and visibility in most systems without losing data. Changing the field type is possible but riskier — some systems will reformat or lose data if you change a text field to a number field, for example. Check your CRM's documentation or test on a small set of records first.

What happens if I delete a custom field?

The field and all the data in it are usually deleted permanently. Most CRMs let you hide a field instead, which keeps the data but removes it from view. If you think you might need the information later, hide it rather than delete it.

Can I use a custom field in reports and filters?

Yes, in most systems. Once a custom field exists, you can filter records by it, sort by it, and include it in reports. Dropdown and checkbox fields are easiest to filter because the system knows all possible values. Text fields can be filtered too, but the search is less precise.

Do I need permission to create a custom field?

In most CRMs, only administrators can create custom fields. If you don't have access to settings, ask your CRM administrator to create the field for you. They can also set who can see and edit it.

How many custom fields can I create?

Most CRMs have limits. Salesforce allows hundreds of custom fields per object, but very large numbers can slow down the system. HubSpot and Pipedrive also allow many custom fields, but check your plan — some limits depend on your subscription level. Start with the fields you actually need rather than creating extras.