Migrate your Case UI data

Cases are Case UI's primary container, holding all client, document, time, and billing relationships. We migrate Cases 1:1 with status, practice area, assigned attorneys, and creation/close dates intact.

Clients are core records linked to one or more Cases, carrying contact details and billing history. We preserve the Client-Case association and map all standard fields directly to the destination.

Contacts (opposing parties, co-counsel, witnesses) are referenced from Cases but Case UI's marketing does not explicitly call them out as a top-level entity. We extract any contact-style records attached to Cases and route them to the destination's Contacts object, mapping the case relationship as a custom property.

Documents attach to Cases and Clients. We migrate file blobs along with their parent-record association. Path structure and folder organization vary between Cloud and On-Premise deployments and must be reconstructed in the destination.

Tasks are deadline and to-do records linked to Cases with status, assignee, and due date. We migrate task records preserving owner and parent-Case association.

Time entries support hourly billing and feed Case UI's invoice generation. We export time records with date, duration, billing code, and Case association. Locked or already-billed time may require status mapping to the destination's time-entry model.

Invoices are generated from time entries and flat-fee charges and tie to a Case and Client. We migrate invoice headers, line items, and payment status. Open vs. paid status requires translation if the destination uses different invoice lifecycle states.

Payment records link invoices to received funds. We migrate payment history with date, amount, and invoice reference. Trust vs. operating account designation, if used, must be confirmed during scoping.

Calendar events tied to Cases (hearings, depositions, deadlines) are exported with date, type, and Case linkage. Case UI's calendar module is not deeply documented; we confirm which event types exist during discovery and map them to destination calendar or task objects.

Custom field support is not publicly documented for Case UI. We inspect the source database (on-premise) or CSV exports (cloud) to identify any custom attribute columns, then map them as extended properties on the destination object.

User records (attorneys, paralegals, staff) hold name, email, and Case assignments. We migrate user records and preserve ownership relationships, but role/permission mapping must align with the destination's access model.