Migrate your Dent-O-Soft data

The primary record in Dent-O-Soft. Each patient carries demographics, insurance references, balances, and a link to an oral situation chart. We map patient records 1:1 to the destination Contacts or Patients object and carry forward the most recent balance and account status.

Dent-O-Soft stores per-tooth charting with a graphical illustration of conditions and treatment history. We extract the structured chart data where available and fall back to the narrative notes field when the chart schema is not exportable via the available data path.

Appointment records include date, time, provider, operatory, and status. We map appointment dates, provider assignments, and status codes directly to the destination scheduling object.

Charge entries represent the fee ledger for services rendered. Each charge is tied to a patient and a procedure code. We preserve charge amounts, date of service, procedure codes, and provider attribution across the migration.

Payment records represent amounts received and applied to a patient's account. We map payment date, amount, payment method, and the patient-to-payment linkage so receivables reconcile post-migration.

Supplier records store vendor contact information used to order materials and lab work. We extract name, contact details, and account notes but the supplier-to-product linkage is not always structured as a separate object and may require manual verification post-import.

Technician entries are distinct from suppliers and represent the lab personnel or internal staff responsible for cases. We carry forward name and contact data but the technician-to-case assignment is stored as a reference field that may require field mapping to the destination schema.

Treatment planning data appears within the oral situation record and may include proposed procedures, notes, and case status. We extract plan entries where they are stored as distinct records; otherwise they are preserved as part of the clinical notes migration.

We do not currently have documented evidence of a publicly accessible API or export mechanism for custom fields in Dent-O-Soft. Any practice-specific custom properties would need to be identified during the scoping call and handled as manual data capture or CSV re-entry.

Insurance claim status and history are managed within the patient account context but there is no evidence of a separate Claims object with a stable schema available for bulk export.