Migrate your Pearl Dental Software data

Patients are the central record in Pearl's data model. We export all core demographic fields, contact details, and identifiers and map them 1:1 into the destination schema. No transformation required for standard fields.

Medical history is attached to each patient record. We preserve the full history as structured fields including conditions, medications, allergies, and clinical notes. Value-level review is recommended if destination uses coded medical history fields.

Treatment plans are stored as per-patient records with plan status, proposed treatments, and outcomes. We export the full treatment plan structure and recreate it in the destination, preserving links back to the originating patient.

Appointments carry date, time, surgery/room, provider, and appointment type. Cross-system migration requires mapping Pearl's surgery and practitioner IDs to the destination's equivalent identifiers. We flag any unmapped appointment types for manual review.

Charting data is stored in Pearl's internal format. We extract tooth-by-tooth chart entries including conditions, existing restorations, and treatment flags. Where the destination uses a different charting schema, we map tooth positions and status codes explicitly rather than bulk-importing.

Patient documents including PDFs, referral letters, and consent forms are stored alongside the patient record. We export documents as files and associate them to the correct patient in the destination via patient ID cross-reference. Large document sets are chunked for reliable transfer.

X-ray images are stored in Pearl's online backup storage. We export the image files separately from demographic data and flag associations for manual verification post-import, since image-to-chart linking requires destination-specific configuration.

Custom fields on patient or treatment records are supported where they exist in Pearl's export. We extract them as key-value pairs and map them to custom fields in the destination. Any custom fields that have no clear destination equivalent are flagged for customer review.

Pearl's diary stores recurring appointments and schedules. We export diary entries as structured data. Cross-system migration requires mapping surgery rooms and time slots to the destination's scheduling structure.

Insurance information and billing history are associated to patients and appointments. We export payer details, plan codes, and claim status. Destination systems use different billing object models, so we map insurance carriers and codes explicitly during the transformation phase.

Surgeon and room configuration, provider lists, and workflow settings are practice-level data. We extract these as structured records. They require manual mapping to the destination's equivalent configuration section.

Attachments associated to treatments, referrals, or clinical notes are exported as files. We preserve the parent-object association so each file lands against the correct record in the destination system.