Migrate from Insight Legal Case Management to Salesforce Sales Cloud

Matter-to-Case mapping loses the flat matter hierarchy when parties serve multiple matters

Insight Legal parties are role-bound to a matter, and one person or organization can be a party on N matters simultaneously with different roles per matter. Salesforce Contacts live under a single Account regardless of how many Cases they appear on. We handle this by creating a MatterParty__c junction object (or using Account Contact Relations with a Role__c field) to track the party role per Case. If your Insight Legal setup uses complex multi-party role hierarchies where the same person appears with conflicting roles across matters, those role conflicts require a reconciliation step before migration — your admin decides which role takes precedence per Case.

Insight Legal billing and trust accounting have no native Salesforce equivalent — ledger rows must map to custom objects

Insight Legal stores per-matter billing ledger entries (fees, disbursements, VAT, payment status, bill number) and trust accounting rows (receipts, payments, running balance) as structured sub-records. Salesforce has no native billing ledger or trust accounting object. FlitStack creates two custom objects — Matter_Financials__c and TrustLedger__c — on the Case, with fields that preserve amounts, types, payment status, and audit timestamps. However, Salesforce reporting on these custom objects requires your admin to build custom report types if you need ledger-level roll-up summaries in Salesforce reports.

Matter-specific workflows, conflict checks, and document automation do not migrate

Insight Legal matter workflows (e.g., conveyancing workflow stages, family law process steps, employment matter checklists) are internal state-machine configurations that are not data-exportable. Salesforce Flow handles equivalent automation but requires manual rebuild. We export a structured JSON description of your Insight Legal workflow definitions (stage names, step sequences, assignment rules) as a reference document your Salesforce admin uses to configure Flow. Conflict-check rules and document generation templates in Insight Legal cannot be migrated at all — those must be reconfigured post-migration.

Document file content must be re-uploaded — original upload timestamps are not transferable

Insight Legal document records contain file references (file names, URLs, internal file IDs) but the file content may be stored in Insight Legal's own document management system. Salesforce Files use ContentDocument and ContentVersion objects where CreatedDate reflects the upload time in Salesforce. We re-upload file content to Salesforce Files during migration. The original Insight Legal upload timestamp is preserved in a custom field (OriginalUploadDate__c) on ContentVersion, but Salesforce's native CreatedDate will reflect the migration run time. If your matter audit trail requires the exact original upload date to appear in Salesforce's native file audit fields, a Salesforce admin must update ContentVersion CreatedDate via API after migration.

Large matter history creates Salesforce API rate limit pressure during migration

Law firms with 5–10 years of matter history often carry hundreds of thousands of records across matters, time entries, documents, billing ledger rows, and trust accounting entries. Salesforce enforces a 100,000 daily API request limit for Enterprise Edition orgs, plus 1,000 additional requests per user license. FlitStack uses Salesforce Bulk API with batch sizes up to 10,000 records per batch to stay within limits, but firms with very large datasets may require multi-day migration runs or night-time batch windows. We assess your record volume during the discovery phase and plan batch sequencing accordingly.