Migrate your MerusCase data

Cases are the central MerusCase object, housing parties, documents, activities, ledger lines, and custom fields. We migrate Cases as the top-level record, preserving all sub-object relationships. Document Archive exports provide per-case zipped documents and a CSV of case activities.

Contacts are a distinct object used for clients, opposing counsel, witnesses, and other parties. The CSV Import tool supports bulk contact loading. We map contact fields 1:1 where the destination schema supports person-type records.

Parties on a case represent named individuals or entities tied to a specific Case. Party records include role assignments (plaintiff, defendant, witness, etc.) that vary by case type. We preserve party-role associations but map role names to destination equivalents.

Activities are time-stamped entries within a Case file — calls, emails, tasks, calendar events, and notes. The Document Archive CSV export covers all case activities. We migrate Activities preserving date, type, description, and linked contact.

Documents are stored per Case and included in the Document Archive as a zipped bundle. Binary files require a file-level migration pass. We extract document filenames and metadata from the archive manifest and map them back to the destination's document management structure.

Case Ledgers capture billable time (with UTBMS task and activity codes) and expenses (with UTBMS expense codes). The API supports bill_to_contact_id, task_code, activity_code, and expense_code fields. We preserve full ledger granularity including rejected/reviewed status flags.

Charges represent open, reviewed, exported, or rejected billing items across the firm. The Charges tab aggregates ledger items for accounting review. We migrate Charges with status flags and link them back to their originating Case Ledger records.

Settlement records are case-type-specific and store structured settlement outcomes and damages data. Availability depends on whether the firm's case type exposes the Settlements tab. We migrate Settlement data where present and map fields to destination equivalents.

MerusCase supports up to 50 custom fields per firm across five types: Date, Currency, Text (250 char), Numeric, and Yes/No dropdown. Custom fields apply to individual Case Views only. We map custom field names and types to destination custom fields, flagging any that exceed destination field limits.

Case Types drive which tabs and fields appear in a Case — Criminal, Personal Injury, Workers' Compensation, Employment, etc. We preserve the case_type_id reference and replicate the firm's case type structure in the destination where applicable.

MerusCase Workflows trigger on activity tags or description text and create tasks or events automatically. Workflow logic is platform-specific and not exposed via API. We document existing Workflow configurations during scoping but do not migrate them — they must be rebuilt manually on the destination platform.

Statutes are case-type-specific automation rules that create reminders and to-do items based on statutory deadlines. They are tied to calendar entries and use the date of the triggering item. We capture Statute configurations during discovery but migration requires manual recreation in the destination system.

MerusCase assigns Staff members to Cases and ledger entries. User records include role-based access (attorney, paralegal, admin). We migrate Staff as Owner/User records and map role assignments to the destination's permission model.