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 attach to any object, custom objects are unlimited on every plan, the Organization tier takes permissions down to fields and rows, and a metadata API creates and deletes objects, fields and relations, while emails and meetings log themselves onto records. The import guide requires no duplicate email addresses in the file, so cleanup sits with the buyer before upload, and we found no public information on field validation, required fields, bulk merge or field-level change history. 11 5 6 2