Migrate from BackDocket to monday CRM

BackDocket contacts map to Items in a dedicated Contacts Board. First name, last name, email, phone, address, and firm affiliation become separate columns. A Status column (Lead, Active, Archived) replaces BackDocket's contact state flag. Monday CRM does not enforce AccountId lookups the way relational CRMs do — firm affiliation stores as a Text column or links to a separate Firm Board Item.

BackDocket cases have a rich schema: case number, case type (plaintiff/defense/transactional), assigned attorney, opposing counsel, court venue, filing date, case status, and related claim records. Monday CRM has no native case object. We map each BackDocket case to an Item in a Cases Board, with columns for each BackDocket field. Case type becomes a Dropdown or Status column. Related claim records become Subitems within the Case Item.

BackDocket claims are child records of cases. They carry claim type, claim amount, insurance carrier, adjuster information, and settlement status. Each claim maps to a Subitem on its parent Case Item. The Subitem inherits the parent Case's board and carries its own set of columns for claim-specific fields. Multiple claims on a single case become multiple Subitems under one Item.

BackDocket tasks with a direct case association map to Subitems under the Case Item. Standalone tasks (not linked to a specific case) map to Items in a separate Tasks Board. Each task carries assignee, due date, priority, and description columns. BackDocket's task sequence ordering is preserved as a custom Number column (sequence_order__c) since Monday CRM Subitems have no native ordering field.

BackDocket calendar events (court dates, client meetings, filing deadlines) map to Items in a Calendar Board. Event title, start datetime, end datetime, location, and associated case become columns. A Status column (Scheduled, Completed, Cancelled) replaces BackDocket's event state. Monday CRM's Timeline column type is ideal for multi-day events spanning court proceedings.

BackDocket documents attached to cases are re-uploaded to the Monday CRM Item's Files column. Each document preserves its original filename, upload date, and uploader. Monday CRM's file size limit applies (standard storage plan limits). Documents without a case association are attached to their parent Contact Item. Merge templates from BackDocket are not migratable — we export them as PDF references.

BackDocket intake records capture new client/matter leads: referral source, intake date, initial case type, conflict-check result, and assigned intake attorney. These map to Items in a dedicated Intake Board. A Status column (New, Conflict Check, Approved, Converted to Case) replaces BackDocket's intake workflow stages. Conflict-check notes field migrates as a long-text column.

BackDocket billing records (time entries, expenses, invoice amounts) are aggregated per case and stored as custom numeric columns on the Case Item: total billed hours, total invoiced amount, outstanding balance, and last billing date. Individual line-item records are preserved as a linked table (Separate Board) if the firm requires granular billing history; otherwise they merge into summary columns.

BackDocket owner assignments (assigned attorney, paralegal, intake specialist) map to Monday CRM's Person column type, which allows selecting a workspace member. Unmatched BackDocket users — those no longer active — are flagged before migration and assigned to a fallback owner. BackDocket does not have a role-based access model equivalent to Monday CRM's permission groups.

BackDocket automations — task sequences tied to case stage changes, conflict-check triggers, and document-merge workflows — have no structural equivalent in Monday CRM. FlitStack AI exports BackDocket automation definitions as a structured JSON reference document that maps each BackDocket trigger and action to its nearest Monday CRM automation recipe. Your Monday CRM admin uses this document to rebuild the automations post-migration.