Migrate from Marg ERP to Apragya: Items, Batches and Balances Moved at a Month Start
For pharma distributors, FMCG stockists and retailers on Marg who want one cloud record for stock, billing and accounts, moved without a gap in batches or balances.
If you plan to migrate from Marg ERP, the worry is rarely the new screens. It is whether every batch, expiry date and party balance arrives intact, and whether the salesman's next order still goes out on time. That worry is fair, and it is manageable with a fixed date and a checklist.
Marg is a desktop billing, inventory and accounting package used widely by distributors, chemists and retailers. Many businesses move when they add branches, field sales or users who need access away from the office machine.
This guide covers what to export, what to import, how an illustrative distributor ran the switch, and how Apragya keeps the moved data on one record.
How to migrate from Marg ERP: the short answer
Moving off Marg is mostly a data question, not a software one. You carry across masters (items with HSN and GST rates, batches, customers, suppliers, ledgers), then closing figures as at one date (stock by batch, party outstanding, ledger balances). Old invoices stay in Marg for reference.
Pick the first day of a month, ideally a quarter, so GST returns for the earlier period are filed from Marg and the new period starts cleanly. Take the closing reports from Marg after the last day is posted, clean them in a spreadsheet, and import.
Then run both systems for a few weeks on the same bills, compare stock and outstanding, and stop entry in Marg once the numbers agree.
- Choose a cut-over date at the start of a month or quarter.
- Export item, batch, customer, supplier and ledger lists from Marg reports to Excel.
- Clean duplicates, fix HSN codes and GSTINs, and map columns to the import templates.
- Import masters, then stock by batch and expiry, party outstanding and ledger balances.
- Check item counts, stock value and total outstanding against Marg's closing reports.
- Run both systems in parallel for two to four weeks.
- Stop entry in Marg and keep it read-only for history and audits.
What a rushed Marg ERP data migration costs
Lost batch detail
Stock moved as one total per item, so expiry-wise picking stops working.
Wrong outstanding
Party balances carried without bill-wise detail cannot be followed up.
GST gaps
A mid-month switch splits returns across two systems.
Double work
Months of re-entry because the cut-over date was never fixed.
An example: a pharma distributor in Indore
Take an illustrative distributor with 3,800 items, 900 chemist customers and two godowns. It chose 1 October as the cut-over date and took Marg's closing reports on the evening of 30 September.
Four weeks from Marg to one cloud record
Week 1
Date fixed; item, party and batch lists exported to Excel.Week 2
Duplicate chemists merged and HSN codes corrected.Cut-over day
Masters, batch stock and bill-wise outstanding imported.Weeks 3 and 4
Same bills in both systems; stock and dues compared.Switch
Marg made read-only after the figures agreed.
The parallel run showed eleven batches with a wrong expiry month, all from one supplier's old entries. They were corrected before billing. By the end of October the salesmen were taking orders on their phones and accounts closed the month without touching Marg.
How the move works in Apragya
Step 1 of 5
Preview the file
Upload a spreadsheet, see its headers and sample rows first.
- Preview the file: Upload a spreadsheet, see its headers and sample rows first.
- Map the columns: Match Marg's column names to Apragya's fields once.
- Import in the background: Large lists load as a job with a count of rows and errors.
- Opening stock by batch: Stock arrives per item, batch, expiry and godown.
- Opening bills: Customer and supplier dues come in bill by bill with one opening entry.
Planning the switch from Marg to cloud ERP
The real difference after the move is where the data lives. On Marg, stock, billing and accounts sit on one machine or network. On Apragya, the same customer, item and batch are shared by sales, inventory, purchase and finance, and can be reached from any browser with the right access.
What changes after the move
| Feature | Marg ERP | Apragya |
|---|---|---|
| Where it runs | Desktop or office network | Cloud, in a browser |
| Field sales | Check the vendor's current options | Phone-friendly web app on the same record |
| Batches and expiry | Supported | Batches, expiry, bins and barcode |
| GST | Supported | E-invoice IRN, e-way bill, GSTR-1 and GSTR-2B |
| AI help | Check the vendor | Agents on records, with human review |
Checked against public information on 16 September 2026.
What makes the Marg ERP data migration hold
One record
An item or chemist entered once is used by every app.
Batch-level stock
Expiry-wise picking works from the first day.
Bill-wise dues
Outstanding keeps its invoice numbers and due dates.
Access by role
Salesmen, godown and accounts each see their part.
AI with review
Agents can read supplier bills and flag slow stock, with a person approving.
Orders on the phone
Field staff use the phone-friendly web app.
Before deciding, read the Marg ERP alternative page and the Apragya vs Marg ERP comparison. For batches, see batch tracking and opening invoices.
Getting started
- Fix the cut-over date and tell your team and auditor.
- Export one list, customers, and try it in the import preview.
- Clean all lists in one pass, not one at a time.
- Import closing stock and dues on the cut-over day.
- Compare totals weekly until the parallel run agrees.
Most of the effort is in cleaning the lists. The import itself is the short part.
What it costs to start
Migrating from Marg ERP, answered
Can we bring old invoices across?
Will batch and expiry details survive the move?
Should we switch mid-month?
How long does it take?
What does it cost to start?
Fix your cut-over date
Try one Marg export in the import preview and see how your data maps.