CRM migration
Field-level mapping, validation, and rollback between Dentally and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Dentally
Source
monday CRM
Destination
Compatibility
12 of 12
objects map 1:1 between Dentally and monday CRM.
Complexity
BStandard
Timeline
48–72 hours
Overview
Dentally organizes a dental practice around Patients, Treatments, Practitioners, and Appointments, with custom fields on treatment items and a per-surgery pricing model. Monday CRM uses a board-and-item architecture where Contacts, Deals, Companies, and Tasks live as Items on customizable boards, each Item holding data in typed Columns. The migration carries Dentally's patient records into Monday CRM as Contact Items, treatments into a Treatment board using custom Columns, practitioners as Team Members, and appointments into a scheduling board. Because Monday CRM has no native clinical-treatment object, Dentally's treatment-item custom fields map to Monday's custom Column types — text, numbers, dropdown lists, and date columns. We extract via Dentally's API (aware of per-account rate limits) and write via Monday's API using Board and Item creation calls. Workflows, automations, and appointment-reminder sequences built in Dentally do not migrate — those must be rebuilt in Monday's Automation Center. We deliver a sample migration with field-level diff before committing the full run, and a delta-pickup window captures any Dentally changes 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 Dentally 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.
Dentally
Patient
monday CRM
Contact (Monday CRM Item)
1:1Dentally Patient records map 1:1 to Monday CRM Contacts. Each patient becomes an Item in the Contacts board. The patient's first name, last name, email, phone, and address fields translate directly to Monday Contact Columns. Original Dentally patient ID preserved as a custom Column for traceability.
Dentally
Patient Custom Fields
monday CRM
Contact Custom Columns
1:1Dentally allows custom fields on patient records (administered via Settings > Practice Settings > Custom Fields). These map to Monday custom Columns — text fields become Text Columns, tick-boxes become Checkbox Columns, preset options become Dropdown Columns. Each custom field requires a corresponding Column created in Monday before migration writes data.
Dentally
Treatment Plan
monday CRM
Treatment Board (Monday CRM Board)
1:1Dentally treatment plans contain treatment items with clinical notes, procedures, and status. These migrate as Items in a dedicated Treatment board — one Item per treatment plan, with Columns capturing plan status, total value, and linked patient. The Item's sub-items represent individual treatment items within the plan.
Dentally
Treatment Item
monday CRM
Treatment Board Sub-item
1:1Individual treatment items within a Dentally plan (e.g., 'Root Canal – UR6') migrate as Sub-items under the parent Treatment Plan Item in Monday CRM. Sub-item Columns capture procedure name, tooth surface, clinical notes, status, and estimated cost. Original Dentally treatment-item ID stored as a custom Sub-item Column.
Dentally
Treatment Item Custom Fields
monday CRM
Treatment Sub-item Custom Columns
1:1Dentally treatment items support custom fields added via Settings > Treatments & Plans > Fields tab. Custom field types (text, tick-box, dropdown) map to Monday Sub-item Column types. Level 4 (Administrator) permission is required to create these fields in Dentally — FlitStack documents the full custom-field inventory before mapping begins.
Dentally
Practitioner
monday CRM
Monday Team Member / Contact
1:1Dentally practitioner records (dentist, hygienist, specialist) map to Monday Team Members if they have Monday CRM login credentials. If a practitioner does not have a Monday seat, their record migrates as a Contact Item in a Practitioners board with Columns for role, registration number, and surgery assignment.
Dentally
Appointment
monday CRM
Schedule Board Item (Monday CRM)
1:1Dentally appointments (with date, time, duration, and practitioner) map to Items in a Schedule board in Monday CRM. Columns capture appointment date, time slot, duration in minutes, practitioner name, and patient link. Monday's Calendar view can then render the Schedule board as a calendar — but appointment reminders must be rebuilt as Monday Automations.
Dentally
Invoice
monday CRM
Invoice Board Item (Monday CRM)
1:1Dentally invoices with line items, totals, payment status, and patient link migrate as Items in an Invoice board. Columns capture invoice number, issue date, due date, total amount, amount paid, outstanding balance, and payment status. Monday's formula Columns calculate outstanding balance from total minus amount paid.
Dentally
Practice / Site
monday CRM
Monday Workspace or Board Group
1:1Multi-site Dentally accounts (one account managing multiple surgeries) map to separate Monday Workspaces or Board Groups per site. Each workspace contains a full copy of Contacts, Treatment, Schedule, and Invoice boards scoped to that site. This prevents cross-site record collision and mirrors Dentally's per-surgery data isolation.
Dentally
Patient Notes / Clinical History
monday CRM
Contact Update Stream (Monday CRM)
1:1Dentally patient notes (clinical history, medical alerts) migrate as Updates on the corresponding Contact Item in Monday CRM. Each Update carries the original timestamp and author — preserving the chronological clinical narrative without creating separate objects. Monday's Updates section provides a per-contact audit trail equivalent to Dentally's note history.
Dentally
Document / File Attachment
monday CRM
Monday CRM Item File Attachment
1:1Files attached to Dentally patient records, treatment plans, or invoices are downloaded and re-uploaded as Monday CRM Item attachments. File size limits apply per Monday plan tier. Inline images in Dentally clinical notes are extracted, hosted as files, and linked back to the Contact Item Update where they originated.
Dentally
Workflow / Automation
monday CRM
Not Migrated
1:1Dentally appointment reminders, recall sequences, and treatment-plan automations are workflow-level constructs with no Monday CRM equivalent. These must be rebuilt using Monday's Automation Center after migration. FlitStack exports a machine-readable summary of Dentally workflow definitions as a rebuild reference for the practice's Monday admin.
| Dentally | monday CRM | Compatibility | |
|---|---|---|---|
| Patient | Contact (Monday CRM Item)1:1 | Fully supported | |
| Patient Custom Fields | Contact Custom Columns1:1 | Mapping required | |
| Treatment Plan | Treatment Board (Monday CRM Board)1:1 | Fully supported | |
| Treatment Item | Treatment Board Sub-item1:1 | Fully supported | |
| Treatment Item Custom Fields | Treatment Sub-item Custom Columns1:1 | Mapping required | |
| Practitioner | Monday Team Member / Contact1:1 | Fully supported | |
| Appointment | Schedule Board Item (Monday CRM)1:1 | Fully supported | |
| Invoice | Invoice Board Item (Monday CRM)1:1 | Fully supported | |
| Practice / Site | Monday Workspace or Board Group1:1 | Fully supported | |
| Patient Notes / Clinical History | Contact Update Stream (Monday CRM)1:1 | Fully supported | |
| Document / File Attachment | Monday CRM Item File Attachment1:1 | Fully supported | |
| Workflow / Automation | Not Migrated1: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.
Dentally gotchas
API rate limits are undocumented and require a support request
Dentally manages inbound migrations rather than offering self-service export
Final migration runs the day before go-live, leaving a narrow correction window
Dentally Vision imaging requires separate product setup
Tier-gated features may be inactive in the migrated environment
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 Dentally data model and custom fields
FlitStack connects to Dentally via API using scoped read access and inventories the full object hierarchy: patients, practitioners, appointments, treatment plans, treatment items, invoices, and all custom fields added via Settings > Treatments & Plans > Fields. For multi-site accounts, we identify site segmentation and flag any patient records sharing the same name across sites. This audit generates a Dentally Object Manifest that drives the mapping plan and determines Monday Column creation requirements before any data moves.
Create Monday CRM board structure and custom Columns
Based on the Dentally Object Manifest, your Monday admin (or FlitStack) creates the target board structure: a Contacts board, a Treatment board with Sub-items, a Schedule board, an Invoice board, and separate Workspaces per site. Custom Columns matching Dentally's field types (dropdown lists, checkbox flags, date fields) are created in Monday before migration writes begin. This step is sequenced first because Monday requires Columns to exist before Items can populate Column data via API.
Extract Dentally data via API with batched pagination
We extract Dentally records in paginated API batches, handling per-account rate limits by monitoring response headers and backing off between requests. For multi-site accounts, extraction runs per-site, tagged with the site identifier for Workspace routing. Patient records are extracted with their linked treatment plans, treatment items, and appointment history in a single pass to preserve relationships. Created_at and updated_at timestamps are captured for every record for delta-pickup use later.
Run sample migration with field-level diff
A representative slice — typically 200–500 patient records with associated treatments, appointments, and invoices — migrates first into Monday CRM test boards. We generate a field-level diff report comparing source Dentally values against Monday Item Column values, highlighting any mapping discrepancies, missing Columns, or truncated text. You review the diff report and approve before the full run commits. This catches custom field type mismatches and value-mapping gaps before thousands of records are written.
Execute full migration and delta-pickup cutover
Full Dentally dataset migrates into Monday CRM production boards, writing Items via Monday's API in sequenced batches per object dependency (Contacts first, then Treatments, then Appointments and Invoices). A delta-pickup window — typically 24–48 hours after full extraction timestamp — re-queries Dentally for any records modified during the migration window and applies those changes to Monday. An audit log records every Item created and updated. One-click rollback reverts all Monday writes if reconciliation fails.
Deliver reconciliation report and rebuild reference
FlitStack generates a post-migration reconciliation report: record counts per object in Dentally versus Monday, missing records flagged, and any unmapped custom fields documented. The Dentally workflow automation JSON export (appointment reminders, recall sequences, treatment-plan automations) is delivered alongside the report. Your Monday admin uses both documents to rebuild automations in Monday's Automation Center. FlitStack remains available for a 14-day post-migration support window to address any data discrepancies discovered after go-live.
Platform deep dives
Dentally
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Dentally and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Dentally and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Dentally 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
Dentally: Not publicly documented; practices requiring higher limits must request them via Dentally support.
Data volume sensitivity
Dentally 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 Dentally to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Dentally 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 Dentally
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.