CRM migration
Field-level mapping, validation, and rollback between MyCase and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
MyCase
Source
monday CRM
Destination
Compatibility
11 of 11
objects map 1:1 between MyCase and monday CRM.
Complexity
BStandard
Timeline
3–5 business days
Overview
MyCase organizes legal practice data around Cases/Matters — a single object that bundles client, opposing counsel, case type, status, dates, billing, and documents in one record. Monday CRM has no native legal matter object; it models all data as items inside customizable boards, where each column functions as a field. The migration therefore translates MyCase's flat matter structure into a multi-board Monday workspace: contacts and companies land as Person and Organization items, case-matters become a dedicated custom board with columns mirroring MyCase case fields, tasks map as subitems, and time entries become custom subitem rows. We extract data from MyCase via the MyCase API (25 requests per second, Advanced tier required for full API access) and write into Monday via the monday.com GraphQL API subject to plan-tier rate limits (1,000 calls per day on Basic/Standard, 10,000 on Pro). MyCase workflows, automations, and billing logic have no Monday CRM equivalent and must be exported as reference documentation and rebuilt manually. Document files migrate to Monday's file columns or attachments, subject to plan-tier storage limits (5 GB Standard, 100 GB Pro). The migration runs in a sequenced, dependency-aware order — contacts and companies first, then cases as parent items, then tasks and time entries as subitems — with a delta-pickup window capturing any records modified during cutover.
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 MyCase 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.
MyCase
Contact
monday CRM
Person (Contacts board)
1:1MyCase contacts map directly to Monday Person items in a dedicated Contacts board. Each contact's name, email, phone, address, and custom properties become Monday columns. Primary company is stored as a connected board link to the Companies board. During migration, we preserve the original created date and source system ID for traceability and delta-run synchronization.
MyCase
Company
monday CRM
Organization (Companies board)
1:1MyCase companies map to Monday Organization items. Company name, domain, address, industry, and employee count become Monday columns. Multi-contact associations from MyCase collapse to a primary contact link plus secondary contact subitems. We also preserve the original MyCase company ID as a custom column for cross-reference and to support future delta synchronizations between the systems.
MyCase
Case / Matter
monday CRM
Item (Matters board — custom board)
1:1MyCase case-matters have no direct Monday CRM equivalent. Each matter migrates as an item in a dedicated custom board. Case number, status, type, responsible attorney, opposing counsel, court, case type, open date, and close date become Monday columns. A board-level connection links the matter to its client contact item.
MyCase
Task / To-Do
monday CRM
Subitem (under Matter item)
1:1MyCase tasks associated with a matter migrate as subitems under the corresponding Matter item in Monday. Task title, due date, priority, assigned user, status, and description map to subitem columns. Orphan tasks without a parent matter land in a separate Tasks board.
MyCase
Time Entry
monday CRM
Subitem (Time Entries sub-board or custom column)
1:1MyCase time entries map to a dedicated sub-board or subitem rows under each Matter item. Entry date, duration, billing rate, description, and invoiced status map to Monday columns. Since Monday has no native billing engine, time entries are preserved as historical data; the billing workflow must be rebuilt in Monday or handled externally.
MyCase
Document / File
monday CRM
File column / Attachment
1:1MyCase documents stored in MyCase Drive migrate as file attachments on the corresponding Matter item in Monday. Each document's name, upload date, and uploader are preserved. Monday's plan-tier storage limits apply — Standard has 5 GB total account storage; Pro has 100 GB.
MyCase
Activity / Note
monday CRM
Update / Note column
1:1MyCase activity log entries (calls, emails, notes, meetings) attached to a matter become Monday updates or note column entries on the Matter item. Original timestamp, user, and activity type are preserved in the update metadata. This allows your team to review the full communication history within Monday's activity feed for each matter.
MyCase
Custom Field
monday CRM
Column (custom column type)
1:1MyCase custom fields on contacts, companies, and cases require Monday column types. Where a direct Monday column type exists (date, number, text, person, status, checkbox), it is created automatically. Fields using MyCase formula logic or unsupported types are stored as text columns and flagged for manual verification post-migration.
MyCase
User / Owner
monday CRM
Person (Team Members)
1:1MyCase firm users are matched to Monday team members by email address. A person item is created in the Contacts board for each matched user, and the MyCase Owner ID maps to Monday's Assigned To column. Unmatched owners are flagged before migration — the firm either creates their Monday account first or reassigns records to a fallback user.
MyCase
Workflow / Automation
monday CRM
No equivalent
1:1MyCase workflows, task templates, and automations tied to matter lifecycle stages do not have a Monday CRM equivalent. We export the workflow definitions as a structured reference document for the firm's Monday admin to rebuild using Monday's automation recipes. This step is always manual.
MyCase
Billing / Invoice
monday CRM
No equivalent (preserve as reference data)
1:1MyCase invoices, trust account entries, and IOLTA records have no native Monday CRM equivalent. We preserve invoice and payment history as custom subitem rows on Matter items and flag the full billing workflow as requiring an external tool or Monday's optional invoice module setup post-migration.
| MyCase | monday CRM | Compatibility | |
|---|---|---|---|
| Contact | Person (Contacts board)1:1 | Fully supported | |
| Company | Organization (Companies board)1:1 | Fully supported | |
| Case / Matter | Item (Matters board — custom board)1:1 | Fully supported | |
| Task / To-Do | Subitem (under Matter item)1:1 | Fully supported | |
| Time Entry | Subitem (Time Entries sub-board or custom column)1:1 | Fully supported | |
| Document / File | File column / Attachment1:1 | Fully supported | |
| Activity / Note | Update / Note column1:1 | Fully supported | |
| Custom Field | Column (custom column type)1:1 | Fully supported | |
| User / Owner | Person (Team Members)1:1 | Fully supported | |
| Workflow / Automation | No equivalent1:1 | Fully supported | |
| Billing / Invoice | No equivalent (preserve as reference data)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.
MyCase gotchas
QuickBooks sync is strictly one-directional
Advanced API access is tier-gated
Document migration requires offline file transfer
Bulk rate updates on historical time entries are not supported
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
Discover and audit MyCase data model
We connect to MyCase via API (Advanced tier required for full export) and extract all contacts, companies, case-matters, tasks, time entries, documents, custom fields, and user records. We audit record counts, data quality (duplicate detection, blank required fields), and identify any billing-related fields. This phase produces the migration scope document that defines board structure, column types, and migration sequencing before any data moves.
Design Monday workspace and column mapping plan
We create the Monday workspace structure: a Contacts board, a Companies board, and a custom Matters board with columns mapped from MyCase case-matters. Each custom field is mapped to a Monday column type — direct mappings are created automatically; unsupported types become Text columns with a flag for post-migration column-type upgrade. MyCase users are mapped to Monday team members by email; unmatched users are flagged for your team to resolve before migration.
Run sample migration with field-level diff
A representative slice of 50–100 records — spanning contacts, companies, matters across different case types, and a mix of custom field types — migrates first. We generate a field-level diff comparing source values against Monday item values so your team can verify case-status mapping, attorney owner resolution, and custom field preservation before the full run commits. Issues discovered here are corrected in the mapping plan before the full migration.
Execute full migration with delta-pickup window
The full dataset migrates into the Monday workspace in dependency-aware sequence: contacts and companies first, then matters as parent items, then tasks and time entries as subitems. A delta-pickup window (24–48 hours) captures any new or modified MyCase records created during the cutover window. Documents are uploaded to Monday file columns or as item attachments. Workflow definitions are exported as a structured reference document for your Monday admin to rebuild.
Validate, deliver audit log, and confirm go-live readiness
We generate a post-migration audit report: record counts by object, field completeness percentages, any unmapped or flagged fields, and storage usage against Monday plan limits. We walk through the report with your firm, confirm all ownership assignments, and verify that the flagged custom column types have been upgraded. One-click rollback remains available for 48 hours after migration completion if reconciliation reveals unexpected gaps.
Platform deep dives
MyCase
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 MyCase 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
MyCase: 25 requests per second per client.
Data volume sensitivity
MyCase 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 MyCase to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your MyCase 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 MyCase
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.