Migrate from LegalServer to Salesforce Sales Cloud

LegalServer Case Data maps to Salesforce Case. Salesforce's Case object is the closest structural match for case-record data, but it requires custom fields for every LegalServer property. We create Case custom fields for financial data, court details, practice area, and all Case Data subtable fields. The Case object supports the standard Case Number and Subject fields, with Status and Priority pick-lists controlled by Salesforce admin.

LegalServer Contact records map 1:1 to Salesforce Contacts. Name, email, phone, and address fields resolve directly. Contact records linked to a Case in LegalServer are migrated as Salesforce Contacts with a lookup to the related Case record. Primary Contact assignment on a Case uses the Salesforce Case ContactRoles junction object.

LegalServer Organization records map to Salesforce Accounts. Organization name maps to Account Name; website maps to Account Website. LegalServer organizations with multiple contacts map to one Account with all linked Contact records connected via AccountId lookups. Billing address and shipping address are separate address fields in both systems.

LegalServer financial fields (poverty percentage, billing type, grant amount available, grant amount used, total billable hours, total expenses, flat hourly rate, staff assigned date) are merged into custom fields on the Salesforce Case object: Poverty_Percentage__c (percent), Billing_Type__c (picklist), Grant_Amount_Available__c (currency), Grant_Amount_Used__c (currency), Flat_Hourly_Rate__c (currency), Staff_Assigned_Date__c (date). Financial data requires decimal precision preservation.

Court name, case number, judge name, opposing counsel, and litigation status from LegalServer map to custom fields on the Salesforce Case object: Court_Name__c (text, 80 char), Judge_Name__c (text), Opposing_Counsel__c (text), Litigation_Status__c (picklist). Court_Name__c is capped at 80 characters per Salesforce field limits — values exceeding this are flagged for manual truncation during validation.

Practice area, case type, and case status from LegalServer use pick-list values. These map to Salesforce custom pick-list fields (Practice_Area__c, Case_Type__c, LegalServer_Case_Status__c) with value-by-value mapping. Any pick-list values in LegalServer that do not have a Salesforce equivalent are added as values during the Salesforce schema setup phase before migration runs.

LegalServer e-transfer records carry information about cases transferred between organizations. We map e-transfer data as custom fields on the Case (Transfer_Status__c, Referring_Organization__c, Transfer_Date__c) and resolve the referring organization to a Salesforce Account record. E-transfer history is preserved as a Salesforce Note attached to the Case record.

LegalServer staff contacts who are system users map to Salesforce Users. Matching occurs by email address. Unmatched staff members are flagged before migration — either invited to Salesforce first or assigned to a fallback Salesforce user. LegalServer user roles do not have a Salesforce equivalent and must be re-created as Salesforce Profiles and Permission Sets.

LegalServer's grant management module (funding codes, grant balances, deduction logic by billing type) has no Salesforce standard equivalent. We create a Salesforce custom object Grants__c with fields for grant name, balance, billing type, and linked Case records. Grant deduction tracking must be re-implemented as Salesforce Flow triggers or manual processes post-migration.

Timekeeping entries (date, hours, billable flag, notes) do not map to any Salesforce standard object. We create a custom Timekeeping__c object with a lookup to Case and a lookup to User. Billable hours from timekeeping are also aggregated into a custom Hours_Billable__c currency field on the Case for reporting continuity.