CRM migration

Migrate from Case UI to monday CRM

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 logo

Case UI

Source

monday CRM

Destination

monday CRM logo

Compatibility

100%

12 of 12

objects map 1:1 between Case UI and monday CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Case UI logo

Case UI

What's pushing teams away

  • Small law firms report outgrowing the platform when they need advanced integrations, custom workflows, or multi-office support that Case UI does not provide.
  • Lack of public API documentation makes Case UI difficult to connect with third-party tools, forcing firms to manually export and re-enter data when workflow needs change.
  • Users with complex practice areas report that the platform lacks depth in features like advanced reporting, conflict checking, or specialized litigation tools.
  • On-Premise customers who lack dedicated IT staff struggle with self-managed security updates and backups, leading some to move to fully managed alternatives.

Choosing

monday CRM logo

monday CRM

What's pulling them in

  • Users praise the board-based visual interface for making pipeline stages immediately legible to non-technical team members without CRM training.
  • The no-code automation builder lets sales ops teams create lead routing, stage updates, and email triggers without developer involvement.
  • Integration ecosystem connects to Slack, Gmail, Outlook, and Zapier with minimal configuration, reducing friction for teams already using these tools.
  • The flexible column system lets teams build custom CRM views — deal value, close date, lead source — without needing a developer or pre-defined schema.
  • Teams already using monday Work Management can layer CRM features onto existing boards rather than starting from scratch.

Object mapping

How Case UI objects map to monday CRM

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

maps to

monday CRM

Contact + Company Board Item

1:1
Fully supported

Case 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

maps to

monday CRM

Cases Board Item

1:1
Fully supported

Case 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

maps to

monday CRM

Cases Board — Status Column

1:1
Fully supported

Case 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

maps to

monday CRM

Cases Board — Sub-item

1:1
Fully supported

Case 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

maps to

monday CRM

Monday Files

1:1
Fully supported

Case 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

maps to

monday CRM

Cases Board — Date Column + Sub-item

1:1
Fully supported

Case 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

maps to

monday CRM

Matter Item — Updates Column

1:1
Fully supported

Case 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)

maps to

monday CRM

Contacts Board — Custom Column

1:1
Fully supported

Case 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)

maps to

monday CRM

Cases Board — Custom Column

1:1
Fully supported

Case 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

maps to

monday CRM

Cases Board — Number + Status Column

1:1
Fully supported

Case 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

maps to

monday CRM

Monday CRM User Account

1:1
Fully supported

Case 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

maps to

monday CRM

Not Migrated — Rebuild Reference Export

1:1
Fully supported

Case 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.

Gotchas + challenges

What specifically takes care here

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 logo

Case UI gotchas

High

No public API documentation found

Medium

On-Premise perpetual license has upgrade isolation risk

Low

No verified public reviews or G2/Capterra feedback

monday CRM logo

monday CRM gotchas

High

Subitems are not included in bulk exports

High

Daily API call limits vary sharply by plan

Medium

Legacy automations (Sentence Builder) are being deprecated

Medium

Excel and account exports only include table views

Low

Enterprise admins can disable non-admin exports

Pair-specific challenges

  • Monday CRM's flat board architecture loses matter-to-client relational integrity without explicit link columns

    Case UI enforces that every Matter belongs to exactly one Client via a foreign-key relationship. Monday CRM has no equivalent — Items on the Cases Board and Contacts Board are independent rows. We bridge this by creating a Link to Item column on each Matter Item that points to the originating Contact Item. However, if the link column is removed or the Contact Item is deleted, the relationship breaks silently. Teams must treat the link column as a required field and protect it from bulk edits. We validate link integrity post-migration and surface any orphaned Matter Items.

  • Monday CRM's Status column is a UI label, not a structured pick-list with API-readable stage values

    Case UI stores matter status as a structured pick-list value that can be queried by API. Monday CRM's Status column uses human-readable labels (Open, In Progress, Closed) that are not machine-readable in the same way — automations reference the label string, and renaming a status label in the board settings breaks all automations that reference it. We store the original Case UI status value in a parallel Text column (Legacy_Status__c) alongside the Monday Status column so reporting remains accurate even if the Monday label changes. This dual-column approach is delivered as part of the migration schema.

  • Document re-upload is throttled by Monday CRM's file ingestion and plan-tier storage limits

    Case UI documents must be downloaded and re-uploaded to Monday CRM as Monday Files. Monday CRM enforces a 25MB per-file limit and account-level storage caps per plan tier. Large PDF briefs, multi-page exhibits, or image-heavy document sets can exceed these limits. We split oversized files, flag any that cannot be uploaded, and deliver them as a separate ZIP archive with a reference column pointing to the archive location. Storage overages on the monday.com account are a post-migration billing consideration — we document the total migrated file volume before migration begins.

  • Monday CRM API rate limits can extend migration timelines for high-volume matter archives

    Monday CRM's daily call limits (1,000 on Basic/Standard, 10,000 on Pro) constrain how fast we can insert Items, update columns, and attach files. For matter archives exceeding 5,000 records with attachments, the API-bound migration clock can stretch beyond 48 hours even on a Pro plan. We address this by using Monday's bulk mutation endpoints where available, batching Items in groups of 50–100 per API call, and applying exponential backoff on COMPLEXITY_BUDGET_EXHAUSTED and IP_RATE_LIMIT_EXCEEDED errors. Enterprise accounts (25,000 daily calls, 250 concurrent) reduce this risk significantly. The migration plan specifies the expected API call count before the project begins.

  • Case UI billing and trust accounting data has no native home in Monday CRM's data model

    Case UI stores trust account balances, client ledger entries, and invoice line items as structured financial records. Monday CRM has no trust accounting, ledger, or invoice-native data model — these must be represented as Number columns and Status labels on Matter Items, which does not constitute financial-record integrity. We migrate the billing data as a reference dataset (Total Billed, Balance Due, Billing Status) but clearly flag in the migration report that actual trust accounting must be handled in a dedicated legal accounting platform post-migration. We do not represent the migrated billing data as authoritative financial records.

Migration approach

Six steps for a successful Case UI to monday CRM data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Case UI logo

Case UI

Source

Strengths

  • Clear per-user pricing with no surprise fees or mandatory add-ons on the Cloud plan.
  • On-Premise perpetual option eliminates per-user billing for firms with many attorneys and staff.
  • Free trial lets firms validate fit before committing to a paid subscription.
  • Daily backups and segregated databases reduce data loss risk for solo practitioners.
  • Straightforward interface purpose-built for small law firm workflows.

Weaknesses

  • No publicly documented API limits third-party integrations and automated migration tooling.
  • Limited public documentation and no verified reviews make independent evaluation difficult.
  • Smaller feature set compared to enterprise legal platforms may not support complex or multi-practice operations.
  • On-Premise version requires firm IT staff to manage upgrades, security, and backups independently.
  • No transparent rate limits or SLA terms published on the website for Cloud customers.
monday CRM logo

monday CRM

Destination

Strengths

  • Board-based UI makes pipeline stages and deal progress visually obvious without training.
  • No-code automation builder requires no developer resources to create lead routing and stage-triggered actions.
  • Flexible column system supports custom CRM fields without schema changes or admin involvement.
  • Integrates natively with Slack, Gmail, Outlook, and Zapier with minimal configuration overhead.
  • Layered product means teams already on monday Work Management can add CRM without migrating existing data.

Weaknesses

  • No native Contacts object separate from Items — contacts are managed inside a CRM module's People feature.
  • Pipeline and deal relationships use a flat item model rather than a relational object model, making complex CRM associations awkward.
  • Automations are plan-gated (250 actions/month on Standard, 25,000 on Pro) and the legacy Recipe system is being deprecated.
  • Customization and advanced views (Chart, Formula, Dependency) are locked behind Pro and Enterprise tiers.
  • Per-seat pricing with non-refundable annual billing creates cost lock-in risk during migration.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Case UI and monday CRM.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Case UI: Not publicly documented.

  • Data volume sensitivity

    B

    Case UI doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Case UI to monday CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Case UI to monday CRM data migrations

Answers to the questions buyers ask most during Case UI to monday CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Case UI to Monday CRM migrations complete in 48–72 hours of clock time for under 10,000 matter records with standard custom fields. Large matter archives exceeding 50,000 records with heavy document sets and multi-board structures extend to 5–10 days, primarily due to Monday CRM API rate limits on the Standard and Pro plans. The planning and schema-design phase typically adds 3–5 business days before the migration run begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Case UI.
Land in monday CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day