Migrate your Legal Case Tracker data

Cases is the primary object in Legal Case Tracker, containing case name, status, type, description, and client linkage. Standard fields are stable and migrate 1:1. We flag any case with a null or duplicate case-number field for manual review before final import.

Contacts hold lawyer, client, and third-party party records linked to cases. Name, email, phone, address, and role fields map directly. We deduplicate against existing contacts in the destination using a composite key on name plus email domain.

Documents are attached to Cases and Contacts. No native export endpoint exists; we extract files from the underlying storage layer and re-associate them by case reference during import. We flag any document with a missing parent-case link for manual triage.

Tasks track action items linked to a Case, with due date, assignee, status, and description fields. Subtasks are not a native object but are sometimes stored as repeating tasks; we flatten these into the destination task structure and preserve parent-child relationships as a custom property.

Time entries capture billable hours logged against a Case with description, duration, date, and billing rate. Rate and currency fields vary by tier; we normalize to a standard decimal-hour format and flag any entry where the currency field is absent or non-standard.

Expenses are case-linked cost records with amount, category, date, and receipt reference. We migrate the structured fields directly and attach any extracted receipt file to the corresponding expense record in the destination.

Calendar Events represent hearings, deadlines, and appointments linked to Cases. We extract the event title, start/end datetime, and case reference. Events with no case link are imported as standalone calendar items and flagged for manual review.

Case status values (e.g., Intake, Active, Pending, Closed) map directly to the destination pipeline stage. We preserve the original status label as a read-only field in the destination so teams can validate that no cases were inadvertently skipped during cutover.

User accounts carry name, email, role, and access level. Role-based access flags are preserved as a custom property in the destination. We map the owner/assignee field on each Case to the corresponding user record by email to maintain referential integrity.