CRM migration
Field-level mapping, validation, and rollback between Case UI and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Case UI
Source
monday CRM
Destination
Compatibility
12 of 12
objects map 1:1 between Case UI and monday CRM.
Complexity
BStandard
Timeline
48–72 hours
Overview
Case UI is a vertical-specific legal practice management system: it stores client records, case files, time entries, and document attachments in a normalized relational schema designed for law firm workflows. Monday CRM is a horizontal Work OS that models CRM data as Items on Boards, with Status columns serving as the pipeline stage mechanism, text/number/date columns for fields, and sub-items for activity logs. The two data models are structurally divergent — Case UI uses normalized tables with foreign-key relationships, while Monday CRM uses a flat board-item architecture with no native relational integrity enforcement between boards. FlitStack AI bridges this by first mapping Case UI entities to Monday CRM board structures: clients become Contacts (or Board Items), active matters become Items on a Cases board, time entries map to sub-items, and documents are re-uploaded as Monday Files attached to the appropriate Items. We preserve Case UI's original create/update timestamps as custom Date columns and resolve attorney assignments by email match against Monday CRM user accounts. Custom fields from Case UI translate to Monday CRM's column types (Text, Number, Dropdown, Date, etc.) with value mapping for pick-list equivalents. Workflows, billing rules, and trust-account configurations do not migrate — they are Case UI-specific logic that has no Monday CRM equivalent. We export Case UI workflow definitions as a rebuild reference so your Monday admin can reconstruct automation logic using Monday's Automation infrastructure. The migration runs via Monday's REST API with throttling aligned to your plan tier: 1,000 calls/day on Standard, 10,000 calls/day on Pro, and up to 25,000 calls/day on Enterprise. We apply staggered batch inserts to stay within Complexity and Concurrency limits, retrying on IP_RATE_LIMIT_EXCEEDED and COMPLEXITY_BUDGET_EXHAUSTED responses.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Case UI object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Case UI
Client
monday CRM
Contact + Company Board Item
1:1Case UI Client records map directly to Monday CRM Contacts (name, email, phone, address). The primary practice area or firm name becomes a Company Board Item linked to the Contact via Monday's Link to Item column, preserving the one-to-many matter relationship.
Case UI
Matter
monday CRM
Cases Board Item
1:1Case UI Matter records map to Items on a dedicated Cases Board in Monday CRM. Matter name becomes the Item name, status maps to a Status column, responsible attorney maps to an Assignee column, and the client link becomes a Link to Item column pointing to the Contact.
Case UI
Matter Status
monday CRM
Cases Board — Status Column
1:1Case UI matter statuses (Open, Pending, On Hold, Closed, Archived) map to Monday CRM Status column labels. We preserve the original status-transition timestamps as a secondary Date column (Last_Status_Change__c) for audit continuity in the new board. If a status label in Case UI has no direct Monday CRM equivalent, we create a custom Status label that mirrors the source term and document the mapping in the schema plan.
Case UI
Time Entry
monday CRM
Cases Board — Sub-item
1:1Case UI time entries (hours, date, billing rate, description) migrate as Sub-items on each Matter Item in Monday CRM. The Sub-item contains Date, Number (hours), Number (rate), and Text (description) columns. Billing status (billed/unbilled) maps to a Status sub-column. Additionally, each Sub-item records the attorney’s email in a People column for traceability, and any external billing codes are preserved as Text fields to facilitate reporting in accounting tools after migration.
Case UI
Document / Attachment
monday CRM
Monday Files
1:1Case UI file attachments on matters are downloaded and re-uploaded as Monday Files attached to the corresponding Matter Item. File name, upload date, and uploader are preserved as metadata columns on the file attachment Item. Files exceeding Monday CRM's 25 MB per‑file limit are flagged, split when possible, and unsplittable files are delivered as archive with a reference link in the Item. Storage usage is tracked against plan limits before migration.
Case UI
Calendar Event / Court Date
monday CRM
Cases Board — Date Column + Sub-item
1:1Case UI calendar entries and court dates migrate as Date columns on the Matter Item (primary date) and as Sub-items (for multi-event days) with a Label column distinguishing event types (Court Hearing, Deposition, Filing Deadline). Time zone information from Case UI is stored in a Text column, and recurrence patterns are captured as Text notes. The team can set Monday’s reminders on each date to trigger notifications ahead of deadlines.
Case UI
Note / Communication Log
monday CRM
Matter Item — Updates Column
1:1Case UI notes and client communication logs migrate to the Matter Item's Updates column in Monday CRM, with original author and timestamp preserved. Long notes are split into multiple Update entries to respect column character limits. Attachments referenced in notes are uploaded as Monday Files and linked within the Update text, and any inline images are re-hosted on monday.com's CDN to ensure they display correctly in the board view.
Case UI
Custom Field (Client)
monday CRM
Contacts Board — Custom Column
1:1Case UI custom fields on Client records (e.g., Bar Number, Referral Source, Practice Area) become custom columns on the Contacts Board in Monday CRM. Column type is inferred from the Case UI field data type: text fields become Text columns, pick-lists become Dropdown columns, dates become Date columns.
Case UI
Custom Field (Matter)
monday CRM
Cases Board — Custom Column
1:1Case UI matter fields (e.g., Case Type, Opposing Counsel, Court Location, Insurance Carrier) migrate as columns on Cases Board. Column type is inferred from data type: text fields become Text columns, numeric values become Number columns, and dates become Date columns. Multi-select pick‑lists translate to Monday's Tags column, while single‑select pick‑lists map to Dropdown columns. Any pick‑list options without a Monday equivalent are recorded as text entries, flagged for review.
Case UI
Billing / Invoice Record
monday CRM
Cases Board — Number + Status Column
1:1Case UI invoice records migrate as a combination of Number columns (Total Amount, Amount Paid, Balance Due) and a Status column (Billed, Paid, Overdue, Written Off) on the Matter Item. Trust account balances are stored as a separate Number column. Actual financial ledger integrity requires a dedicated accounting tool post-migration.
Case UI
Attorney / Staff User
monday CRM
Monday CRM User Account
1:1Case UI attorney and staff user accounts are resolved by email match against Monday CRM workspace members. Unmatched users are flagged as a pre-migration action item — the team either creates Monday accounts or assigns their matters to a fallback assignee.
Case UI
Workflow / Automation
monday CRM
Not Migrated — Rebuild Reference Export
1:1Case UI automations and matter workflows have no structural equivalent in Monday CRM. FlitStack exports the workflow definitions (trigger events, conditions, actions) as a JSON reference document. Monday's Automation or Integrations setup (using Monday's native recipe blocks) handles the rebuild.
| Case UI | monday CRM | Compatibility | |
|---|---|---|---|
| Client | Contact + Company Board Item1:1 | Fully supported | |
| Matter | Cases Board Item1:1 | Fully supported | |
| Matter Status | Cases Board — Status Column1:1 | Fully supported | |
| Time Entry | Cases Board — Sub-item1:1 | Fully supported | |
| Document / Attachment | Monday Files1:1 | Fully supported | |
| Calendar Event / Court Date | Cases Board — Date Column + Sub-item1:1 | Fully supported | |
| Note / Communication Log | Matter Item — Updates Column1:1 | Fully supported | |
| Custom Field (Client) | Contacts Board — Custom Column1:1 | Fully supported | |
| Custom Field (Matter) | Cases Board — Custom Column1:1 | Fully supported | |
| Billing / Invoice Record | Cases Board — Number + Status Column1:1 | Fully supported | |
| Attorney / Staff User | Monday CRM User Account1:1 | Fully supported | |
| Workflow / Automation | Not Migrated — Rebuild Reference Export1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Case UI gotchas
No public API documentation found
On-Premise perpetual license has upgrade isolation risk
No verified public reviews or G2/Capterra feedback
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Audit Case UI data model and build the Monday CRM schema plan
FlitStack AI reads the Case UI API or export to catalog all active clients, matters, time entries, documents, and custom fields. We analyze field data types, pick-list values, and matter-board structures. Simultaneously, we plan the Monday CRM workspace: the Contacts Board, Cases Board, column types for every migrated field, Link to Item column setup for client-matter relationships, and Sub-item configuration for time entries. The schema plan is delivered as a Monday-compatible board-template export before any data moves.
Resolve attorney and staff user assignments by email match
Case UI attorney and staff records are matched against Monday CRM workspace members by email address. Unresolved users — those without a Monday CRM account at migration time — are flagged in a pre-flight report with their Case UI user name and email. The team either creates Monday accounts for them before migration or designates a fallback assignee. No matter Item is created without an assignee value, either resolved or fallback.
Migrate clients to the Contacts Board first, then matters to the Cases Board
We sequence the migration to respect Monday CRM's dependency order: Contact Items must exist before Matter Items can link to them via the Link to Item column. Clients migrate first as Contact Items with their custom fields. Matters migrate second as Items on the Cases Board, with the client link resolved at insertion time. Time entries, documents, and calendar entries follow as Sub-items and file attachments on each Matter Item. The migration runs in API-rate-limited batches aligned to the Monday CRM plan tier.
Run a sample migration with field-level diff and board-structure verification
A representative slice — typically 50–200 matters spanning all practice areas and matter statuses — migrates first. We generate a field-level diff comparing each Case UI field value against the corresponding Monday CRM column value on the sample Items. We also verify that Link to Item columns resolve correctly, Status column labels map from Case UI values, and Sub-items attach to the correct parent Matter Item. The diff is reviewed with the team before the full run is committed.
Execute full migration with delta-pickup and post-migration audit
The full dataset migrates in rate-limited batches. A delta-pickup window (24–48 hours) captures any Case UI records modified or created during the cutover period — new matters, updated statuses, newly attached documents. After the delta window closes, we run a reconciliation audit: record counts per board, link-integrity check on all client-matter relationships, document attachment count, and a comparison of the sample diff baseline against production values. One-click rollback is available if the audit reveals critical mismatches. The workflow export JSON is delivered alongside the migrated data as a rebuild reference.
Platform deep dives
Case UI
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Case UI and monday CRM.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Case UI: Not publicly documented.
Data volume sensitivity
Case UI doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Case UI to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Case UI to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Case UI
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.