Migrate from CosmoLex to HighLevel

CosmoLex clients map directly to HighLevel contacts. Client name splits into first name and last name; email and phone fields map 1:1. Primary client address becomes the contact address fields. CosmoLex client type (individual vs. organization) determines whether the contact is person or company based.

CosmoLex matters have no direct HighLevel equivalent. We create a Matter custom object in HighLevel with fields for matter name, matter number, matter status, matter type, and matter owner. Each migrated contact gets linked to its matter records via custom object associations using the N:N relationship model.

CosmoLex matter owners are assigned lawyers. HighLevel has no matter-owner field on contacts. We match CosmoLex matter owners by email to HighLevel user accounts and store the assignment as a custom field on the matter record. Unmatched attorneys are flagged for manual HighLevel user creation before migration.

CosmoLex address book contacts migrate as HighLevel contacts with a custom tag field marking them as non-client records. These contacts are available for conflict checks and matter-party associations in HighLevel but do not receive marketing communications by default. The contact type field is set to indicate address book origin, and a custom taxonomy distinguishes them from billable client contacts.

CosmoLex custom field types (single-line text, text area, drop-down select, date picker, currency, number, option list, contact field) each map to the closest HighLevel custom field type. Drop-down and option-list fields require value-by-value mapping when the pick-list values differ between systems.

CosmoLex calendar events and to-do items migrate to HighLevel tasks. Event dates and task due dates preserve original timestamps. Assigned attorney maps to the matched HighLevel user. HighLevel does not have a native matter-linked calendar — tasks link to the contact record and the matter reference is stored in a custom field.

CosmoLex matter notes migrate to HighLevel contact notes, with the original note text and create date preserved verbatim. Notes that were tagged or authored by a specific attorney in CosmoLex retain the author attribution as a custom field on the note record for audit continuity and compliance tracking across the migrated dataset.

HighLevel does not have a legal billing or invoice object. CosmoLex invoice numbers, amounts, statuses, and dates migrate as a custom object linked to the contact and matter. Outstanding invoice balances and due dates are preserved as reference data for billing continuity.

CosmoLex IOLTA trust account balances and matter trust ledger entries have no HighLevel equivalent. We preserve trust balance, operating balance, and any uncleared transactions as a custom object linked to the matter and contact for reference. Reconciliation must occur in CosmoLex before migration.

CosmoLex unbilled time and disbursement work-in-progress migrates as a custom object linked to both the matter and the associated contact record. We preserve the time entry date, hours logged, billing rate, and description fields exactly as they appear in CosmoLex. Actual invoice generation must be completed in HighLevel's invoicing module post-migration.

CosmoLex accounts payable vendor contact information migrates as HighLevel company records tagged as vendors. Vendor address and payment details such as payment terms and default accounts are stored in custom fields on the company record since HighLevel lacks a native accounts payable vendor object for AP tracking.