The Single Customer Record: Which Fields Earn Their Place — and Which to Delete
Post 27 Sep 2026 CRM data hygienecustomer recordssales operationsdata privacyhandover process
Delete any field that doesn't change a decision. If leaving it blank stops no call, no quote and no installation, its only contribution is drag. A customer record isn't a registration form — it's a decision source. Every surplus field lowers the accuracy of the important ones, because your team treats the whole form at the same speed.
One test decides whether a field stays: what changes if it's empty?
Ask a single question of each field: who would act differently because of it? "Industry" changes the rep's opening message and the product list worth pitching — it stays. "Approximate headcount" at a company selling per-user subscriptions changes the price — it stays. "Year founded" changes nothing in most businesses — delete it.
The working rule: a field with no identifiable decision owner is a dead field, however pleasant the trivia looks.
The four layers of a customer record
- Identity: who they are and who you're legally dealing with — registered name, tax number, city, industry.
- Commercial terms: price tier, payment terms, currency, renewal clause.
- Buying committee: who decides, who recommends, who signs, who pays.
- Service history: what happened after the sale — tickets, installations, recurring complaints.
Any field that doesn't belong to one of these layers is probably surplus.
Fields that earn their place
| Field | The decision it changes |
|---|---|
| Tax number | Invoice validity; prevents the same customer existing twice under two names |
| First-touch channel | Where marketing budget goes next |
| Decision maker and role | Who receives the proposal, and whose sign-off is needed |
| Agreed payment terms | Finance gets a warning before shipping |
| Actual installation site | Technician scheduling without an extra phone call |
| Previous loss reason | The angle for the next attempt |
Fields to delete today
- Duplicates: "Mobile," "Contact mobile" and "Phone number" — three fields for one number, and nobody knows which is current.
- Long free-text boxes: a "General notes" field where every rep writes in their own style is never read, never filtered, and never reportable. Replace it with a short picklist.
- Filled once, never read: "Current competitor" is a luxury unless you have a written competitive response for each named competitor.
- Manually calculated values: anything the system can derive from other fields doesn't deserve human data entry.
Privacy and compliance: data that shouldn't have a field at all
Don't create a field for ID card scans, bank card numbers, or personal notes about the customer (health, affiliation, family circumstances). The existence of a field is an invitation to fill it. If you don't need it to fulfil the contract or issue the invoice, don't collect it. With personal data, the default is minimisation, not "just in case."
The real test: handover from sales to operations
Useful fields reveal themselves at handover. If operations has to call the customer back about something they already told the rep, that detail either has no field or has a field nobody fills.
Put both teams in a room for one hour and ask: what are the five questions we keep asking customers twice? Those five are your required fields. Everything else is optional.
In Effistar you can make a deal's move to "Won" conditional on exactly those fields being complete, so completeness becomes a by-product of the process rather than an admin chase.
## A two-week cleanup planWeek one — measure: pull the fill rate for every field. Anything under 30% is either useless or unclear; ask the team which before you judge.
Week two — archive, then delete: hide candidate fields from the interface without deleting the underlying data. Wait another two weeks. If nobody asks for them, remove them permanently.
Start tomorrow with one field. Open the customer form, pick the longest text field in it, and ask who last read it. The answer decides its fate.