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
The merge story is unusually thorough: duplicate warnings at creation, a master-record merge in the interface with field-by-field advanced mode, and the same merge exposed through the API. Custom entities exist via the API and activities carry history on the records, though duplicate detection only fires on an exact name match and we found no public information on field validation or field-level permissions. Strong hygiene tooling, a step short of the full toolbox. 2 3 5 9