Migrate from Legal Case Tracker to Twenty CRM

Legal Case Tracker's Case record maps to a Twenty custom object named 'Case'. The custom object must be pre-created in Settings → Data Model before import. All case-level fields (status, type, court, opposing party, statute of limitations) become custom fields on this object. The Case's original create date and last-modified date are preserved as custom datetime fields since Twenty's system timestamps reflect migration time.

Legal Case Tracker's Client record maps directly to Twenty's People object. The client's name, email, phone, address, and firm affiliation all have direct equivalents. If the Client has a firm name, that firm must be migrated as a Company record first so the People record can reference it via companyId.

Legal Case Tracker's client organization maps to Twenty's Company object. Firm name becomes Company.displayName. Industry, size, and address fields map to their Company equivalents. Multiple attorneys at the same firm collapse to one Company record linked by multiple People records.

Plaintiff and defendant parties in Legal Case Tracker may be existing clients (People) or external parties. We migrate them as related People records and create a custom 'Party Role' field (select: Plaintiff, Defendant, Third-Party) on the Case object to label each relationship. Multiple parties per case are handled as multiple relation links.

Legal Case Tracker status values (Open, Pending, Closed, Appeal) map to a custom select field on the Case object. We preserve the exact status label for each Case record. If your firm uses custom status values, we create a value-by-value mapping before migration and flag any unmapped statuses for manual review.

Court hearing dates, filing deadlines, and client meeting reminders in Legal Case Tracker map to Twenty Tasks. The Task.title carries the hearing description, dueDate carries the hearing date, and the Case object is linked via a custom relation field. Recurring reminders are not replicated — these must be rebuilt as Twenty workflow triggers.

Documents attached to Legal Case Tracker cases are downloaded and re-uploaded as file attachments on the corresponding Twenty Case record. File name and original upload date are preserved as metadata. Large document sets are batched to respect Twenty's file size limits and API throughput.

Billable time entries and expense records tied to a Case become structured custom fields on the Case object (Total_Hours__c, Total_Fees__c, Last_Billed_Date__c) plus a Note capturing the entry narrative. Since Twenty has no native billing module, fee data is preserved as reference fields rather than live invoice records.

Free-form attorney notes on a Case record migrate as Twenty Notes attached to the Case object. The note body, author, and create timestamp are preserved. Rich-text formatting is converted to Twenty's note format. Notes that reference other Cases are linked via a custom cross-reference field.

Any custom fields defined on Case or Client in Legal Case Tracker — such as court district, malpractice carrier, referral source, or insurance policy number — are migrated as custom fields on the corresponding Twenty object. Field type mapping: text→TEXT, number→NUMBER, date→DATE, picklist→SELECT. Fields must be pre-created in Settings → Data Model before the import batch runs.

Opposing counsel and external parties not already in Legal Case Tracker as contacts are migrated as People records with a custom Type__c value of 'Opposing Counsel' or 'External Party'. A custom relation field on the Case object links the attorney to the matter. This requires a custom field and a custom relation to be pre-created in Twenty's data model.

Legal Case Tracker workflows (deadline alerts, status-change triggers, email notifications) have no equivalent in Twenty CRM's workflow builder. We export the workflow definitions as a structured JSON document that your Twenty admin can use as a rebuild specification. Automations must be manually recreated in Twenty's workflow builder post-migration.