Migrate from LegalEdge to Salesforce Sales Cloud

LegalEdge Clients map directly to Salesforce Contacts. Each Client's first name, last name, email, phone, and address fields migrate to the corresponding Salesforce Contact fields. Salesforce requires an AccountId on every Contact — FlitStack creates a default Account named after the client's firm or 'Individual Client' for solo matters.

LegalEdge law firm or company names associated with a Client migrate as Salesforce Accounts. When a Client represents an individual (solo practitioner or solo client), their name also becomes an Account for Contact linkage. Parent-child firm hierarchies in LegalEdge map to Salesforce Parent Account field.

LegalEdge Matters have no Salesforce standard equivalent. FlitStack creates a Matter__c custom object in Salesforce with a Status__c pick-list (Open, Closed, Pending), Type__c pick-list (Litigation, Transactional, Advisory, etc.), and lead attorney lookup to the Salesforce User who owned the matter in LegalEdge.

The standard Salesforce Case object is reserved for client support inquiries by convention in legal migrations. LegalEdge Matters do not map to Case — they require the custom Matter__c object. Case is left available for client intake and inquiry tracking in Salesforce.

LegalEdge billable hours and expense entries linked to a Matter migrate as TimeEntry__c records. Fields include Hours__c (decimal), Billing_Rate__c, Date__c, Description__c, and a lookup to the Matter__c record and the Salesforce User who performed the work. Each TimeEntry__c is linked to its parent Matter__c using the Source_System_ID__c cross-reference stored during matter migration, ensuring accurate time tracking continuity.

LegalEdge documents attached to a Matter are re-uploaded as Salesforce Files (ContentDocument / ContentVersion). File names, content, and original upload dates are preserved in Salesforce. FlitStack links each Salesforce File to the corresponding Matter__c record via ContentDocumentLink so documents remain accessible in context. The original LegalEdge file metadata including upload author and version number is stored in custom fields on ContentVersion.

LegalEdge tasks (e.g., 'File complaint', 'Send engagement letter') migrate as Salesforce Tasks with the original Subject, Status, Priority, and due date. Owner resolved by email match to Salesforce users. Tasks linked to a specific Matter__c record are associated via the WhatId field.

LegalEdge calendar entries — hearings, depositions, filing deadlines — migrate as Salesforce Events with original StartDateTime and EndDateTime preserved. Court hearing events include a custom Type__c pick-list value ('Court Hearing') for filtering in Salesforce calendars. Attorney assignments are resolved via email matching to Salesforce Users, and the WhatId field links events to their associated Matter__c record.

LegalEdge allows unlimited custom fields per Matter (e.g., 'Court Docket Number', 'Opposing Counsel', 'Jury Trial Date'). Each custom field becomes a custom field on Matter__c in Salesforce. Field type is preserved — date fields become Date fields, pick-lists become pick-lists, text fields become Text fields.

LegalEdge Client custom properties (e.g., 'Bar Number', 'Matter of Interest', 'Conflict Check Status') migrate as custom fields on the Salesforce Contact record. Each custom field created in LegalEdge maps to a corresponding custom field on Contact, with field type preserved to maintain data integrity. The Salesforce admin confirms field creation before migration validates the mapping.

LegalEdge staff who created records (attorneys, paralegals, admins) are matched to Salesforce Users by email address. Unmatched LegalEdge users are flagged — the firm either creates a Salesforce User record first or assigns their records to a fallback attorney owner before migration.

LegalEdge's court docket integrations (e.g., Pennsylvania Unified Judicial System connection) are platform-specific settings with no Salesforce equivalent. The court docket number field migrates as Court_Docket_Number__c on Matter__c for reference. Docket automation must be rebuilt using Salesforce Flow triggers or an AppExchange court integration tool after migration completes.