Migrate from CosmoLex to Salesforce Sales Cloud

CosmoLex clients are law firm counterparties (individual attorneys, corporate clients, or other law firms). They map to a Salesforce Account for the organization plus a Contact record for the primary billing or administrative contact. Corporate clients with multiple matter contacts receive one Account and multiple Contact records linked to that Account.

CosmoLex matters are the central record for a legal engagement. We map them to Salesforce Cases or a custom Matter__c object depending on whether the firm wants to use Salesforce's native Case object or a fully custom structure. Practice area, matter type, jurisdiction, and status migrate as custom fields on the target object. Matter-Case relationships to the Account (client) are preserved via the AccountId or a custom Client_Link__c lookup field.

Law firm staff contacts — attorneys, paralegals, billing administrators — map directly to Salesforce Contacts. Role information (origin attorney, timekeeper, billing contact) migrates as custom pick-list fields on the Contact record. Multi-office firms may need multiple Contact records per person if roles vary by office.

CosmoLex time entries contain matter link, timekeeper, billing rate, hours, date, task description, and billing status. Salesforce has no native billable-time object — we create a custom Time_Entry__c object with fields for Matter__c (lookup), Timekeeper__c (Contact lookup), Billing_Rate__c, Hours__c, Date__c, Description__c, and Billable__c. Entries marked as billed link to the corresponding Invoice__c record.

CosmoLex invoices are tied to a matter, contain line items from time entries and expenses, and carry LEDES billing codes. We map invoices to a custom Invoice__c object linked to the Matter__c and Account. Invoice line items map as Invoice_Line_Item__c records referencing the Invoice__c and Time_Entry__c or Expense__c records they were generated from. CosmoLex invoice templates do not transfer — formatting must be rebuilt in Salesforce's letterhead system.

CosmoLex expenses are linked to matters and categorized as hard costs (disbursements) or soft costs. Expenses map to a custom Expense__c object with fields for Matter__c lookup, category, amount, date, vendor, and cost type. Expenses billed to the client appear on the corresponding invoice as line items; costs paid from trust (IOLTA) carry a flag to the Trust_Account__c object.

CosmoLex trust accounts track operating and IOLTA balances with client-specific sub-accounts and transaction history. Salesforce has no native trust accounting — we create Trust_Account__c (for the firm-level account record with bank and account type) and Trust_Transaction__c (for per-client trust activity). Only current balances migrate as live records; historical trust transactions are exported as a reference file from CosmoLex and stored in Salesforce Files for audit purposes.

CosmoLex operating account balances and GL balances carry forward as balance-forward records in Salesforce. We create a GL_Balance__c object with fields for Account__c (firm-level), balance amount, as-of date, and account type (operating, trust, or GL). Historical GL transactions are not imported as records — they remain in CosmoLex export files. A journal-entry tool within Salesforce can be used by the firm's accountant to post opening balances.

CosmoLex calendar events and tasks linked to matters map to Salesforce Tasks and Events. The WhatId field on the Salesforce record links to the Matter__c or Case so attorneys can see matter-specific activities. CosmoLex's deadline and docketing features require a custom Deadline__c field on the Matter__c object or a Salesforce-native feature like Milestones if using Cases with entitlements.

CosmoLex documents attached to matters are exported as files and re-uploaded to Salesforce Files linked to the corresponding Matter__c or Case record. File size limits (Salesforce default 25MB per file; 2GB via Salesforce CRM Content) apply. Inline images in CosmoLex notes are downloaded and re-hosted as Salesforce Files. Document version history is not preserved unless CosmoLex exports include version metadata.

CosmoLex's native QuickBooks Online sync handles accounting synchronization. Salesforce has no equivalent built-in sync — firms must select an AppExchange accounting connector (such as、会计, or a native QuickBooks Salesforce connector) and re-establish the sync after migration. The existing CosmoLex-QuickBooks sync must be disabled before migration to avoid duplicate transactions.

CosmoLex stores custom invoice templates and billing formats per matter type or client. Salesforce has no native invoice template system — firms using custom billing formats need to rebuild templates using Salesforce's letterhead and email template system, or adopt Salesforce CPQ for more complex billing format requirements. We provide a template audit list before migration so the firm can prioritize rebuilds.