Migrate from Praktika Australia to Pipedrive

Praktika patient records map directly to Pipedrive Persons. Patient name, email, phone, address, and date of birth map to corresponding Pipedrive Person fields. Medical history flags and consent form status migrate as custom fields since Pipedrive has no native medical history model.

Praktika stores one emergency contact per patient. The emergency contact name, relationship, and phone number migrate as custom fields on the primary Patient Person record since Pipedrive Persons do not support nested contact relationships natively. Each emergency contact field appears as a separate custom property on the Person, allowing front-desk staff to view contact details without opening additional records.

Each Praktika practice location becomes a Pipedrive Organization. Location name maps to Organization name; full address maps to Organization address fields. Provider rosters attached to each location link to Pipedrive Users via email match. When a practice operates multiple sites, each location's Organization record maintains its own address, phone, and assigned provider list for location-specific reporting in Pipedrive's dashboard views.

Praktika appointments map to Pipedrive Activities with type='meeting' for chair appointments and type='task' for recall follow-ups. Original appointment datetime, provider, surgery, and procedure codes preserve in activity notes. Multi-day or recurring appointments generate one Activity per occurrence. Each Activity links to the Patient Person and the Provider User, ensuring appointment history is traceable by patient and by treating provider in Pipedrive's activity feeds.

Praktika treatment plans become Pipedrive Deals. The treatment plan name maps to Deal title; estimated fee maps to Deal value (amount). Plan status (proposed, accepted, in-progress, completed) maps to a custom pick-list field since Pipedrive Deal stages are pipeline-specific. Each treatment item within a plan migrates as a Deal note.

Praktika quotes with line items map to Pipedrive Deals with associated Product items. Each quoted procedure code becomes a Product entry linked to the Deal. Quote expiry date and payment terms migrate as custom date and text fields on the Deal.

Praktika HICAPS/Tyro payment records store transaction ID, insurer/payer, amount, and provider attribution. These cannot map to native Pipedrive fields. We create monetary custom fields (HICAPS_Transaction_ID__c, HICAPS_Payer__c, HICAPS_Amount__c) on the related Deal to preserve payment audit trail. Multiple payments on one treatment plan create multiple custom field entries linked to the same Deal.

Praktika perio charting (BPE scores, pocket depths) and restorative charting (surfaces treated, materials used) have no Pipedrive equivalent. We extract the most recent chart summary as human-readable text and attach it as a Pipedrive Note on the Patient Person record. Full historical chart data is preserved as an exported PDF attached to the Person.

Praktika recall intervals (e.g., 6-month hygiene recall, 12-month examination) cannot map to any native Pipedrive object. We migrate the next recall due date as a custom datetime field (Next_Recall_Date__c) on the Person and create a Pipedrive Task with due date set to the recall date and subject 'Patient Recall: [Patient Name]'. This requires manual activation in Pipedrive since automations do not migrate.

Praktika electronic forms and signed consent documents re-upload as Pipedrive Files attached to the corresponding Patient Person record. File size limits (25MB per file in Pipedrive) apply. Scanned or PDF consent forms preserve original timestamps, and file names retain the Praktika document ID prefix for traceability back to the source record during compliance audits.

Praktika provider records (dentist, hygienist, practice manager) match to Pipedrive Users by email address. Unmatched providers are flagged before migration; their Praktika records assign to a fallback Pipedrive User specified by the practice admin. Provider specialty (general dentist, specialist) migrates as a custom pick-list field on the User.

Praktika procedure codes (ADA dental codes, equipment codes) map to Pipedrive Products with name, code (mapped to Product code field), and standard price. Custom or practice-specific codes without a standard ADA equivalent create Products with the custom code as name and a flag indicating non-standard pricing.

Praktika patient insurance fund details (fund name, membership number, dependent status) have no Pipedrive native equivalent. We create custom fields on the Person record (Insurance_Fund__c, Insurance_Member_ID__c, Insurance_Group__c) and optionally link the fund as a minimal Organization if the practice uses the fund name for reporting.