Migrate from Lawmatics to Salesforce Sales Cloud

Lawmatics Contact maps 1:1 to Salesforce Contact. Every standard field (name, email, phone, address) migrates directly. Lawmatics contacts without a primary company land as Contacts without an AccountId — your admin assigns them to a default Account or merges duplicates post-migration.

Lawmatics Contacts in Prospect or Lead status with no active Matter split to Salesforce Lead. Active Matter contacts route to Salesforce Contact. The split is driven by Matter.status — firms can customize the routing rule to match their intake funnel stages.

Lawmatics Company maps to Salesforce Account using direct field-to-field mapping for name, phone, address, and website. Lawmatics parent-company hierarchies (parent_company_id) translate to Account.ParentId, preserving the organizational structure. Lawmatics N:N contact-to-company associations collapse to one primary AccountId per Contact plus Account Contact Relations for secondary affiliations, ensuring referential integrity across the CRM.

Lawmatics Matter is the primary migration object and maps to Salesforce Case. The Matter's contact_id becomes Case.ContactId, company_id becomes Case.AccountId. Matter type, status, and practice_area map to custom fields on Case (Practice_Area__c, Matter_Type__c, Matter_Status__c). Billing and financial fields on Matter migrate to custom fields or a linked custom object.

When Lawmatics Matter represents a revenue-generating engagement (contingency matters, flat-fee matters with a defined value), it can map to Salesforce Opportunity instead of Case. Amount__c, StageName, and CloseDate pull from Matter.fee_type, Matter.status, and Matter.close_date. Your firm chooses per practice area which object makes more reporting sense.

Every Lawmatics custom field on Matter requires a pre-created Salesforce custom field. FlitStack generates a setup manifest with field name (API name with __c suffix), data type (Text, Picklist, Date, Number, Checkbox), and pick-list values. The manifest is delivered before migration runs so your Salesforce admin can create fields in a sandbox first.

Lawmatics custom fields scoped to Contact objects migrate as Salesforce custom fields on Contact with __c suffix. Multi-select pick-lists in Lawmatics become multi-select pick-lists in Salesforce preserving all selected values. Boolean fields become Checkbox fields, and date fields map directly to Salesforce Date fields with original values preserved through the transformation pipeline.

Lawmatics Company custom fields migrate to Salesforce Account custom fields with __c suffix. Industry and employee-count pick-lists use Salesforce standard pick-list values where a direct match exists, reducing manual admin overhead. Non-matching values are preserved as-is and flagged for admin review to ensure no data loss occurs during the migration process.

Lawmatics practice_area is a key migration field with no Salesforce native equivalent. We create a custom pick-list (Practice_Area__c) on Case with values pulled directly from Lawmatics. Firms with more than 15 practice areas should consider a custom Practice_Area__c object instead to avoid pick-list value limits and enable cross-object reporting.

Lawmatics timeline activities (calls, emails, meetings, notes, form submissions) map to Salesforce Task (for calls and emails) and Event (for meetings). Original timestamps, activity type, and subject text are preserved. Notes with rich text formatting migrate as Salesforce Notes (ContentNote/ContentDocument model).

Lawmatics file attachments download from the API and re-upload to Salesforce Files. Each file becomes a ContentVersion linked to the target Case via ContentDocumentLink. Salesforce has a 25MB per-file limit and org-level storage limits — firms with thousands of large documents should audit available storage before the bulk load.

Lawmatics billing records (invoices, transactions, time entries) migrate as a custom financial object linked to Case, or as custom currency fields on Case depending on reporting complexity. If the firm uses Lawmatics LMPay, those records are migrated separately and linked by Matter ID.

Lawmatics tags are free-form labels on any record. Salesforce has a native Tag object shared across objects but with limited reporting value. FlitStack migrates tags as a custom multi-select pick-list or comma-separated text field on the relevant object, preserving the full tag set for filtering and reporting.

Lawmatics user assignments on Matters (assigned_attorney, intake_specialist, paralegal) resolve to Salesforce User records by email match. Unmatched users are flagged before migration so your admin can either invite them to Salesforce first or assign a fallback user as the owner.

Lawmatics Matter status values (New, Contacted, Qualified, Engaged, Closed-Won, Closed-Lost) map to Salesforce Case Status or a custom Matter_Status__c pick-list. The mapping is 1:1 by value; closed statuses re-map to Salesforce's canonical closed values with a custom override field tracking the original Lawmatics status.