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 linked through modules, and duplicate checking runs on create and edit, blocking the save and offering the existing record — but the check keys on fixed fields (company ID, contact email) and I found no public information on bulk merge or cleanup tooling. Custom fields scale from 50 on Standard to unlimited on Plus, with mandatory fields, unique fields and field-level permissions at the top tier; no custom objects are documented. Decent entry hygiene, thin for repairing a dirty import. 2 3 4