Migrate from Dent-O-Soft to monday CRM

Monday CRM has no native tooth-charting or periodontal charting object

Dent-O-Soft stores per-tooth status and periodontal measurements as structured clinical data. Monday CRM boards have no equivalent clinical schema — there is no tooth-grid column type or periodontal charting view. We capture tooth-level status as structured text in a custom column (e.g., 'Tooth 3: restored, Tooth 14: missing') and detailed periodontal data as a long-text custom field. If your team relies on graphical tooth charts for clinical decisions, that visual context does not transfer and must be rebuilt manually or by using monday CRM's integrations with dental imaging tools. This is a clinical data representation gap that requires your clinical lead to define acceptable text-based alternatives before migration.

Billing ledger migration requires a custom board structure with no native accounting logic

Dent-O-Soft maintains a real-time patient ledger with charges, payments, adjustments, and insurance payments that always sum to a current balance. Monday CRM has no native accounting module — there is no concept of a running balance, credit vs. debit, or insurance write-offs. We create a Billing board where each ledger entry becomes an item with charge, payment, and balance number columns, but the balance must be calculated per entry or maintained manually. If your practice relies on automated billing alerts or insurance claim status tracking inside Dent-O-Soft, those automations cannot migrate and must be rebuilt as monday CRM automation recipes.

CDT code value mapping requires a static lookup table that monday CRM labels do not natively support

Dent-O-Soft procedure codes follow the ADA CDT code set — a standardized taxonomy with ~800 active codes. Monday CRM Labels columns store arbitrary text values with no native cross-reference to external taxonomies. When we map CDT codes to monday CRM Labels, the code and description text are stored as the label name. If your team relies on CDT code lookups for insurance pre-authorization or treatment planning inside Dent-O-Soft, the code-to-description mapping is flattened in monday CRM. We recommend creating a separate CDT Reference board with code numbers and descriptions that your team can reference alongside the labeled items.

Appointment board migration loses Dent-O-Soft's chair and operatory scheduling constraints

Dent-O-Soft's appointment book enforces scheduling constraints: provider availability, chair availability, operatory type, and procedure duration combine to suggest valid time slots. Monday CRM's board model has no native scheduling engine — there is no concept of a chair resource, operatory type, or conflict detection. We map appointments to items with date and timeline columns, but duplicate or conflicting appointments on the same chair at the same time are not flagged by monday CRM. Practices with multi-chair, multi-provider scheduling should plan to rebuild a scheduling workflow using monday CRM's Calendar view and automations or a dedicated integration with a dental scheduling tool.

Monday CRM API daily call limits cap bulk migration throughput on Basic and Standard plans

Monday CRM enforces API rate limits: 200 calls/day on Free/Trial, 1,000 calls/day on Basic/Standard, 10,000 calls/day on Pro, and 25,000 calls/day on Enterprise. A migration with 50,000+ patient records, 200,000+ appointments, and treatment subitems can exhaust Basic-plan limits in a single pass. We throttle migration runs and batch writes to respect limits, which extends timeline. We recommend running the migration on a Pro or Enterprise monday CRM account where daily call limits are high enough to complete bulk loads within the delta-pickup window without throttling.