Migrate your Nookal data
Practice management CRM for Australian allied health clinics with native Medicare claiming and per-practitioner pricing. Built for physios, OTs, and podiatrists who need diary, clinical notes, and billing in one place.
In its favor
Why people choose Nookal
The signal that keeps Nookal on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Per-practitioner pricing model means solo practitioners and small allied health clinics get affordable access without paying for unused seats, with unlimited staff on higher tiers.
Native Medicare and DVA Online Claiming 2.0 integration lets Australian health practices submit bulk-bill and client-reimbursement claims directly without a third-party middleware tool.
Accounting software sync with Xero and QuickBooks keeps financial records current without manual re-entry, a major time-saver for small practice bookkeepers.
Ease of use for non-technical staff reduces onboarding friction; multiple reviews cite the platform as accessible for team members who are not comfortable with technology.
Scheduling, clinical notes, and practice reporting in a single platform replaces the need to stitch together separate tools for diary management and billing.
Feature scope is narrow; practices needing patient engagement beyond reminders, social messaging, or AI-powered intake chatbots must layer in additional tools.
Limited accounting depth — Nookal handles invoicing and payments but does not produce completed accounting records on its own, requiring Xero or QuickBooks to close the loop.
Absence of a documented public API means practices with complex custom integrations or developer-dependent workflows hit a ceiling and must migrate manually.
Patient engagement features lag competitors; no WhatsApp or social channel integration and no native AI chatbot for handling patient enquiries at scale.
Growing practices report outgrowing the platform's customisation surface when they need advanced custom objects, complex automation, or multi-location scalability beyond what Nookal provides.
Reasons to switch
Why people leave Nookal
The recurring reasons buyers give for replacing Nookal. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Nookal fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Nookal pricing overview
Nookal charges per active practitioner per month at approximately $55/month. Additional costs apply per SMS message sent and per Medicare or DVA claim submitted. There is no free tier; the platform does not publish tier names above the base plan. Multi-location and multi-practitioner practices are billed per practitioner with no additional location fees.
Standard
Tier 1 of 3
$55/practitioner/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Nookal's schedule — see our quote-based pricing →
What gets migrated
Nookal object support
Object-by-object support for Nookal migrations. Per-pair details surface during scoping.
Patients
Fully supportedPatient records are the primary contact object in Nookal. Each Patient has a profile containing demographics, contact information, Medicare/DVA details, Australian Immunisation Register status, and clinical history. We map all standard patient fields 1:1 and flag any custom properties that require explicit value-mapping at the destination.
Practitioners
Fully supportedPractitioner profiles include name, provider numbers (required for Medicare claiming), provider type, and location associations. Multiple Provider Numbers per practitioner require specific handling when migrating claiming groups, particularly for practices with more than 20 provider numbers.
Locations
Fully supportedNookal supports multiple clinic Locations, each with its own address, contact details, and assignment of practitioners. We preserve location-level configuration and map practitioners to their correct locations at the destination.
Appointments
Fully supportedAppointments link a Patient to a Practitioner at a Location with a date, time, duration, and appointment type. We export full appointment history including cancellations and no-shows, preserving the original timestamps for reporting continuity at the destination.
Clinical Notes
Mapping requiredClinical notes are attached to appointments and contain structured clinical data relevant to the practice type (physiotherapy, OT, podiatry, etc.). Nookal allows custom note templates per practice, so field names and layouts vary between accounts. We map clinical note content and flag custom template structures that require destination-side reconfiguration.
Treatment Plans
Mapping requiredTreatment plans document a course of care for a patient including goals, interventions, and review dates. The schema supports custom fields per practice type. We export treatment plan content and flag custom fields for destination-side mapping.
Invoices
Fully supportedInvoices are generated at the appointment or itemised level and include line items, prices, and payment status. Nookal integrates with Xero and QuickBooks for accounting sync. We preserve full invoice history including line items, amounts, and payment allocation, noting any invoices pending sync to connected accounting software.
Payments
Fully supportedPayment records track what was paid against each invoice, including method (credit card, Medicare bulk bill, DVA, cash, eftpos) and date. We export payment history in full and map payment methods to equivalent fields at the destination.
Medicare and DVA Claims
Mapping requiredMedicare/DVA Online Claiming 2.0 is integrated into Nookal. Claims are tied to Provider Numbers and claiming groups. The Medicare 2.0 migration deadline of June 30, 2025 is critical: after migration, no further claim status updates apply to Medicare 1.0 claims. We export all claim history, separate active 1.0 claims from 2.0 claims, and flag the Medicare Minor ID association for each record.
Claims (Invoices)
Fully supportedBulk-bill claims submitted through Nookal create invoice records automatically. We export these with full claiming metadata including service type, item number, and claiming group. Pendable claims are identified and flagged for manual follow-up if not resolved before migration.
Custom Fields
Mapping requiredNookal supports custom fields on patient records, appointment types, and clinical note templates. Custom field definitions vary between accounts and are not exposed through a documented schema API. We identify and catalogue all custom fields during the scoping phase and map them explicitly to destination equivalents.
SMS Messages
Mapping requiredNookal includes SMS messaging with per-message pricing (approximately 10 cents per message with free replies). Message history and patient SMS preferences are stored but the export scope for SMS content depends on the account tier and data retention settings in force at time of migration.
Documents and Attachments
Mapping requiredDocuments can be attached to patient records and appointments. File attachments are stored within Nookal's file management system. We export attached files and associate them to the correct patient and appointment records at the destination, noting any size or format restrictions.
Practice Reports and Analytics
Mapping requiredNookal provides built-in reporting on appointments, billing, and business performance. Custom report configurations are account-specific. We export available report data and flag custom report layouts that need rebuilding at the destination.
Xero and QuickBooks Integration
Mapping requiredNookal syncs invoices and payments to Xero and QuickBooks via a built-in integration. The integration does not expose a raw export of accounting records in a format usable for migration to non-accounting platforms. We work with the source-side accounting export to map transactions into the destination's chart of accounts.
| Object | Support | Notes |
|---|---|---|
| Patients | Fully supported | Patient records are the primary contact object in Nookal. Each Patient has a profile containing demographics, contact information, Medicare/DVA details, Australian Immunisation Register status, and clinical history. We map all standard patient fields 1:1 and flag any custom properties that require explicit value-mapping at the destination. |
| Practitioners | Fully supported | Practitioner profiles include name, provider numbers (required for Medicare claiming), provider type, and location associations. Multiple Provider Numbers per practitioner require specific handling when migrating claiming groups, particularly for practices with more than 20 provider numbers. |
| Locations | Fully supported | Nookal supports multiple clinic Locations, each with its own address, contact details, and assignment of practitioners. We preserve location-level configuration and map practitioners to their correct locations at the destination. |
| Appointments | Fully supported | Appointments link a Patient to a Practitioner at a Location with a date, time, duration, and appointment type. We export full appointment history including cancellations and no-shows, preserving the original timestamps for reporting continuity at the destination. |
| Clinical Notes | Mapping required | Clinical notes are attached to appointments and contain structured clinical data relevant to the practice type (physiotherapy, OT, podiatry, etc.). Nookal allows custom note templates per practice, so field names and layouts vary between accounts. We map clinical note content and flag custom template structures that require destination-side reconfiguration. |
| Treatment Plans | Mapping required | Treatment plans document a course of care for a patient including goals, interventions, and review dates. The schema supports custom fields per practice type. We export treatment plan content and flag custom fields for destination-side mapping. |
| Invoices | Fully supported | Invoices are generated at the appointment or itemised level and include line items, prices, and payment status. Nookal integrates with Xero and QuickBooks for accounting sync. We preserve full invoice history including line items, amounts, and payment allocation, noting any invoices pending sync to connected accounting software. |
| Payments | Fully supported | Payment records track what was paid against each invoice, including method (credit card, Medicare bulk bill, DVA, cash, eftpos) and date. We export payment history in full and map payment methods to equivalent fields at the destination. |
| Medicare and DVA Claims | Mapping required | Medicare/DVA Online Claiming 2.0 is integrated into Nookal. Claims are tied to Provider Numbers and claiming groups. The Medicare 2.0 migration deadline of June 30, 2025 is critical: after migration, no further claim status updates apply to Medicare 1.0 claims. We export all claim history, separate active 1.0 claims from 2.0 claims, and flag the Medicare Minor ID association for each record. |
| Claims (Invoices) | Fully supported | Bulk-bill claims submitted through Nookal create invoice records automatically. We export these with full claiming metadata including service type, item number, and claiming group. Pendable claims are identified and flagged for manual follow-up if not resolved before migration. |
| Custom Fields | Mapping required | Nookal supports custom fields on patient records, appointment types, and clinical note templates. Custom field definitions vary between accounts and are not exposed through a documented schema API. We identify and catalogue all custom fields during the scoping phase and map them explicitly to destination equivalents. |
| SMS Messages | Mapping required | Nookal includes SMS messaging with per-message pricing (approximately 10 cents per message with free replies). Message history and patient SMS preferences are stored but the export scope for SMS content depends on the account tier and data retention settings in force at time of migration. |
| Documents and Attachments | Mapping required | Documents can be attached to patient records and appointments. File attachments are stored within Nookal's file management system. We export attached files and associate them to the correct patient and appointment records at the destination, noting any size or format restrictions. |
| Practice Reports and Analytics | Mapping required | Nookal provides built-in reporting on appointments, billing, and business performance. Custom report configurations are account-specific. We export available report data and flag custom report layouts that need rebuilding at the destination. |
| Xero and QuickBooks Integration | Mapping required | Nookal syncs invoices and payments to Xero and QuickBooks via a built-in integration. The integration does not expose a raw export of accounting records in a format usable for migration to non-accounting platforms. We work with the source-side accounting export to map transactions into the destination's chart of accounts. |
Gotchas
What to watch for in Nookal migrations
Issues we've hit on past Nookal migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Medicare 2.0 migration deadline is hard-gated
No public API forces reliance on built-in exports
Custom clinical note templates are account-specific
Medicare claiming groups tied to Provider Numbers restrict bulk migrations
Accounting sync does not export raw ledger data
| Severity | Issue |
|---|---|
| High | Medicare 2.0 migration deadline is hard-gated |
| High | No public API forces reliance on built-in exports |
| Medium | Custom clinical note templates are account-specific |
| Medium | Medicare claiming groups tied to Provider Numbers restrict bulk migrations |
| Medium | Accounting sync does not export raw ledger data |
Leaving Nookal?
Where Nookal customers move next
12 destinations Nookal can migrate to.
How a Nookal migration works
Four steps, Nookal-specific
Connect
Not publicly documented into Nookal. Scopes limited to read-only on the data we move.
Map
We translate Nookal-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Nookal quirks before production.
Migrate
Full migration with Nookal rate-limit handling. Rollback available throughout.
FAQ
Nookal migration FAQ
Answers to the questions buyers ask most during Nookal migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Nookal migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Nookal.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Nookal setup and destination — written quote back within a business day.