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
Companies and people sit on separate lists with deals, correspondence, tasks and notes on each profile, custom form fields, and an admin-gated duplicate search that matches on Tax ID, Regon and contact details; merging up to ten records carries over deals, tasks, wall posts and files. I found no public information on custom objects, field-level permissions or field-level change history. Import-time dedupe this specific is exactly what I look for when moving a company in. 2 3 11