Migrate from The Legal Assistant to Twenty CRM

The Legal Assistant stores client contact records with name, phone, email, and address. These map directly to Twenty's People object. Clients with multiple matter files all attach to the same People record — The Legal Assistant's practice-area modules all share the same client database. Email and phone fields map to the standard Twenty People fields; address fields map as a composite or to separate address line fields.

The Legal Assistant's matter records are the core of the platform — they store practice-area type, assigned attorney, case status, relevant dates, and all linked documents and time entries. Twenty has no native Matter object, so matters migrate as Opportunities with a custom matter type field, practice-area classification, and the original matter number stored for reference. The Opportunity Stage maps from The Legal Assistant's case status (Active, Pending, Closed Won, Closed Lost).

The Legal Assistant has a firm/organization record that holds firm-level settings, billing configuration, and user list. This maps to Twenty's Company object as the primary account record for the firm's own organization. If The Legal Assistant tracks referring firms or opposing counsel as separate organizations, those also map to Company records in Twenty.

The Legal Assistant stores documents per matter with template support for letters, contracts, and court filings. Documents migrate as Files attached to the corresponding Opportunity (matter) record in Twenty. Template bodies are preserved as Notes attached to the related matter so the firm can rebuild them in Twenty's document workflow. Rich-text formatting in The Legal Assistant documents converts to plain text or markdown for Notes compatibility.

The Legal Assistant tracks calendar events, court dates, and deadline reminders per matter. These migrate as Tasks in Twenty, linked to the corresponding Opportunity (matter) record. The original event date and time map to the Task due date; attorney assignments map to the Task assignee. Statute-of-limitations alerts and deadline reminders that fire automatically in The Legal Assistant must be rebuilt as Twenty workflow automations.

The Legal Assistant tracks time entries per matter for billing purposes. Twenty has no native time-tracking or billing object. We create a custom TimeEntry object in Twenty (available on Pro and Organization plans) with fields for matter reference, attorney, hours, date, and billing rate. If the firm uses Pro plan with a 10 custom-object limit, we discuss prioritizing this object or combining it with the matter record.

The Legal Assistant tracks trust account balances and operating accounts per client for IOLTA compliance. Twenty has no native accounting object. We create a custom TrustAccount object with client reference, account type, balance, and transaction history fields. The firm should verify that Twenty's custom object model meets their bar association's record-keeping requirements for trust accounting.

The Legal Assistant stores practice-area-specific custom fields (e.g., Personal Injury module: insurance carrier, claim number, injury type; Family Law module: custody arrangement, divorce status). Each practice-area module has its own custom property set. We create corresponding custom fields in Twenty on the relevant object (People for client attributes, Opportunity for matter attributes). Module names are preserved as field group labels.

The Legal Assistant user list includes attorneys, paralegals, and administrative staff with role-based access. These map to Twenty Workspace Members. User email addresses are the key for matching; any The Legal Assistant user without an email address is flagged before migration so the firm can assign one or map the records to a fallback user.

The Legal Assistant generates invoices from time entries and expense records. Twenty has no native invoicing object. Historical invoices are preserved as Notes on the related matter with the invoice amount, date, and status. The firm should verify that their state bar's record-keeping rules allow invoice history to be stored in a CRM custom object rather than a dedicated accounting system.