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 Migrator
Companies and people are proper separate objects with custom fields across persons, companies and deals, ownership changes, visibility limits, and a merge that genuinely carries over tasks, deals, files and wall posts. But duplicate search needs admin permission and the Automation plan or higher, and bulk merging stops at ten contacts — hygiene is a paid privilege. We found no public information on custom objects, field-level history, or field-level validation. 2 3 11