Migrate from Legal Workspace to monday CRM

Legal Workspace contacts and clients map 1:1 to Monday CRM People items on a Contacts board. The contact's full name splits into First Name and Last Name columns; email, phone, and address map to their Monday CRM equivalents. Matter associations are preserved via a Link-to-items column pointing to the Matters board.

Each Legal Workspace matter becomes a deal Item on a Matters board in Monday CRM. The matter number migrates as a text column for reference. The primary client contact is linked via a Link-to-items column. All other matter metadata — status, practice area, responsible attorney, open date — map to Monday CRM columns matching their source types.

Legal Workspace matter status values (Active, Pending, Closed, On Hold) map to Monday CRM Status column options. Each status label is mapped value-by-value. If Legal Workspace uses custom status values, those are created as custom Status options before migration runs so no mapping falls through to a default.

Documents attached to Legal Workspace matters are either re-uploaded to Monday CRM's file upload column (preserving the original filename and upload date as metadata) or mapped as external link columns if the team prefers to keep files in their existing document management system. File version history is preserved as a text column note.

Legal Workspace billing and time entries are aggregated into a separate Time & Billing board linked to the Matters board via Link-to-items. Each billing entry becomes an Item with date, hours, rate, description, and linked matter columns. The Monday CRM invoice module (Standard+ plan) can then generate invoices from this board's data.

Every Legal Workspace custom matter property gets a new Monday CRM column created before migration. The column type is inferred from the source data type — text properties become Text columns, date properties become Date columns, multi-select values become Labels columns. Multi-select pick-list values with more than 20 options are mapped as Text columns with the original values preserved verbatim.

Contact-level custom properties from Legal Workspace — such as preferred contact method, bar association number, or billing notes — become custom columns on the Contacts board. The same type-inference logic applies: text → Text column, date → Date column, numeric → Number column.

Legal Workspace activity log entries (calls, emails, meetings logged against a matter) are migrated as Updates on the corresponding matter Item in Monday CRM, with the activity type, date, and description preserved. If the team needs structured activity tracking, these can alternatively be created as Items on a separate Activities board linked to the relevant matter.

Legal Workspace allows multiple contacts per matter (e.g., opposing counsel, third parties). These secondary contacts are migrated as additional Link-to-items entries on the matter Item, pointing to People items on the Contacts board. Monday CRM supports multiple links per item, making this a direct 1:N mapping.

Legal Workspace matter tags and contact tags map to Monday CRM Labels columns on their respective boards. Each unique tag value from Legal Workspace becomes a Label option in Monday CRM. Tags that appear on both contacts and matters are preserved independently on each board, maintaining the original tag vocabulary without merging across record types.

Legal Workspace user accounts (attorneys, paralegals, admins) are mapped to Monday CRM team members by email. The user name and email are stored in a Name and Email column respectively on a Team board for reference. Monday CRM boards use a People column type to assign owners to Items, which is the primary owner assignment mechanism post-migration.

Legal Workspace matter workflows (status-change triggers, approval chains, document-assembly automations) have no direct Monday CRM equivalent. Monday automations operate on column-change triggers within a board and cannot replicate Legal Workspace's multi-step matter workflows. These must be rebuilt using Monday's Automation Center after migration; FlitStack exports workflow definitions as a rebuild reference document.