Migrate from Close to Twenty CRM

Close Leads map to Twenty Person records. The Lead status label, owner, and all standard fields (name, email, phone, address) migrate directly. We resolve the owner by email match against Twenty's Members. If the customer has deduplication rules in Twenty they want to enforce, we flag the dedupe key strategy during scoping; Close Lead IDs are preserved in a custom field close_lead_id__c for audit.

Close Contacts map to Twenty Persons. Contacts in Close carry an organisation field linking to a Lead or Company; we resolve that reference during import. Like Leads, the owner maps by email to a Twenty Member. We preserve any contact-specific Custom Fields attached at the Contact level. close_contact_id__c is stored for cross-reference.

Close does not have a standalone Company object; organisation data lives as the Organisation field on a Lead or Contact. If the customer uses Close's Organisation field as a normalised company record, we extract unique Organisation values, deduplicate by name and domain, and create Twenty Company records first so that the Person-to-Company lookup is satisfied at import time.

Close Opportunities map directly to Twenty Opportunities. Pipeline stage, deal value, expected close date, and owner migrate with the same field types. We create the Twenty Opportunity before importing records so that the pipeline-stage reference is valid. Custom fields on Opportunities carry over as Twenty Custom Fields on the Opportunity object.

Close Pipelines are containers for Opportunity stages. We configure the Twenty Opportunity pipeline column and stage values in Settings before migration, matching Close stage names and ordering. Stage probabilities from Close migrate as Twenty stage-level weights if the customer uses them for forecasting.

Close call logs stored as activity records in the JSON export map to Twenty Task records with the body carrying call duration, disposition, and outcome. We set ActivityDate to the original Close timestamp and link the Task to the corresponding Person or Opportunity by resolving the activity's associated Lead or Contact reference. Call recording audio files are downloaded from Close and re-uploaded as attachments on the matching Twenty Task.

Close email activity records migrate as Twenty Task records with the email body preserved in the Task body field and the subject carried as Task title. Direction (sent/received) is encoded as a custom field. We link each email Task to the correct Person by resolving the Close activity's associated Contact or Lead reference.

Close SMS activity records migrate as Twenty Task records with the SMS body in the Task body and direction stored as a custom field. We resolve the associated Contact or Lead to the correct Person in Twenty and link the Task. Threading context is preserved by setting the parent reference to the same Person.

Close task activities (assigned tasks, to-dos) map to Twenty Tasks with Status, Priority, due date, and assignee preserved. Assignee resolves by email match to a Twenty Member. Completed status and completion timestamp carry over from Close's completed field.

Close Custom Activities require a three-phase migration sequence. First, we create the matching Custom Object in Twenty via Settings → Data Model with the same name and field structure. Second, we create all type-scoped Custom Fields on the Twenty Custom Object before any records are imported. Third, we import the Custom Activity instances with their field values. Skipping phase two results in validation errors because Twenty's CSV import creates records only; fields must pre-exist per Twenty's documentation (docs.twenty.com/user-guide/data-model/how-tos/create-custom-fields).

Custom Fields on Close Leads, Contacts, and Opportunities map to Twenty Custom Fields on the corresponding object. We read the Close field definition (type, choices, required flag, default value) via the API and create matching Twenty fields with the same type and option labels. Multi-select options in Close map to Twenty multi-select fields. Fields must be created in Twenty before CSV import begins; we flag this as a required pre-import step in the scoping document.

Close attachments on Leads and Contacts are retrieved via the Close API as binary files and re-uploaded to the corresponding Twenty Person record as attached Files. We preserve the original filename, MIME type, and upload timestamp. If a referenced attachment is missing (deleted in Close before export), we flag it in the reconciliation report.