Migrate from Thomson Reuters Case Center to Twenty CRM

Case Center's Case record (legal matter) translates to Twenty's Opportunity object. The Case ID becomes the Opportunity name or a custom field (Case_ID__c). Filing date maps to CloseDate or a custom field (Filing_Date__c). The legal matter's status (Active, Closed, Pending) maps to Opportunity stage values, requiring a custom legal-matter pipeline in Twenty.

Case Center allows multiple Participant roles per Case (Counsel, Respondent, Panel Member, Court Staff, Self-Represented Litigant). Each distinct role translates to a separate People record with a custom field (Participant_Role__c) capturing the role type. If the same individual appears in multiple roles, FlitStack AI creates one People record per role to preserve context.

Case Center's organization-level entities (law firm names, court names, government agencies) map to Twenty Companies. The organization's address, jurisdiction, and type translate to standard Company fields. FlitStack preserves the organization name exactly and maps jurisdiction to Industry or a custom select field.

Case Center evidence files (PDF, video, audio) cannot be transferred to Twenty, which has no document management module. Instead, FlitStack AI creates a Note record per evidence file containing the file name, submission date, file size, page count, and document type — linked to the corresponding Opportunity. This preserves the filing catalog without transferring the files themselves.

Case Center hearing records (hearing date, hearing type, outcome) map to a custom Event object or to Note records with datetime fields (Hearing_Date__c, Hearing_Type__c, Hearing_Outcome__c) on the Opportunity. If the team needs a calendar-style view, FlitStack AI structures these as Twenty Tasks with due dates and linked to the Opportunity.

Free-text case notes and panel annotations in Case Center migrate as Twenty Notes linked to the parent Opportunity. Rich-text formatting is preserved where Case Center's export format supports it. Timestamp and author information is stored in custom fields on the Note record (Original_Created_Date__c, Author_Name__c).

Case Center supports custom fields per Case (Practice_Area__c, Court_Name__c, Judge_Assigned__c, etc.). FlitStack AI creates matching custom fields on Twenty's Opportunity object via Settings → Data Model before import. Custom field type mapping follows the destination field type closest to the source (select → select, text → text, date → date).

Participant-level custom fields in Case Center include attorney bar number tracking, participant appearance status flags indicating whether an individual filed appearances, waived participation, or withdrew from proceedings, and witness classification types distinguishing between expert witnesses, fact witnesses, and character witnesses. These Case Center attributes require FlitStack AI to pre-create matching custom fields on Twenty's People object via Settings → Data Model before migration. This schema preparation ensures the CSV import process can populate each custom field directly without post-migration field creation errors.

Case Center users (attorneys, court staff, panel members) map to Twenty Workspace Members by email match. FlitStack AI flags unmatched owners before migration — your team either provisions them in Twenty first or assigns records to a fallback Workspace Member. This is critical because Case Center role-based access does not translate to Twenty's permissions model.

Case Center case templates (reusable structures for specific court types or matter categories) have no direct equivalent in Twenty. FlitStack AI preserves template field names and structures as a custom mapping document for manual reconstruction in Twenty's workspace settings after migration.

Case Center accepts eDiscovery production folder imports for complex litigation. Twenty has no eDiscovery or document processing module. FlitStack AI captures the production folder name, import date, and document count as Note records and flags that the source files must be managed in a dedicated document platform post-migration.

Case Center enforces role-based access per case (Judge, Counsel, Panel Member, Self-Represented Litigant). Twenty's permission model operates at the workspace level with view and edit permissions per object. FlitStack AI documents the Case Center permission structure and provides a mapping plan to Twenty Permission Groups for manual configuration after migration.