Migrate from The Plaintiff to Twenty CRM

Direct 1:1 map. The Plaintiff contacts migrate as Twenty People records. The email field serves as the unique identifier for People records, matching Twenty's CSV import requirement for unique values. Original contact IDs preserved as Source_Contact_ID__c for traceability and delta-run de-duplication.

Direct 1:1 map. The Plaintiff companies migrate as Twenty Companies records. Domain field maps to Twenty's domain field for company matching. Parent-company hierarchies map to the twenty.com Company relation field. Multi-contact companies in The Plaintiff each get one primary People record with a companyId lookup in Twenty.

The Plaintiff matters (cases) map to Twenty Opportunities — the closest pipeline-analogue object. A custom pick-list field Matter_Type__c is added to the Opportunity to preserve the original matter category (e.g., litigation, advisory, transactional). The Opportunity name derives from the matter name with a [Matter] prefix for disambiguation.

The Plaintiff matter status values (Open, Pending, In Progress, Closed, Archived) map to Twenty Opportunity stage values. We use a value-mapping table at migration time to route each The Plaintiff status to the appropriate Twenty stage. Stage-transition timestamps from The Plaintiff are preserved as custom datetime fields on the Opportunity.

The Plaintiff stores attorney and staff assignments per matter. These map to Twenty's user-assignment fields on the Opportunity. Owner resolution runs by email match against Twenty workspace members. Unmatched attorneys are flagged before migration and assigned to a fallback user.

The Plaintiff activity log entries (calls, emails, meetings) migrate as Twenty Tasks (for calls and emails) or Events (for calendar meetings). Each activity retains its original timestamp, owner, and the linked People or Company record. Activity type is stored as a custom field on the Task.

The Plaintiff notes map to Twenty Notes. Notes are linked to the associated People, Company, or Opportunity record. Rich-text formatting in The Plaintiff notes is preserved as-is in Twenty's note body.

The Plaintiff tasks map directly to Twenty Tasks. Due dates, assignees, and completion status all translate directly. Tasks linked to specific matters connect to the corresponding Opportunity record in Twenty.

The Plaintiff custom contact properties that have no direct Twenty equivalent migrate as custom fields on the People object. Field type is inferred from the The Plaintiff schema: text fields become text, pick-lists become select, and number fields become number.

The Plaintiff custom matter fields migrate as custom fields on the Twenty Opportunity object. These include any client-specific matter tracking fields that don't map to standard Opportunity fields. Custom field metadata (field type, pick-list values) is preserved in Twenty.

The Plaintiff file attachments on matters and contacts do not have a direct Twenty equivalent for re-upload. We preserve the file metadata (name, size, original URL) as a custom text field on the related record. Actual file re-hosting requires separate handling — we document the file list for your admin to re-upload post-migration.

The Plaintiff's trust account ledgers and billing records are legal-specific financial constructs with no equivalent in Twenty CRM's data model. These records must be exported separately as CSV and handled by your accounting team or a dedicated legal billing tool. We provide the export and schema documentation.