Migrate from Tango CRM to Twenty CRM

Tango CRM Contact records map to Twenty Person records. Standard fields (full name, email, phone, address) migrate directly. We use email address as the dedupe key. If Tango CRM exports Contacts with associated Company links, we preserve the relationship by resolving the Company name to the Twenty Company record at import time. Custom Contact properties require explicit field-level mapping and type matching against Twenty's field type options.

Tango CRM Company records map directly to Twenty Company. Domain, industry, size, and address fields migrate to Twenty Company equivalents. Company name serves as the dedupe key. Parent-company or hierarchy relationships in Tango CRM map to Twenty's self-referential Company relationship field if present. We resolve Company records before Person records to satisfy the lookup relationship at import time.

Tango CRM Deal records map to Twenty Opportunity. Deal name, value, expected close date, and owner transfer directly. The pipeline stage name does not map 1:1 to Twenty's stage labels — we produce a stage mapping worksheet during the mapping phase and reconcile labels at import time. Probability and stage order are preserved independently of label names.

Tango CRM pipeline definitions (stage order, stage labels) export as a configuration worksheet. We configure Twenty's Opportunity pipeline stages in Settings > Data Model to match the source stage order before any Deal records are imported. Stage labels are reconciled via the mapping worksheet so that stage semantics are preserved even when exact wording differs between platforms.

Activity records logged against Contacts or Deals in Tango CRM migrate to Twenty Task or Note records. Call disposition, duration, and timestamps transfer to custom Task fields. Meeting start and end times and attendee information preserve as custom fields on the linked Task or Note. Without a confirmed bulk API on Tango CRM, activity migration is sequenced in batches to avoid overwhelming the export process.

Free-text notes attached to Contacts or Deals in Tango CRM import as Twenty Note records linked via content associations to the parent Person or Company. HTML-formatted notes are stripped to plain text unless the destination's note field supports rich text. Note timestamps are preserved for timeline ordering.

Tags applied to Contacts or Deals in Tango CRM transfer as label arrays in Twenty. Multi-select tag fields split into individual label values during the transformation step. If Twenty's label model differs from the source, we document the tag vocabulary during scoping and apply the reconciliation at import.

Custom properties on any Tango CRM object require explicit field-level mapping. Field types (dropdown, date, number, text) are matched to Twenty field type equivalents. Dropdown fields need value mapping because picklist option sets rarely align between platforms. Per Twenty's import documentation, all custom fields must exist in Settings > Data Model before CSV import runs — we create destination fields first, then import data.

If Tango CRM supports custom object records, these map to Twenty Custom Objects of equivalent name. We pre-create the destination custom object schema in Twenty's Data Model, including all custom fields and lookup relationships, before any data import. Twenty's custom object model uses standard field types and supports lookup relationships to both standard and other custom objects.

Tango CRM users and record owners map by email address to Twenty Member accounts. The customer's admin must invite all Members in Settings > Members and confirm acceptance before any record import that references owner fields runs, per Twenty's import prerequisites. We hold owner-unresolved records in a reconciliation queue until the Member mapping is confirmed.