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
Lead and deal management, dynamic customer lists and an automatically maintained customer history are confirmed, and the Lexware contact import checks existing records for duplicates — though that duplicate checking is evidenced only for the Lexware path. We found no public information on custom fields, field types and validation, merge tooling, or permissioned field access, which keeps this in the basic tier with history on the record as its one real hygiene point. 1 3 4