Your Batch Data Is Not Portable by Default — and That Has a Price
Open your current software's export options. If you see a CSV export that outputs product name, quantity, and price — but no batch number, no manufacturing date, no expiry date — you have already found the problem. Many desktop pharmacy systems were built around billing speed, not data portability, and in some of them batch-level detail does not come out in a standard export.
Picture a pharmacist in Thane who exports his stock file before switching billing software. After import, the new system shows every product — but FEFO (First Expiry, First Out) batch selection is impossible because the expiry field is blank for most SKUs. Staff default to picking whatever is at the front of the shelf. Within months, he is writing off stock that could have gone back to distributors if he had caught it in the return window.
Batch data lost at migration turns straight into expiry write-offs.
---
A Missing Schedule H1 Register Is a Regulatory Liability, Not Just an IT Problem
Under Rule 65(3)(h) of the Drugs and Cosmetics Rules, every retail pharmacy keeps a separate Schedule H1 register — prescriber's name and address, patient's name, drug and quantity — for three years. Register gaps can put the licence at risk, and in serious cases, license cancellation is on the table.
When you switch billing software, two things typically go wrong with this register:
- The old software's H1 entries don't export in a format the new system recognizes, so the register appears empty on day one of the new system.
- The new system starts a fresh register from migration date, creating a gap in the chain of records.
Picture a drug inspector visiting a pharmacy three months after a software switch and finding exactly this: a gap in the H1 register covering the migration period. The pharmacist has the paper records but no continuity between them. That is how a show-cause notice starts, and reconstructing and re-entering the records can take a staff member weeks of back-office time.
The regulation doesn't distinguish between "we migrated software" and "we didn't keep records." The three-year clock runs regardless.
---
Your GST Ledger and Party Balances Won't Survive a Naive Export
Most medicines under HSN 3004 are at 5% GST since 22 September 2025, when the 12% slab was withdrawn, after the 56th GST Council meeting, and compliance accuracy at the invoice level is non-negotiable. When you export data from one system and import it into another, GST breakdowns — CGST, SGST, IGST, and the HSN mapping — often collapse. The receiving system may re-calculate differently, or worse, show totals that match on the surface but are wrong at the transaction level.
A bigger immediate problem is party ledger aging. Outstanding balances with distributors and hospital accounts don't just need a closing number — they need the invoice-by-invoice trail. If your export produces a single opening balance per party, you lose:
- Which specific invoices are outstanding
- Which payments are partially settled
- What credit periods apply to which invoices
For a pharmacy with 40 active distributor accounts, this is not a minor inconvenience. It means your next payment cycle runs on guesswork.
---
What a Clean Migration Actually Looks Like — Before and After
The difference between a migration that costs you three months of recovery time and one that costs you an afternoon is almost entirely in what you export and in what format.
| Before (typical legacy export) | After (structured data-exit) |
|---|
| Product name + MRP + quantity only | Product name + batch no. + mfg date + expiry date + purchase price + MRP + quantity per batch |
| Single opening balance per party | Invoice-wise outstanding with aging |
| No H1 register export | H1 entries with date, product, batch, quantity, patient/prescriber reference |
| GST totals at product level | HSN-wise GST breakdowns per invoice |
| No prescription linkage | Prescription reference retained per dispensing record |
When a pharmacist has this export in hand — even from a 10-year-old system — a receiving platform that accepts those columns can import it accurately, and the old register stays readable for continuity. FEFO batch selection works immediately. The party ledger shows aging detail, not just balances. The first billing cycle on the new system runs on real data, not reconstructed guesses.
This is the difference between a migration that takes a weekend and one that takes six weeks.
---
How Nesayo Handles This Switch
Picture a neighborhood pharmacy owner in Coimbatore who has been on a Windows desktop system for seven years, nervous after hearing enough migration horror stories.
If his old software gives a CSV or Excel export with batch-level columns intact, Nesayo's import reads the batch numbers and expiry dates directly, and a photo of a stock list works too. Imported rows are matched against more than 2.5 lakh pre-loaded medicines, which fill in HSN codes and GST rates his file leaves blank, and rows that need a second look are held for review before they go live. The Nesayo team will also move his current software's data across for him, free. His old H1 register stays readable for the retention period, and from go-live Nesayo logs each H1 sale at billing: date, medicine, batch, quantity and bill number, with the patient and prescriber names entered on the bill. Nesayo does not record the prescriber's address yet, so the pharmacist adds it to complete the register.
Once the batches are in, expiry alerts show what is getting close, FEFO picks the earliest-expiring batch at billing, and Nesayo refuses to bill a batch once its expiry month has passed. On the AI Employee plan, Expiry Guard sorts stock into 30, 60 and 90-day buckets with return suggestions, and Payment Advisor tracks what he owes distributors and when.
On a paid plan he can bill by voice in Hindi or English (beta) the same morning, without retraining his staff on a new keyboard layout.
Billing on Nesayo is free permanently. If he wants all five AI agents running — Morning Briefing, Expiry Guard, Refill Radar, Stock Sense, and Payment Advisor — that's the AI Employee plan at ₹999 a month (as of September 2026), which also includes the export for Tally for his accountant.
---
The Choice Is Between Planned Downtime and Unplanned Recovery
If you stay on your current software because the migration feels risky, the cost of that decision compounds quietly. Every month of batch data you can't export cleanly is a month of expiry risk you can't see. Every month the H1 register runs on a system you plan to leave is a month of data that may not travel.
If you migrate badly — the way it typically happens over a long weekend with a flat CSV — you pay in recovery time, staff hours, accountant fees, and possibly a drug inspector's notice.
The third option is a migration that is planned at the data level before anyone touches the new system. That means knowing exactly what you need to export, in what structure, before you start.
Go to nesayo.com/demo — a sample pharmacy is pre-loaded, no signup required — to see how batches and expiry dates look once they are in. When you are ready, create a free account at nesayo.com/setup and upload your own stock export: you will see which columns were read and which rows need a second look before anything goes live.
---
FAQ
How do I export batch and expiry data from my current pharmacy software before switching?
Go into your current software's stock report or inventory module and look for an export option that includes columns for batch number, manufacturing date, and expiry date separately — not just product name and quantity. If the export doesn't show those columns, ask your current software vendor for a database-level export or a custom report. Without batch and expiry detail, FEFO selection on the new platform is impossible from day one.
Is FEFO (First Expiry, First Out) a legal requirement in India for retail pharmacies?
FEFO is referenced in Good Storage Practices under Schedule M of the Drugs and Cosmetics Rules, which applies primarily to manufacturers and licensed warehouses. For retail pharmacies, there is no separate statutory provision that mandates FEFO by name, but Schedule H and H1 dispensing records and the general duty to not supply sub-standard or expired medicines make batch-level tracking strongly advisable. Consult your state licensing authority or a D&C-qualified consultant for your specific license category.
What happens to my Schedule H1 register when I change pharmacy billing software?
Your old software's H1 entries typically remain in the old system and are not automatically carried into the new one. You need to either export the historical H1 data in a structured format for import, or maintain the old system in read-only mode for the three-year retention window required under Rule 65(3)(h) of the D&C Rules. The new system should start recording from migration date forward — but there should be no gap in the physical or digital trail, or you risk non-compliance.
Can I migrate GST invoice data when switching pharmacy software mid-financial year?
Yes, but it requires invoice-level export from your old system — not just a closing GST summary. You need GSTIN, invoice date, HSN code, taxable value, CGST, SGST, and IGST per invoice. A flat opening balance will not satisfy your GST return for the months already filed. Your CA should reconcile GSTR-1 and GSTR-3B data from both systems across the financial year. Verify with your CA what format the new system's export needs to be in for reconciliation.
How long does it take to migrate pharmacy data from a legacy desktop system?
The import itself — once the export file is correctly structured — typically takes minutes to hours depending on SKU count. The preparation work is what takes time: getting batch-level exports, cleaning product names that differ between systems, mapping HSN codes, and verifying party ledger balances. The larger your catalogue, the more preparation it needs, so plan it before the import weekend. Rushing this preparation phase is where migrations go wrong.
What patient data regulations apply when switching pharmacy software in India?
The Digital Personal Data Protection Act 2023 (DPDPA) applies to any platform that stores patient names, contact numbers, or prescription data. When migrating, ensure that your data export does not expose patient records to unsecured channels (unencrypted email attachments, personal drives), and that your new platform processes patient data only for the purpose for which it was collected — dispensing and compliance records. Check that your new vendor has a published data processing agreement. This is not currently enforced uniformly, but DPDPA enforcement timelines are expected to tighten.
How do I verify that my party ledger outstanding balances are correct after a migration?
Do not rely solely on the opening balance that imports into your new system. Before migration, print or export an aging report from your old system — party-wise, invoice-wise — and reconcile it against the imported data in your new system within the first billing cycle. Call your top 10 distributor accounts and confirm outstanding amounts match their records. Discrepancies found in week one are fixable; discrepancies found after six months become disputes.
How does Nesayo handle the import of data from other pharmacy software during migration?
Nesayo imports stock with batch numbers and expiry dates from a CSV, Excel or text export, or a photo of a stock list, and the Nesayo team moves your current software's data across for you, free. Imported rows are matched against more than 2.5 lakh pre-loaded medicines, which fill in HSN codes and GST rates your file leaves blank, and rows that need a second look are held for review before they go live. Keep your old software's Schedule H1 register and party ledger as they are, readable, for the retention period. Billing is free on Nesayo permanently, so there is no cost pressure to rush the migration — you can run a parallel import test before going live. The specific export format your current software produces will determine how much pre-processing your data needs.