Migrate your Twenty CRM data

People is the core contact object storing individuals with fields for name, email, phone, job title, and a companyId relation. We migrate People records using email as the unique reference key and preserve company associations via the companyId foreign key. Soft-deleted People records still count toward uniqueness checks during import.

Companies stores business accounts with industry, size, location, and domain fields. Companies must be imported first because both People and Opportunities reference them via foreign keys. We use domain as the unique lookup when importing related records. Any deleted Company with the same domain will be restored on import.

Opportunities tracks deals with stage, amount, close date, and links to both a Company and a Person (or multiple Persons). We map stage names explicitly to avoid silent mismatches when source and destination use different pipeline stage naming conventions. Opportunities must be imported after Companies and People exist.

Tasks store to-dos linked to People, Companies, Opportunities, or other records with fields for title, due date, assignee, and completion status. We preserve the record-to-task relations by importing parent records before Tasks and referencing them by their unique identifier or email.

Notes are free-form text attachments that can be linked to any record. We migrate Notes by mapping their relational target to the corresponding record ID or email in the destination. Note body content transfers as-is; formatting fidelity depends on the source system exporting rich text or plain text.

Custom Objects are user-defined entities created to hold business-specific data (e.g., Subscriptions, Events, Rockets). Unlimited on Organization tier, capped at 10 on Pro. We map Custom Object schemas field-by-field, handling field type differences between source and destination. Custom objects with relations to standard objects must be imported last.