Migrate from LegalE to Salesforce Sales Cloud

Direct map: Legale contacts migrate as Salesforce Contacts. Salesforce requires an AccountId lookup on Contact — Legale contacts without a primary organization attach to a default 'Unaffiliated' Account record created for this purpose. Contact addresses, phone numbers, email, and title fields map directly to Salesforce standard fields. Bar license numbers and original create dates migrate as custom fields on Contact.

Direct map: Legale organizations become Salesforce Accounts. Organization name maps to Account.Name, website to Account.Website, and industry to Account.Industry with value mapping for pick-list alignment. Parent-child organization hierarchies in Legale map to Account.ParentId — the parent organization must migrate before its children to resolve the reference correctly.

Legale's matter-centric model doesn't map directly to Salesforce Opportunity, which is deal-centric rather than case-centric. FlitStack creates a Matter__c custom object for legal practices that need case-number tracking, court information, jurisdiction fields, and matter-stage pick-lists beyond standard opportunity stages. The Matter__c object requires pre-creation in Salesforce Setup with appropriate page layouts and record types.

Legale matter stages (e.g., Intake, Active, Pending Review, Closed) map value-by-value to Salesforce Stage values. Each stage probability percentage is re-applied from Salesforce's forecast category settings during migration. The mapping table is validated against both systems before the full run.

Billable hours have no Salesforce standard equivalent, so FlitStack creates a Time_Entry__c custom object with Matter__c lookup, Attorney__c lookup to User, Hours__c, Rate__c, Billing_Status__c, Date__c, and Description__c fields. The custom object requires a custom tab and list view configuration post-migration for attorney time entry.

Legale documents attach to matters and migrate as Salesforce Files (ContentDocument + ContentVersion) linked via ContentDocumentLink to the corresponding Matter__c or Account record. Version history is preserved in Salesforce's version numbering system. The Legale e-signature execution status migrates as a custom field on ContentVersion.

Legale call logs, meeting records, and notes migrate as Salesforce Tasks (for calls), Events (for meetings), or Notes objects. Original timestamps and the assigned attorney (resolved as User) are preserved. Parent record links point to the related Matter__c via the WhatId field. Activity type determines the target Salesforce object.

Legale type-specific fields (e.g., Court_Name__c, Jurisdiction__c, Case_Number__c, Statute_of_Limitations__c) migrate as custom fields on Matter__c. Each field requires pre-creation in Salesforce Setup before data loads. Pick-list values require a value-mapping table; text and date fields map directly.

Legale invoice records track payment status, amount, and reference numbers. A custom Invoice__c object is created with Matter__c lookup, Invoice_Number__c, Amount__c, Status__c, Issue_Date__c, and Original_Legale_ID__c for traceability. Invoice status maps to a custom pick-list (Draft, Sent, Paid, Overdue).

Legale allows multiple organizations and contacts per matter (plaintiff, defendant, co-counsel). Since Salesforce Contact links to one primary Account, FlitStack creates a Matter_Party__c junction object to preserve all party associations. Each Matter_Party__c record stores the AccountId or ContactId reference plus a Role__c field (Plaintiff, Defendant, Co-Counsel, etc.).

Legale attorneys are resolved by email match against Salesforce Users. Unmatched attorneys are flagged before migration — your team either invites them to Salesforce or assigns their records to a fallback User. Bar license numbers migrate as a custom Bar_License__c field on the User record for compliance tracking.

Legale workflow rules for matter-stage transitions and deadline reminders have no direct Salesforce equivalent. FlitStack exports rule definitions as a reference document listing triggers, conditions, and actions so your Salesforce admin can reconstruct the logic in Flow Builder. Workflow reconstruction is a manual step not included in data migration pricing.