Migrate from Real Intelligence to Twenty CRM

Real Intelligence Contact maps directly to Twenty People. Email, phone, name, and job title fields transfer as-is. The People record must be imported after Companies because People carries a companyId relation — Twenty requires the parent Company to exist first.

Real Intelligence Account or Company maps to Twenty Company. The Company object is the 'one' side of the People-Company relationship and must be imported first per Twenty's import-order constraint. Industry, employee count, and website fields map to Twenty's standard Company fields.

Real Intelligence Deal maps to Twenty Opportunity. Stage, amount, close date, and name transfer directly. Opportunities in Twenty carry a companyId and can optionally link to a primary People record. Deal owner maps via email resolution against Twenty workspace members.

Real Intelligence Activity records with action type 'Task' or 'To-Do' migrate as Twenty Tasks. The Task object links to People, Company, or Opportunity by record ID. Due date, assignee, and completion status transfer as standard fields. Task priority and any custom flags on the source Task also map to the corresponding Twenty Task fields, preserving the full task context from Real Intelligence.

Real Intelligence Activity records of type 'Note' migrate as Twenty Notes. Notes attach to People, Company, or Opportunity. The original body text and creation timestamp transfer; note visibility follows Twenty's sharing model. Any Rich Text formatting in the original note body is preserved as HTML in Twenty's Note body field, maintaining the full note content and structure.

Real Intelligence email activity records (Subject, Body, Timestamp, From/To addresses) migrate as Twenty Notes with a type flag 'Email'. The email thread subject becomes the Note title; the body preserves the message content. This is a transformed mapping because Twenty has no native email object.

Real Intelligence call logs (Call duration, outcome, notes) migrate as Twenty Notes with type flag 'Call'. The note title records the call subject or contact name with call duration appended. Call outcome maps to a custom select field on the Note if needed.

Any Real Intelligence custom property on Contact, Account, or Deal maps to a corresponding Twenty custom field. Custom fields must be created in Settings → Data Model before the CSV import runs — FlitStack delivers a field-creation checklist as part of the migration plan so no records land without their fields in place.

If Real Intelligence stores a domain-specific custom object (e.g., Projects, Subscriptions), FlitStack maps it 1:1 to a Twenty custom object. The custom object is created in Twenty's Settings → Data Model first, then data loads via CSV referencing the relation IDs of existing standard objects.

Real Intelligence owner references resolve by email match against Twenty workspace Members. Unmatched owners are flagged before migration — your team must invite them to Twenty or assign their records to a fallback member. No record lands without a resolved owner reference.

Real Intelligence file attachments linked to contacts, companies, or deals are re-uploaded as Twenty Note attachments. File size limits apply (Twenty default 25MB per file for cloud; self-hosted limits depend on your PostgreSQL configuration). Inline images in notes are preserved as attachments.

If Real Intelligence tracks a lifecycle or lead-stage property, it migrates as a Twenty custom select field (e.g., Lifecycle_Stage__c) on the People object. The pick-list values map value-by-value from the source. Since Twenty does not have a native lead/contact split, all records land as People.

Real Intelligence workflow rules and automation triggers do not map to any Twenty object. FlitStack documents the workflow definitions (object, trigger type, conditions, actions) in a rebuild reference file. Twenty's workflow builder (Settings → Workflows) supports event-based automations and must be reconfigured manually post-migration.