Migrate from Clarify CRM to Twenty CRM

Clarify Contact records map to Twenty Person records. The Person object in Twenty covers individual contacts with name, email, phone, and job title fields. We preserve AI-enriched properties (autonomous field updates from Clarify's agents) as standard text fields in Twenty, but flag any AI-generated content for customer review since Twenty has no autonomous field engine to interpret or continue populating those properties.

Clarify Company records map directly to Twenty Company records. Domain-based enrichment from Clarify transfers to Twenty's Website and domain fields. We validate domain normalization during the transform phase since Clarify sometimes stores domain variants (with/without www, http/https) differently than Twenty expects.

Clarify Deal records map to Twenty Opportunity. Deal value, stage, close date, and custom properties transfer directly. Clarify's autonomous agents may have updated deal fields automatically; we preserve those values but note them as manually-entered in Twenty since Twenty's Opportunity records do not receive autonomous updates.

Clarify's configurable pipeline stages map 1:1 to Twenty Pipeline Stages. We capture the full stage sequence and any custom stage names, creating equivalent stages in Twenty before Deal import. Stage probability values from Clarify transfer to Twenty's stage configuration.

Clarify call activities map to Twenty Task records with task type distinguished via a custom field or tag. Call duration, disposition, and outcome from Clarify transfer to Twenty custom fields on the Task. Parent record (Person or Company) links resolve via email or name matching.

Clarify email activities map to Twenty Task records. Email subject and body content transfer to the Task description field. We flag emails that were generated or enriched by Clarify AI for customer review since the AI context does not carry forward in Twenty.

Clarify meeting activities map to Twenty Event records. Meeting title, date, duration, and attendee list transfer. Location and meeting notes transfer to Twenty Event fields. We create Person records for attendees that do not yet exist in Twenty.

Clarify notes map to Twenty Note records. Note body content and timestamps transfer directly. Notes are linked to the parent Person, Company, or Opportunity via Twenty's attachment model.

Clarify's AI-generated meeting summaries are stored as enriched note content attached to activity records, not as structured fields. We export these summaries as Note records in Twenty and flag them during delivery so the customer knows which records contain AI-generated content that requires review. Twenty has no native AI summary field; the content is preserved as plain text.

Clarify tag-based labeling for records and deals maps to Twenty's Tag system. We preserve tag assignments during migration and map them to Twenty's equivalent tagging structure. Customers choose during scoping whether to migrate tags as native Twenty tags or as a custom multi-select field.

Clarify custom fields on Contacts, Companies, and Deals map to Twenty custom fields. We pre-create all custom field definitions in Twenty Settings → Data Model before importing records, matching Clarify field types (text, number, date, currency, select) to the appropriate Twenty field types. Fields that have no Twenty equivalent are flagged in the scoping report.