Migrate from Case UI to Twenty CRM

Case UI Client records map directly to Twenty CRM People records. The name, email, phone, and address fields translate 1:1. The email field in Twenty serves as the unique identifier for import deduplication — Case UI client emails are used as the match key. Clients without an email are assigned a generated placeholder address and flagged for manual review after migration.

Case UI firms or organization affiliations stored on Client records map to Twenty CRM Companies. Company name, domain, industry, and address fields translate directly. For solo practitioners with no firm affiliation, FlitStack creates a 'Solo Practice' placeholder Company record and links the People record to it, ensuring every People record has a valid companyId.

Case UI Case records map to Twenty CRM Opportunities — the closest structural analogue in Twenty's standard object model. Case fields like case_number, status, practice_area, court_jurisdiction, and assigned_attorney migrate as custom fields on the Opportunity. The Opportunity Stage maps to Case UI status values (e.g., 'Active', 'Pending', 'Closed'), and Amount can carry the billing total or at-risk value if present in Case UI.

Case UI Matters are often sub-entities of Cases. FlitStack maps each unique Matter to an Opportunity record with a custom matter_type field distinguishing it from top-level Cases. If Case UI uses a separate Matters object with a one-to-many relationship to Cases, we create a custom object 'Matter' in Twenty and build the Case-to-Matter relationship via a custom relation field on the Opportunity, preserving the parent-child hierarchy.

Case UI activity logs (call notes, meeting summaries, internal notes) migrate to Twenty CRM Notes attached to the corresponding People or Opportunity record. Each Note preserves its original create date, author, and content body. Tasks from Case UI (e.g., filing deadlines, court dates) migrate as Twenty Tasks with due dates, assignees matching the assigned_attorney, and status preserved as the Task completion flag.

Case UI document attachments (pleadings, contracts, correspondence) are re-hosted in Twenty's storage and attached to the relevant Note or Opportunity record. FlitStack downloads each file from Case UI's document store, uploads it to Twenty's file storage, and creates a Note record linking to the file URL. File size limits follow Twenty's storage configuration for self-hosted or cloud deployments.

Case UI custom fields defined at the case level — such as court_jurisdiction, presiding_judge, opposing_counsel, billing_arrangement — are mapped to custom fields on Twenty's Opportunity object. Each custom field is pre-created in Twenty Settings → Data Model before the migration run. Field types are inferred from Case UI's field definitions: text fields become Twenty text fields, pick-lists become select fields, and date fields become date fields.

Case UI custom fields at the Client level — such as bar_number, practice_focus_areas, billing_rate — migrate to custom fields on Twenty's People object. Like case-level custom fields, each is pre-created in Twenty before the migration run. FlitStack generates a custom-field creation checklist from the Case UI field inventory so nothing is missed before data lands.

Case UI attorney and staff user accounts map to Twenty CRM Workspace Members. FlitStack resolves Case UI user records by email against Twenty workspace members, which must be invited and accept their invitation before the migration runs (per Twenty's documentation). Unmatched Case UI users are flagged as fallback-owner assignments on migrated records. Twenty does not support a roles-and-profiles model equivalent to Case UI's permission sets — those must be rebuilt manually in Twenty's permissions settings.

Case UI workflow rules and automation triggers (e.g., case-status-change notifications, deadline reminders, assignment rules) have no direct equivalent in Twenty CRM's workflow builder. FlitStack exports the full workflow definitions as a structured JSON document referencing Case UI's rule names, conditions, and actions. This document serves as the rebuild specification for your Twenty admin to reconstruct equivalent automations in Twenty's workflow builder after migration.