I Have 40 Custom Fields and Nobody Fills Them Out — Should I Just Delete Them?

A CRM with 40 custom fields often looks impressive during setup. It seems thorough. You can capture industry, employee count, service interest, referral partner, budget range, software stack, urgency, territory, renewal chance, preferred contact method, and twenty more things someone thought might be useful.

Then the team starts using it.

A salesperson opens a new deal, sees a long form, and fills in the fields needed to save it. Or they pick the first dropdown option that works. Or they skip the CRM and make a note in their inbox. Three months later, you have lots of fields, thin data, and reports that suggest precision you do not actually have.

The most reliable predictor of CRM failure is too many fields. Every required field is a tax on data entry. Beyond a certain point, the tax exceeds the value and users enter garbage to bypass it.

So yes: you should probably remove some fields. But do it with a little discipline instead of deleting everything in a frustrated afternoon.

A field that is 20% complete is worse than no field at all

An empty field is annoying. A field filled out one-fifth of the time is dangerous.

Say you ask every lead for "estimated annual revenue," but only 20% of contacts have a value. A report by revenue band will still make charts. It will still show totals. But it is describing the small group your team happened to complete, not your whole market.

That creates false confidence. You start making decisions from a partial sample without realizing it.

Before deciding what to delete, make a list of every custom field and answer four questions:

1. What business decision does this field support?
2. Who fills it out?
3. When do they fill it out?
4. Has anyone used it in the last 90 days?

If there is no clear answer to the first question, the field should not be required. If nobody has used it in 18 months, it is probably not an asset. It is a forgotten option sitting in the way.

Fields rarely get removed once added because they are perceived as data, even when nothing meaningful has been entered in 18 months. Treat unused fields like an old subscription: keeping them "just in case" still has a cost.

What a lean CRM actually needs

For a typical small business, roughly 15 fields across contacts, deals, and activities is enough to run a usable CRM.

Your contact record usually needs five to seven essentials:

• Name
• Company
• Email
• Phone
• Role
• Source
• Maybe customer status or service interest

A deal needs about six:

• Deal name
• Primary contact
• Value
• Stage
• Expected close date
• Source

An activity record needs four:

• Activity type
• Contact or deal
• Date
• Notes

That does not mean every business must use exactly 15 fields. A roofing contractor, bookkeeping firm, and IT provider have different needs. It means every additional field needs to earn its place. If your team cannot name the action it changes, do not ask people to fill it out.

Separate tags from custom fields

A lot of field sprawl comes from using custom fields for things that should be tags.

Tags group contacts by category. "Referral partner," "past customer," "event attendee," and "VIP" are examples. A person can have multiple tags, and the list can change over time.

Custom fields store structured, filterable facts. "Service package," "annual contract value," "state," or "renewal month" are examples. These need consistent values because you want to filter, report, or automate from them.

Use both, but do not use them interchangeably. A tag should not become your workaround for a missing structured field. A custom field should not become a pile of loosely named categories.

Keep tags under control too. Five to seven tags per contact is a practical ceiling. Review and prune them every six months. If "Webinar Lead," "Webinar Attendee," "Webinar 2024," and "Webinar March" all mean roughly the same thing, your tags are telling you the system needs a clearer rule.

Archive before you delete

If you are nervous about deleting fields, hide or archive them first. Remove them from forms, record views, and required steps. Give the team 30 days with the simpler setup.

Watch what people ask for. If nobody misses "Decision Maker LinkedIn URL," that tells you something. If your sales manager truly needs "Property Type" to qualify every deal, keep it—but make sure the field appears at the right stage, not on every new contact.

The goal is not a bare CRM. The goal is a CRM where the fields that remain are complete enough to trust.

Key takeaway

A field only earns its place if it's actually filled in and actually used. Everything else is friction dressed up as data.

Next step: Export or screenshot your custom-field list. In a 30-minute owner-and-sales-lead review, mark each field Keep, Optional, or Hide. Hide five fields nobody has used in the last 90 days, and remove every hidden field from new-record forms before your next workweek starts.