Migrate from The Plaintiff to monday CRM

Each The Plaintiff Case record maps to one Monday CRM Item in a dedicated 'Cases' board. Monday requires the board to be created first; Items are then ingested via the GraphQL API with column values mapped from The Plaintiff field names. Case ID from The Plaintiff is stored as a custom column (Source_ID__c equivalent) for traceability and delta-run de-duplication.

The Plaintiff stores attorney names and contact information within the Case record or as related Contact objects. We split this into a Monday Contacts board (one Item per attorney with Name, Email, Bar_Number__c, Firm__c columns) and a Person column on the Cases board linking each case to its assigned attorney. The Person column resolves attorney email matches to Monday user accounts automatically.

Courts and opposing counsel contacts that The Plaintiff stores as related records map to Items in a separate Monday board (e.g., 'Courts & Counsel'). Each court is an Item with Name, Address, Judge_Name__c, and Calendar_Link__c as custom columns. We preserve the court-to-case relationship by adding a Link to Item column on the Cases board so attorneys can jump from a case to the court record without leaving Monday.

The Plaintiff's case-status pick-list values (e.g., Active, Pending_Discovery, Awaiting_Trial, Settled, Closed) map to Monday's Status column options. Each The Plaintiff status value is re-created as a matching colored Status pill in Monday. We also add a Text column capturing the historical status label in case teams use color-coded boards for triage-level sorting.

The Plaintiff attachments (pleadings, contracts, medical records) stored against a case are downloaded and re-uploaded as Monday Files attached to the corresponding Item. File size limits on Monday CRM (25 MB per file) are enforced during ingestion; files exceeding this threshold are flagged and linked via URL reference in a Text column pointing to the source location.

The Plaintiff's activity log entries (status changes, attorney notes, court appearances) that form the case narrative have no direct Monday equivalent. We map them to a dedicated 'Case Activity' board where each update becomes a Subitem or an Item linked to the parent Case Item, with columns for Date, Actor, Update_Type, and Notes. This preserves the chronological case history in a searchable structure.

The Plaintiff's custom legal fields — Statute_of_Limitations__c, Insurance_Carrier__c, Adjuster_Name__c, Policy_Number__c, Jurisdiction__c, Judge_Assigned__c — have no Monday CRM native equivalent. We create custom columns (Date, Text, Text, Text, Location, Person respectively) on the Cases board for each. Pick-list values for fields like Jurisdiction__c require manual re-entry in Monday's column settings post-migration.

The Plaintiff's owner/assigned-attorney field resolves to Monday user accounts via email match. Unmatched attorneys (no Monday user account) are flagged in the pre-migration audit — firms either create Monday accounts for them or assign orphaned cases to a fallback attorney in Monday before the migration run. No case lands without an owner.

For The Plaintiff instances with no accessible API, FlitStack exports via admin CSV export (up to 24-hour turnaround for large accounts per Monday's account-export documentation) and ingests via Monday's bulk import or GraphQL API. We validate row counts and column coverage against the source CSV before committing to the Monday workspace.

The Plaintiff's automation rules (e.g., 'when case status = Awaiting_Trial, assign to senior partner') do not map to any Monday CRM object. We export the rule definitions as a reference document for the firm's Monday admin to rebuild using Monday's automation recipes. This is disclosed upfront so firms budget admin time for post-migration workflow setup.