
Aesthetic Clinic Software Migration Checklist for Australian Clinics
Moving clinic software is safest when you treat it as a records project, not an IT task. Inventory what you hold, confirm what your current provider can export, map every field, test with a small sample, reconcile it, then agree a cutover day. This checklist walks through each step in that order, separates general migration advice from what ZibaDesk does, and lists what to confirm with any vendor before you sign.
It is written for Australian aesthetics clinic owners and practice managers. It does not promise automatic imports, zero downtime or regulatory compliance, because no checklist can. What it gives you is a way to find the gaps before your clients do.
TL;DR
- Start with an inventory of records, consent forms, treatment notes, photos, memberships and deposits, then ask your current provider in writing which export formats it supports.
- Map old fields to new ones, test with a small sample set, and reconcile counts and spot-checked records before anything goes live.
- Health information is sensitive under the Australian Privacy Principles, so plan secure transfer, access permissions and destruction of old copies.
- Run old and new systems in parallel for a short period, and agree a freeze time and a rollback plan for cutover day.
- Before committing to ZibaDesk, confirm in writing how your export file will be handled. The consent and treatment record suite is on the Ultra plan only.
Table of Contents
- Why a checklist matters before you switch
- Step 1: Name who decides and who does the work
- Step 2: Inventory your records and consent
- Step 3: Confirm export formats with your current provider
- Step 4: Map fields and clean before you move
- Step 5: Secure the transfer and plan access
- Step 6: Test bookings, deposits and payments
- Step 7: Pilot, reconcile and spot-check
- Step 8: Agree the cutover
- Illustrative worked example
- What to verify with ZibaDesk before committing
- Try ZibaDesk before you move everything
- FAQ
- Sources
Why a checklist matters before you switch
Most migration problems are not technical. They are questions nobody asked early: who owns the data, which format it leaves in, and what happens to signed consent forms that do not fit a spreadsheet.
Alma Lasers Australia argues that clinics often choose software backwards, starting with demos instead of requirements. Its suggested order is to write down your non-negotiables, test the migration with a real export, check who owns the data and how to get it out, price the whole arrangement, and run a fortnight in parallel before switching off the old system. That order is a sound backbone for the checklist below.

Step 1: Name who decides and who does the work
A migration with no owner drifts. Before you touch any data, write down:
- The decision maker, usually the clinic owner or practice manager, who signs off each stage.
- The person who runs the export and import work, who might be you, a staff member or an IT contractor.
- The clinical lead, who confirms that treatment records and consent history are complete enough to rely on.
- Your contact at the old provider and at the new one, with a phone number and an agreed response time.
A readiness checklist from Podium IT recommends naming decision makers, agreeing what is in scope (sites, users, records, templates, billing, appointments, reporting and integrations), confirming dates and old-system access, and keeping one risk register that records decisions, dependencies, open questions, owners and due dates. A shared spreadsheet is enough. The point is that every open question has a name and a date next to it.
Step 2: Inventory your records and consent
List everything the old system holds, by category, with an approximate count for each. Do this before you look at any new product, because the inventory becomes your requirements list.
| Category | What to record | Question to answer |
|---|---|---|
| Client details | Contact details, preferences, referral source | Are there duplicates or incomplete profiles? |
| Health questionnaires | Completed pre-visit forms | Are they stored as structured data or attached files? |
| Consent forms | Signed forms, photo consent, dates | Can signed copies be exported as files with dates intact? |
| Treatment notes | Per-visit notes, treatment charts, injection maps | Do notes export as text, PDF or not at all? |
| Clinical photos | Before and after images | Are images exportable in original quality, linked to the right client? |
| Appointments | Past and future bookings | Which future bookings must be re-created? |
| Billing | Invoices, deposits, memberships, gift vouchers | Which balances and recurring plans are still active? |
| Templates | Forms, reminder wording | Which are worth rebuilding? |
Mark each row as must move, archive only or leave behind. Clinical records are usually the “must move or archive” group. Marketing lists and old reminder templates are often the “rebuild” group.
What counts as health information
Your inventory is also a privacy exercise. The OAIC’s Australian Privacy Principles guidelines define health information to include notes of symptoms or diagnosis and the treatment given, as well as appointment and billing details. That means much of what an aesthetic clinic holds is sensitive health information, and it should be handled that way throughout the move. Confirm your specific obligations with your adviser, and see the OAIC for current guidance. If your clinic holds records tied to a registered practitioner’s obligations, AHPRA and your professional body are the places to check practitioner-specific expectations.
Step 3: Confirm export formats with your current provider
Ask your current provider for the answers in writing. Do not assume the “export” button covers everything.
Questions to put to them:
- Which data types can be exported: clients, appointments, notes, consent forms, photos, invoices, memberships?
- In which formats (CSV, PDF, image files, a database dump)?
- Are consent forms and treatment notes exported as individual files, and are they named or indexed by client?
- Are photos exported at original resolution with their dates?
- Is there a fee for exports, and how long does one take?
- How long will you keep access to the old system after you cancel?
- How is your data retained or deleted after you leave?
Alma Lasers also recommends asking each vendor to import a real export of your patient list, appointment history and outstanding treatment plans before you sign, and checking how the system handles privacy obligations and data retention. Apply that to every product on your shortlist, including ZibaDesk.
Step 4: Map fields and clean before you move
Cleaning first is cheaper than cleaning afterwards. Take your export and:
- Merge duplicate clients and fix obviously broken contact details.
- Standardise date formats, phone number formats and name fields (one column for given name, one for family name).
- Decide how to handle fields that have no home in the new system, such as free-text “notes” columns. Often the safest choice is to keep them as an attached document on the client record.
- Build a field map: a two-column table of old field name against new field name, with a note where a value needs converting.
The CleverOps healthcare data migration checklist breaks this into planning (scope, source audit, field mapping, data owner sign-off), data preparation (backups, duplicates, required fields, lookup values) and a 50 to 100 record test set. You do not have to follow its full template, but the idea of a defined test set is worth borrowing.
Step 5: Secure the transfer and plan access
Because the files contain health information, treat the export itself as a risk.
- Send export files through an encrypted or access-controlled channel, never by ordinary email attachment or a shared personal drive link.
- Keep one controlled working copy, and record who has access to it.
- Take a full backup of the old system before any import, and store it separately.
- Plan permissions in the new system: who sees clinical notes, who sees only bookings and payments, who can export records. Reception staff rarely need treatment notes.
- Decide what happens to temporary copies once the move is finished.
On that last point, APP 11 requires reasonable steps to protect personal information and, where it is no longer needed and not required to be kept by law, to destroy or de-identify it. The AMA privacy code for private-sector medical practitioners summarises that principle. Retention periods for health records vary by state and by circumstance, so confirm how long you must keep records with your adviser before deleting anything, including the old system’s copies.
Step 6: Test bookings, deposits and payments
Clinical records get most of the attention, but a broken booking flow costs you revenue the first morning. Before cutover, run through:
- A new online booking from a client’s perspective, including the confirmation message.
- A deposit taken at booking, and how it shows on the invoice at the visit.
- A card payment and, if you use it, an EFTPOS payment.
- A reminder sent by SMS, WhatsApp or email.
- A recurring membership charge, if you sell memberships.
- A refund or a cancellation within your policy.
Check each result against your bookkeeping. If you use Xero, confirm what is synced and when, and check the output with your accountant or adviser before you rely on it for BAS or tax reporting. The ATO is the authority on your tax obligations, and your adviser should confirm that the new setup supports them.
Step 7: Pilot, reconcile and spot-check
Never run the full import first. Use a small pilot, then compare.
A Halaxy migration project described by Lunaris shows one careful approach: patient matching compared existing IDs, dates of birth, contact details and record relationships before accepting a match, started with a 10-patient pilot, and sent uncertain matches for human review instead of guessing. You can apply the same principle at clinic scale: uncertain matches go to a person.
In practice:
- Reconcile counts. Number of clients, appointments, consent forms and photos in the old system against the new one.
- Spot-check records. CleverOps suggests spot-checking 20 records at production migration. Choose a mix: a long-standing client, a recent one, one with several treatments, one with a membership.
- Check relationships. Does each consent form and each photo sit on the right client? Does each treatment note link to the right visit?
- Log every issue with an owner and a date, then fix and retest.
- Do not proceed until the sample passes. Tregovia’s clinic migration checklist takes the same staged approach: test migration, sample validation, then proceed only when validation passes.
Handling missing, duplicated or inaccessible records
- Missing: keep the old system accessible and read-only until you have confirmed the gap. Re-export that category if needed, or attach the original file to the client record.
- Duplicated: merge in the new system only after a person confirms they are the same client. Never merge on name alone.
- Inaccessible: a file that will not open is a problem to find now, not during a client visit. Ask the old provider for a re-export in another format, and keep a dated note of what was requested.
Step 8: Agree the cutover
Cutover is a short, planned event. NetLuma’s clinic server migration guidance describes the pattern: agree when users stop making changes, capture the final backup or sync point, then validate record counts, permissions, appointments, billing and interfaces before general access resumes. It also advises confirming tested backups, agreeing a downtime workflow, and having vendor availability and a contact tree ready.
A practical cutover plan:
- Choose a quiet window, such as a day with fewer bookings, and tell clients if bookings will be affected.
- Set a freeze time after which nobody edits the old system.
- Take the final export and backup, then import and reconcile again.
- Prepare a paper fallback for the first day, such as printed consent forms, so treatments are not held up if something is wrong.
- Brief the team on logins, where to find things and who to call.
- Keep the old system read-only for the parallel period. Alma Lasers suggests around a fortnight in parallel before switching off the old system.
- Restrict and then close access to the old system once you have signed off the new one.
Illustrative worked example
This example is illustrative only. The numbers are invented to show the method and do not describe any real clinic or ZibaDesk customer.
A two-room skin clinic plans to move on a Monday, its quietest day.
| When | Task | Owner | Pass condition |
|---|---|---|---|
| Week 1 | Inventory records, request export formats in writing | Practice manager | Written reply from current provider |
| Week 2 | Clean duplicates, build field map | Practice manager | Map signed off by owner |
| Week 3 | Import a 50-record test set, check 20 | Practice manager and clinical lead | Counts match, 20 of 20 correct |
| Week 3 | Test booking, deposit, card payment, reminder | Reception lead | Each appears correctly in sales |
| Week 4 | Freeze Friday evening, final export, import, reconcile | Practice manager | Counts match, permissions checked |
| Weeks 5 and 6 | Parallel period, old system read-only | Owner | No missing records raised |
| Week 7 | Close access to old system after backup is stored | Owner | Sign-off recorded |
If the 20-record check fails at week 3, the clinic fixes the field map and retests. It does not move to week 4.
What to verify with ZibaDesk before committing
This section is specific to ZibaDesk. Everything above is general advice that applies to any provider.
What ZibaDesk includes for clinics. On the Ultra plan, the aesthetics clinic suite includes consent forms with e-signature and photo consent, pre-visit health questionnaires, per-visit treatment notes with an injection map, clinical photos with before and after comparisons, and client records that can be exported as a PDF. It also covers memberships with recurring billing, deposits, online booking, reminders by SMS, WhatsApp and email, Stripe card payments (including Apple Pay and Google Pay) and Tyro EFTPOS, and a Xero sync. You can see how these fit together on the aesthetic clinic software page.
What to ask us in writing before you commit. We do not promise an automatic import, compatibility with any particular vendor’s export, zero downtime or regulatory compliance. Ask these instead:
- Can you take a sample of my export, and what will be loaded for me versus what I must rebuild?
- Which of my data types (clients, appointments, signed consent forms, treatment notes, photos, memberships) can be brought across, and in what form?
- How should historical signed consent forms and notes be attached, so they sit on the right client record?
- Which plan do I need? The consent forms, treatment charts, before and after photos and patient records are part of the Ultra plan only.
- How are staff permissions set up so reception cannot see clinical notes?
- How will you support us in the cutover window?
Pricing. ZibaDesk is priced per business, not per staff member. Free is A$0, Pro is A$19.99 per month and Ultra is A$39.99 per month. The current details are on the pricing page. If you want to see how the booking side behaves with your own services, there is a guide to online booking for aesthetic clinics.
Try ZibaDesk before you move everything
A small trial is a good first test of your field map. You can start on the free plan, or take the 14-day Pro trial, which needs no card. Set up your services, a few test clients, a deposit and a reminder, and see whether the workflow matches how your clinic runs. Remember that consent forms with e-signature, treatment charts, before and after photos and patient records sit on Ultra, so ask us about that part of the suite before you plan your cutover.

Start free or begin the 14-day Pro trial with no card required
FAQ
How long should a clinic software migration take?
It depends on how much data you hold and how clean it is. A common pattern is several weeks: inventory and mapping, a pilot, a final import, then a parallel period of around a fortnight. Build the schedule from your own checklist rather than a vendor’s promise.
Can I move signed consent forms to a new system?
Often they can be exported as individual files, but this depends on your current provider. Ask for a sample export and check that each file is linked to the right client and shows the signing date. Confirm with ZibaDesk how historical forms would be attached to a client record before you commit.
Do I need to keep the old system after switching?
Keep it read-only for a parallel period, and keep a verified backup after that. How long you must retain health records depends on your state and circumstances, so confirm it with your adviser before deleting anything. The OAIC publishes guidance on protecting and destroying personal information.
What should I do about duplicate clients?
Merge them before the move where you can, using more than a name: date of birth and contact details help. Anything uncertain should go to a person to review, not be merged automatically.
Sources
- Practice Software Migration Readiness Checklist, Podium IT
- What to Look for in Aesthetic Clinic Software, Alma Lasers Australia
- Data Migration Checklist for Healthcare and Allied Health, CleverOps
- Australian Privacy Principles guidelines, OAIC
- AMA Privacy Code of Practice for medical practitioners in the private sector
- Healthcare Data Migration to Halaxy, Lunaris
- Zero-Downtime Clinic Software Migration Checklist, Tregovia
- Clinic Server Migration: Patient Data and Rollback Checklist, NetLuma IT
