Migrate from CosmoLex to Freshsales

CosmoLex clients map to Freshsales accounts. The client name becomes the Account Name field in Freshsales. Client status (Active, Inactive, or Pending) is preserved as a custom Account pick-list field (Client_Status__c) since Freshsales has no native client lifecycle concept. Client-level custom fields from CosmoLex migrate as Freshsales custom fields on the Account object.

CosmoLex matters map to Freshsales deals. A custom field (CosmoLex_Matter_ID__c) links each Freshsales deal back to its source matter for traceability. The deal name is constructed from the matter name, and the matter number is stored in a custom deal text field for reference. Billing-method and practice-area fields from CosmoLex migrate as Freshsales custom pick-list fields on the deal. The parent client resolves to the Freshsales account via account_id lookup.

CosmoLex contact records (on matters or in the address book) map directly to Freshsales contacts. Email uniqueness is enforced in Freshsales — duplicates are flagged and resolved before migration commits. Primary contact per matter is linked to the corresponding Freshsales account via account_id lookup. Original CosmoLex create dates are preserved in a custom datetime field.

CosmoLex matter owners are matched to Freshsales users by email address using a pre-migration resolution scan. Unmatched owners are flagged before migration — you either invite them to Freshsales first or reassign their records to a fallback user designated in your migration spec. CosmoLex timekeepers follow the same email-resolution logic during migration.

CosmoLex tasks and to-do items map directly to Freshsales tasks with no transformation required. Original due dates, task descriptions, completion status, and owner assignments are preserved. Tasks are linked to the corresponding Freshsales account or deal via the matter-to-account association established during migration. CosmoLex task categories map to Freshsales task types.

CosmoLex calendar events migrate as Freshsales events with original start and end timestamps preserved in Freshsales datetime fields. Events are linked to the account or deal through the matter-to-account association. Prior historical events and future scheduled events are both migrated in full. CosmoLex event locations map to Freshsales event location fields.

CosmoLex matter notes migrate as Freshsales notes attached to the corresponding account or deal record. Original creation timestamps are preserved in a custom Original_Create_Date__c datetime field. Rich-text formatting is retained where supported by Freshsales Notes. The parent matter association is maintained via the deal lookup on the account.

CosmoLex vendors and payees have no Freshsales equivalent — Freshsales has no AP, vendor-management, or payment-tracking module. They are preserved as Freshsales accounts with a custom Boolean field (Vendor_Flag__c = true) and contact records for the vendor's primary contact. These accounts are for reference only — Freshsales does not support AP workflows or disbursement tracking.

CosmoLex matter custom fields migrate as Freshsales custom fields on the Deal object. All CosmoLex practice-area pick-list values are re-created as Freshsales custom pick-list options on the deal. Numeric, date, datetime, and text custom fields map by their field type. Multi-select pick-lists from CosmoLex require custom handling during migration.

CosmoLex client custom fields migrate as Freshsales custom fields on the Account object. Fields that store billing references (e.g., billing contact, rate agreement, payment terms) are preserved as Freshsales custom text fields on the account for historical reference. Client-level date fields map to Freshsales custom date fields on the Account object.

CosmoLex files attached to matters re-upload as Freshsales Files linked to the corresponding account or deal. File size limits apply per Freshsales file storage constraints. CosmoLex's document folder structure is not preserved — files are attached directly to the parent matter record after migration.

Invoices, payments, trust account transactions, IOLTA balances, and GL journal entries have no Freshsales equivalent and are explicitly excluded from the migration scope. Freshsales lacks any accounting, AP, or financial object. FlitStack AI exports a complete financial snapshot from CosmoLex (invoice register, trust ledger, GL trial balance) as a dated archive file for your records before the migration window opens. All billing, trust accounting, and financial reporting continue in CosmoLex post-migration.

CosmoLex matter workflows, task automation rules, and matter-owner routing configurations do not export via CosmoLex data templates — there is no machine-readable export format for these objects. Freshsales has its own Workflow Builder and Sequence Builder with different trigger logic, action types, and object scope. FlitStack AI exports a human-readable workflow-definition reference document from CosmoLex listing every active workflow, its trigger conditions, assigned actions, and affected matter types. Your Freshsales admin uses this as a rebuild checklist for manual recreation in Freshsales.

QuickBooks links, law firm portal integrations, e-filing connections, and third-party apps connected to CosmoLex are not migratable to Freshsales. Each integration must be re-established manually in Freshsales or evaluated for replacement by a Freshworks Marketplace app. FlitStack AI documents your active CosmoLex integrations in the pre-migration audit for your IT team to address post-migration.