Migrate from Daffodil CRM to Twenty CRM

Daffodil CRM Contact records map to Twenty Person records. We extract name fields (firstName, lastName), email address, phone number, company association, lifecycle stage, and all custom field values via CSV export or direct database query. The contact-to-company link resolves via the Organization field during People import. Daffodil CRM lifecycle stage values are preserved as a custom picklist field on Person for audit and reporting continuity.

Daffodil CRM Company records map to Twenty Company records. We extract company name, domain or website, industry classification, address fields, employee count, and annual revenue if present. Company records are imported before People records to satisfy the Organization lookup relationship. The company name or an assigned external ID serves as the dedupe key during import to prevent duplicate Organizations.

Daffodil CRM Deal records map to Twenty Opportunity records. We extract deal name, amount, stage, expected close date, owner assignment, and associated Person and Company links. Custom pipeline stages present in the source are translated to Twenty stage values configured in Settings → Data Model before import. Amount fields are validated for numeric format; currency handling is coordinated with the customer during scoping.

Each distinct deal stage present in the Daffodil CRM export maps to a Twenty Opportunity stage value that we pre-configure in the Twenty workspace before migration. Stage ordering and probability percentages transfer where present in the source data. If the customer uses multiple deal pipelines, we map each to a separate stage group in Twenty's pipeline configuration.

Daffodil CRM Activity records export as flat rows with a type field indicating call, email, meeting, or task. We map activities to Twenty Task records (for calls and tasks) or Note records (for emails and freeform notes). The activity date, duration, outcome, and related Person or Company link migrate with the original timestamp preserved for timeline accuracy. Activities without a resolvable parent Person or Company are linked to the closest related Organization.

Daffodil CRM custom fields vary per customer implementation. We request a complete field inventory from the customer before mapping begins and create matching custom fields in Twenty's Settings → Data Model before any data import. Multi-select picklist fields are recreated as multi-select picklists; date fields are reformatted to ISO 8601; text fields map directly. Fields must exist in Twenty before the CSV import runs because the import creates records, not fields.

Daffodil CRM custom objects map to Twenty Custom Objects created in Settings → Data Model. We pre-create the destination schema including all custom fields and lookup relationships before migration begins. Custom object records import after standard objects to ensure parent-record lookups resolve correctly. Any lookup fields in the custom object that reference Contacts, Companies, or Deals are resolved using the external ID or name matching established during standard object import.

Daffodil CRM User or Owner records map to Twenty User accounts. We extract user name, email address, role designation, and active status. Users must be provisioned in Twenty (via Settings → Members) before importing records that reference them as owners or assignees. Inactive users are archived in Twenty with their original role preserved for historical record assignment.

Tags applied to Contacts, Companies, or Deals in Daffodil CRM export as comma-separated values or individual rows per tag. We parse these values and create corresponding Twenty Topics, then generate TopicAssignment records linking each topic to the relevant Person, Company, or Opportunity. The customer selects whether tags should become Topics or custom picklist values during scoping.

File attachments stored within Daffodil CRM are not reliably exportable via standard CSV. We export attachment metadata (filename, upload date, associated record ID) as a CSV reference table rather than migrating the file content. The customer receives this attachment inventory as a spreadsheet and can manually re-upload files to the relevant Twenty records, or we provide a separate file re-upload service as an add-on engagement.