Migrate from Lemon Tech to Salesforce Sales Cloud

Lemon Tech standard entities that represent people (attorneys, clients, opposing counsel) map to Salesforce Contact. Entities that represent organizations (law firms, corporate clients, courts) map to Salesforce Account. We inventory all standard entity types during discovery and assign the mapping based on the entity's role in the firm's workflow rather than a static rule. The entity name becomes the Contact LastName or Account Name; entity email becomes Contact Email or Account Email.

Custom entities in Lemon Tech map to Salesforce custom objects pre-created with the same API name (normalized to remove spaces and special characters, with __c suffix). Each custom entity's custom fields become custom fields on the destination custom object with appropriate Salesforce types (text, number, date, picklist, lookup). Lookup relationships between custom entities are preserved as Salesforce lookup fields, and we resolve the parent record ID during migration rather than at import time.

Lemon Tech Contact records map directly to Salesforce Contact with standard fields (Name, Email, Phone, MailingAddress) preserved. Any custom contact properties (bar number, practice area, client classification) migrate as custom fields on Contact. The AccountId on Contact is resolved by matching the Contact's associated Entity (if mapped to Account) or by holding the Contact in a staging queue until the parent Account is created.

Matter records map to Salesforce Case (using Service Cloud) if the firm uses matters primarily for legal matter tracking, or to Opportunity if matters represent revenue-generating engagements. The mapping decision is made during scoping based on the firm's workflow. Matter status maps to Case Status or Opportunity StageName; Matter number becomes Case CaseNumber or Opportunity InvoiceNumber. Custom matter fields migrate to custom fields on the destination object. We flag any Matter with a linked time entry total greater than zero as requiring an Opportunity conversion if Case was chosen as the destination.

Lemon Tech's link between Matters and Contacts (representing attorney on record, client, opposing counsel, expert witness) maps to Salesforce CaseContactRole or OpportunityContactRole. We preserve the role name and contact reference. If the Contact has not yet been migrated, we hold the link in a staging queue until Contact import completes.

Lemon Tech User records map to Salesforce User by email match. We extract all users referenced on Matters, Contacts, and time entries during discovery and match against the destination org's User table. Any Lemon Tech user without a matching Salesforce User is flagged in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Lemon Tech users map to inactive Salesforce users.

Time entries linked to Matters migrate to a Salesforce custom object (Time_Entry__c) with fields for Date, Hours, Billable_Amount__c, Description__c, and Matter_Reference__c (lookup to Case or Opportunity). This preserves the granular time tracking that law firms require for billing and compliance. Non-billable administrative time can optionally map to Task records for activity reporting. The mapping decision is made during scoping based on whether the firm uses Salesforce's native invoicing or an external billing system.

Lemon Tech billing records (invoices, payments, adjustments) map to a custom Invoice__c object linked to the Matter (Case or Opportunity) with invoice number, amount, date, status, and payment reference fields. If the firm uses Salesforce Opportunities for matter revenue tracking, billing amounts update the Opportunity Amount field. We preserve the full billing history including invoice PDFs as ContentDocument records attached to the Invoice__c record.

SQL Wrapper exports are structured relational tables created by Lemon Tech's custom SQL definitions. Simple wrappers (single table, no joins) map directly to Salesforce custom objects. Complex wrappers with multi-table joins, computed columns, or third-party data sources require manual field mapping during migration. We inventory all SQL Wrapper definitions during discovery, flag wrappers with nested logic or external data sources as requiring custom mapping work, and preserve the original wrapper SQL in a custom Long Text Area field on the destination object for auditability.

File attachments associated with Entities, Contacts, or Matters export as binary blobs from Lemon Tech. We map these to Salesforce ContentDocument (the library entry) and ContentVersion (the file revision) records linked via ContentDocumentLink to the parent Contact, Account, Case, or Opportunity. Filenames and file type are preserved. The original file association (e.g., Contract PDF linked to Matter) is preserved as the ContentDocumentLink's LinkedEntityId.

Custom fields on Lemon Tech entities (standard or custom) map to Salesforce custom fields on the corresponding object. Field type mapping follows standard conventions: text inputs become Text fields, numbers become Number fields with appropriate precision, dates become Date fields, and multi-value fields become Multi-Select Picklists. We normalize custom field names to a consistent format (removing spaces, applying PascalCase) and preserve the original Lemon Tech field name in a custom field label for auditability.

Matter status values in Lemon Tech (Active, Pending, Closed, On Hold, etc.) map to Salesforce Case Status picklist values or Opportunity StageName values depending on the Matter-to-object mapping decision. Each status value gets a probability percentage aligned with the firm's pipeline expectations. We configure the Status field during Salesforce org setup before migration begins so that the picklist is ready for data load.