Migrate from Court Clerk to Twenty CRM

Every party in a Court Clerk case — plaintiff, defendant, or witness — becomes a People record in Twenty. Names, addresses, phone numbers, and email addresses map directly. Party roles are preserved as a custom field (PartyRole__c) so the legal role is visible on the Twenty contact record. The case-party association is preserved by linking the Person to the corresponding Opportunity record.

Attorneys appearing on a case become People records in Twenty with their bar number stored in a custom field (AttorneyBarNumber__c). The attorney's firm name maps to the standard Company field, and their role on a specific case is stored as a custom text field (AttorneyRoleOnCase__c) on the Person record linked to the Opportunity.

Each Court Clerk case becomes an Opportunity in Twenty. The case number and case title concatenate to form the Opportunity name so both identifiers are visible in the Twenty pipeline view. Case status maps to Opportunity stage values via a value-mapping table, and the case type is stored as a custom field (CaseType__c) on the Opportunity.

Courts, judges' chambers, and government entities referenced in Court Clerk cases that are not party-related do not fit neatly into Twenty's Company object. We create a 'Court Organization' Company record per court and link it as a custom field (IssuingCourt__c) on the related Opportunity, preserving the court reference without distorting the Company object with court-administration records.

Docket entries from Court Clerk — filing dates, motion submissions, hearing schedules — migrate as Notes linked to the parent Opportunity. The Note body contains the entry description and entry date, preserving the full chronological history on the Twenty opportunity record so case timelines are visible in the CRM context.

Court filings and supporting documents referenced in Court Clerk become Notes attached to the corresponding Opportunity. The Note body holds the document description and filing date. Document files are re-hosted if Court Clerk provides a downloadable URL; otherwise the Note captures the document reference metadata for manual retrieval.

Financial assessments associated with a case — fines, court fees, bond amounts — have no equivalent in Twenty's standard Opportunity model. We create a CaseFinancial custom object in Twenty with fields for amount, type, status, and due date, linked to the parent Opportunity via a lookup relationship. This preserves the financial record in the same workspace without cluttering the standard deal fields.

Scheduled hearings and case deadlines stored in Court Clerk become Tasks in Twenty linked to the corresponding Opportunity. The task title uses the hearing description, the due date is set to the scheduled date, and the status reflects whether the hearing has occurred. This gives the Twenty team a task-level view of case calendar events without requiring a separate court calendar tool.

Court Clerk distinguishes party roles (plaintiff, defendant, co-counsel, etc.) as attributes of the party-case relationship. Twenty does not have a native party-role concept on the Person-Case association. We store the role as a custom select field (PartyRoleOnCase__c) on the Person record, set per case context, so users can filter People by their role on specific matters.

Bond amount, surety name, and bond status associated with a case migrate as custom fields (BondAmount__c, SuretyName__c, BondStatus__c) on the Opportunity record. This court-specific financial data has no standard CRM equivalent, so it is preserved as a structured custom field group on the Twenty opportunity for reference during case management.

Every migrated record in Twenty carries a SourceSystemID__c custom field storing the original Court Clerk internal ID. This serves two purposes: it enables delta-run de-duplication (we skip records already migrated by ID), and it provides an audit trail linking each Twenty record back to its source case or party in Court Clerk.