CRM migration
Field-level mapping, validation, and rollback between Open Dental and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Open Dental
Source
monday CRM
Destination
Compatibility
11 of 11
objects map 1:1 between Open Dental and monday CRM.
Complexity
BStandard
Timeline
5–7 business days
Overview
Open Dental and Monday CRM solve fundamentally different problems: Open Dental is a patient-centric clinical database built for procedure tracking, insurance billing, and recall management inside a dental practice. Monday CRM is a board-item work management platform that organizes leads, deals, and tasks in columns and groups. The migration carries over patient contact data, appointment history, recall schedules, custom fields, and document references. Clinical procedures, insurance claims, and billing ledger entries have no direct Monday CRM equivalent and are surfaced as reference records for your team to consult after go-live. FlitStack AI reads Open Dental's MySQL database directly via API using read-only credentials, maps patient records to Monday Contacts, appointment data to Board items organized by date, and insurance plans to separate linked items. Custom patient fields (recall intervals, coverage percentages, pick-list values) are created as Monday columns using type-aware mapping. Monday CRM's lack of HIPAA compliance means clinical PHI review is required before migration; we handle this by isolating clinical fields into a dedicated board with restricted access.
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 Open Dental 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.
Open Dental
Patient
monday CRM
Contact (Monday CRM Contacts section)
1:1Open Dental patient records migrate to Monday CRM Contacts. Fields including name, phone, email, address, and birthdate map directly. Patients without email addresses are flagged for manual email assignment before migration because Monday uses email as the unique contact identifier. Original Open Dental PatNum is stored in a custom column for traceability.
Open Dental
Appointment
monday CRM
Board Item (Patient Appointments board)
1:1Open Dental appointments become items inside date-grouped boards in Monday CRM. Each item stores appointment date, time, provider, operatory, and type in columns. Status is determined by the appointment's recall_status field in Open Dental: Completed → Done group, Future → respective date group, Broken → Archive group. Monday boards do not natively support appointment scheduling — this is a reference board, not a calendar replacement.
Open Dental
Company / Referrals
monday CRM
Contact or Board Item (Referral Partners board)
1:1Open Dental referral sources (other dental practices or doctors who refer patients) migrate as either Monday CRM Contacts or as items on a dedicated Referral Partners board depending on whether you want referral tracking separated from patient records. The referral doctor name and contact info map to the standard name, phone, and email fields.
Open Dental
Document / Patient Image
monday CRM
Board Item with File Attachment (Patient Documents board)
1:1Open Dental stores documents and patient images in the OpenDentImages folder, with references in the document table (DocNum, DocCategory, FileName). Documents migrate as Monday board items with the file re-uploaded as a Monday attachment. The DocCategory maps to a Monday column so you can filter by document type. Note: image conversions incur a separate fee from Open Dental and must be completed before migration.
Open Dental
PatField (Custom Patient Fields)
monday CRM
Monday Column (on patient Contact record)
1:1Open Dental custom patient fields (PatFieldDefs) store data tied to the field name with field types: Text, Date, Checkbox, Currency, PickList. Each PatField type maps to the equivalent Monday column type. Date fields become Date columns, currency becomes Number columns, and pick-lists become Dropdown columns with values preserved. If the field name in Open Dental has changed, both old and new names are preserved — the data is not lost but requires Monday-side cleanup.
Open Dental
Provider
monday CRM
Monday Team Member
1:1Open Dental providers (FName + LName) migrate to Monday CRM as team members who can be assigned to patient items and appointment items. Unmatched providers are flagged before migration — your team either creates the Monday user first or assigns their records to a fallback team member. Provider specialty and notes map to a Text column on the provider's profile.
Open Dental
InsPlan (Insurance Plan)
monday CRM
Board Item (Insurance Plans board) + Link
1:1Open Dental insurance plans store carrier name, group number, subscriber ID, and coverage percentages per procedure category. Since Monday CRM has no native insurance object, plans migrate as separate items on an Insurance Plans board. Each plan is then linked to the patient contact via a Link to Item column on the patient record. This preserves the N:1 patient-to-plan relationship and allows filtering by carrier or plan type.
Open Dental
Payment / PayPlan
monday CRM
Board Item with Subitem (Patient Billing board)
1:1Open Dental payments (PayNum, PayAmt, PayType) and payment plans (PayPlanNum) migrate as subitems on patient items. The payment amount and date are stored in Number and Date columns. Payment plan amortization schedules are not reconstructed — the current balance and next payment due date are captured as reference fields. Monday's deal tracking is not designed for dental billing; this data is migrated for historical reference, not for use as an active billing tool.
Open Dental
Recall
monday CRM
Date Column (on patient Contact record)
1:1Open Dental recall intervals generate automated patient reminders for hygiene, perio maintenance, and general recall. These intervals and next-due dates migrate as custom Date columns on the patient Contact in Monday CRM. Because Monday has no native recall scheduler, these date columns serve as the trigger for manually configured board automations that send reminders. The automation logic from Open Dental is exported as a reference document for your team to rebuild in Monday.
Open Dental
ProcedureLog / TreatmentPlan
monday CRM
Board Item with Subitem (Treatment Plans board)
1:1Open Dental procedure codes (CDT D####), tooth surfaces, surfaces treated, and treatment plan status have no equivalent in Monday CRM's data model. These records migrate as text-reference items on a Treatment Plans board — the procedure description, code, and status are readable, but Monday cannot drive clinical workflows from this data. This board is for reference only; clinical treatment planning remains in Open Dental.
Open Dental
Claim / ClaimProc
monday CRM
No equivalent
1:1Open Dental insurance claim tracking (ClaimNum, ClaimStatus, InsPayAmt, Writeoff) has no Monday CRM equivalent. Claims data is not migrated as operational records. If your team needs claim status reference, we can export this data as a CSV file for offline use.
| Open Dental | monday CRM | Compatibility | |
|---|---|---|---|
| Patient | Contact (Monday CRM Contacts section)1:1 | Fully supported | |
| Appointment | Board Item (Patient Appointments board)1:1 | Fully supported | |
| Company / Referrals | Contact or Board Item (Referral Partners board)1:1 | Fully supported | |
| Document / Patient Image | Board Item with File Attachment (Patient Documents board)1:1 | Fully supported | |
| PatField (Custom Patient Fields) | Monday Column (on patient Contact record)1:1 | Fully supported | |
| Provider | Monday Team Member1:1 | Fully supported | |
| InsPlan (Insurance Plan) | Board Item (Insurance Plans board) + Link1:1 | Fully supported | |
| Payment / PayPlan | Board Item with Subitem (Patient Billing board)1:1 | Fully supported | |
| Recall | Date Column (on patient Contact record)1:1 | Fully supported | |
| ProcedureLog / TreatmentPlan | Board Item with Subitem (Treatment Plans board)1:1 | Fully supported | |
| Claim / ClaimProc | No equivalent1: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.
Open Dental gotchas
X-ray images do not migrate between systems
Scanned documents require a separate image conversion with additional cost
Server must run MySQL with myISAM engine, not InnoDB
API pagination is limited to 100 records per request
Custom sheets use proprietary XML that only imports to Open Dental
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 Open Dental schema and Monday CRM workspace structure
FlitStack AI connects to your Open Dental database via read-only API credentials and inventories the patient table, custom field definitions (PatFieldDefs), appointment types, provider list, insurance plan structure, and document references. In parallel, we audit your target Monday CRM workspace and configure the column types required for the migration: Date columns for recall dates, Number columns for coverage percentages, Dropdown columns for insurance status and appointment types, and Link to Item columns for insurance-to-patient relationships. This step generates a schema setup plan delivered to you before any data moves.
Map Open Dental custom fields and family relationships
Open Dental's PatFieldDefs are read and mapped to Monday column types: text fields → text columns, date fields → date columns, currency → number columns, pick-lists → dropdown columns with exact option values. Family guarantor relationships (Open Dental's Guarantor field) are resolved and stored in a Family_Guarantor__c custom text column. Patients without email addresses are flagged — your team assigns emails before migration because Monday uses email as the unique contact identifier. All mapping decisions are documented in a field-level diff delivered to you for approval.
Migrate patient contacts and appointment items
Patient records are imported into Monday CRM Contacts using the name, phone, email, address, and birthdate fields. The Open Dental PatNum is stored in a custom OpenDental_PatNum__c column for traceability. Appointment data is pulled in date order and created as items on the Patient Appointments board, organized into groups by month. Each appointment item stores the provider (assigned to the Monday team member), operatory, appointment type, status, and duration. Completed appointments are placed in a Done group; broken appointments are archived. The migration reads appointments in batches of 100, respecting Monday's daily API call limits.
Migrate insurance plans, documents, and billing references
Insurance plans are created as items on a dedicated Insurance Plans board, with carrier name, group number, subscriber ID, and coverage percentages in columns. Each plan is linked to the corresponding patient contact via a Link to Item column. Documents and patient images are re-uploaded to Monday and attached to the relevant patient item — the DocCategory field maps to a Monday Dropdown column so documents can be filtered by type. Payment history is added as subitems on patient items with amount, date, and payment type. All of this is delivered as a test migration to a non-production Monday workspace for your team to verify before the full run.
Run test migration, delta pickup, and go-live
A representative sample (100–500 records) migrates first to a test workspace, and FlitStack generates a field-level diff between the Open Dental source values and the Monday CRM target values. You verify recall date accuracy, insurance link connectivity, and appointment group placement before approving the full run. The full migration executes during a low-activity window. A delta-pickup window of 24–48 hours captures any new patients or updated appointments created in Open Dental during the cutover. FlitStack delivers an audit log of all operations and a rollback snapshot if reconciliation uncovers unexpected gaps.
Platform deep dives
Open Dental
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Open Dental and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Open Dental and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Open Dental and monday CRM.
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
Open Dental: Remote mode: 1,000 elements; Local/Service mode: 10,000 elements; Enterprise tier doubles Remote mode limits.
Data volume sensitivity
Open Dental 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 Open Dental to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Open Dental 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 Open Dental
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.