Migrate from The Case File to Salesforce Sales Cloud

The Case File stores clients as matter-centric contact records. We split these into Salesforce Contacts linked to an Account (representing the client organization). Individual clients without a firm affiliation become Contacts linked to a default 'Individual Client' Account record. All Contact fields—name, email, phone, mailing address—are mapped to their Salesforce counterparts, and the original matter-client relationship is preserved via the Case_Contact_Role__c junction object.

The Case File matters map directly to Salesforce Cases. Matter number becomes Case CaseNumber; matter title becomes Subject. We preserve the original matter open date in a custom field since Salesforce's CreatedDate reflects migration time. Matter status maps to Case Status via value mapping per status set.

The Case File practice area labels (Litigation, Transactional, IP, etc.) map to Salesforce Case Type values. If your firm uses sub-practice areas, we create a custom Practice_Area__c pick-list field on Case and map values one-by-one. This preserves granular practice-area distinctions for reporting and routing while maintaining compatibility with Salesforce Flow automations that trigger based on Case Type.

Opposing parties and their counsel are stored as Account records with a contact role indicator. We create Account records for law firms and opposing parties, then create Contact records for individual attorneys with a custom Role__c field set to 'Opposing Counsel' or 'Adverse Party'.

The Case File documents re-upload to Salesforce Files. Each document becomes a ContentVersion record linked to the parent Case via ContentDocumentLink. Files exceeding 25MB are flagged for chunked upload or external storage (SharePoint) integration. Version history is preserved as ContentVersion metadata.

Billable time entries map to Salesforce Tasks with custom fields: Hours__c, Rate__c, Billable__c, and Invoice_Reference__c. We preserve the original entry date, attorney name, matter association, and description. Time entries are linked to the Case via WhatId. Billed entries are flagged as non-editable in Salesforce.

The Case File court dates, deadlines, and appointments migrate as Salesforce Events. Original start/end times and reminders are preserved. Events are linked to the associated Case via WhatId. All-day events map with IsAllDayEvent=true. Recurring events are expanded into individual Event records, and event descriptions are preserved in the Subject or Description fields for calendaring accuracy.

Matter notes migrate as Salesforce Notes (the enhanced Notes object, not legacy Note). Body text, author, and creation date are preserved. Notes are linked to the parent Case via ParentId. Rich-text formatting is maintained where The Case File supports it.

The Case File invoices do not map to any native Salesforce object. We create a custom Invoice__c object with fields for invoice number, amount, status, date, and line items linked to time entries. The related Opportunity represents the matter's financial pipeline for reporting. Invoice PDFs are stored as Salesforce Files linked to Invoice__c records.

Any custom fields defined in The Case File for specific matter types (e.g., Case Code, Court Jurisdiction, Jury Trial Flag) are created as custom fields on the Case object in Salesforce with the __c suffix. Field types are matched: pick-list to pick-list, date to date, text to text. Multi-select fields require custom handling via a text field with delimiter or a custom junction object.