Migrate from Praktika Australia to monday CRM

Praktika patient records map directly to Monday CRM Contact items on a dedicated People board. The patient's name, email, phone, and address fields translate to Monday's default Name, Email, Phone, and Location columns. Praktika's internal patient ID is stored as a custom text column (praktika_patient_id__c) for traceability and delta-run matching.

Date of birth, health fund details, NHS number, and Praktika's recall date fields have no Monday CRM native equivalent. We create custom columns — Date, Text, and Text respectively — on the People board to preserve this context. Clinical charting and periodontal data are surfaced as long-text notes fields since Monday has no structured clinical record type.

Praktika treatment plans with procedure codes, itemised fees, and stage (proposed, in-progress, completed) become Monday Deal items on a Deals board. The deal Name is constructed from the patient name + plan date. Total fee maps to the Amount column. Stage maps to a Status column with values aligned to Praktika's treatment plan statuses. The Praktika plan ID is preserved as a custom text column.

Each procedure line within a Praktika treatment plan — procedure code, description, fee, and status — becomes a Subitem attached to the corresponding Monday Deal item. The Subitem inherits a link back to the parent Contact (patient). This preserves the itemised treatment structure within Monday's relational model.

Praktika appointment records (date, time, type, duration, clinician) are aggregated and linked to the patient Contact record via a custom Date column and a long-text Clinical Notes column. Monday has no native appointment object; appointment history is stored as structured text so staff can reference it at the patient record level. Upcoming appointments can be surfaced via a Date column with automation triggers.

Praktika account balances, last payment amounts, and outstanding invoice flags map to custom number and status columns on the patient Contact item. This gives the practice a financial snapshot within the patient record without a separate billing board. The mapping preserves payment history for reference during follow-up calls or collections workflow.

Praktika invoices — invoice number, date, line items, total, status, and HICAPS/Tyro reference — become items or subitems on a dedicated Invoices board linked to the patient Contact. A URL column stores a reference back to the original Praktika invoice record. HICAPS/Tyro transaction IDs do not migrate (incompatible with Monday's payment model).

Praktika's recall date per patient maps to a custom Date column (recall_due_date__c) on the Contact. A Status column (recall_status__c) tracks whether the recall has been actioned. Monday automation recipes can then trigger email or in-app notifications when the recall date is reached — a rebuilt equivalent of Praktika's automated recall SMS workflow.

Monday CRM has no clinical record type. Praktika's periodontal charting, restorative notes, intraoral imaging references, and sterilisation logs cannot be stored structurally in Monday. We preserve the raw text content of clinical notes in a long-text column (clinical_notes__c) so staff retain the context at the patient record level without losing the data entirely.

HICAPS and Tyro real-time health fund claim processing at the chairside terminal is a Praktika-specific integration with no Monday CRM equivalent. This integration cannot migrate. Practices must source a separate, Monday-compatible payment terminal integration post-migration if real-time health fund claims are required.

Praktika appointment reminders, SMS recall sequences, and billing alert workflows are automation logic, not data records. They do not export as migration-ready artefacts. We document each automation trigger and action from Praktika and deliver a rebuild brief so your Monday admin can recreate the logic as Monday automation recipes.