Migrate from InTouch to Twenty CRM

InTouch contacts migrate directly to Twenty People records. The People object includes name fields, email, phone, jobTitle, and a companyId lookup that requires a matching Company record to exist first in Twenty. We resolve contacts with no company to standalone People records.

InTouch company records map 1:1 to Twenty Companies using direct field-to-field translation. The Companies object holds name, domain/website, industry, employee count, and annual revenue fields from the corresponding InTouch company record. Parent-child company hierarchies in InTouch map to Twenty's nested company structure using the parentCompanyId lookup field. We preserve all company-level custom fields during the migration.

InTouch deals become Twenty Opportunities. Each deal's name, amount, stage, expected close date, and ownerId map to the equivalent Twenty fields. Opportunity records require a companyId or personId foreign key — we resolve these before migration to prevent orphaned records.

InTouch notes migrate to Twenty Notes attached to People, Companies, or Opportunities via the id of the parent record. Notes preserve body text, author/owner, and creation timestamp. Rich-text formatting in InTouch notes gets simplified to plain text for Twenty compatibility.

InTouch tasks become Twenty Tasks linked to People, Companies, or Opportunities. Every task field including title, body text, dueDate, assignee, and completion status transfers directly into Twenty's corresponding task fields. InTouch completed status maps to Twenty's completedAt timestamp, preserving the completion date from the source system.

InTouch deal stage names map to Twenty Opportunity StageName pick-list values. We create the stage options in Twenty before import and match each InTouch stage value to its Twenty equivalent. Stage probability percentages transfer as custom fields if InTouch stores them.

InTouch owner/user assignments resolve by email match against Twenty Workspace Members. Unmatched owners get flagged before migration — your team either invites them to Twenty or assigns records to a fallback user. No record lands in Twenty without a valid assignee.

InTouch activity logs (calls, emails, meetings) merge into Twenty Tasks or Notes depending on activity type. Call logs with duration and outcome become Tasks with type classification; email logs become Notes with subject preserved. Original activity timestamps transfer as custom datetime fields in Twenty.

InTouch custom fields defined in matter templates map to Twenty custom fields on People, Companies, or Opportunities. Twenty requires these fields pre-created in Settings → Data Model before import — we deliver a field creation checklist as part of the migration plan.

InTouch file attachments on contacts, companies, or deals re-upload to Twenty Files. Files attach to the parent record by id after both file and record exist. File size limits follow Twenty's storage configuration — no attachment larger than 25MB transfers without chunking.

InTouch tags and labels on contacts or companies migrate to Twenty as multi-select custom fields. We create a Select field in Twenty with the unique tag values as options, then populate each record's field with applicable tags. Unused tags get flagged for cleanup.

InTouch users map to Twenty Workspace Members. Email serves as the unique identifier for matching between systems. Before migration begins, all active InTouch users must accept their Twenty invitations so user references resolve correctly during the migration run. User accounts left uninvited will cause owner assignment failures and orphaned records in Twenty.