Migrate from Lawcus to Twenty CRM

Lawcus Contacts map directly to Twenty Persons. First name, last name, email, phone, mobile, job title, and address fields map field-for-field. Every Lawcus Contact must have an email for Twenty's Person lookup-by-email to resolve the CompanyId relationship correctly and ensure proper linking.

Lawcus Companies map to Twenty Companies. Name, domain/website, industry, number of employees, annual revenue, and address fields migrate as-is. Multi-company contacts in Lawcus (N:N model) collapse to one primary CompanyId per Person in Twenty — secondary companies preserved as a custom multi-select field or custom relation.

Lawcus Matters are the core legal record and have no direct Twenty CRM equivalent. We map Matters to Twenty Opportunities if your workflow resembles a sales pipeline (stage, probability, amount). If Matters represent legal cases with practice areas and billing, we map them to a Twenty Custom Object named 'Matters' so the legal structure is preserved and not forced into a sales-deal schema.

Lawcus matter statuses (Open, Closed Won, Closed Lost, Archived, Pending) map to Twenty Opportunity Stage values or a custom pick-list on the Custom Object. We apply a value-by-value mapping defined in the migration plan before the import runs — stage order is preserved as a sort-index field.

Lawcus Leads migrate as Twenty Persons tagged with a Lawcus_Lead_Status__c custom field. Lead name, email, phone, company, source, and notes map directly. The custom field preserves the original Lawcus lead status so you can filter or segment lead-origin records in Twenty without a separate object.

Lawcus activity logs (calls, emails, meetings, notes) map to Twenty Tasks or Notes depending on type. Call and email activities become Tasks with Type='Call' or Type='Email'. Meeting summaries and general notes become Twenty Notes. Original timestamps, owners, and parent-record links are preserved.

Lawcus file attachments associated with matters or contacts are re-uploaded as Twenty attachments on the corresponding Person, Company, or Opportunity record. Files must be downloaded from Lawcus first via the full backup ZIP, then uploaded to Twenty — file size limits apply per Twenty's storage configuration. Your admin should verify that the file sizes comply with Twenty's upload limits before re-uploading large batches.

Lawcus Tasks migrate as Twenty Tasks. Subject, description, due date, priority, status, and assignee all map field-for-field. Assignee resolution happens by email match to Twenty workspace members — unmatched assignees are flagged before migration for manual assignment.

Lawcus allows multiple primary contacts per Matter (N:N relationship). Twenty supports one primary Person per Opportunity. We handle this by: (1) setting the most recently modified contact as the primary Opportunity Person, (2) appending additional contact names to a custom Matter_Contacts__c multi-select field, and (3) surfacing the full list in the migration plan for your review.

Every Lawcus custom field on Matters must be pre-created in Twenty's Settings → Data Model before the CSV import runs. The Lawcus API exposes custom field definitions (name, type, options). We use this to auto-generate the Twenty field creation list, so your admin sets up the schema before data lands.

Lawcus owner IDs resolve by email match against Twenty workspace members. Your Twenty admin must invite all active Lawcus users and confirm they accept the invitation before migration — otherwise their records cannot link to an owner and land in an 'Unassigned' state.

Lawcus workflows and automations do not migrate. They must be rebuilt manually in Twenty's workflow builder (Pro/Organization tiers). We export your Lawcus workflow definitions — trigger conditions, stage-change rules, task-assignment logic — as a structured reference document for your Twenty admin to use during rebuild.

Lawcus invoices, trust transactions, and billing records have no equivalent in Twenty CRM's object model. If billing history is required, we can export Lawcus invoice data as a CSV reference file and store it as an attachment on the relevant Matter/Custom Object record in Twenty for audit purposes.