Migrate your CosmoLex data

CosmoLex maintains Client records as the primary contact entity. We map Clients 1:1 to the destination contact schema, preserving all standard fields (name, email, phone, address). Client-to-Matter relationships are preserved via our relationship graph during migration.

Matters are the core case/matter objects in CosmoLex. We migrate Matters with full metadata including Matter owner assignment, billing type, responsible attorney, and status. Custom Matter fields are mapped field-by-field to the destination schema.

Timekeepers represent attorneys, paralegals, and billable staff whose time is tracked. We migrate Timekeeper records and link them to their respective time entries and Matter assignments so billing authority is preserved at the destination.

Time entries are tied to Matters and Timekeepers. We carry forward all billed and unbilled time entries, preserving hours, rates, descriptions, and billing status so no WIP is lost during the transition.

CosmoLex uses a separate Trust Accounting module for IOLTA-compliant client funds. We migrate trust account balances and retainer credits, but historical trust transaction history is typically migrated as a balance-forward only. Trust Admin Fees and IOLTA levy codes require field-level mapping to the destination trust schema.

CosmoLex invoices carry billing method (hourly, fixed fee, contingency), line items, payment status, and aging data. We migrate open AR balances and outstanding invoices. Fully paid historical invoices are referenced by balance only since CosmoLex recommends maintaining prior invoice copies for reference rather than reimporting closed billing history.

CosmoLex maintains a Chart of Accounts that must be customized by the user after migration setup per their financial preferences. We replicate the COA structure at migration time but note that journal entry setup and GL balance migration are the customer's responsibility post-import per CosmoLex's migration guide.

CosmoLex includes document storage linked to Matters. We migrate document references and, where the export is available, the files themselves. Large document repositories may require chunked migration with a dedicated file transfer protocol.

Operating bank balances, uncleared checks, and credit card account balances are migrated as balance-forward entries. CosmoLex does not import historical bank transactions — those must be reconciled manually or via the destination bank's transaction feed post-migration.

Unpaid AP bills are migratable. We preserve vendor details, open AP amounts, and due dates. Historical paid AP records are not carried forward — only outstanding payables land in the destination.

CosmoLex stores billing rates and fee arrangements per Matter or per Timekeeper. We preserve these so the destination can continue billing under the same rate structures without manual re-entry.

CosmoLex supports custom fields on Matters and Clients. We map custom field values field-by-field. The destination field types must be compatible — we flag any type mismatches (e.g., dropdown vs. free text) for manual review before import.

Firm staff records including role, permissions, and login status are migrated. Role-to-permission mapping varies by destination system, so we preserve the role assignment and flag permission gaps in the target.

CosmoLex report templates and invoice/letter templates are not structurally migratable to other platforms due to proprietary template formatting. We recommend rebuilding key templates in the destination using exported field lists rather than attempting to import the template files themselves.