Migrate from Rainbow CRM to Twenty CRM

Rainbow CRM Companies export as flat records and map directly to Twenty's Company standard object. We import Companies first in every migration batch so that Person imports can satisfy the company-name lookup relationship that Twenty's Person schema supports. The export's company domain field maps to Twenty's website field and is used as a dedupe key if multiple company records share the same domain.

Rainbow CRM Contacts map to Twenty's Person standard object. Standard fields (name, email, phone, address) migrate directly. Lifecycle stage is not a native field in Rainbow CRM and will not appear in exports; we create a custom picklist field on Person to capture any customer-defined stage data if present in the export schema. Email deduplication runs at import time against the full Person batch, and duplicate email conflicts are surfaced for customer review before records are committed.

Rainbow CRM Leads export as a separate object but may share email addresses with existing Contacts, creating overlap in Twenty's Person records. We deduplicate at import time by comparing email addresses across the Contact and Lead batches, flagging any duplicate email conflicts for customer review before writing records. If the customer requires a separate Lead pipeline for unqualified prospects, we create a custom Person view filtered by a lead-status field rather than a separate object.

Rainbow CRM Deals map to Twenty's Opportunity standard object. The export includes pipeline stage labels in Rainbow CRM's internal naming convention, which do not match Twenty's default Opportunity stages. We present a stage mapping table during scoping and apply the agreed mapping before the first import batch. Closed-won and closed-lost outcomes migrate as Opportunity stage values rather than separate deal-state fields.

Each Rainbow CRM pipeline becomes a Twenty Opportunity pipeline with its own stage values. We configure the pipeline in Twenty's settings before migration, adding stages that correspond to the exported dealstage labels. Stage probability percentages are mapped from the Rainbow CRM export where present, or set to Twenty defaults for unmapped stages.

Rainbow CRM Tasks export as flat records without assignee user IDs. We map task titles, due dates, and descriptions directly. Assignee resolution requires a cross-reference against the Twenty workspace Members list after scoping; the customer's admin must invite all team members before migration so that assignee email addresses can be matched to Twenty User records and the TaskAssignee field can be populated.

Rainbow CRM exports activity history (calls, emails, meetings, notes) in a denormalized flat format. We reconstruct activity threads by parsing the export, grouping records by contact and timestamp, and creating individual Task records for each engagement event. Call disposition, duration, and meeting location fields map to custom fields on the Task record. Activity ordering is preserved by setting the Task due date and completion date to the original Rainbow CRM timestamp.

Rainbow CRM exposes a subset of custom fields in exports. We inspect the export schema during discovery and flag any custom properties that do not appear in the raw file. For fields that are present, we create matching custom fields in Twenty via Settings Data Model before the import batch runs. Fields must exist in Twenty before CSV import because the import creates records, not fields. This pre-creation step is the most common point of failure in CSV-based migrations and we treat it as a prerequisite.

Rainbow CRM custom objects export in the same flat format as standard objects if they are present in the export. We create the corresponding custom object in Twenty via the /metadata API, including all custom fields, field types, and any lookup relationships to standard objects. Custom object schema must be deployed before the standard object import so that lookup fields on imported records can resolve to the correct target.

Rainbow CRM Owner records reference team members on Contacts, Companies, Deals, and Tasks. We extract owner email addresses from the export and match them against the Twenty workspace Members list. Any owner without a matching Twenty User is held in a reconciliation queue; the customer's admin provisions the missing User account before record import resumes. Owner resolution is a dependency gate: no Opportunity or Task import runs until all Owner references can be resolved.