Migrate from Denticon to HighLevel

Clinical data (periodontal charting, treatment plans, tooth conditions) has no HighLevel native equivalent

Denticon stores clinical charting, periodontal measurements, treatment plans, and tooth conditions as structured clinical data. HighLevel has no native dental clinical objects and no clinical workflow triggers. We migrate all clinical data points as structured custom fields on the Contact record so historical context is preserved. However, HighLevel cannot trigger automations based on periodontal staging or tooth condition data — those rules must be rebuilt manually in the HighLevel workflow builder using custom field conditions.

Multi-location DSO data requires manual location modeling in HighLevel

Denticon manages multi-location DSOs with separate office IDs, cross-location reporting, centralized billing, and per-office provider assignments. HighLevel's location model is a single location field per contact with no native multi-office hierarchy. We store each office name as a Primary_Office__c custom field and apply location tags for filtering, but HighLevel's reporting dashboards cannot natively aggregate performance across multiple offices without manual dashboard rebuild. If your organization requires per-office revenue or production reporting, you will need to configure separate sub-accounts or rebuild cross-office aggregates using HighLevel's custom report builder.

Automated recall, appointment reminders, and patient messaging do not transfer to HighLevel

Denticon's automated recall lists, two-way patient SMS, and appointment reminder sequences are built on Denticon's patient communication engine. HighLevel's workflow builder has no pre-built recall or appointment reminder templates — these automations must be rebuilt from scratch using HighLevel's triggers, tags, and wait-step actions. We export your Denticon workflow definitions as a rebuild reference document for your HighLevel admin. This means you will lose any conditional logic that timed reminders based on recall intervals or treatment stage, so plan to recreate those rules in HighLevel's automation canvas before go‑live.

Appointment operatory assignments and production types cannot be natively mapped in HighLevel

Denticon schedules appointments by operatory, provider, and production type (procedure color category) for clinical workflow optimization. HighLevel's appointment calendar is contact-centric with no operatory or production-type fields. We migrate operatory and production-type as custom fields on the CalendarEvent, but HighLevel's calendar view cannot filter or color-code by these fields natively — your team must adapt scheduling workflows to HighLevel's simpler calendar model. If operatory utilization reports are critical, you will need to export the custom field data and build separate analytics outside of HighLevel's native dashboards.

Insurance claims and RCM workflow state has no HighLevel equivalent

Denticon tracks insurance claims, billing status, and RCM workflow states as part of the practice management data model. HighLevel has no billing, claims, or RCM objects. We preserve insurance carrier and group number as custom fields on Contact, but active claims, billing workflow states, and accounts receivable data cannot be modeled in HighLevel without a separate RCM tool. These records are exported in a reference file for audit continuity. Your billing team should retain the exported RCM file for any payer audits or disputes that may arise after go‑live.