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
Lead, contact, company, deal and activity objects are all named, custom CRM entities can be created, and required fields plus custom access permissions are documented — a real system of record. Import hygiene is my worry: deduplication appears only as a find-or-create step inside a Zapier recipe, and we found no public information on bulk merge or duplicate-handling tooling in the CRM itself, which is exactly the scar I check for before a migration. 7 8 9 11 6