Migrate from Case Status to Twenty CRM

Case Status contact records migrate to Twenty People. Core fields (name, email, phone, address) map directly. Case-status values (active, pending review, closed) migrate as a custom Select field (Case_Status__c) with original pick-list values preserved so reporting continuity is maintained in Twenty views.

Case Status stores client-intelligence scores, NPS ratings, and portal URLs as custom contact properties. These have no native equivalent in Twenty's People object and are migrated as custom fields (Client_Intelligence_Score__c, NPS_Score__c, Client_Portal_URL__c, Last_Case_Update__c). Each field's type is matched to the source data type — number fields become Number fields, text becomes Text, URLs become Links.

Case Status company records migrate to Twenty Companies with direct field mapping for name, domain, industry, employee count, and annual revenue. Industry pick-list values are mapped value-by-value against Twenty's default industry options; unmapped values are preserved as-is in a custom text field to avoid data loss.

Case Status custom company fields (billing tier, firm type, referral source) migrate as custom fields on Twenty's Company object. These are created in Twenty's Data Model settings before migration begins. The field type is inferred from the source data — pick-lists become Select fields, dates become Date fields, monetary values become Currency.

Case Status deal records (representing active case files) migrate to Twenty Opportunities. Case-specific fields like practice area, opposing counsel, and court venue are created as custom fields on the Opportunity object. Case file amounts map to Opportunity Amount; case-status values use the same custom Select field pattern as contacts — Case_Status__c — so all records share a consistent status dimension.

Case Status pipeline stage values (e.g., Active, Discovery, Filed, Closed) are mapped value-by-value to Twenty Opportunity Stage pick-list values. If Twenty's default stages don't match, custom stage values are created in Settings → Data Model before migration. Stage-enter timestamps are preserved as custom datetime fields on each Opportunity.

Case Status tasks migrate to Twenty Tasks with direct mapping for title, due date, assignee, and completion status. Priority values map to a custom Priority field on Twenty Tasks since Twenty's base task object does not include a priority pick-list. Task owner resolution uses email matching against Twenty workspace members.

Case Status tasks carry case-linked fields (case ID, task category, billable hours) that require custom fields on Twenty's Task object. These are created before migration begins and linked to the parent Opportunity via Twenty's relation field system. Billable hours become a Number field; task_category becomes a Select field with the original pick-list values.

Case Status notes migrate to Twenty Notes. The note body maps to Note.Body and the title maps to Note.Title. Notes linked to a specific person or company carry the same relation in Twenty. Case-status notes are preserved with their full body text; no truncation occurs for records within the 20,000-record export limit.

Case Status automations and workflows have no equivalent in Twenty CRM. The migration cannot carry them over — they must be rebuilt from scratch in Twenty's workflow builder. FlitStack exports the Case Status automation definitions (trigger conditions, actions, and sequence logic) as a documented rebuild reference so your team or a Twenty partner can reconstruct them in Twenty Workflows.