Migrate from Lawmatics to Twenty CRM

Lawmatics contacts map directly to Twenty People. Every contact field (name, email, phone, address) migrates as the equivalent Twenty People field. Lawmatics contacts without a primary company receive no default company assignment in Twenty—your team sets that manually post-migration or during import via a fallback rule.

Lawmatics companies map 1:1 to Twenty Companies. Company name, domain/website, industry, employee count, and annual revenue transfer directly. Lawmatics parent-child company hierarchies map to Twenty's recursive Company relation if your Twenty workspace has that field configured, otherwise parent relationships are stored as a custom field for manual linking.

Lawmatics matters (the core intake/lead/client object) map to Twenty Opportunities. This is the primary structural transformation: matter status (Prospect, Active Client, Closed) maps to Opportunity stage values you define in Twenty's pipeline settings. Matter create dates migrate as Opportunity creation timestamps. Lawmatics matter owners resolve to Twenty workspace members by email match before records land.

Practice area (Family Law, Personal Injury, etc.), case type, statute of limitations date, conflict-check status, retainer amount, and referral source all need custom fields created in Twenty before the migration runs. We deliver a custom-field creation plan based on your Lawmatics custom field inventory so your Twenty workspace is schema-ready before data imports.

Lawmatics lets a single contact work across multiple firms. Twenty People records have one primary CompanyId. We migrate the primary company (most-recently-modified or by your specified rule) as the primary relation and create a custom multi-relation field in Twenty for additional company associations—your admin decides how to expose those in the UI post-migration.

Lawmatics timeline activities (calls, emails, meetings, notes) migrate to Twenty Notes or Tasks depending on type. Emails and call logs become Tasks with Type='Email' or Type='Call'. Meetings with start/end times become Events. Notes become Twenty Notes attached to the parent People or Opportunity record. Original timestamps and assigned users are preserved.

Lawmatics tags on contacts, companies, and matters migrate as comma-separated values in a Twenty custom multi-select field or as tags on Notes. If you use tags for segmentation, we recommend creating a dedicated custom field in Twenty for the primary tag taxonomy and attaching remaining tags as a Note for reference.

Lawmatics custom form submissions are stored as form-field responses linked to matters. Twenty has no native form-submission object. We surface form response data as Notes on the related Opportunity (migrated matter) or as individual custom fields if the form is a fixed structure. Dynamic intake forms with conditional logic cannot be reconstructed in Twenty without a separate form tool integration.

Lawmatics file attachments on matters and contacts re-upload to Twenty as Notes with file links, or we store the original Lawmatics file URL as a text field for reference. File size limits and storage costs in Twenty cloud apply—larger document archives may warrant a separate document management strategy post-migration.

Lawmatics automations (triggers, conditions, actions) do not migrate. We export your automation definitions as JSON reference files for your Twenty admin. Time-based triggers (e.g., reminder 1hr before appointment), action-based triggers (status change), and email sequences must be rebuilt in Twenty's workflow builder. Budget 2–4 weeks for a mid-size automation set to be fully reconstructed.

Lawmatics email templates and drip sequences used in automations do not transfer to Twenty. We export template content (subject, body HTML, merge fields) as text files. Your Twenty admin recreates templates in the connected email tool or uses Twenty's CRM email features. Merge field mappings are documented so the correct Twenty fields are referenced in rebuilt templates.

Lawmatics users map to Twenty workspace members. Resolution happens by email address match before migration—unmatched users are flagged and assigned to a fallback Twenty user you designate. Lawmatics role-based permissions (Attorney, Paralegal, Intake Coordinator) do not have a direct Twenty equivalent; Twenty's role system uses more granular object-level permissions that must be reconfigured post-migration.