Migrate your RunSensible data

Clients are the primary contact object in RunSensible. We map all standard fields including name, email, phone, address, and custom properties. Source CRM contacts without matter history are imported as Clients. We preserve the client-created date and any tags.

Matters represent cases or files in RunSensible's legal data model. We map matter name, number, type, status, assigned attorney, responsible attorney, open date, and custom fields. We preserve the pipeline stage and any associated lead source.

Time entries link to a Matter and a Client. We map description, duration, hourly rate, billing status, and date. Time entries without an associated matter must be flagged—RunSensible requires a matter context for billable entries. We convert duration formats to RunSensible's expected decimal hours.

RunSensible invoices reference a Client and optionally a Matter. We map line items, totals, status, due date, and currency. We cannot migrate partial payments that span multiple invoices unless they are split into per-invoice allocations. Multi-currency invoices require explicit currency mapping.

Trust accounts track client funds held in IOLTA accounts. We map account number, type (operating, trust, advanced), and current balance. Transaction history is migrated as individual entries. Three-way reconciliation status is preserved where available.

Documents are associated with Matters or Clients. We migrate file name, type, upload date, and associated metadata. Binary file content is transferred via direct storage access where available. Document templates are migrated separately from generated documents.

Events link to Matters and include title, date/time, duration, assigned attorney, and invitees. We map the event data and any recurrence rules. We do not migrate active meeting links or video conference credentials—these must be regenerated on the destination platform.

RunSensible stores intake form submissions linked to Leads or Clients. We map field values and submission dates. Conditional logic in the form is not preserved—forms must be rebuilt on the destination platform to replicate branching rules.

RunSensible distinguishes Leads from Clients during the intake phase. We map lead status, source, assigned user, and custom fields. Leads not yet converted to Clients require mapping to the destination's lead object with a status flag.

Tasks are associated with Matters or Clients and include assignee, due date, priority, and completion status. We map task name, description, due date, assignee, and status. Recurring task rules are preserved where documented.

RunSensible uses tags for labeling Clients, Matters, and Documents. We map all tag names and their associations. Tags must be recreated on the destination if the target platform uses a different taxonomy model.

Custom fields extend Clients, Matters, and other objects. We map field names, data types, and values. Picklist options and validation rules must be reviewed post-migration to ensure consistency on the destination platform.