Migrate from MerusCase to Salesforce Sales Cloud

MerusCase case files map to Salesforce native Case records. Salesforce Case.Number becomes the legacy case identifier; the original MerusCase case number is stored in Legacy_Case_Number__c. Practice area maps to Salesforce Case RecordTypeId per firm-defined record types (Criminal, Personal Injury, Employment, etc.).

MerusCase parties with role Client map to Salesforce Contact. Each Contact gets the Case record as its primary case association via a custom Case_Party__c junction object or the native Case Contact Role. The Contact.AccountId is resolved by matching the party's firm name to a Salesforce Account.

Parties with roles outside the firm (Opposing Counsel, Expert Witness, Insurer) lack a Salesforce Account relationship and map to Lead instead of Contact. The Lead.Company field stores the party's firm name; role is preserved in Party_Role__c for reference. Additionally, Lead.Status can be set to a custom value like 'External Party' to distinguish these records from marketing leads, and contact details are mapped to standard Lead fields.

MerusCase calendar events map to Salesforce Events with original start/end datetimes, assigned staff (OwnerId resolved by email match), and the linked case as WhatId. Event.Subject carries the MerusCase event title. Recurring event series are expanded into individual Event records. Time zones are preserved as entered; if the source stores UTC offset, we store it in a custom Timezone__c field and apply it when displaying the event in Salesforce.

MerusCase activities map to Salesforce Tasks. Original activity dates become Task.ActivityDate; staff assignment becomes OwnerId via email match. The UTBMS task_code and activity_code from MerusCase are stored in Task.Task_Code__c and Activity_Code__c custom fields. Task.Priority is set based on the MerusCase urgency flag, and Task.Status defaults to 'Completed' for historical entries; open activities retain their original status for reconciliation.

MerusCase billing ledger entries (charges, payments, damages, settlements) have no Salesforce standard equivalent and migrate as a Salesforce custom object. The Case_Ledger__c custom object links to the Case via Case__c lookup and stores all financial amounts, UTBMS codes, and status values as custom fields.

MerusCase documents are downloaded from the Document Archive and re-uploaded as "Salesforce Files" attached to the Case record via ContentDocumentLink. Large multi-document zips are split; individual files under 25 MB are uploaded via the Salesforce File object. Each file receives a ContentVersion entry with the file name, type, and creation timestamp, and is shared with the case's Salesforce group via a ContentDocumentLink with Visibility set to 'AllUsers' or 'InternalUsers'.

MerusCase Date-type custom fields become Salesforce Date custom fields on the Case object. Field labels are preserved; API names are sanitized (spaces removed, special characters stripped). Up to 50 custom fields per firm map across this pattern. Help text and description strings from MerusCase are copied to the Salesforce field-level help text, and any default date values are set in the field definition if present.

MerusCase Currency custom fields become Salesforce Currency custom fields on Case. The ISO currency code is stored alongside the value. Firms billing in multiple currencies should flag this during discovery for multi-currency org configuration. The decimal precision and scale of each Salesforce Currency field are set to match the MerusCase field definition, and if the org's default currency differs, a conversion formula or Salesforce Currency Management can be applied post‑migration.

MerusCase Numeric fields map to Salesforce Number; Text fields (≤250 chars) map to Text; Yes/No dropdowns map to Salesforce Checkbox or a custom pick-list depending on whether the field is multi-valued. Field-level validation rules can be applied post-migration. The Text field length is set to the lesser of 250 characters or the MerusCase defined length, and any picklist values are transferred as Salesforce picklist options for consistency.

MerusCase staff records resolve to Salesforce Users by email address. Unmatched staff are flagged before migration; your team either creates Salesforce users or assigns records to a fallback OwnerId. Staff role and practice-area assignments are stored in a custom User field.

MerusCase Workflows are not migratable to Salesforce. We export the workflow definitions (trigger types, conditions, resulting tasks) as a structured JSON reference document your Salesforce admin uses to rebuild equivalent Flows in Flow Builder or Process Builder post-migration. The export includes the original workflow name, activation criteria, step sequence, assigned staff roles, and any conditional branching logic, providing a clear blueprint for re‑creating each automation in Salesforce.