Migrate from Praktika Australia to Freshsales

Praktika patients map directly to Freshsales Contacts. Every patient field (name, date of birth, address, contact details) copies to the Contact record. Praktika's patient ID is stored as Source_System_ID__c on the Freshsales Contact for traceability and delta-run de-duplication.

If a Praktika record represents a enquiry or consultation booking without a confirmed treatment, FlitStack stages those records as Freshsales Leads first. The Lead-to-Contact conversion is recommended post-migration when the patient confirms their first appointment in Freshsales.

Praktika practice locations (Single Location, 2 Locations, 3+ Locations tiers) map to Freshsales Account records. Each Account holds the clinic name, address, and HICAPS/Tyro terminal ID as custom fields. Multi-location practices generate multiple Account records with a custom Parent_Group__c field linking them.

Praktika appointments with a confirmed date and time map to Freshsales Events (for calendar visibility) or Tasks (for follow-up tracking). The appointment practitioner resolves to a Freshsales User by email. Cancelled appointments are logged as completed Tasks with a Cancelled status to preserve the record without cluttering the calendar.

Treatment plans contain procedure codes, clinical notes, and recommended intervals — these don't map to any native Freshsales object. FlitStack encodes each treatment plan as a long-text custom field (Treatment_Plan__c) on the Contact record, preserving procedure descriptions, codes, and practitioner recommendations in chronological order.

Praktika's Perio Charting and Restorative Charting data has no equivalent in Freshsales. FlitStack stores the charting snapshot as a structured-text custom field (Clinical_Charting__c) on the Contact record. Post-migration, the practice can either reference the field manually or export it to a clinical tool.

Praktika invoices and HICAPS/Tyro payment records have no native Freshsales equivalent. FlitStack exports the complete billing ledger as a structured CSV file and attaches it to the relevant Contact or Account record as a reference document. Practices rebuilding billing should integrate Xero or QuickBooks via Freshsales' marketplace.

Praktika's recall intervals (e.g. '6-month periodontal recall') map to Freshsales Tasks with a due_date calculated from the last treatment date plus the recall interval. Practices can rebuild automated recall reminders as Freshsales workflows on the Pro and Enterprise plans.

Praktika staff records (dentist, hygienist, receptionist roles) resolve to Freshsales Users by email address. The staff role in Praktika maps to Freshsales' user profile role and team assignment. Unmatched staff are flagged before migration; practices either invite them to Freshsales or reassign their records to a fallback user.

Praktika's fee schedule items and procedure codes map to Freshsales Products. Each product carries the item description, ADA code (mapped to a custom SKU field), and standard fee amount. Product-to-deal associations require a Freshsales Deal to exist first.

Praktika's SMS and communication logs against a patient record migrate as Freshsales Sales Activities (custom activity type 'SMS') or as Notes attached to the Contact. Original timestamps and direction (sent/received) are preserved in the activity description field.

Praktika custom fields created by the practice (e.g. Insurance Provider, Emergency Contact, Preferred Appointment Time) map to Freshsales custom fields of matching type (text, picklist, date, number). FlitStack creates the corresponding Freshsales custom field via the API before the migration batch runs. Field-level permissions are set to match Praktika's visibility configuration.