CRM migration
Field-level mapping, validation, and rollback between MerusCase and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
MerusCase
Source
monday CRM
Destination
Compatibility
9 of 10
objects map 1:1 between MerusCase and monday CRM.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
monday CRM
Item (Cases Board)
1:1MerusCase 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)
monday CRM
Item (Contacts Board)
1:1MerusCase 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)
monday CRM
Item (Companies Board)
1:1MerusCase 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)
monday CRM
Item (Activities Sub-board or Subitems)
1:1MerusCase 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)
monday CRM
Custom Columns on Case Item
1:1MerusCase 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
monday CRM
Custom Board (Settlements)
1:1MerusCase 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)
monday CRM
Monday Column Types
1:1MerusCase 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
monday CRM
Monday Files (attached to Items)
1:1MerusCase 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.)
monday CRM
Separate Boards per Case Type
1:manyMerusCase 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
monday CRM
Monday Automations (rebuild required)
1:1MerusCase 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.
| MerusCase | monday CRM | Compatibility | |
|---|---|---|---|
| Case | Item (Cases Board)1:1 | Fully supported | |
| Contact (Party) | Item (Contacts Board)1:1 | Fully supported | |
| Company (Opposing Counsel, Insurer) | Item (Companies Board)1:1 | Fully supported | |
| Activity (Filing, Hearing, Meeting) | Item (Activities Sub-board or Subitems)1:1 | Fully supported | |
| Case Ledger (Billable Time) | Custom Columns on Case Item1:1 | Fully supported | |
| Settlement / Damages | Custom Board (Settlements)1:1 | Fully supported | |
| Custom Fields (Date, Currency, Numeric, Text, Yes/No) | Monday Column Types1:1 | Fully supported | |
| Document Archive | Monday Files (attached to Items)1:1 | Fully supported | |
| Case Type (Personal Injury, Criminal, Immigration, etc.) | Separate Boards per Case Type1:many | Fully supported | |
| Workflow Rules | Monday Automations (rebuild required)1: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.
MerusCase gotchas
Annual subscription and data access tied together
Outbound migration is not supported by MerusCase
Document Archive exports are per-case, not bulk
Built-in CSV import tools are not easy to use
Custom Fields apply to Cases only and have a 50-field cap
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 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).
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.
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.
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.
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.
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
MerusCase
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 MerusCase and monday CRM.
Object compatibility
1 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
MerusCase: Not publicly documented.
Data volume sensitivity
MerusCase 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 MerusCase to monday CRM migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave MerusCase
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.