Marg ERP Migration Playbook for Indian Pharmacies

A pharmacy ERP migration is not a software installation project. It is a counter continuity project. If billing stops, patients wait, staff panic, and owners lose trust in the new system before it has a chance to prove itself. That is why a Marg ERP migration, or any switch from a legacy desktop billing setup, should start with operational mapping rather than a sales promise about a one-day go-live.

Start with what the old system actually controls

Many pharmacies underestimate how much process has grown around their current ERP. Marg may hold item masters, batches, GST rates, supplier ledgers, customer history, purchase records, returns, stock adjustments, and reports that staff export into Excel. Some branches also depend on reseller customizations that nobody has documented. Before migration, list every counter, branch, printer, barcode habit, report, and spreadsheet that touches billing or inventory.

• Item masters, compositions, pack sizes, HSN, GST rate, and MRP.
• Batch stock, expiry dates, purchase rate, sale rate, and opening quantity.
• Suppliers, customers, doctors, parties, and credit accounts.
• Recent sample bills, returns, adjustments, and day-close reports.
• Printer formats, barcode workflows, and staff login patterns.

Export quality decides migration quality

A clean import cannot be built from dirty exports without decisions. If batch numbers are inconsistent, expired stock remains active, or duplicate items exist under slightly different names, the migration must either clean them or carry the confusion forward. The right approach is to import into a staging environment first, then let pharmacy and finance leads review samples before live counters are touched.

Use a pilot branch before group rollout

A pilot branch exposes real staff behavior. Can cashiers find items quickly? Do pharmacists understand batch selection? Does the printer format satisfy the counter? Do GST lines reconcile with accountant expectations? Does the closing report match how the owner reads business today? A pilot also proves offline-first behavior: staff should know what happens when internet drops, how sync catches up, and when escalation is required.

Do not promise impossible history transfer

Some historical data can be imported when structured exports are available. Some old reports, custom fields, or reseller-built workflows may not map one-to-one. That is not failure; it is scope. A trustworthy migration plan says what will move, what will be archived, what will be rebuilt, and what staff should reference in the old system during the overlap period.

Keep old renewal overlap until sign-off

The riskiest migration is one where the old license expires on Friday and the new system is expected to save Monday morning. Plan overlap. Run staged validation. Keep exports and backups. Confirm who is available on first close. Pharmacy ERP migration should feel boring at go-live because the hard questions were answered earlier.

Where Hayati fits

Hayati AI Nexus is designed for offline-first counters, FEFO inventory, GST-shaped billing, multi-branch visibility, and governed migration from legacy workflows where exports allow. It does not pretend every old customization has a perfect twin on day one. The walkthrough should use your actual exports, branch count, stock condition, and close process so the plan reflects your pharmacy, not a generic demo.