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
Contacts and companies are plainly related records — the Gmail tool matches a contact to an existing company and keeps emails as closed activities on the record, which is history I want to leave with. But we found no public information on custom field types, required fields, or any deduplication or merge tooling, and that hygiene layer is exactly what decides whether a move-in or a move-out is clean. 3 1