Migrate your Case.one data

Matters is the primary case object in Case.one, housing all case metadata, status, client reference, and assigned attorney. We migrate Matters 1:1 preserving all standard fields and the client-matter relationship. Custom fields on Matters require field-level mapping during scoping.

Client records contain contact information, billing details, and matter associations. We map Clients into the destination CRM's Contact or Account object, preserving the client-matter link so the relationship graph reconstructs on the target platform.

Time entries track billable and non-billable hours against Matters, linked to the responsible user. We preserve the user reference, matter association, date, duration, description, and billing rate. Closed matters retain their time entry history intact.

Invoices are generated from time entries and expense records within a Matter. We migrate invoice records including line items, totals, payment status, and trust account application. Open invoices are flagged for reconciliation during cutover.

Trust account balances are monetary records tied to Clients rather than Matters. We migrate the current balance and transaction history as financial records, but the mapping depends on whether the destination supports a separate trust accounting object or maps this to a generic financial account.

Documents are stored within Matters and organized by folder structure. We export documents with their matter reference and folder path so hierarchies reconstruct on the destination. Very large document sets may require chunked export and verification steps.

Tasks are associated with Matters and assigned to Users. We migrate task records preserving the matter link, assignee, due date, status, and description. Completed versus open task status is preserved.

User accounts include name, email, role, and billing rate. We export user records and map them to corresponding users on the destination platform. If the destination uses a different role model, we perform role-level mapping during the scoping call.

Case.one supports custom fields on Matters, Clients, and potentially other objects. Custom field schemas vary by firm. We enumerate all custom fields during discovery and map each to an equivalent destination field or store it as a custom property.

Billing rates are associated with Users and optionally with Matters. We preserve rate schedules so time entries calculate correctly on the destination if the same billing logic is in use.