Migrate your Praktika Australia data

Patient records hold demographics, medical history, insurance details, and contact preferences. Praktika stores custom notes per patient that may use practice-specific abbreviations. We map each Patient File field-by-field and flag any non-standard fields for manual review before import.

Periodontal charting records pocket depths, recession, and mobility per tooth. Praktika uses a tooth-by-tooth grid format that varies between practices. We preserve the full chart as a structured block and map it to the destination's Perio schema or a compatible custom object.

Restorative charting tracks existing restorations, decay, missing teeth, and surfaces (MO, DO, MOD, etc.). The charting notation can differ between clinicians. We carry forward the chart snapshot as a text or XML block to avoid losing surface-level detail during migration.

Appointments are stored with patient links, provider assignments, time slots, and status (confirmed, completed, cancelled). Praktika does not expose a bulk export endpoint — we extract via their conversion file and map dates, providers, and statuses to the destination calendar schema.

Treatment plans associate diagnoses with planned procedures, fee items, and stages. Plans can be linked or standalone. We migrate each plan as a structured object and flag any plan with a status of In Progress so the destination does not mark it complete by default.

Quotes link to a patient and contain itemised fee estimates with or without insurance estimates. Expired or superseded quotes require a status review — we carry them forward but tag them so the destination can optionally suppress or expire them on import.

Accounts track patient balances, payment history, and HICAPS/Tyro transaction records. Praktika holds open item data in a ledger-style format. We preserve the full account history including zero-balance accounts that may contain valuable payment behaviour context.

Recall records drive automated patient re-engagement intervals (e.g., 6-month hygiene recall). Recall rules and individual patient due dates are both stored. We map these to the destination's recall or reminder system and flag any with overdue status that need immediate follow-up.

Communication history between the practice and patient is stored per patient file. We extract the log as a text block and map it to the destination's communication timeline, noting that not all platforms display inbound/outbound separately.

Online booking configuration — calendar availability, slot durations, booking rules — is a platform-specific setting that does not migrate as a data record. We document the current configuration for manual reconfiguration on the destination platform.

Electronic patient intake and consent forms are stored as completed records attached to a Patient File. We extract completed form submissions and map them as PDF or structured data depending on what the destination accepts.

Sterilisation tracking is an internal compliance log not tied to patient data. It is environment and equipment-specific and does not have a standard migration path. We recommend exporting as a PDF backup and reconfiguring on the destination.

Imaging attachments (X-rays, intraoral photos) are referenced via TWAIN or file link in Praktika. We extract the file references and image files where accessible and map them to the destination's imaging module, flagging any orphaned images without a valid patient link.

Health claims processed through HICAPS or Tyro are recorded in the Accounts module with transaction IDs, claim amounts, and patient links. We preserve the transaction ledger so the destination can reflect the full payment history for each patient account.