Migrate your Curve Dental data

Patient demographics, contact information, insurance details, medical history, and preferences are standard fields in Curve's schema. We migrate Patients 1:1 with all standard fields intact. Custom patient properties require field-level mapping to the destination.

Appointments include provider assignment, chair location, procedure codes, and status. We map appointment records including historical appointments and recall dates. Recurring appointment patterns must be reconstructed from individual records in the destination.

Treatment plans include procedure codes, fee schedules, insurance estimates, and acceptance status. We migrate treatment plan headers and line items. Case presentation notes and patient-signed acceptance records require review for completeness after import.

Charting includes tooth-by-tooth conditions, existing restorations, perio probing depths, treatment history, and clinical notes. We map charting records but perio pocket depth data requires validation against the destination's perio chart format.

Perio probing data, recession measurements, and bone level records are stored in a structured sub-object. Not all destination PMS platforms preserve this structure. We flatten perio records into compatible fields and flag which measurements require manual verification.

Curve converts and stores x-ray images and intraoral photographs. We migrate image files and their mount associations. Large imaging databases require chunked transfer and we verify image integrity after upload. Some destination systems store images differently and require re-mounting.

Claims history including submitted amounts, payer information, status, and payment postings migrate. Secondary claims, claim adjustments, and write-off records require careful sequencing because they reference parent claim IDs that must already exist in the destination.

Payment records include patient payments, insurance payments, adjustments, and write-offs. We map the full payment ledger including method, amount, date, and posting status. Accounts receivable balances must be reconciled after import because rounding and applied payments can drift.

Uploaded documents, consent forms, referral letters, and lab prescriptions migrate with their associated patient or treatment plan linkage. Large document stores require bulk transfer with integrity verification. Document naming conventions vary between systems and we apply a normalization pass.

Provider records include credentials, specialty, scheduling preferences, and insurance participation. We migrate provider and staff records including role assignment. User login credentials do not transfer and must be recreated in the destination.

Curve's Smart Forms and custom form fields are configurable per practice. We map form structure and response data but note that the visual layout and conditional logic of custom forms do not export and must be rebuilt in the destination.

Recall schedules map to the destination's recall system. Active recall tasks, unscheduled recalls, and patient-based alerts require mapping to the destination's recall logic which varies significantly between PMS platforms.