Migrate from InTouch CRM to Twenty CRM

InTouch Contact records map directly to Twenty People. The InTouch contact's name fields (first name, last name, salutation) map to Twenty's nameComponents. Email, phone, and address fields map to the corresponding standard fields on People. We extract the contact's associated Company reference and use it as the link to the Twenty Company record during People import.

InTouch Company records map directly to Twenty Company. The company name becomes the Twenty Company display name. Domain, industry, and address fields migrate to the corresponding standard fields. Company is imported before People so that the relationship lookup is satisfied at the moment of People insert.

InTouch Deal records map to Twenty Opportunity. The deal name maps to Opportunity name. Deal amount, expected close date, and pipeline stage map to the corresponding Opportunity fields. We resolve the associated Contact (as the Opportunity's primary person link) and the associated Company at migration time using the lookup relationships.

InTouch's user-defined pipelines and their stage labels (Open, Qualified, Proposal Sent, Won, Lost) map to Twenty's Opportunity stage values. Each InTouch pipeline becomes a set of stage values in Twenty's Data Model. We preserve the stage ordering and probability percentages where InTouch exposes them. Closed-won and closed-lost reasons from InTouch migrate as custom picklist fields on Opportunity.

InTouch activities with a task type map to Twenty Task. The activity subject, description, due date, and status migrate to the corresponding Task fields. We set the Task assignee by resolving the InTouch activity owner email to a Twenty User. Activity timestamps are preserved on the Task's ActivityDate for timeline ordering.

InTouch activities with a note type map to Twenty Note. The note body migrates as the Note content, and the note title becomes the Note title. Notes are linked to the parent People, Company, or Opportunity record via Twenty's relationship model.

InTouch call activity records map to Twenty Task with TaskSubtype set to Call. Call duration and disposition migrate to custom Task fields if present in the InTouch export. ActivityDate is preserved from the original InTouch timestamp.

InTouch meeting activities map to Twenty Task records with a meeting type flag. The meeting title, description, start time, and end time migrate to the corresponding Task fields. Attendee information from InTouch migrates as additional Note records or as custom multi-select fields on the Task.

InTouch custom fields defined on Contact map to custom fields on Twenty People. Field types are translated: InTouch text fields become Twenty text fields, picklist fields become select fields, date fields become date fields. Custom fields must be pre-created in Twenty Settings → Data Model before CSV import; the CSV import creates records, not fields.

InTouch custom fields defined on Deal map to custom fields on Twenty Opportunity. We preserve field labels, data types, and any picklist option values. The same pre-creation requirement applies: custom fields must exist in Twenty before the Opportunity CSV import runs.

InTouch Owner records map to Twenty User accounts. We resolve owners by email match. The customer's admin must invite all team members to Twenty and wait for acceptance before importing any records with owner references. Owners without a matching Twenty User go to a reconciliation queue for manual provisioning.

InTouch supports multi-company contact management, where a single contact is linked to multiple companies. Twenty's data model links a People record to one primary Company but allows additional company associations via custom fields or linked records. We preserve all company associations during migration and flag any multi-company links that require a custom configuration in Twenty.