Before you switch clinic software: getting your data and team ready to migrate

Getting ready to switch clinic software is mostly work you do before migration day, inside the system you already have. Clean your patient list, standardise your service catalogue and its tax codes, decide what is worth bringing across, reconcile your outstanding dues, and write down a few baseline numbers. Do this readiness pass first and the actual move becomes a calm, checkable task instead of a panicked weekend.

This is the companion to our step-by-step migration guide, which covers the move itself: export, map fields, run both systems in parallel, and verify. This post is the part that comes before any of that. It is the data hygiene and team prep that decides whether the migration goes well. Skip it and you simply move your mess into a clean new home.

Why readiness is the half nobody plans for

Most owner-doctors think of a software switch as the day the new system goes live. In reality the migration is the easy half. The hard half is everything you fix while the data still lives where it always has, because cleaning is far easier in a system your team knows than in one nobody has logged into yet.

There is also a duty hiding in here. Under India's Digital Personal Data Protection Act, 2023, a clinic processing personal data has to ensure its completeness, accuracy, and consistency, and the same Act expects you to stop holding personal data once the purpose it was collected for is over. In plain terms, deduping a patient list and retiring records you no longer have a reason to keep is housekeeping the law already nudges you towards, and a switch is the natural moment to do it. Confirm your own obligations with a qualified professional, since the DPDP Rules are still being rolled out.

Clean the patient list while it is still in the old system

Your patient list is the spine of the migration, so it is the first thing to get right. Work through it in the old system and fix the four problems every clinic database collects over the years.

• Duplicate patients. The same person entered twice with a slightly different spelling, or once with a mobile number and once without. Merge them so a patient has one record and one history, not two halves.
• Blank or wrong identifiers. Missing phone numbers, missing or impossible dates of birth, names like "Walk-in" or "Test". Fill what you can and flag what you cannot.
• Inconsistent formatting. Phone numbers written five ways, names in mixed case, dates in different orders. Pick one format and apply it.
• Dead test data. Records created on training day or while someone learned the system. Delete them.

You do not need fancy tools for this. Most systems let you export the patient list, and sorting each column in a spreadsheet makes the errors jump out. The point is to do the merging and fixing here, on data you understand, so that when you eventually move it across cleanly, there is nothing left to fight. A structured record that is already clean imports without drama.

Standardise the service catalogue and its tax codes

This is the step clinics skip and regret. Your service catalogue, the list of consultations, procedures, and products you bill for, tends to grow organically until you have three slightly different entries for the same thing at three different prices. Migrate that as-is and you have rebuilt the confusion in a brand new tool.

Decide your final catalogue before you import a single line. For each item, settle three things: whether it is a service or a product, its single correct price, and its HSN or SAC code with the right tax rate. In Avinya Plus, every catalogue item carries its own HSN or SAC code and rate so the correct tax flows onto each invoice line automatically. That is only as good as the codes you set, which is exactly why you fix them once, deliberately, before the move rather than discovering wrong codes on live invoices afterwards.

Getting these codes right is genuinely fiddly. The CBIC tax information portal lets you look up HSN and SAC codes and their GST rates, but healthcare sits awkwardly across exempt and taxable lines, and the correct code for a given item is a judgement call. Set your catalogue with your chartered accountant rather than guessing, and read our HSN and SAC codes guide for the clinic-specific context. A clean, correctly coded catalogue is one of the most valuable things you can carry into a new system.

Decide what travels and what gets archived

Not every record earns a seat in the new system. The instinct to "bring everything" is what makes a migration slow and a new database cluttered from day one. Set a simple rule and apply it.

Bring it across	Archive it as exported files
Patients seen in roughly the last two to three years	Patients with no visit in many years
Outstanding dues and active treatment plans	Fully settled invoices from long ago
Records you actively reference at the desk	Historical files kept only "just in case"

Archiving does not mean deleting. It means keeping a clean exported copy, safely stored, of the records you are not loading into the live system. This keeps your new database lean and, again, matches the DPDP direction of holding live personal data only while you have a reason to. Where a medical-record retention rule requires you to keep a file, you keep it; our guide on records retention and disposal covers where that line sits. Decide your migrate-versus-archive cut here, on paper, so the migration team is not making judgement calls mid-import.

Reconcile your opening dues so the number is trustworthy

Dues are the one number where a quiet error costs you real money, so reconcile them before you move, not after. In the old system, pull the list of every patient who owes a balance and total it. Then sanity-check that total against your own records: your daily cash closing, your bank statements, what you believe is genuinely outstanding.

This matters because a migration can only verify a number you trusted in the first place. If your old system says ₹2,40,000 is outstanding but half of that is stale entries that were actually paid in cash and never marked, importing it faithfully just carries a wrong figure forward. Clean the dues list now: chase or write off what is genuinely uncollectable, mark what was quietly paid, and arrive at a real opening-dues figure. Our guide on recovering outstanding dues and the discipline of a daily cash closing both help you get this honest. After the switch, the per-branch revenue dashboard in your new system, showing collection, dues, and average ticket, is where you confirm the reconciled figure landed intact.

Write down your baseline before anything moves

A migration is only "verified" if you can compare against something. So before you touch an export, write down three numbers from the old system and keep them somewhere safe.

• Total active patients you intend to migrate.
• Total reconciled outstanding dues, the figure you just trued up.
• Last full month's collection, from the old system's own report.

These three numbers are your proof. After the import, you check the same three in the new system and they should match, allowing for the duplicates you deliberately merged. The before-and-after reconciliation is a step in the migration guide; your job now is simply to capture honest opening figures so that later check has something to land on.

Get the team ready, not just the data

Data readiness and team readiness travel together. While you are cleaning, settle a few things so the human side does not undo the data side. Pick who owns the cleanup, usually the owner-doctor with the practice manager, so it does not become everybody's job and therefore nobody's. Freeze sloppy data entry in the old system during the prep window, because the list keeps drifting if reception is still creating loose duplicates while you are merging them. Choose a cut-over date in a quieter stretch of the calendar, and brief reception and billing on what is changing and when, so nobody ends up entering the same patient in two systems on one morning.

When you reach the move, the question to put to any vendor protects you regardless of which tool you pick: ask whether you can export every record yourself, in a usable format, at any time. That single answer tells you whether your data is truly portable or quietly trapped, and we unpack it in who owns your clinic data. Do the readiness work, ask that question, and you walk into migration day with clean data, a clear baseline, and a team that knows the plan.

This is general guidance for running a clinic, not legal or tax advice. Confirm your HSN and SAC codes with a chartered accountant and your data-protection duties with a qualified professional.