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 standard model is evidenced — customers, leads and opportunities in a visualized pipeline, with customer history, notes and automatic logging of calls, visits and emails on the record. What I found no public information on is the hygiene layer that makes a database trustworthy after a migration: custom fields, required fields, field-level permissions, and any merge or deduplication tooling, and that silence decides this score. 1