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
Leads as companies, contacts as people and opportunities as deals, all linked, with up to 250 typed custom fields assignable across leads, contacts, opportunities and custom activities, and every call, text and email already part of the record. The importer checks for existing leads before creating duplicates and offers add-missing, replace or skip handling, which is the hygiene I want; native bulk merging of existing duplicates is not documented — merge and dedupe tooling comes through a third-party called Dedupely — and field-level control stops at restrict-editing by role. 4 5 6 13 1 11 2