Migrate from RunSensible to monday CRM

RunSensible CRM contacts map directly to Monday CRM person items. First name, last name, email, phone, and address split into separate text columns. Source contact ID stored as a text column for delta-run de-duplication. Multi-company affiliation on a RunSensible contact collapses to the primary company record with secondary affiliations surfaced as text notes.

RunSensible companies map to items on a dedicated Company board with columns for company name, domain, industry, employee count, and revenue. For small CRM setups, company name is stored as a text field on the contact person item. Monday CRM does not have a native Company object — the Company board is a best-practice substitute.

RunSensible client records (the law firm practice management entity) map to Monday CRM person items or items on a dedicated Client board. Fields include client name, contact info, client type, source, responsible attorney, and status. We preserve the client–matter link by linking the client item to its associated matter items via a connect boards column.

RunSensible matters map to items on a Matter board. Each matter type (litigation, corporate, personal injury, family law) gets its own board so status columns reflect the correct stage workflow. Columns include matter name, number, type, status, responsible attorney, court, opposing counsel, filing date, statute of limitations (custom date column), and description. Matter–client link uses a connect boards column or person column.

RunSensible billing records map to items on a dedicated Billing board with columns for matter name (connect boards), invoice number, amount, status (open/paid/overdue), due date, and payment date. Monday CRM has no native invoice or billing module — this board serves as a reference record. IOLTA trust accounting balances, operating trust balances, and reconciliation status are stored as text or number columns since Monday lacks a native trust ledger.

RunSensible time entries map to items on a Time Tracking board with person column (attorney), connect boards column (matter), date, duration (number of hours), hourly rate (number), billable flag (status or checkbox), and description. Monday CRM Pro and Enterprise plans include native time tracking columns — time entries can alternatively map to the native time tracking column on matter items if the plan supports it.

RunSensible documents attached to matters and clients re-upload to Monday CRM using the Files column type on the associated matter item. External file URLs (documents hosted outside RunSensible) store as text columns with the URL. File size limits per Monday.com apply — documents over 25 MB are flagged for manual re-upload.

RunSensible client intake form records map to items on a dedicated Intake board with person column (client), status (New/In Review/Complete), form data fields (text columns), submission date, assigned attorney, and notes. Conditional form logic and required-field rules require manual rebuild in Monday's form and automation system.

RunSensible's IOLTA trust accounting ledger — with trust balance, operating balance, client ledger entries, and three-way reconciliation status — has no native Monday CRM equivalent. We migrate trust account name, client matter reference, transaction type, amount, and running balance as text and number columns on a custom Trust Accounting board. Compliance-grade reconciliation procedures must be rebuilt as manual processes or third-party tools.

RunSensible's conflict check results (screening new clients against the entire client database before intake) have no Monday CRM equivalent. We preserve conflict check date, client name, parties screened, and result (Clear/Conflict) as text columns on a custom Conflict Check board. The conflict-check procedure must be rebuilt as a manual checklist or integrated third-party tool in Monday CRM.

RunSensible custom fields on contacts, clients, and matters map to custom columns on the corresponding Monday CRM board. Column type is selected based on the RunSensible field data type: text for strings, number for integers/decimals, date for dates, status for pick-list values, checkbox for booleans, and person for user lookups. Custom objects in RunSensible (Enterprise feature) map to separate boards with connect boards columns for relationships.

RunSensible automations use a trigger-condition-action model with multi-step sequences, time delays, and field-update rules. Monday CRM automations use a when-then structure with no support for nested sequences or complex conditional branching. We export RunSensible automation definitions as a JSON reference document during discovery. Your Monday admin uses this as a rebuild guide — mapping each RunSensible trigger to a Monday automation recipe.