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 and companies sit in one linked model with custom fields across number, currency, file, contact-link and text-area types, relationships between companies, contacts at multiple companies, and a history of notes, meetings, follow-ups and emails on each record. Duplicate hygiene is documented end to end — entry-time warnings, a bulk merge page that detects on shared email or phone, merge undo and import undo — which is exactly the scar tissue I probe. We found no public information on field validation, required fields, field-level permissions or custom objects, so I stop short of the top levels. 1 4 5 4