ZavyLogoZavy360

← Back to Blog

Switching Dental Software: The Complete Checklist for Australian Practices

13 min readdental-practice-management
Scott Rotton

Scott Rotton

Founder & CEO, Zavy360

Founder, Zavy360 Dental Practice Management | Experience partnering with 50+ Australian dental practices

Switching dental practice management software is one of the biggest operational decisions a practice owner makes. It affects every team member, every patient interaction, and every workflow in your practice. Get it right, and the transition leads to better efficiency, better data, and a platform that grows with you. Get it wrong, and you face weeks of disruption, frustrated staff, and potentially lost patient data.

Many Australian practices are weighing this decision right now. Some run software installed on a server in the practice, and that server eventually needs replacing. Others already use a cloud system but have outgrown it, or want features such as online booking, automated recalls or multi-site management to work differently from how their current system handles them.

This guide provides a structured, phased checklist for Australian dental practices planning to switch software. Whether you are moving from server-based software to the cloud or switching between cloud systems, these steps will help you manage the transition with minimal disruption to your patients and team.

Before You Start: Evaluating Whether to Switch

Before committing to a migration, be honest about whether switching is the right decision for your practice right now. A software migration is an investment of time, money, and team energy. It should solve real problems, not just satisfy curiosity about a newer system.

Signs Your Current Software Is Holding You Back

  • Hardware dependency: Your server is more than four years old, and your IT provider has flagged it for replacement.
  • Feature gaps: You cannot offer online bookings, automated SMS recalls, or digital treatment plans because your current system does not support them.
  • Support decline: Response times from your current vendor have lengthened, or they have stopped developing new features for your product tier.
  • Multi-site limitations: You have opened (or plan to open) a second location, and your current system cannot manage multiple sites from a single platform.
  • Integration gaps: Your system does not integrate with HICAPS, Tyro, or other tools your team relies on without manual workarounds.

If three or more of these apply, a switch is worth evaluating seriously. For a detailed look at what to compare across platforms, see our dental software comparison guide.

Questions to Ask Before Committing

  1. Can our current vendor address our concerns with an upgrade or configuration change?
  2. Do we have the team capacity to manage a migration in the next quarter?
  3. What is our budget for the transition (including temporary productivity loss during the learning curve)?
  4. Who will own the migration project internally?

Phase 1: Planning Your Migration (4-6 Weeks Before Go-Live)

A successful migration starts with thorough planning. Rushing this phase causes problems that are hard to fix after go-live.

Document Your Current Workflows

Before you can set up a new system, you need to understand how your team actually uses the current one. Map out the key workflows for each team role:

  • Front desk: How are appointments booked, confirmed, and rescheduled? How are recalls managed? What is the patient check-in process?
  • Clinical: How are treatment plans created and presented? How is charting done? What imaging integrations are used?
  • Management: What reports are run weekly and monthly? How is end-of-day reconciliation performed? How are health fund claims processed?

Document these workflows, not as you think they should work, but as they actually work today. This becomes your configuration guide for the new system.

Identify Must-Have vs Nice-to-Have Features

Create two lists. The must-have list includes features your practice cannot operate without: HICAPS claiming, appointment scheduling, clinical charting, patient records, and reporting. The nice-to-have list includes features you want but could phase in later: online bookings, patient communication automation, advanced analytics.

Review your new provider's feature set against both lists. Every must-have should be confirmed as available and tested before you commit.

Evaluate Data Export Options from Your Current System

If your current software is installed on a server in your practice, the data sits on your own server and your new provider can usually work from a copy of it. If it is a cloud system, ask the vendor how to request a full export, what format it comes in and whether there is a fee. Either way, understand what formats are available (CSV, XML, proprietary database dumps) and what data is included. Key data categories to verify:

  • Patient demographics and contact details
  • Treatment history and clinical notes
  • Appointment history
  • Outstanding treatment plans
  • Financial records and account balances
  • Documents and attachments stored in the practice software (radiographs held in separate imaging software stay there and are re-linked to the new system)
  • Recall dates and intervals (ask whether they will be carried over or recalculated from each patient's last exam)
  • Past SMS and email history, which often does not transfer, so plan to keep the old system accessible if you need it

Some vendors make data export straightforward. Others take longer, charge a fee, or only export some data categories. Know what you are dealing with early, as this directly affects your migration timeline.

Set a Realistic Timeline

Many practices choose an early-week go-live so the team has the rest of the week to settle in while support is on hand. Avoid your own busiest weeks, school holidays (often busier for family appointments) and the end of the financial year (accounting complexity), and do not plan a go-live for a week when key staff are on leave.

As a rough guide, allow one to two months from decision to go-live for a single-site practice, and longer for a group. Ask your new provider for their typical timeline.

Phase 2: Data Migration (Trial 2-4 Weeks Before, Final at Go-Live)

Data migration is the most technically critical phase. This is where patient records, financial history, and clinical data move from your old system to your new one.

Plan for two exports. A trial export 2-4 weeks before go-live lets your new provider migrate the data so you can review it together before sign-off. A final export, taken when the old system is frozen at go-live, lets the new provider migrate everything entered since the trial export, so no appointments, payments or notes are lost.

What Data to Migrate

Ask your new provider to bring across the full record in one migration: patient details, clinical notes and treatment history, appointments, treatment plans, invoices and payments, and attachments. Account balances are worked out from the invoice and payment history, so the two have to move together. If you decide to leave very old records behind, check the retention rules that apply in your state (in NSW, Victoria and the ACT, at least seven years after the last visit for adults and until age 25 for patients treated as children) and make sure those records stay accessible for that period.

Australian Privacy Act Considerations for Data Transfer

Under the Privacy Act 1988, APP 11 requires you to take reasonable steps to protect patient information, and that includes during a migration. In practice, that means:

  • Transfer data securely, with encryption in transit
  • Limit access to data during migration to authorised personnel
  • Make sure both your outgoing and incoming providers have documented data handling procedures
  • If anyone outside Australia, such as an overseas migration contractor, will receive or be able to access patient data during the migration, APP 8 cross-border disclosure obligations apply. Ask both providers where the data will be handled.

Your new provider should be able to explain their data migration security practices clearly. If they cannot, that is a warning sign.

Testing Migrated Data for Accuracy

After the trial migration, do not assume the data is correct. Systematically verify:

  1. Select ten active patients seen by different practitioners and compare every field in the new system against the old
  2. Verify that financial balances match for at least twenty accounts
  3. Confirm that upcoming appointments transferred with correct dates, times, practitioners, and appointment types
  4. Check that recall schedules are intact and will trigger at the correct intervals
  5. Verify that clinical notes and treatment history are readable and complete

About Smiles, which operates five clinics across Sydney, first chose Zavy360 for a new clinic and later moved its other clinics across from D4W and Praktika. Bringing several clinics onto one system is exactly where careful, record-by-record verification pays off.

Phase 3: Staff Training and Go-Live (1-2 Weeks Before)

Your software is only as effective as the team using it. Underinvesting in training makes a transition much harder.

Training Sessions by Role

Different team members need different training. A one-size-fits-all session wastes time and leaves gaps:

  • Front desk: Appointment scheduling, patient check-in/check-out, recalls, payment processing, HICAPS claiming, phone call workflows
  • Clinical staff: Charting, treatment planning, clinical notes, imaging integration, prescription workflows
  • Practice managers: Reporting, end-of-day procedures, user management, system configuration, financial reconciliation
  • Practice owners: Dashboard overview, key reports, system administration, practitioner performance metrics

Ask your new provider how long each session runs and what self-paced training is available.

Schedule the main training in the week before go-live, not weeks before, and book a follow-up session for the first week or two after go-live. People forget what they do not use immediately.

Running Parallel Systems During Transition

Keep your old system accessible (read-only) as a reference for at least the first few weeks after go-live, and for as long as the retention rules require if any records were not migrated. This gives your team a safety net: if they cannot find a patient's historical treatment note in the new system, they can look it up in the old one while the data migration is verified.

Do not run both systems actively (entering data into both). This doubles the workload and creates data integrity issues. The old system is a reference, not a backup workflow.

Verify HICAPS and Tyro Integration

Before go-live, run a small real health fund claim through HICAPS from the new system (for example on a staff member's card) and cancel it the same day, and process a small Tyro payment and refund it. Do not wait until the first patient is standing at the desk. Confirm that health fund claiming and EFTPOS payments work correctly with your specific hardware and, if you claim CDBS or other Medicare items, that Medicare claiming works through your terminal.

Learn more about how Zavy360 handles the onboarding process for Australian practices, from data migration to go-live support.

Phase 4: Post-Migration Verification (First 2 Weeks)

The go-live is not the finish line. The first two weeks are when issues surface and need to be resolved quickly.

What to Verify After Switching

  • Patient data accuracy: spot-check records daily for the first week
  • Automated recalls: confirm that recall SMS and emails are being sent at the correct intervals
  • Financial reconciliation: compare end-of-day totals against your bank and HICAPS settlement reports
  • Appointment reminders: verify that patients are receiving confirmations and reminders
  • Imaging integration: confirm that new images are saving and existing images are accessible
  • Report accuracy: run your standard weekly reports and compare outputs to expectations

Common Issues and How to Resolve Them

  • Missing patient data: Usually caused by a migration mapping error. Report to your provider with specific patient IDs for correction.
  • Incorrect appointment types: Colour coding or appointment categories may not have mapped perfectly. Adjust configuration settings.
  • HICAPS claiming errors: Often caused by incorrect provider numbers in the new system. Verify provider number configuration for every practitioner.
  • Staff reverting to old habits: Normal. Encourage the team to use the new system for everything and only reference the old system for historical lookups.

When to Contact Support

Contact your new provider's support team immediately for: data discrepancies affecting patient care, HICAPS or payment processing failures, system access issues, and anything that prevents a patient from being seen. Do not try to work around clinical or financial issues yourself.

The Complete Switching Checklist

This consolidated checklist covers every step from evaluation to post-migration verification. Use it as a practical tracking tool for your migration project.

Planning Phase (4-6 weeks before):

  1. Document current workflows for front desk, clinical, and management teams
  2. Create must-have and nice-to-have feature lists
  3. Confirm how a full data export will be produced (from your own server or by your cloud vendor)
  4. Evaluate data export formats and completeness
  5. Set go-live date (avoid peak periods)
  6. Assign internal migration project owner
  7. Confirm new provider's migration support process

Data Migration Phase (2-4 weeks before):

  1. Provide a trial data export to your new provider for review
  2. Review the trial migration with your new provider before sign-off
  3. Verify ten patient records field by field
  4. Verify twenty financial account balances
  5. Confirm appointment data accuracy
  6. Check recall schedule integrity
  7. Sign off on data migration accuracy

Training and Go-Live Phase (1-2 weeks before):

  1. Schedule role-specific training sessions
  2. Complete front desk training
  3. Complete clinical staff training
  4. Complete practice manager training
  5. Complete practice owner orientation
  6. Test HICAPS claiming with a real claim, then cancel it the same day
  7. Test Tyro EFTPOS processing
  8. If you claim CDBS or other Medicare items, test Medicare claiming through your terminal
  9. Set old system to read-only on go-live date
  10. Take a final data export when the old system is frozen, so the new provider can migrate everything entered since the trial export

Post-Migration Phase (first 2 weeks):

  1. Daily spot-check of patient data accuracy
  2. Verify automated recall delivery
  3. Compare end-of-day financial reconciliation
  4. Confirm appointment reminder delivery
  5. Verify imaging integration
  6. Run standard weekly reports and compare
  7. Schedule two-week review meeting with provider

Moving Forward with Confidence

Switching dental software is a significant undertaking, but it is entirely manageable with proper planning, realistic timelines, and the right support from your new provider. The practices that have the smoothest transitions are the ones that invest time in the planning phase, train their teams thoroughly, and verify data methodically rather than assuming everything transferred correctly.

If you are still evaluating which platform to move to, our cloud dental software guide covers what to look for in a cloud-based dental practice management system, including Australian compliance, payment integration, and feature comparison.


Planning a switch and want to see how the migration process works? Book a free demo and we will walk you through how Zavy360 handles data migration, HICAPS setup, and staff onboarding for Australian practices.

switching-dental-softwaredental-software-migrationpractice-managementaustralian-dental

Ready to get started?

Book your free demo.