Migrate from Core Practice to monday CRM

Monday CRM has no native appointment or clinical entity — appointment data requires a new board structure

Core Practice stores appointments with structured fields (date, time, duration, type, provider, status) in a dedicated Appointments table. Monday CRM has no equivalent entity — appointments must be modeled as Items on a custom Calendar board with date/time columns, and the patient-provider relationship must be rebuilt using Connect Board columns. If your Core Practice setup uses appointment series or recurring appointment rules, Monday's Workflows builder can recreate simple recurrences but complex clinical scheduling logic requires manual reconfiguration. The Calendar board must be designed before data migration begins so column IDs are stable for the relationship wiring step.

Monday API complexity limits throttle bulk migration throughput on Standard and Basic plans

Monday CRM enforces a Complexity Limit per API call that restricts how many nested relationships and column values can be queried or written in a single operation. Teams migrating large Core Practice datasets (25,000+ patients with full appointment and treatment histories) will hit COMPLEXITY_BUDGET_EXHAUSTED errors on Basic (1,000 calls/day) and Standard plans. We batch writes to respect complexity units and stagger calls to stay within the Daily Call Limit, which extends migration clock time. Pro plans (10,000 calls/day) and Enterprise (25,000 calls/day) provide enough throughput for most dental practice migrations without throttling delays.

Insurance provider and claim data require a custom board with no native Monday CRM equivalent

Core Practice maintains insurance provider name, policy number, group number, coverage percentage, and claim status as structured fields on patient records. Monday CRM has no native insurance entity — these fields must be modeled as a separate Insurance board with custom text and number columns, linked back to the patient record via Connect Board. Coverage percentage and deductible amounts must be entered as number columns rather than a specialized insurance field. Practices relying on Core Practice's insurance tracking for claims management will need to rebuild claim status workflows in Monday's Workflows builder after migration.

Monday's board-per-entity model means multi-board relationships must be pre-planned

Core Practice's relational model enforces referential integrity between patients, appointments, treatments, and billing through foreign keys. Monday CRM requires Connect Board columns to replicate these relationships — and each Connect Board column can only link to one other board. If your Core Practice setup uses complex N:N relationships (one appointment linked to multiple providers, or one treatment linked to multiple insurance claims), each additional link requires its own Connect Board column on the relevant board. These must be designed in the Monday workspace before migration begins. FlitStack delivers a board-and-relationship architecture plan before any data moves.

Appointment reminder and recall automations do not migrate — Monday Workflows must be rebuilt

Core Practice appointment reminders, patient recall alerts, and clinical follow-up triggers are platform-defined automations that do not export. Monday CRM's Workflows builder can recreate date-based and status-change-based automations, but the trigger conditions and action logic differ substantially from Core Practice's rule engine. We export your Core Practice automation definitions as a reference document and provide Monday Workflow configuration guidance, but the actual rebuild is a manual step that your Monday admin must complete after go-live. Recurring appointment rules (e.g., 'recall every 6 months after cleaning') cannot be auto-migrated and require manual re-implementation in Monday.