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
Contact records carry the standard relations — organization, deals, quotes, interactions and notes on one record — and import time offers real duplicate handling with skip, create-new or update-existing choices plus a summary counting merged, skipped and failed records. But we found no public information on custom field types with validation, required fields, or dedupe and merge tooling outside of the import flow, so anything beyond the standard model stays unproven. 2 3