CRM migration
Field-level mapping, validation, and rollback between Dental-Exec and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Dental-Exec
Source
monday CRM
Destination
Compatibility
10 of 11
objects map 1:1 between Dental-Exec and monday CRM.
Complexity
BStandard
Timeline
3–7 days
Overview
Dental-Exec structures its data around patients, appointments, treatment plans, insurance records, and billing—everything stored in a vertically integrated clinical model designed for compliance and procedure logging. monday CRM structures its data around People (contacts), Organizations (companies), Deals (opportunities), Inbox (activities), and unlimited custom boards that function as flexible databases. The migration maps Dental-Exec patient records to monday People, Dental-Exec insurance and billing data to monday custom board columns with value-mapped pick-lists, and Dental-Exec treatment histories to monday sub-items linked to People records. monday's automations have no direct equivalent to Dental-Exec's clinical workflow rules—those must be rebuilt as monday automation recipes post-migration. monday's per-seat pricing and API rate limits (200 calls per day on Basic, 10,000 on Pro, 25,000 on Enterprise) shape the migration architecture: FlitStack uses Dental-Exec's export API, transforms data to monday's bulk-import format, and sequences board creation so foreign-key relationships resolve correctly before contacts land. The migration also preserves original timestamps, source system IDs, and document metadata to maintain audit continuity. Because monday's board hierarchy does not enforce referential integrity automatically, FlitStack builds Link columns and sub-item relationships in a sequence that respects foreign keys, ensuring that each appointment, treatment plan, and claim is correctly attached to its patient record. Additionally, the per-seat pricing model influences the design of board-level permission groups, which must be configured to reflect Dental-Exec's role-based access before the import begins.
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 Dental-Exec 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.
Dental-Exec
Patient
monday CRM
People (Contact)
1:1Dental-Exec patient records map 1:1 to monday People. Fields: patient name, date of birth, contact phone, email, address, emergency contact. monday People are the primary contact record in monday CRM's data model. Each patient lands as a single People item; multiple addresses collapse to one primary address with additional locations stored in a custom Location column.
Dental-Exec
Appointment
monday CRM
Calendar Board / Timeline Column
1:1Dental-Exec appointments (date, time, provider, procedure code, status: Scheduled/Completed/Cancelled) map to a monday custom board where each appointment is an item and the Timeline column shows start/end times. Provider name maps to a Person column; procedure status maps to a Status column with Dental-Exec's appointment statuses as values. Original appointment timestamps preserved in a Date column.
Dental-Exec
Treatment Plan
monday CRM
Sub-items on Patient Board
1:manyDental-Exec treatment plans contain multiple line items (CDT codes, tooth numbers, surfaces, materials, fees). We split each treatment line item into a monday sub-item linked to the parent Patient item. Each sub-item carries the procedure code, tooth reference, surface detail, material, fee amount, and completion status. Parent item holds the overall treatment plan name and plan date.
Dental-Exec
Insurance Record
monday CRM
Custom Insurance Board with Link to People
1:1Dental-Exec insurance records (carrier name, group number, subscriber ID, effective dates, coverage percentages) map to a monday custom board where each item represents one insurance plan. A Link column connects the insurance item to the associated Patient People item. Coverage percentages map to Number columns; effective dates map to Date columns. One patient can have multiple insurance items linked.
Dental-Exec
Insurance Claim
monday CRM
Custom Claims Board
1:1Dental-Exec insurance claims (claim ID, status: Submitted/Paid/Denied/Appeal, submitted amount, paid amount, paid date, payer notes) map to a monday custom board. Claim status maps to a Status column with pick-list values matching Dental-Exec's claim lifecycle. Provider name, submission date, and payer reference stored in Text and Date columns. Linked to the corresponding Patient and Insurance items via Link columns.
Dental-Exec
Billing / Ledger Entry
monday CRM
Custom Billing Board
1:1Dental-Exec billing ledger entries (charge date, procedure code, charge amount, payment amount, adjustment, balance, payment method) map to a monday custom board where each item is one ledger transaction. Charge and payment amounts map to separate Currency columns. Running balance is a calculated field in monday or re-derived from source data post-migration. Linked to Patient and Treatment Plan items for full traceability.
Dental-Exec
Provider / Staff
monday CRM
monday Team Members / Person Column options
1:1Dental-Exec provider and staff records (name, role: Dentist/Hygienist/Admin, license number, email, phone) map to monday team members. We resolve each Dental-Exec provider by email match against monday workspace members. If a provider has no monday account, their name is stored as a Text column value on the relevant items and flagged for monday account creation before go-live.
Dental-Exec
Clinical Document / File Attachment
monday CRM
monday Files / Link Column
1:1Dental-Exec patient documents—X-rays, intraoral photos, consent forms, treatment plan PDFs—are downloaded and re-uploaded to monday Files, attached to the relevant Patient item. Files exceeding monday's 25MB limit are flagged: we host them externally (Google Drive, Dropbox) and store the URL in a monday Link column with descriptive naming. Original file names and upload timestamps preserved in file metadata.
Dental-Exec
Referral Source
monday CRM
Custom Column on Patient Board / Tag
1:1Dental-Exec referral source fields (referring dentist name, referral type: New/Existing/Promotion) map to monday as a Dropdown or Tag column on the Patient board. Referral source names become Dropdown values; referral type becomes a Status or Tag. This field is entirely optional in Dental-Exec, so null values are preserved as 'Unknown' in monday.
Dental-Exec
Custom Dental Field (platform extension)
monday CRM
monday Custom Column
1:1Dental-Exec custom fields for specialties—orthodontic stage tracking, implant case status, oral surgery flags—map to monday custom columns. We identify the Dental-Exec field type (text, number, date, pick-list) and create the equivalent monday column type. Pick-list custom fields in Dental-Exec become monday Status or Dropdown columns with values mapped value-by-value. Custom fields are documented in the migration plan before import begins.
Dental-Exec
Practice Location
monday CRM
monday Location Column / Organization
1:1Dental-Exec multi-location setups (location name, address, phone) map to monday Location columns on relevant boards or as separate Organization items in monday. Each location gets its own Workspace or board Group so staff see only the items relevant to their location. Provider assignments per location are preserved as Person columns filtered by location Group.
| Dental-Exec | monday CRM | Compatibility | |
|---|---|---|---|
| Patient | People (Contact)1:1 | Fully supported | |
| Appointment | Calendar Board / Timeline Column1:1 | Fully supported | |
| Treatment Plan | Sub-items on Patient Board1:many | Fully supported | |
| Insurance Record | Custom Insurance Board with Link to People1:1 | Fully supported | |
| Insurance Claim | Custom Claims Board1:1 | Fully supported | |
| Billing / Ledger Entry | Custom Billing Board1:1 | Fully supported | |
| Provider / Staff | monday Team Members / Person Column options1:1 | Fully supported | |
| Clinical Document / File Attachment | monday Files / Link Column1:1 | Fully supported | |
| Referral Source | Custom Column on Patient Board / Tag1:1 | Fully supported | |
| Custom Dental Field (platform extension) | monday Custom Column1:1 | Fully supported | |
| Practice Location | monday Location Column / Organization1: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.
Dental-Exec gotchas
No public API for automated exports
Recall and hygiene data embedded in task records
Drug interaction flags are binary, not structured
Thin vendor footprint raises continuity risk
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
Extract and profile Dental-Exec data via API
FlitStack connects to Dental-Exec using your API credentials and runs a full data extraction across all modules: patients, appointments, treatment plans, insurance records, claims, billing ledger, and document metadata. We profile the data for completeness, duplicate rates, and null-field frequency before any mapping work begins. The profiling report identifies which Dental-Exec fields are populated consistently, which are sparsely used, and which contain non-standard values that need explicit mapping decisions. This step produces the data map that drives every subsequent transformation.
Design monday workspace structure and column types
Before any data moves, FlitStack delivers a monday workspace design plan based on your Dental-Exec module structure. We specify the boards to create (Patient Board, Appointments Board, Treatment Plans Board, Insurance Board, Claims Board, Billing Board), the column types for each board, and the relationship links between boards. Custom dental fields from Dental-Exec are translated to equivalent monday column types—CDT codes become Text, coverage percentages become Numbers, status fields become Status/Dropdown. Your monday admin creates the boards and columns before the migration run; we validate the schema matches the data map before proceeding.
Resolve provider and staff assignments by email
Dental-Exec providers and staff are matched against monday workspace members by email address. FlitStack generates a pre-migration owner resolution report: every Dental-Exec provider is listed with their email, their monday match status (found, not found, or ambiguous), and the monday account they would be assigned to. Providers without monday accounts are flagged for account creation before go-live. Records assigned to unresolved providers are staged in a holding board until their monday account exists, preventing orphaned items with no owner.
Run sample migration with field-level diff
A representative slice migrates first—typically 100–300 patient records with appointments, treatment plans, and insurance data included. We generate a field-level diff comparing the Dental-Exec source values against the monday destination values for every mapped column. You review the diff to confirm CDT codes, insurance percentages, appointment statuses, and treatment plan stages look correct. Large imaging files are tested for Link column resolution. This sample run validates the transformation logic and identifies any value-mapping gaps before the full migration commits.
Execute full migration with delta-pickup window
The full migration runs against monday CRM. A delta-pickup window—typically 24 hours after the migration run completes—captures any Dental-Exec records created or modified during the cutover window so monday reflects your final Dental-Exec state at go-live. All files are uploaded or linked, all timestamps preserved as custom date fields, all monday relationships (Patient → Insurance, Patient → Treatment Plan, Patient → Appointments) established via Link columns. An audit log records every record created, every file uploaded, and every relationship linked. One-click rollback is available for 72 hours post-migration if reconciliation uncovers data integrity issues.
Platform deep dives
Dental-Exec
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Dental-Exec and monday CRM.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
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
Dental-Exec: Not publicly documented.
Data volume sensitivity
Dental-Exec 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 Dental-Exec to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Dental-Exec 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 Dental-Exec
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.