CRM migration

Migrate from MerusCase to monday CRM

Field-level mapping, validation, and rollback between MerusCase and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.

MerusCase logo

MerusCase

Source

monday CRM

Destination

monday CRM logo

Compatibility

90%

9 of 10

objects map 1:1 between MerusCase and monday CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

MerusCase organizes legal practice data around case files: contacts (parties), companies (opposing counsel, insurers), case activities (filings, hearings), time ledger entries (billable hours with UTBMS codes), and custom fields scoped per case type. Monday CRM uses a board-and-column model where every record is an Item, columns define field types, and Groups segment records by status or category. There is no native legal billing, case ledger, or UTBMS coding structure in Monday CRM — those become custom column types that your team rebuilds after migration. FlitStack AI extracts MerusCase data via its API and CSV exports, then loads it into Monday's Items using the monday.com GraphQL API with bulk operations respecting per-plan rate limits (1,000 calls/day on Basic/Standard, 10,000 on Pro, 25,000 on Enterprise). We map cases to a Cases board, parties to a Contacts board, and create custom columns for currency, date, numeric, and yes/no fields that MerusCase supports up to 50 of per firm. Workflows, automations, document templates, and case-type-specific tabs from MerusCase do not transfer — we export definitions as rebuild reference files for your Monday admin.

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

MerusCase logo

MerusCase

What's pushing teams away

  • Annual subscription required — payments must be made annually in advance unless a separate Order Form is negotiated.
  • Per-case Document Archive is the primary data export path; there is no one-click full firm data dump, making migrations out manual and time-consuming.
  • Credit card payments incur a 3% transaction fee plus variable network fees deducted monthly, adding cost for high-volume billing firms.
  • Third-party migrations (moving away from MerusCase) are not supported by MerusCase's own migration team — the firm must handle or hire independently.
  • Built-in CSV import tools are documented as not easy to use, pushing firms toward paid white-glove onboarding for any data loading.

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 MerusCase objects map to monday CRM

Each row shows how a MerusCase 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.

MerusCase

Case

maps to

monday CRM

Item (Cases Board)

1:1
Fully supported

MerusCase case files map 1:1 to Monday Items in a Cases board. Each case becomes an Item; the case name becomes the Item name. Case status (Open, Closed, Pending) maps to a Status column. Case number becomes a text column. All other case properties map to custom columns by type.

MerusCase

Contact (Party)

maps to

monday CRM

Item (Contacts Board)

1:1
Fully supported

MerusCase parties (plaintiffs, defendants, witnesses) map to Monday Items in a Contacts board. Each party is an Item with name, phone, email, address columns. Party role (Plaintiff, Defendant, Witness) maps to a Labels column so boards can filter by party type. Multiple parties per case use Subitems linked to the parent case Item.

MerusCase

Company (Opposing Counsel, Insurer)

maps to

monday CRM

Item (Companies Board)

1:1
Fully supported

MerusCase companies associated with cases map to Monday Items in a Companies board. Company name becomes Item name. Contact name and phone for opposing counsel or insurance adjuster map to text and phone columns. Law firm vs. insurance company distinction uses a Labels column.

MerusCase

Activity (Filing, Hearing, Meeting)

maps to

monday CRM

Item (Activities Sub-board or Subitems)

1:1
Fully supported

MerusCase activities attached to cases map to Monday Subitems under the parent case Item. Activity type (Filing, Hearing, Telephone Call) becomes a Labels column value. Activity date maps to a Date column. Activity description maps to a Text column. For high-volume activity histories, a separate Activities board with a Link to Item column connects back to the parent case.

MerusCase

Case Ledger (Billable Time)

maps to

monday CRM

Custom Columns on Case Item

1:1
Fully supported

MerusCase time entries with UTBMS L-Codes and A-Codes (task and activity codes) become Numeric columns on the case Item. Total billable hours accumulate in a Numbers column; individual line items with descriptions, dates, and UTBMS codes are preserved as JSON in a Long Text column for rebuild reference. Monday's native time-tracking integration is a separate product; the migration preserves the data so your team can set up the integration post-migration.

MerusCase

Settlement / Damages

maps to

monday CRM

Custom Board (Settlements)

1:1
Fully supported

MerusCase settlement records and damages figures map to a dedicated Settlements board linked to the parent Cases board via a Connect Boards column. Settlement amount becomes a Currency column; damages breakdown (economic, non-economic, punitive) uses Numbers columns. Settlement status (Negotiating, Executed, Appeal) maps to a Status column.

MerusCase

Custom Fields (Date, Currency, Numeric, Text, Yes/No)

maps to

monday CRM

Monday Column Types

1:1
Fully supported

MerusCase custom fields map by type to Monday column types: Date fields → Date column; Currency → Currency column (displays with $ symbol); Numeric → Numbers column; Text (up to 250 chars) → Text column; Yes/No → Checkbox column. Firms with 30–50 custom fields need multiple boards to avoid column clutter; we partition by case type and document the column layout in the migration plan.

MerusCase

Document Archive

maps to

monday CRM

Monday Files (attached to Items)

1:1
Fully supported

MerusCase document archives (zipped PDFs and case-related files) are re-uploaded to Monday as file attachments on the corresponding case Item. The original file names are preserved. Monday's 250MB file size limit applies; larger files are flagged for manual download reference. File timestamps from MerusCase are noted in the Item's Last Updated column.

MerusCase

Case Type (Personal Injury, Criminal, Immigration, etc.)

maps to

monday CRM

Separate Boards per Case Type

1:many
Fully supported

MerusCase case types determine the board destination in Monday. Immigration cases route to an Immigration Board; personal injury to a PI Board. Each board has type-specific columns (e.g., immigration board has Visa Type, Expiration Date columns). The Case Type value from MerusCase is preserved as a Labels column on the master Cases board for cross-type reporting.

MerusCase

Workflow Rules

maps to

monday CRM

Monday Automations (rebuild required)

1:1
Fully supported

MerusCase workflows triggered by Activity Tags or description text have no direct Monday equivalent. Monday automations use When-Then pairs scoped to board-level changes. We export your MerusCase workflow definitions (triggers, actions, assigned users) as a JSON reference file your Monday admin uses to rebuild automations post-migration. The migration itself does not transfer workflow logic.

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.

MerusCase logo

MerusCase gotchas

High

Annual subscription and data access tied together

High

Outbound migration is not supported by MerusCase

High

Document Archive exports are per-case, not bulk

Medium

Built-in CSV import tools are not easy to use

Medium

Custom Fields apply to Cases only and have a 50-field cap

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

  • MerusCase case-type tabs require board partitioning in Monday CRM

    MerusCase surfaces different field tabs per case type (Personal Injury shows Insurance fields; Immigration shows Visa fields; Criminal shows Bond fields). Monday CRM has no native case-type tab concept — all columns are visible on every Item in a board. We partition by case type: each MerusCase case type gets its own Monday board with type-specific columns. If you have 5 case types, you get 5 boards. Firms with more than 8 case types may find column proliferation on a master Cases board unmanageable; we recommend a hub-and-spoke model with a master Cases board linking to type-specific boards via Connect Boards columns.

  • MerusCase UTBMS time-coding has no native Monday equivalent

    MerusCase time ledger entries carry 4-character UTBMS L-Codes (task codes) and A-Codes (activity codes) that legal billing requires for court reporting and fee agreements. Monday CRM has no native UTBMS field — time tracking uses plain hours or integrates with a third-party app. We preserve every UTBMS code in a Long Text column on the case Item as a rebuild reference. Your Monday admin must decide: rebuild time entries with codes in a third-party time-tracking integration (Harvest, Toggl), or accept that new time entries post-migration lack UTBMS coding unless a custom Monday integration is built.

  • Monday API rate limits restrict bulk migration speed

    Monday GraphQL API enforces complexity limits, daily call limits (1,000/day on Standard, 10,000/day on Pro), and concurrency limits (40 concurrent on Standard, 100 on Pro). Large MerusCase exports with 20,000+ activities can hit daily limit walls mid-migration, requiring overnight pauses. We throttle requests to stay under limits and batch by 100 Items per mutation call. Firms on Enterprise can request limit increases; Basic-plan accounts (200 API calls/day) are not viable for bulk migration without manual batching. We flag plan tier mismatches before migration starts.

  • MerusCase document archives require manual re-upload to Monday

    MerusCase Document Archives download as a zip containing all case files and a CSV of case activities. Monday does not accept zip imports — each file must be attached individually to the corresponding Item via the Monday UI or API. We extract the archive, match files to case Items by filename patterns, and re-upload via the monday.com API using the file.upload endpoint. Files larger than 250MB are flagged for manual handling. The original file timestamps are noted in a Text column on the Item so your team can verify completeness after re-upload.

  • MerusCase workflows cannot be migrated to Monday automations

    MerusCase workflow rules trigger when an Activity Tag or description text matches a rule, then create tasks, events, or assignments for firm staff. Monday automations use When-Then trigger-action pairs scoped to board changes — there is no description-matching trigger, no activity-tag trigger, and no direct equivalent to MerusCase's statute-driven deadlines. We export your MerusCase workflow definitions as a JSON reference file documenting trigger conditions, actions, and assigned users. Your Monday admin uses this to rebuild automations using Monday's native triggers (When Status Changes, When Date Arrives, When Item Created). The migration does not transfer any workflow logic automatically.

Migration approach

Six steps for a successful MerusCase to monday CRM data migration

  1. Audit MerusCase data structure and export data

    FlitStack AI connects to your MerusCase account via API credentials and reviews your case type configuration, custom field count, and activity volume. We request a Document Archive export (zip of case files + activity CSV) and pull time ledger entries via the caseLedgers endpoint. We also export custom field definitions, user list, and workflow rules. This audit produces a data inventory listing record counts per case type, total activities, total ledger entries, and file attachment counts. Your team reviews the inventory and confirms which historical cases to migrate (typically last 2–5 years depending on practice needs).

  2. Design Monday board structure and column schema

    Based on the MerusCase data audit, FlitStack AI designs the Monday board hierarchy: a master Cases board with Connect Boards columns linking to type-specific boards (PI Board, Immigration Board, Criminal Board, etc.). We map each MerusCase custom field to its Monday column type and document the column layout per board. The schema plan includes UTBMS reference columns for time entries, Labels columns for party role and case status, and Date columns for filing/hearing/SOL dates. Your Monday admin approves the board structure before data moves.

  3. Migrate contacts and companies first

    Monday requires parent records to exist before Subitems link to them. We migrate Contacts and Companies first — each becomes an Item in their respective board. For contacts who appear in multiple cases (e.g., a plaintiff in three cases), we create one contact Item and link it via Subitems to each case Item. Company Items for opposing counsel and insurers are created next. Email addresses are validated for duplicates; matches are consolidated into a single Item with a note listing all associated cases.

  4. Migrate cases with mapped columns and time ledger entries

    Cases are created as Items in the appropriate type-specific board with all mapped columns populated (case number, court, filing date, lead attorney). Time ledger entries for each case are aggregated: total billable hours populate a Numbers column; UTBMS codes populate a Long Text reference column. If your firm has a separate Settlements board, settlement Items are created and linked to parent case Items via Connect Boards. All custom field values (currency, date, numeric, yes/no) populate their corresponding Monday column types.

  5. Re-upload documents and run field-level diff

    We extract the MerusCase Document Archive, match files to case Items by filename and date patterns, and upload files via the monday.com file.upload API. Files over 250MB are flagged for manual upload. After all data lands, we run a field-level diff comparing source MerusCase records against Monday Items — checking that custom field values, dates, currency amounts, and party links match the source. Discrepancies are corrected before the delta window opens. Your team reviews a sample of 50–100 cases and confirms the diff is acceptable.

  6. Delta window and workflow export handoff

    A delta-pickup window (24–48 hours) captures any cases, contacts, or activities modified in MerusCase during the cutover period. Your team continues working in MerusCase during this window; FlitStack AI applies a second pass to sync changes to Monday. After delta closes, we deliver the MerusCase workflow definitions as a JSON export and a rebuild guide for your Monday admin. The guide maps MerusCase Activity Tags to Monday automation triggers and documents which workflows require manual rebuild. Audit log and rollback plan are provided; rollback reverts Monday to pre-migration state if reconciliation fails.

Platform deep dives

Context on both ends of the pair

MerusCase logo

MerusCase

Source

Strengths

  • Fully HIPAA-compliant cloud platform with bank-grade encryption across all stored firm data.
  • Integrated billing ledger with UTBMS task, activity, and expense code support out of the box.
  • Document automation, batch scanning, and EAMS integration built into the core platform.
  • Dedicated migration coordinator assigned to each firm transitioning from another system.
  • Monthly product updates with new features and refinements across case types.

Weaknesses

  • Annual subscription model requires prepayment; no month-to-month flexibility for smaller firms.
  • Primary data export is per-case Document Archive — no single full-firm export without contacting support and paying a manual processing fee.
  • MerusCase's own migration team only supports inbound migrations, not outbound.
  • Built-in CSV import tools are explicitly documented as not easy to use, requiring white-glove service for most data loading tasks.
  • Workflows and Statutes cannot be exported or migrated programmatically — they are platform-native and must be rebuilt from scratch.
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. 1 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 MerusCase and monday CRM.

  • Object compatibility

    B

    1 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

    MerusCase: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your MerusCase 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 MerusCase to monday CRM data migrations

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

Can't find your answer?

Walk through your MerusCase to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most MerusCase-to-Monday migrations complete in 48–72 hours for firms with under 10,000 records and a single practice area. Firms with multiple case types, 30+ custom fields, or historical time ledger entries spanning years extend to 5–10 days. The longest phase is designing the Monday board and column schema to match your MerusCase case types — that planning step runs before any data moves and typically takes 3–5 business days depending on your team's availability for schema approval.

Adjacent paths

Related migrations to explore

Ready when you are

Move from MerusCase.
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