Migrate from MerusCase to Twenty CRM

MerusCase Party records map directly to Twenty People. Each Party has first name, last name, email, phone, and firm association. We split full-name Party records into FirstName and LastName fields on Twenty People. Parties without an email receive a placeholder identifier for import validation. Primary firm association maps to the companyId relation on the People record.

MerusCase stores the law firm itself as the primary organization — this maps to Twenty Companies. Domain, address fields, industry (Legal Services), and employee count migrate as Company fields. Multi-party associations to the same firm collapse to one Company record with multiple People linked via companyId.

MerusCase Case records have no standard equivalent in Twenty CRM. We create a custom Case object in Twenty (or map to Opportunities with a case-type field) to preserve case number, case status, jurisdiction, assigned staff, and case-type. Case records must exist before importing related Activities and Party-Case associations.

MerusCase CaseType (personal injury, workers' comp, criminal, family law) determines which specialty tabs and fields appear. We map CaseType as a select field on the custom Case object. Each case type value creates a corresponding option in Twenty's field configuration before import.

MerusCase CaseLedger stores billable time with task codes (UTBMS L-Codes) and expense codes (E-Codes). Twenty has no native ledger — we create a CaseLedger custom object with fields for hours, rate, amount, task_code, expense_code, and a relation to the Case object. Bill-to contact resolves to a People record.

MerusCase Activity records (with activity_type, description, date, contact_id, staff_id) map to Twenty Tasks. Activity type determines Task status and type field. Original activity date and assigned staff map to dueDate and assigneeId respectively. Filing-related activities preserve the activity_type value in a custom field.

MerusCase Statute records auto-generate calendar entries and filing reminders. Statute dates migrate as a date field on the custom Case object. Statute-triggered workflow reminders must be rebuilt in Twenty's workflow builder — we export the statute configuration as a reference document for your Twenty admin.

MerusCase Document Archive (per case) includes case documents and a CSV of case activities. We download document files and re-upload them as Note attachments linked to the corresponding Case record in Twenty. File size limits apply — documents over Twenty's attachment size cap are noted for manual retrieval.

MerusCase supports up to 50 firm-wide custom fields (Date, Currency, Text, Numeric, Yes/No). We map each to a Twenty custom field with matching type on the relevant object (Case, People, or Companies). Text fields capped at 250 characters map to Twenty Text fields without truncation.

MerusCase staff records (name, email, role) map to Twenty WorkspaceMembers. Owner resolution uses email match — each MerusCase staff_id on activities and cases resolves to the corresponding WorkspaceMember by email. Unmatched staff are flagged before migration for manual user provisioning.

MerusCase Workflows trigger on Activity Tags or descriptions (e.g., statute filing reminders). Twenty's workflow builder handles automation differently — event-based triggers, field-update actions, and task creation. We export MerusCase workflow definitions as a reference JSON so your Twenty admin can rebuild them. This is not a data migration; it is a configuration-rebuild task.

MerusCase's MerusPay (3% credit card transaction fee, 1.3% eCheck) is a payment-processing configuration with no Twenty CRM equivalent. Payment processing must be handled by an external payment tool integrated via Twenty's API or webhook system. We preserve the MerusPay fee structure as a reference note.