Migrating from Halaxy to Praxi
This guide walks a Halaxy-using practice through a complete move to Praxi. Praxi has a built-in Halaxy parser for CSV exports, and also supports a FHIR R4 connection where Halaxy makes this available for your account.
Who can run the migration
- Practice Owner
- Practice Manager
You will need:
- Administrator access to your Halaxy account
- An active Praxi account
- Roughly 1–2 hours for a sole trader; 2–4 hours for a larger practice
What gets migrated
| Data | Status |
|---|---|
| Clients / patients (demographics) | Full — name, DOB, gender, contact details |
| Medicare numbers and IRNs | Full |
| DVA and concession card details | Full where exported by Halaxy |
| NDIS plan information | Full where present in Halaxy fields |
| Referring practitioners | Full — GP name and provider number |
| Appointments (historical and upcoming) | Full for the date range you export |
| Practitioners and AHPRA numbers | Full |
| Locations / sites | Full |
| Service types | Full |
| Clinical notes | Imported as participant documents or converted to Praxi format |
| Invoices | Off by default — enable in the wizard's entity selection if needed |
| Health fund and claiming details | Not imported — reconfigure in Praxi billing after cutover |
configurations — Medicare provider numbers, health fund details, payment gateways — need to be set up for Praxi's engine anyway. Outstanding balances can be recorded manually. :::
What Halaxy does not export via standard CSV
Depending on your Halaxy version and subscription tier, the standard data export may not include:
- Detailed HICAPS / health fund claim history — reconcile outstanding claims before cutover.
- Invoice and payment history — export invoices to PDF from Halaxy's Reports section if you need a permanent record.
- SMS / email message history — not included in the standard patient export.
- Online booking configuration — rebuild your booking rules in Praxi after cutover.
These are Halaxy's export limitations, not Praxi's. A FHIR R4 connection (where available on your Halaxy account) transfers a richer dataset — see below. Contact us at hey@praxi.au and we will confirm what can come across for your specific account.
Step 1 — Reconcile in Halaxy before cutover
- Run end-of-day reconciliation and confirm no outstanding health fund or Medicare claims.
- Note any outstanding client balances you will want to record in Praxi.
- Plan a cutover window — after end-of-day is recommended.
Step 2 — Export your data from Halaxy
Option A — CSV export (all plans)
- Log in to Halaxy as a practice administrator.
- Go to Settings > Data Export (exact menu path may vary by Halaxy version).
- Export your patient list as CSV — this includes demographics, contact details, and funding source information.
- Export appointments separately, selecting your desired date range (we recommend 24 months back and 12 months forward).
- Export practitioner details separately.
- Save all files as UTF-8 CSV. Halaxy exports use Australian date format (DD/MM/YYYY) by default, which Praxi expects.
Option B — FHIR R4 connection (planned)
A direct FHIR R4 transfer from Halaxy — pulling a richer dataset including structured clinical data — is in development but not yet available in the import wizard. If your Halaxy account has FHIR access and you'd like to use this path, contact us at hey@praxi.au to discuss timing; otherwise use the CSV export above.
Step 3 — Open the Praxi import wizard
- In Praxi, go to Settings > Data Migrations (or search "import" in the command palette with Cmd+K).
- Click New Import.
- Select Halaxy as the source system.
- Upload your CSV files (a single ZIP bundle routes each file automatically).
Praxi recognises Halaxy's CSV headers automatically and maps them to Praxi fields. You will see a mapping preview with confidence scores — review any amber-highlighted fields before proceeding.
Step 4 — Review and validate
Praxi runs a full validation pass before importing any records:
- Medicare numbers — 10-digit checksum and IRN validated.
- Phone numbers — normalised to Australian format.
- DVA numbers — format and card type (Gold/White/NLHC) validated.
- Duplicate detection — checked by Medicare number, email, mobile, or name
- DOB.
Download the error report for any rows that fail, correct them in the CSV, and re-upload.
Step 5 — Import in phases
| Phase | What to import | Why |
|---|---|---|
| 1 | Practitioners | Client records reference practitioner IDs |
| 2 | Locations | Appointments reference location names |
| 3 | Service types | Appointments reference service type names |
| 4 | Clients | Core records — import these first |
| 5 | Appointments | Require clients and practitioners to exist first |
| 6 | Clinical notes | Require clients to exist first |
Step 6 — Post-cutover verification
After importing, verify:
- Spot-check 20 client records — confirm demographics and Medicare details match Halaxy.
- Check record counts — compare total client count in Praxi against Halaxy.
- Verify upcoming appointments — confirm dates and practitioner assignments for the next two weeks.
- Test search — search by name, Medicare number, and email.
- Configure billing — set up Medicare provider numbers, health fund details, and gap fees in Praxi before processing any claims.
- Send a test appointment reminder — confirm SMS and email routing.
After cutover
- Keep read-only access to Halaxy for at least 3 months to cross-reference historical records and invoices.
- Configure Praxi's Medicare online claiming (Tyro Health Online integration) before processing Medicare claims.
Rolling back
If something goes wrong, you can roll back the import within 30 days:
- Go to Settings > Data Migrations > Import History.
- Find the import and click Rollback.
Rollback soft-deletes all records created by that import. It 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 Halaxy export steps and FHIR availability, refer to Halaxy's own help centre