Contact & data model
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Data Protection Officer
Custom fields and picklists are evidenced across Cases, People and Activities, with configurable form layouts and fields hidden by default until an administrator exposes them — more than cosmetic customization, and the field visibility hints at permissioned access. We found no public information on deduplication, merging, field validation or relationships beyond the standard model, so complex data models likely still need workarounds. 2 3