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 deals are all present with documented REST endpoints, the API can customize lists and fields, and imports handle existing records with merge-or-replace rules plus a created selection for follow-up processing — real hygiene on the way in. Activity history and notes appear in the sales copy (check a caller's history, shared notes and history in one place). I found no public information on custom objects, field-level permissions, or bulk merging of records already in the database, so this stays a solid standard model rather than a modelable system of record. 5 6 7 12 13