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
Relations between people and companies are real — the import path links contacts to companies via external identifiers — and custom fields exist on contacts, but the evidence shows custom fields arriving via code and a three-part import procedure to keep contacts with their companies. We found no public information on deduplication or merge tooling, which is exactly the silence that bites during a migration. Visibility of pipeline records is governed by sales access-right groups, which is record-level rather than field-level. 1 4 5 6