CRM migration

Migrate from Dentally to monday CRM

Field-level mapping, validation, and rollback between Dentally and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.

Dentally logo

Dentally

Source

monday CRM

Destination

monday CRM logo

Compatibility

100%

12 of 12

objects map 1:1 between Dentally and monday CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Dentally logo

Dentally

What's pushing teams away

  • Multi-site practices report hitting API rate limit ceilings that are not publicly documented and require raising a support ticket to negotiate higher thresholds.
  • Tier-gated advanced features such as full imaging integration and enhanced NHS workflows push growing practices toward the highest pricing tier sooner than expected.
  • Limited public API documentation makes it difficult to scope custom integrations or assess data portability before committing to the platform.
  • Dentally's own migration team manages inbound data transfers, meaning practices cannot self-service an export or cross-check their data independently.
  • Smaller practices on the starter tier report that the 5-user cap becomes restrictive as the team grows, creating pressure to upgrade before the software justifies the cost.

Choosing

monday CRM logo

monday CRM

What's pulling them in

  • Users praise the board-based visual interface for making pipeline stages immediately legible to non-technical team members without CRM training.
  • The no-code automation builder lets sales ops teams create lead routing, stage updates, and email triggers without developer involvement.
  • Integration ecosystem connects to Slack, Gmail, Outlook, and Zapier with minimal configuration, reducing friction for teams already using these tools.
  • The flexible column system lets teams build custom CRM views — deal value, close date, lead source — without needing a developer or pre-defined schema.
  • Teams already using monday Work Management can layer CRM features onto existing boards rather than starting from scratch.

Object mapping

How Dentally objects map to monday CRM

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

maps to

monday CRM

Contact (Monday CRM Item)

1:1
Fully supported

Dentally 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

maps to

monday CRM

Contact Custom Columns

1:1
Mapping required

Dentally 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

maps to

monday CRM

Treatment Board (Monday CRM Board)

1:1
Fully supported

Dentally 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

maps to

monday CRM

Treatment Board Sub-item

1:1
Fully supported

Individual 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

maps to

monday CRM

Treatment Sub-item Custom Columns

1:1
Mapping required

Dentally 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

maps to

monday CRM

Monday Team Member / Contact

1:1
Fully supported

Dentally 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

maps to

monday CRM

Schedule Board Item (Monday CRM)

1:1
Fully supported

Dentally 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

maps to

monday CRM

Invoice Board Item (Monday CRM)

1:1
Fully supported

Dentally 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

maps to

monday CRM

Monday Workspace or Board Group

1:1
Fully supported

Multi-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

maps to

monday CRM

Contact Update Stream (Monday CRM)

1:1
Fully supported

Dentally 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

maps to

monday CRM

Monday CRM Item File Attachment

1:1
Fully supported

Files 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

maps to

monday CRM

Not Migrated

1:1
Fully supported

Dentally 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.

Gotchas + challenges

What specifically takes care here

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 logo

Dentally gotchas

High

API rate limits are undocumented and require a support request

High

Dentally manages inbound migrations rather than offering self-service export

Medium

Final migration runs the day before go-live, leaving a narrow correction window

Medium

Dentally Vision imaging requires separate product setup

Low

Tier-gated features may be inactive in the migrated environment

monday CRM logo

monday CRM gotchas

High

Subitems are not included in bulk exports

High

Daily API call limits vary sharply by plan

Medium

Legacy automations (Sentence Builder) are being deprecated

Medium

Excel and account exports only include table views

Low

Enterprise admins can disable non-admin exports

Pair-specific challenges

  • Monday CRM has no native dental-treatment object — treatment plans become board Items

    Dentally organizes clinical data around treatment plans and treatment items with custom fields. Monday CRM has no native equivalent — there is no Treatment object, no tooth-surface Column type, and no clinical notes field built in. We handle this by creating a Treatment board where each treatment plan is an Item and each treatment item is a Sub-item, with custom Columns mapping Dentally's field types. Custom fields on Dentally treatment items (added via Settings > Treatments & Plans) require Monday Column creation before migration. This is a pre-flight step your Monday admin completes before data lands.

  • Multi-site Dentally accounts need separate Monday Workspaces to avoid record collision

    Dentally supports multi-site practice management under a single account, with data segmented per surgery. Monday CRM scopes data by Workspace — sharing a single Workspace across sites causes patient and appointment records to collide when multiple surgeries have patients with the same name. We map each Dentally site to a separate Monday Workspace containing a full set of Contacts, Treatment, Schedule, and Invoice boards. This requires your Monday admin to pre-create the workspaces and assign seat licenses per site before migration.

  • Dentally appointment-reminder and recall automations do not transfer — Monday's Automation Center must be rebuilt

    Dentally appointment reminders, recall sequences, and treatment-plan follow-up automations are workflow-level constructs stored in Dentally's automation engine. Monday CRM's Automation Center is a separate trigger-action system with no migration path between them. Appointment reminders, recall sequences for hygiene appointments, and treatment-plan status alerts must be rebuilt as Monday Automations post-migration. FlitStack exports a machine-readable JSON summary of your Dentally workflow definitions (trigger, conditions, actions) as a rebuild reference for your Monday admin.

  • Monday CRM API daily call limits cap bulk-write throughput — multi-site extraction requires elevated limits

    Monday CRM enforces daily API call limits per plan: Free/Trial (200), Basic/Standard (1,000), Pro (10,000 soft), Enterprise (25,000 soft). A multi-site Dentally migration with 50,000+ patient records hitting a 1,000-call daily limit requires multiple extraction batches across several days, extending the migration timeline. We monitor Monday API response headers (X-Daily-Limit-Remaining) during write operations and throttle accordingly. For Pro and Enterprise plans, we request increased limits via the Monday developer portal before migration begins.

  • Dentally clinical file attachments must be downloaded and re-uploaded to Monday CRM

    Dentally stores clinical files (treatment images, X-rays, consent forms) attached to patient records or treatment items. Monday CRM does not integrate with Dentally's file storage — attachments must be downloaded from Dentally and uploaded as Monday CRM Item attachments. Monday's file size limits apply per plan tier (storage capacity varies: 5GB on Basic, 20GB on Standard, 100GB on Pro). Large clinical imaging files may exceed Monday's per-file size cap and must be stored in a linked cloud drive (Google Drive, SharePoint) with a URL reference Column added to the Item.

Migration approach

Six steps for a successful Dentally to monday CRM data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Dentally logo

Dentally

Source

Strengths

  • Strong UK market presence with over 12,000 subscribed practices providing peer credibility and local support networks.
  • Consolidates appointment scheduling, clinical records, NHS referrals, and payments in a single cloud-based platform without on-premise hardware.
  • Native integrations with Xero, DenGro, and NHS e-referrals reduce the need for middleware or manual data re-entry.
  • Patient-facing Dentally Portal and integrated Dentally Vision imaging add capability without requiring separate vendor contracts.

Weaknesses

  • API rate limits are not publicly documented and practices with multi-site or high-volume integrations report needing to request increases through support.
  • Public API documentation is limited, making custom development and third-party integration scoping difficult before commitment.
  • Advanced features including full imaging and enhanced NHS workflows are gated behind higher pricing tiers, increasing cost as practices grow.
monday CRM logo

monday CRM

Destination

Strengths

  • Board-based UI makes pipeline stages and deal progress visually obvious without training.
  • No-code automation builder requires no developer resources to create lead routing and stage-triggered actions.
  • Flexible column system supports custom CRM fields without schema changes or admin involvement.
  • Integrates natively with Slack, Gmail, Outlook, and Zapier with minimal configuration overhead.
  • Layered product means teams already on monday Work Management can add CRM without migrating existing data.

Weaknesses

  • No native Contacts object separate from Items — contacts are managed inside a CRM module's People feature.
  • Pipeline and deal relationships use a flat item model rather than a relational object model, making complex CRM associations awkward.
  • Automations are plan-gated (250 actions/month on Standard, 25,000 on Pro) and the legacy Recipe system is being deprecated.
  • Customization and advanced views (Chart, Formula, Dependency) are locked behind Pro and Enterprise tiers.
  • Per-seat pricing with non-refundable annual billing creates cost lock-in risk during migration.

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between Dentally and monday CRM.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Dentally and monday CRM.

  • Object compatibility

    A

    All 8 core objects map 1:1 between Dentally and monday CRM.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Dentally: Not publicly documented; practices requiring higher limits must request them via Dentally support.

  • Data volume sensitivity

    B

    Dentally doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Dentally to monday CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Dentally to monday CRM data migrations

Answers to the questions buyers ask most during Dentally to monday CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Dentally-to-Monday CRM migrations complete in 48–72 hours of clock time for a single-site practice with under 10,000 patient records. Multi-site Dentally accounts with 50,000+ records and extensive custom field usage extend to 5–7 days, primarily due to Monday's API daily call limits per plan tier (1,000 calls/day on Standard, 10,000 on Pro) and the need to route each site to a separate Monday Workspace. The longest planning step is creating the Monday board structure and custom Columns before migration writes begin.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Dentally.
Land in monday CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day