Migrate from My Legal Software to Salesforce Sales Cloud

Matter-type to RecordTypeId mapping creates Salesforce admin work before data lands

My Legal Software matter types (litigation, transactional, compliance) must map to Salesforce RecordTypeId values so stage pick-lists and page layouts vary per practice area. If your firm has four matter types, you need four Salesforce record types pre-created before migration — each with its own page layout, required fields, and stage values. FlitStack delivers a record-type setup plan with field mappings so your Salesforce admin creates the schema before validation runs. Skipping this step causes migration validation to fail on record-type assignment for every matter record.

Trust account and billing data requires custom objects with no native Salesforce equivalent

My Legal Software's trust accounting module stores trust balances, ledger entries, and client retainers that have no Salesforce-native object. Salesforce's Opportunity.Amount tracks opportunity value, not trust account balances. FlitStack migrates these records to custom trust transaction objects (Trust_Transaction__c, Trust_Balance__c) linked to the Account, but the financial logic, reconciliation rules, and IOLTA compliance features must be rebuilt using Salesforce Billing Cloud or a third-party legal accounting integration post-migration. This is not a limitation of FlitStack — it is a structural gap between legal practice management and CRM platforms.

Multi-contact clients collapse to Account-Contact hierarchy requiring post-migration cleanup

My Legal Software allows a single client record to hold multiple individual contacts (for corporate clients with multiple matters across different contacts). Salesforce enforces a single primary AccountId per Contact, with additional relationships managed through Account Contact Relations or custom junction objects. FlitStack migrates the primary contact as Contact with AccountId and surfaces remaining contacts for your admin to resolve via Account Contact Relations. Any client-to-client referral relationships in My Legal Software do not map to Salesforce's standard objects and require a custom relationship object if your firm tracks them.

Document migration count against Salesforce data storage limits

My Legal Software documents migrate as Salesforce Files (ContentVersion records) and count toward your Salesforce org's data storage allocation. At $0.125 per megabyte per month for overage storage, large document volumes (scanned briefs, deposition transcripts, exhibits) represent a meaningful ongoing cost in Salesforce. FlitStack reports your total document volume pre-migration so your firm can evaluate Salesforce storage pricing versus external document management (SharePoint, Google Drive) with Salesforce file linking. Firms with extensive historical archives often archive older closed-matter documents externally and link them via external URLs stored in Salesforce.

Workflow rules cannot migrate and require Flow Builder rebuild from exported definitions

My Legal Software automation rules governing matter stage transitions, conflict-check triggers, deadline reminders, and document auto-filing have no Salesforce equivalent that FlitStack can import. Salesforce Flow Builder provides equivalent functionality, but the automation logic must be recreated. FlitStack exports your My Legal Software workflow definitions as a structured JSON and human-readable reference document your Salesforce admin uses to configure equivalent Flows. Budget 2-4 weeks of admin time for complex matter lifecycle automations. This is disclosed upfront — no data is lost, but the automation rebuild is a post-migration configuration effort.