Switching Hospital Software: A Migration Checklist

Why hospitals switch, and when to wait

Hospitals usually look for an alternative to their current software for familiar reasons: screens are slow, doctors have gone back to paper, the product no longer receives updates, ABDM support is missing, every new user or branch costs extra, or support takes days to reply. Sometimes the reason is growth: a clinic product cannot handle IPD, or a second branch needs a separate login.

Switching takes effort, so time it well. Avoid starting a cut-over in the weeks before an accreditation assessment, during the financial year-end close, or in your busiest season. A calm month with steady OPD numbers is ideal.

Step 1: Read your contract and secure your data

Before you tell your current vendor that you are leaving, read the contract and find out exactly how you will get your data out.

• Notice period and renewal date, so you do not pay for an extra year by accident.
• Export format: ask for CSV or Excel files per table (patients, visits, prescriptions, bills, payments, stock) plus uploaded files, not only printed reports.
• Export fees and timelines, in writing.
• Access after the contract ends: a read-only login for a few months is very useful during reconciliation.
• Deletion: a written confirmation that the vendor has erased your data after you have received and checked the export.

Deletion is not a formality. Under the Digital Personal Data Protection Act, 2023, your hospital is the data fiduciary, and it must have its data processor erase personal data once it is no longer needed for the purpose, unless the law requires it to be kept. Keep your own copy of everything you must retain. Our DPDP Act guide for hospitals explains processor contracts and erasure.

Step 2: Take an inventory of your data

Not everything needs to move in the same way. Decide for each kind of data whether to migrate it, re-enter it at cut-over, or keep it in an archive.

Step 3: Clean and map the data

Old systems collect duplicates and inconsistencies over the years. Cleaning before import is much easier than fixing records one by one later.

• Merge duplicate patients with the same phone number, name and age, but keep family members who share a phone separate.
• Standardise dates, phone numbers and gender values.
• Prepare a mapping sheet that lists each old field and the new field it goes into.
• Import a test batch of about 100 records, check them on screen with a doctor and a receptionist, and fix the mapping before the full import.
• Keep a log of what was imported, when and by whom.

Step 4: Build the masters

Masters are the lists the software uses every day: doctors with OPD timings and fees, departments, services and procedures with prices, packages, room categories, wards and beds, lab tests with reference ranges, medicines, insurers and TPAs, and staff roles. A migration is a good moment to correct prices and remove services you no longer offer.

Ask each department head to check and sign off their own list. Correct masters make the first bill right, which builds trust in the new system from day one. Our guide on how to digitise your clinic or hospital describes masters in more detail.

Step 5: Plan a short parallel run

A parallel run means both systems are available for a short period while you confirm the new one is right. It should be short and clearly defined. A long parallel run doubles the work, and staff quietly go back to the old system.

The key rule: from cut-over day, every new registration, bill and admission is created in the new system only. The old system is used to look things up, not to enter new work.

Step 6: Train every role

Train people on the screens they use, in short sessions, with their own real scenarios: a walk-in OPD patient, a planned surgery with a package and deposit, a TPA admission, a lab report, a pharmacy sale. Choose one confident person in each department as a champion who helps colleagues during the first weeks. Doctors should practise their common prescriptions before cut-over so that their first OPD on the new system is not slower than on the old one.

Step 7: Cut-over day checklist

1. Close the day in the old system and print the day-end and deposit reports.
2. Take the final export and check that the file counts match the old system.
3. Import or enter opening balances for deposits, advances and pending bills.
4. Enter every admitted patient with their bed, doctor, payer and charges so far.
5. Enter opening stock from the physical count.
6. Switch the old system to read-only and remove routine logins.
7. Start the next OPD session on the new system, with the vendor's support person available.

Step 8: Reconcile, then archive

After a week or two, compare the numbers. Patient counts, active admissions, deposits held, receivables by payer and stock value should match what you migrated plus the activity since cut-over. Investigate every difference; small ones usually point to a mapping error that affects many records.

Then archive the old data in a form you can open without the old software, such as the exported files with an index. Retain records for the period required by the rules that apply to you. If you are working towards accreditation, note that the NABH hospital standards, 6th edition expect a hospital to retain clinical records according to its requirements and to destroy them only in line with written guidance.

ABDM: what changes and what does not

Your facility ID in the Health Facility Registry belongs to your hospital, not to the software, so it stays the same. Doctors keep their Healthcare Professionals Registry IDs, and patients keep their own ABHA numbers. What changes is the software that connects to ABDM for you: the new system must be linked to your facility ID before the front desk can create or verify ABHA in it. Ask both vendors how records already linked to patients' ABHA will be handled, and confirm the new vendor's ABDM milestones in a demo.

Common mistakes

• Giving notice to the old vendor before checking that the export is complete.
• Copying old masters, with their wrong prices and duplicate services, straight into the new system.
• Running both systems in parallel for months, so neither is complete.
• Forgetting deposits and unsettled TPA claims, which then surface as disputes at discharge.
• Training one person, who becomes the bottleneck for everyone else.
• Not asking the old vendor to confirm deletion of your data in writing.

How Sehat Nxt helps

Sehat Nxt is cloud software, so there is no server to install on cut-over day. Ask our team about help with importing your patient list and setting up masters, and about role-based training for your staff. You can start with the live OPD queue and EMR and digital prescriptions, then add IPD management, hospital billing and pharmacy. Sehat Nxt is ABDM M1, M2 & M3 Ready.

Owners can download all their patient records at any time, so you are never locked in. Plans start from ₹999 per month. Book a free demo and bring a sample export from your current system.