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
Custom fields of several types sit on leads, deals, contacts, companies and documents with limits per plan, duplicates are matched by phone and email on import, and the API answers 409 with possible duplicates unless you force it through. An activity timeline for calls, messages and tasks is reachable on leads and deals through the API, with stage history and an audit log of every change on the record. We found no public information on bulk merge tooling or field-level permissions, which is what separates a workable model from one I would trust with a migration. 2 4 5 8