Migrate from LEAP to Salesforce Sales Cloud

LEAP clients map directly to Salesforce Contacts. Each LEAP client record becomes one Contact. For multi-matter clients, the primary matter is linked via AccountId; additional matters surface as separate Opportunity records with a custom matter-identifier field. The client's original LEAP ID is preserved in LEAP_ID__c for traceability.

LEAP matters map to Salesforce Opportunities with a custom Matter_Number__c field to preserve the LEAP matter identifier. The matter name becomes Opportunity Name; matter amount maps to Opportunity Amount; matter stage and type map to custom pick-list fields on Opportunity since legal-matter lifecycle has no Salesforce-native equivalent.

LEAP's many-to-many client-matter relationship must be flattened into Salesforce's hierarchy. The primary client per matter becomes the Opportunity AccountId. Additional clients on a matter are preserved using a custom junction object (Matter_Client__c) that links the Opportunity to secondary Contact records, maintaining the full relationship graph.

LEAP documents cannot be pulled via bulk API — they are accessible per-matter inside the LEAP client. We provide a manifest of all document names, matter associations, and original creation dates so the firm can re-upload files to Salesforce Files manually or via a scripted bulk loader.

LEAP cost recovery task codes and billing entries map to Salesforce Tasks linked to the related Opportunity. The task subject carries the cost recovery description; billing amount maps to a custom Decimal field (Cost_Recovery_Amount__c) on the Opportunity for detailed financial tracking alongside the standard Amount field.

LEAP trust accounting has no native Salesforce equivalent. We create a custom Trust_Transaction__c object with fields for Trust_Balance__c, Transaction_Type__c, and a lookup to the primary Contact. If the firm uses Salesforce Financial Services Cloud, these map to the standard trust model.

LEAP time entries map to Salesforce Tasks with Type = 'Time Entry'. The task subject carries the description, the hours map to a custom Number field (Time_Hours__c), and the owner maps to the Salesforce user matched by email. Original LEAP timestamps are preserved in a custom datetime field.

LEAP fee task codes are a billing construct specific to legal practice management. A custom pick-list field (Fee_Task_Code__c) on the Opportunity object carries the source value for reference and reporting continuity. Billing status is captured separately in a custom Billing_Status__c field to maintain complete financial visibility.

LEAP users are matched to Salesforce Users by email address using a pre-flight resolution process. Unmatched LEAP users are flagged before migration so the team can invite them to Salesforce or assign their records to a fallback owner, ensuring no data is orphaned during the migration.

LEAP custom fields on matters map 1:1 to custom fields on the Salesforce Opportunity object. Field type is translated: LEAP text becomes Salesforce Text, pick-list becomes pick-list, date becomes Date, and number becomes Number. We create the __c fields in Salesforce before the migration runs.

LEAP custom fields on clients map to custom fields on the Salesforce Contact object. Barred from Salesforce standard fields, these are created as __c fields in Object Manager prior to the migration run. Field types are preserved or type-mapped per Salesforce constraints.

LEAP matter-progression workflows, compliance checklists, and deadline alerts do not export from LEAP and cannot be imported into Salesforce. We provide a written export of LEAP workflow definitions as a reference document for rebuilding in Salesforce Flow — this is a manual step handled by the firm's Salesforce admin.

LEAP document templates are LEAP-native constructs that do not migrate to Salesforce. Matter-related templates can be stored as Salesforce Files by the team post-migration. We provide a comprehensive template inventory list documenting every active template so nothing is lost during the transition.

LEAP trust receipts (deposits and withdrawals from trust accounts) are recorded as separate trust-transaction entries. Each receipt maps to a Trust_Transaction__c record with Transaction_Type__c set to 'Receipt', linked to the primary Contact record for the matter to maintain audit trails.

LEAP billing entries that record invoiced amounts map to the Opportunity Amount field and a custom Billing_Status__c pick-list field. If LEAP tracks separate billed-versus-unbilled amounts, these become distinct custom fields on the Opportunity object for comprehensive financial visibility.

LEAP allows labeling client-matter roles such as primary client, referring client, or co-counsel with specific relationship designations. Salesforce has no native role-label on Account-Contact relationships. We map these to a custom pick-list (Client_Matter_Role__c) on the Contact or as fields on the custom Matter_Client__c junction object.

Every migrated LEAP record carries its original LEAP internal ID in a custom text field (LEAP_ID__c on Contact, LEAP_Matter_ID__c on Opportunity). This enables delta-run de-duplication, cross-system record traceability, and accurate reconciliation throughout the entire migration lifecycle.

Salesforce's CreatedDate is set at the time of migration, not at the original LEAP record creation. We preserve the original LEAP created date as a custom datetime field (LEAP_Created_Date__c) on Contact and Opportunity for historical reporting continuity and audit purposes.

The last-modified timestamp from LEAP is stored as LEAP_Last_Modified__c on both Contact and Opportunity records. This field is used during the delta-pickup window to identify and migrate records that changed in LEAP between the initial migration run and the final cutover.

LEAP integrations with legal research tools, accounting software, or court filing systems cannot be migrated. These must be identified before migration and rebuilt as Salesforce integrations post-go-live. We provide a detailed integration audit checklist to document every active connection for the migration team.