Migrate from Legal Files to Salesforce Sales Cloud

Legal Files matters have no single Salesforce equivalent. We route each matter to Account, Case, or Opportunity based on your specified type field. Corporate legal matters with external parties route to Account; internal litigation tracks route to Case; billing-bearing matters route to Opportunity. A matter-type mapping table is agreed upon before migration runs.

Each Legal Files party attached to a matter maps to a Salesforce Contact record. The Contact's AccountId is set to the target Account (the migrated matter's related Account). Party role labels (Plaintiff, Defendant, Client) are preserved in a custom Role__c picklist field on Contact for reporting continuity.

Legal Files party role values (Client, Opposing Counsel, Expert Witness, etc.) have no native Salesforce equivalent. We create a Role__c custom picklist on the Contact object and map each source role value one-by-one. If your firm uses 15 role labels, all 15 appear in the picklist on every Contact record.

Legal Files documents are downloaded from the export bundle and re-uploaded to Salesforce as ContentVersion records, then linked to the target Account, Contact, or Case via ContentDocumentLink. Inline images and PDF attachments are re-hosted. Salesforce's 25MB per-file limit applies; files exceeding this are flagged before migration so your admin can decide to split or archive.

Legal Files tasks map directly to Salesforce Task records. The WhatId field links the Task to the target Account, Contact, or Case depending on the matter routing. Original due dates, priorities, and assigned-to values (resolved by email to Salesforce User) are preserved. Completed tasks carry their original completion date.

Legal Files calendar entries mapping to court deadlines and attorney appointments migrate as Salesforce Event records. Start and end times are preserved. The WhatId links the Event to the target matter Account or Case. Reminder settings are carried over as Salesforce Event reminder flags.

Salesforce Sales Cloud has no native billing object. We create a Time_Entry__c custom object with fields for hours, date, rate, and description, linked to the matter's Account or Case via a lookup. If you use Salesforce Billing or CPQ, those objects can be substituted — we document the mapping plan for your implementation team.

Legal Files custom matter properties map to Salesforce custom fields on the target object. Text properties become Text fields, dates become Date fields, currencies become Currency fields. Each custom property requires pre-creation in Salesforce Setup with the __c suffix. We deliver a field-creation checklist as part of the migration plan so your admin creates them before the data load runs.

Legal Files party-level custom fields (e.g., bar number for opposing counsel, conflict-check result) migrate to custom fields on the Salesforce Contact object. Same pre-creation requirement applies — we list every field with its type and pick-list values in the field-creation checklist.

Legal Files matter status values (Open, Pending, Closed, etc.) map to a custom Status__c picklist on the target object. For matters routing to Salesforce Cases, the standard Case Status picklist can be used with a value-mapping table. We align the values and probabilities so reporting shows the correct funnel at go-live.

The responsible attorney stored in Legal Files maps to OwnerId on the Salesforce record. Resolution happens by email match — each Legal Files owner email is matched to a Salesforce User record. Unmatched owners are flagged before migration so your admin can either invite them to Salesforce or assign their records to a fallback user.

Legal Files' internal matter ID is stored as a text field (Source_System_ID__c) on every migrated record. This serves as the External ID for delta-run de-duplication and for traceability if you ever need to reconcile source records against Salesforce after go-live.