Contact & data model
How this is scored
Depth and hygiene of the core records: contacts, companies and deals linked to each other, custom fields, activity history on the record, import hygiene and deduplication.
0 — Not a CRM data model; the product is an address book or mailing list with no companies or deals.
3 — Contacts, companies and deals linked to each other, with a few custom fields and notes on the record.
5 — Custom fields on contacts, companies and deals, an activity timeline (emails, calls, meetings, notes) on each record, and duplicate detection or merging of records.
8 — Custom objects or relationships beyond the standard model, field types with validation and required fields, bulk merge and deduplication tooling, and field-level permissions.
10 — A modelable system of record: custom objects with their own relations, pipelines and permissions, field-level change history, data-quality tooling (enrichment, bulk cleanup, rules) documented, and the model exposed completely through the API.
The Migrator
Contacts, companies and opportunities hang together in a Contact → Opportunity → Pipeline → Stage model, with notes (titles, color labels, attachments, pinning) across all three record types and roles governing visibility. Deduplication is genuinely configurable — primary and optional secondary match on email or phone, automatic merging on CSV upload, auto-merge of messenger contacts, and a manual merge feature — which is the import hygiene I look for, and custom fields are documented on contacts and companies. We found no public information on custom objects, field validation, bulk merge tooling or field-level permissions, so I stop one notch above the middle. 4 5 7 8 9 13