Migrate from Curve Dental to HighLevel

Patient demographics (name, date of birth, contact information, address) map directly to HighLevel Contact fields. Insurance primary fields flatten into Contact custom fields. Inactive patients receive a status tag. Provider assignment resolves by email match to HighLevel users where applicable.

Curve Dental insurance records — carrier name, group number, subscriber ID, subscriber relationship, and coverage percentages — have no native HighLevel equivalent. We create an Insurance custom object in HighLevel with custom fields for each data point and link it to the Contact via a relationship field. Practices choosing a flattened model store insurance data as custom fields on the Contact record instead.

Curve Dental treatment plans include procedure codes, tooth numbers, fees, provider notes, and plan status (proposed, accepted, completed). HighLevel has no treatment plan object. We create a TreatmentPlan custom object with custom fields for procedure description, tooth number, fee, status, and linked Contact. Historical treatment plan status values map via value mapping to HighLevel pick-list options.

Curve Dental appointment blocks (date, start time, end time, provider, operatory, procedure) map to HighLevel calendar events with assigned user, date, start/end time, and tags for procedure type. Historical appointments without specific times or appointments beyond HighLevel's lookback window migrate as Tasks with a custom field for the original appointment date so reporting continuity is preserved.

Curve Dental providers carry credentials and specialty information. HighLevel has users and contacts — not a clinical provider object. We match providers to HighLevel users by email address and assign them as the responsible user on migrated records. Provider credentials and specialties not captured by HighLevel user fields are stored as custom fields on the Contact record or as Contact tags.

Curve Dental tracks payment amounts, payment dates, payment methods, and outstanding balances. HighLevel has no native accounting module. Outstanding balance, last payment amount, last payment date, and payment method migrate as custom fields on the Contact record. Practices needing full A/R management should use HighLevel's integration with an external accounting tool post-migration.

Curve Dental periodontal charting and clinical notes are tooth-specific, highly structured clinical data with no HighLevel equivalent. These records are exported and stored as Contact notes or in a long-text custom field. They are preserved for reference but cannot drive HighLevel clinical workflows — any perio-based recall automation must be rebuilt using tag-based triggers in HighLevel's Workflow Builder.

Curve Dental patient documents, uploaded images, and X-rays re-upload to HighLevel Files and are linked to the Contact record. HighLevel file size limits apply (25MB per file for direct upload). Inline images in clinical notes are extracted and rehosted. Documents are associated with the Contact record via the Files relationship.

Curve Dental custom form fields created by the practice migrate to HighLevel custom fields on the Contact object. Field data types are mapped: text to text, number to number, date to date, pick-list to pick-list or tag. Field-level mapping is verified during the sample migration phase before the full run.

Curve's built-in patient recall and automated messaging sequences are internal workflow definitions with no structural equivalent in HighLevel's Workflow Builder. We export the workflow definitions as a text reference document so the practice can rebuild recall automations in HighLevel using Workflow Builder triggers (appointment date, tag, contact field change). Any HighLevel migration quote excludes workflow rebuilding.