Skip to main content

Migrating from Zanda (Power Diary) to Praxi

This guide walks a Zanda (formerly Power Diary) practice through a complete move to Praxi. Praxi has a built-in Zanda CSV parser, so your client and appointment exports are mapped automatically.

Zanda and Power Diary are the same product Zanda is the current name for

the platform previously known as Power Diary. If you are on Power Diary, the same steps apply — the CSV export format is identical. :::


Who can run the migration​

  • Practice Owner
  • Practice Manager

You will need:

  • Administrator access to your Zanda account
  • An active Praxi account
  • Roughly 1–2 hours for a sole trader; 2–4 hours for a larger practice

What gets migrated​

DataStatus
Clients / contacts (demographics)Full — name, DOB, gender, contact details
Medicare numbers and IRNsFull where captured in Zanda
DVA and concession card detailsFull where captured in Zanda
NDIS plan informationFull where present in Zanda fields
Referral informationFull — referring practitioner and referral dates
Appointments (historical and upcoming)Full for the date range you export
PractitionersFull — name and provider numbers
Locations / sitesFull
Service typesFull
Clinical notesImported as participant documents or converted to Praxi format
InvoicesOff by default — enable in the wizard's entity selection if needed
Health fund detailsNot imported — reconfigure in Praxi billing after cutover
Start fresh with billing Praxi does not import Zanda invoices. Medicare

provider numbers, health fund details, and fee schedules need to be configured for Praxi's billing engine. Outstanding balances can be recorded manually. :::


What Zanda does not export via standard CSV​

Zanda's standard CSV export may not include:

  • Invoice and payment history — export invoices from Zanda's Reports section before cutover if you need a permanent record.
  • HICAPS / health fund claim history — reconcile any outstanding claims in Zanda before switching.
  • SMS and email message history — not included in the standard data export.
  • Online booking rules and availability — rebuild these in Praxi after cutover.
  • Appointment statuses beyond Attended / Did Not Attend — complex status history may not be fully preserved.

These are Zanda's export limitations, not Praxi's.


Step 1 — Reconcile in Zanda before cutover​

  1. Confirm no outstanding health fund or Medicare claims.
  2. Note any outstanding client balances you will want to record in Praxi.
  3. Plan a cutover window — after end-of-day is recommended.

Step 2 — Export your data from Zanda​

  1. Log in to Zanda as an administrator.
  2. Navigate to Settings > Data Management > Export (the exact path may vary by Zanda version).
  3. Export your client list as CSV. Zanda's client export includes contact details, referral information, and funding source fields.
  4. Export appointments separately — select your desired date range (we recommend 24 months back and 12 months forward).
  5. Export practitioners and locations if separate export options are available.
  6. Ensure all exported files use Australian date format (DD/MM/YYYY). Zanda defaults to this format.
  7. Save all files as UTF-8 CSV.

Step 3 — Open the Praxi import wizard​

  1. In Praxi, go to Settings > Data Migrations (or search "import" in the command palette with Cmd+K).
  2. Click New Import.
  3. Select Zanda as the source system.
  4. Upload your CSV files.

Praxi recognises Zanda's CSV column headers and maps them to Praxi fields automatically. Review the mapping preview, paying particular attention to fields highlighted in amber.


Step 4 — Review and validate​

Praxi validates all records before writing anything:

  • Medicare numbers — 10-digit checksum and IRN validated.
  • Phone numbers — normalised to Australian format (04XX XXX XXX).
  • NDIS numbers — format validated where present.
  • Duplicate detection — checked by Medicare number, email, mobile, or name
    • DOB.

Download the error report for any rows that fail, correct them, and re-upload.


Step 5 — Import in phases​

PhaseWhat to importWhy
1PractitionersClient records reference practitioner IDs
2LocationsAppointments reference location names
3Service typesAppointments reference service type names
4ClientsCore records — import these first
5AppointmentsRequire clients and practitioners to exist first
6Clinical notesRequire clients to exist first

Step 6 — Post-cutover verification​

After importing, verify:

  1. Spot-check 20 client records — confirm demographics and funding details match Zanda.
  2. Check record counts — compare total client count in Praxi against Zanda.
  3. Verify upcoming appointments — confirm dates and practitioner assignments for the next two weeks.
  4. Test search — search by client name, Medicare number, and email address.
  5. Configure billing — set up Medicare provider numbers and health fund details in Praxi before processing any claims.
  6. Test appointment reminders — send a test SMS or email to confirm notification routing is working.

After cutover​

  • Keep read-only access to Zanda for at least 3 months to cross-reference historical records.
  • Configure Praxi's Medicare online claiming before processing claims.

Rolling back​

If something goes wrong, you can roll back the import within 30 days:

  1. Go to Settings > Data Migrations > Import History.
  2. Find the import and click Rollback.

Rollback soft-deletes all records created by that import and does not affect records that existed in Praxi before the import.


Help​

  • Praxi onboarding: hey@praxi.au
  • In-app support: Help > Contact Support
  • General migration guide: Switching to Praxi
  • For Zanda export steps, refer to Zanda's own help centre

Was this page helpful?