Migrate from Praktika Australia to Microsoft Dynamics 365 Sales

Praktika Patient maps to Dynamics 365 Contact. Name, email, phone, address, and DOB transfer as standard fields. HICAPS member ID, Medicare number, health fund, provider assignments, and referral source migrate to custom fields on Contact. Dynamics Contact does not have a native clinical record — custom fields or a linked custom Treatment Plan table handle the clinical extension.

Praktika Account (the dental practice entity) maps to Dynamics 365 Account. Practice name, address, phone, ABN, and HICAPS/Tyro terminal configuration transfer as standard and custom fields. Dynamics Account becomes the parent record for all Contact (patient) records at that location. Multi-location setups produce multiple Account records, one per Praktika location.

Praktika appointments map to Dynamics 365 Activities. Appointment type, date, time, duration, status, provider, and surgery location transfer as standard Activity fields plus custom fields (Appointment_Type__c, Provider__c, Surgery__c). Dynamics has no native scheduling calendar — practices should plan to redesign scheduling workflows using Dynamics Activities or a Power Apps canvas app for calendar views.

Praktika Treatment Plans have no Dynamics 365 native equivalent. FlitStack AI creates a custom Dataverse table (Treatment_Plan__c) with fields for plan date, treatment type, procedure codes (Australian dental item numbers), status, clinical notes, cost estimate, and HICAPS item number. A lookup links each Treatment_Plan__c record to the parent Contact (patient).

Praktika periodontal charting (6-point probing, BOP, furcation, mobility) stores per-tooth measurements with chart dates. Dynamics 365 has no native periodontal object — a custom Dataverse table (Perio_Chart__c) with a lookup to Contact captures chart date, tooth number, site (mesial/distal/buccal/lingual), probing depth, BOP flag, furcation grade, mobility grade, and clinical notes.

Praktika imaging records (X-rays, intraoral photos, CBCT) map to either a custom Imaging__c Dataverse table (with imaging date, type, description, and a link to the stored file) or Dynamics 365 Attachments/File storage. FlitStack AI re-uploads image files to Dynamics 365 SharePoint-connected file storage or Dataverse file fields. Large imaging files may need SharePoint document library configuration in Dynamics.

Praktika Cases (patient enquiries, complaints, clinical incidents) map to Dynamics 365 Cases. Case type, status, priority, created date, assigned provider, and description transfer as standard Case fields. Case-to-contact linking is preserved via the Contact lookup on the Case record. Root-cause and resolution notes migrate as Case description fields.

Praktika products and dental service items (procedure codes, consumables, equipment) map to Dynamics 365 Product records. Product name, code (Australian dental item numbers), unit price, and product type transfer as standard Product fields. Dynamics Product supports quantity-driven pricing that aligns with Praktika's fee-management structure.

Praktika Provider records map to Dynamics 365 System Users for active users who log in, and to a custom Provider__c Dataverse table for historical provider records. Provider name, role, provider number, and dental specialty transfer as standard User fields or custom table fields. A provider-patient junction table (custom entity) handles Praktika's many-to-many patient-provider relationship since Dynamics Contact allows only one Owner per record by default.

Praktika HICAPS terminal IDs, Tyro configuration, and BPAY details are stored as account-level configuration data. Dynamics 365 has no HICAPS or Tyro payment terminal integration — FlitStack AI exports this configuration as a structured reference document that your Dynamics admin uses to rebuild payment terminal settings in Dynamics workflow or a connected payment integration.

Praktika custom fields on any entity (patient allergies, clinical flags, recall intervals, insurance policy numbers) map to Dynamics 365 custom fields on the equivalent entity. Dynamics custom fields follow the __c suffix naming convention and require a Dynamics solution for deployment. FlitStack AI creates these fields in the target Dynamics environment before data loads.

Praktika recall records (6-month checkup, annual hygiene recall) map to a custom Recall__c Dataverse table or to Dynamics Tasks with a due date and custom recall-type field. Recall interval, last recall date, next recall due, and associated provider transfer as custom fields on the Recall record, linked to the parent Contact (patient).