Migrate from Criminal Case Management to Twenty CRM

Criminal case management platforms store the case subject — defendant, respondent, or party — as a client contact. FlitStack maps this to Twenty's People object. Role metadata (Defendant, Respondent) is preserved as a custom Role__c pick-list field on the People record, since Twenty has no native role concept for person records.

Attorneys and public defenders assigned to a case are contacts in the source system. These map directly to Twenty People records. The bar number, law firm affiliation, and court jurisdiction are stored as custom text and select fields on the People record. Where the source stores attorney as a lookup to a firm object, we resolve it to a Twenty Company record first and link the attorney People record via companyId.

Multiple role types from the source (prosecutor, investigator, judge, victim advocate, expert witness) are all people with distinct role labels. We merge all of these into the Twenty People object, using a custom Role__c pick-list field to distinguish each person's function per case. Each person may appear on multiple cases with different roles.

Law firms, public defender offices, prosecutor offices, investigative agencies, and courts are stored as Company records in Twenty. The source system's agency or court name maps to Company.name. Domain and court jurisdiction are mapped to custom fields (Agency_Domain__c, Court_Jurisdiction__c) on the Company record.

Cases are the core entity with no direct Twenty CRM equivalent. FlitStack maps each case to a Twenty Opportunity record: the case name becomes Opportunity.name, case number maps to a custom Case_Number__c field, and case status maps to a custom Case_Status__c pick-list with value-by-value alignment to the source status values. The People record representing the defendant links via the Opportunities contact roles where the source stores a defendant-to-case relationship.

Criminal case statuses (Open, Under Investigation, Indicted, Arraigned, Trial, Plea, Sentenced, Closed, Dismissed, Acquitted) have no native Twenty equivalent. We create a custom pick-list field Case_Status__c on the Opportunity object and map each source status value to its Twenty equivalent. Stage-entered timestamps from the source are preserved as a custom field (Status_Changed_At__c) on the Opportunity.

Criminal charges and counts attached to a case have no native Twenty object. We create a custom object named Charges with fields for charge_description (text), statute_code (text), charge_type (select: Felony, Misdemeanor, Infraction), severity (select: Class A through Class C, or state-specific tier), and disposition (select: Convicted, Acquitted, Dismissed, Amended). The Charges object links to the parent Opportunity (case) via a relation field.

Court hearing dates, filing deadlines, and statute-of-limitations deadlines in the source are event records. We map court dates to Twenty Events with the case Opportunity linked via opportunityId. Filing and motion deadlines map to Tasks with a custom Task_Type__c field (e.g., Filing Deadline, Motion Due, Discovery Deadline). Recurrence and court-calendar conflict detection do not carry over — these require manual setup in Twenty.

Evidence records and exhibit lists stored in the source have no native Twenty equivalent. We create a custom Evidence object with fields for evidence_description (text), evidence_type (select: Physical, Digital, Documentary, Testimonial), exhibit_number (text), chain_of_custody notes (text), and a relation to the parent Opportunity (case). Attachments and files are re-uploaded and linked to the Evidence record.

Documents, motions, briefs, and court filings attached to a case migrate as Twenty Notes on the Opportunity record. The source document type label (Motion, Brief, Discovery, Plea Agreement) is stored in a custom Type__c field on the Note. Original file names and timestamps are preserved in the Note's metadata and as custom fields.

Time entries and billing records linked to cases in the source have no native Twenty object. We create a custom TimeEntry object with fields for hours_worked (number), billing_rate (currency), total_amount (currency), date_performed (date), description (text), and a relation to the Opportunity (case) and the People record (attorney). Invoice and payment status may require a separate custom object if tracked.

Criminal case management platforms frequently add custom fields for jurisdiction codes, duty counsel flags, public-record indicators, immigration-hold flags, or restitution amounts. Each unique custom field in the source is analyzed by type (text, number, date, select) and replicated as a custom field on the Opportunity object in Twenty before the migration run.