Migrate from RunSensible to Salesforce Sales Cloud

RunSensible clients contain both individual contact data and organizational information. We split into a Salesforce Contact record attached to an Account record — the primary contact lands on the Account with role assignments for matter associations. RunSensible client IDs are preserved as Source_System_ID__c for delta-run deduplication.

RunSensible matters map to Salesforce Opportunities when the firm uses a sales pipeline model for legal engagements. Matter name becomes Opportunity Name, matter status maps to Opportunity Stage via value mapping, and matter close date maps to CloseDate. Each matter requires a RecordType assignment based on practice area or matter type.

For firms tracking matters as service cases rather than pipeline opportunities, RunSensible matters map to Salesforce Cases. Case Origin, Case Type, and custom matter-type fields are created in Salesforce. Statute-of-limitations dates migrate as Case custom fields with deadline reminders configured in Salesforce.

RunSensible billable time entries are mapped to Salesforce Tasks with Type='Billable Time', preserving original duration, billable amount, and attorney owner. Administrative and non-billable time entries use Type='Admin Time'. Each Task is related to its parent Opportunity or Case via WhatId to maintain the matter association. Time entry records are processed in batch via Bulk API for performance.

RunSensible invoices contain line-item detail and payment status. The invoice header merges into the Opportunity record (Amount, Stage updated to reflect paid/unpaid). Line-item detail migrates to a custom Invoice_Line_Item__c object linked by Opportunity__c lookup. Outstanding balance and payment terms are preserved as custom fields.

RunSensible's IOLTA trust accounts have no native Salesforce equivalent. We create a Trust_Account__c custom object with three-way reconciliation fields (client funds, operating account, IOLTA account), journal entry records linked as Trust_Journal_Entry__c, and a reconciliation status field. Salesforce Billing or Revenue Cloud handles future transactions post-migration.

RunSensible tracks statute of limitations dates per matter. We create a Statute_of_Limitations__c custom date field on the Case object with a validation rule triggering a reminder workflow 30 days before the deadline. Firms using Opportunities for matters create the field there instead.

RunSensible court-rules data including filing deadlines, jurisdictional requirements, and court rules sets are migrated as jurisdiction-specific pick-list values on a Court_Rules_Jurisdiction__c custom field. Each RunSensible court-rules value is mapped to its Salesforce pick-list equivalent, with unmapped jurisdictions flagged in a separate review list for admin resolution before final migration.

RunSensible intake form submissions transfer to Salesforce Leads using standard fields (Name, Email, Phone, Company) alongside custom fields capturing referral source, intake form identifier, and lead status. RunSensible lead source values are mapped to Salesforce LeadSource via a value-mapping table built during the discovery phase to preserve original attribution data.

RunSensible documents and attachments on matters or clients re-upload as Salesforce Files attached to the parent Contact, Account, Opportunity, or Case. File size limits (Salesforce default 25MB per file) apply; documents exceeding this are split or linked via external URL in a custom field. E-signature metadata is preserved in a custom field.

RunSensible court dates and calendar events migrate as Salesforce Events with the original start and end times, subject (matter name + event type), and attorney owner preserved. Recurring events are mapped to Salesforce Series where the recurrence pattern is extractable; otherwise they become individual Events.

Firms using RunSensible custom practice-area objects map those to a custom Practice_Area__c object linked to Matter records via lookup, or as a pick-list value on Practice_Area__c custom field on the Opportunity/Case. We create whichever model the firm's Salesforce admin specifies before migration.

RunSensible notes on matters or clients are migrated as Salesforce Notes (not the legacy Note object), with rich-text formatting preserved where RunSensible's export format permits. Notes attach to their parent record via WhatId for matters and Cases, or WhoId for Contacts and Leads, maintaining the original context and association within the firm's new Salesforce environment.