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 only data-model evidence is marketing copy about 'building blocks for a custom CRM' that 'adapts as the business evolves' — not one word on field types, required fields, dedupe, merge, or activity history. I've been promised 'adapts as the business evolves' before; it usually means I build the model myself and the duplicates are my problem. 1