Migrate from Praktika Australia to HighLevel

Every Praktika patient becomes one HighLevel Contact. Demographics (name, DOB, contact info, address) map directly to standard contact fields. Clinical data (allergies, medical history, insurance) lands in custom fields on the contact record. Praktika PatientID is preserved as Source_System_ID__c for traceability.

Each Praktika appointment becomes a HighLevel Calendar event linked to the Contact record. Appointment date, time, duration, operator/staff, and status (confirmed, completed, cancelled) map to HighLevel appointment fields. Tyro payment terminal linkage in Praktika has no HighLevel equivalent — payment records must be handled separately.

Praktika treatment plans contain procedure codes, phases, cost estimates, and clinical notes. In HighLevel, treatment plans become an Opportunity record (for cost tracking and pipeline stage) with a linked custom object (Treatment_Plan__c) holding procedure detail, phases, and clinical notes. This two-layer approach preserves both the financial and clinical sides of a treatment plan.

Praktika periodontal charting stores tooth-by-tooth measurements (pocket depths, recession, bleeding indices) in a structured clinical format. HighLevel has no clinical charting object. We flatten the charting data into a custom field (Perio_Charting_Data__c) storing the most recent charting record as structured text, or as a long-text note attached to the contact. Historical charting across multiple visits requires a separate note per visit.

Praktika restorative charting tracks existing restorations, missing teeth, crowns, and amalgam/composite records by tooth surface. This data has no equivalent in HighLevel's schema. We map it to a custom field (Restorative_Chart__c) as a formatted text string and attach a detailed note with the full charting diagram for clinical reference.

Praktika stores imaging file references (X-rays, intraoral photos, CBCT scans) as URLs within the patient record. HighLevel supports file attachments up to 25MB per file. Files over 25MB (common for DICOM CBCT scans) cannot be uploaded natively — we store them in external cloud storage and put the URL in a custom field (Imaging_URL__c) on the contact record for click-through access.

Praktika recall scheduling tracks when patients are due for hygiene and check-up appointments. We map recall frequency (e.g., 6-month, 12-month) to a custom field (Recall_Frequency__c) and the next recall date to Recall_Date__c. A HighLevel tag (e.g., Recall-Due) is applied and can trigger a workflow to send an SMS or email reminder — replacing Praktika's built-in recall system.

Praktika stores insurance provider, policy number, and HICAPS health fund details. HighLevel has no native insurance fields. We map these to custom fields (Insurance_Provider__c, Policy_Number__c, Health_Fund__c) on the contact. Tyro HICAPS payment processing in Praktika has no direct HighLevel equivalent — practices must use Stripe or PayPal integrations in HighLevel or retain Tyro as a separate terminal.

Praktika accounts track outstanding balances, payment history, and billing history per patient. HighLevel does not have a native accounts receivable module. We map outstanding balance and last payment date to custom fields (Outstanding_Balance__c, Last_Payment_Date__c) and attach a note with the full payment history for reference.

Praktika electronic forms (medical history forms, consent forms) do not migrate. HighLevel has its own form builder with different logic. We export the field list and structure from Praktika as a reference document so the practice can rebuild forms in HighLevel's funnel and form builder before go-live.

Praktika is licensed per location. Multi-location practices have separate patient databases per location. HighLevel's Unlimited plan ($297/month) includes 3 sub-accounts — one per location. We configure sub-accounts in HighLevel matching the Praktika location structure, with a Location__c custom field on contacts for cross-location reporting if sub-accounts are not used.