Migrate from Nookal to Salesforce Sales Cloud

Nookal patient records map 1:1 to Salesforce Contact records. The clinic itself is represented as a Salesforce Account; each Contact's AccountId links to that Account. Patients without a clinic association land on a default Account or one Account per Nookal location.

Nookal location records map to Salesforce Account records representing the clinic or practice. If Nookal has a single location, one Account is created; multiple locations create multiple Account records with the Nookal location ID preserved in a custom field for reconciliation.

Nookal practitioners who log in to the system map to Salesforce User records. Their Medicare provider numbers, AHPRA registration numbers, and specialisation fields have no Salesforce User standard field equivalent — these migrate as custom text fields (Provider_Number__c, Registration_Number__c, Specialisation__c).

Nookal appointment records map to Salesforce Event records. The practitioner becomes the Event Owner (UserId); the patient becomes the WhoId (Contact lookup). Appointment type, session length, and cancellation reason migrate as custom fields on Event since those are Nookal-specific properties.

Nookal appointment types (Initial Consultation, Standard Review, Telehealth, etc.) are mapped to a custom pick-list field (Appointment_Type__c) on the Event. Each unique Nookal type is created as a pick-list value; Salesforce admins confirm the final value set before migration runs.

Salesforce has no native invoice object. FlitStack creates a custom Invoice__c object with fields for invoice number, date, due date, total amount, GST amount, status, and a link to the patient Contact. Invoice status values are mapped from Nookal (Paid, Pending, Overdue) to Salesforce pick-list values on the custom object.

Nookal payment records map to a custom Payment__c object with a lookup to the Invoice__c record, payment method, amount, date, and Nookal payment ID. If the Nookal setup uses partial payments, each partial payment creates a separate Payment__c record linked to the same invoice.

Nookal Medicare/DVA claiming data — including claim ID, item numbers billed, provider number used, and claim status — has no Salesforce equivalent. These are migrated as custom fields on the relevant Contact (patient insurance reference) and Invoice__c (claim linkage). Medicare 2.0 compatibility fields are also surfaced as custom fields for re-integration planning.

Nookal clinical notes (treatment notes, SOAP notes, assessment records) are migrated to a custom Clinical_Note__c object with a lookup to the Contact (patient) and Event (appointment). Rich-text note content is stored in a Long Text Area field. If the note volume is low, Salesforce Notes are used instead.

Every migrated record receives a Source_System_ID__c text field storing the Nookal internal ID. This field enables delta-run de-duplication (if a record is re-processed, FlitStack matches on this ID rather than creating duplicates), audit traceability, and reconciliation between the Nookal export and Salesforce destination.

Nookal referrer records (external practitioners who refer patients) map to Salesforce Contact records with a custom Referrer_Type__c pick-list field set to 'External Referrer'. These Contacts are linked to patient Contacts via a custom junction object or the Account Contact Relation.

Nookal's accounting software sync connections are platform-level configurations, not data records. These do not migrate. The invoice and payment data they reference is already migrated to custom Salesforce objects. Teams must configure a fresh Xero or QuickBooks connector in Salesforce post-migration.