Loading…
Loading…
What moves from Tally to ERPNext, how to run both in parallel, when to cut over and how to train your team. A practical guide for manufacturers.
Tally is very good at what it was built for: accounts and GST. Most Indian manufacturers start on it, and many of their accounts teams know it by heart. The trouble starts when the business needs more than accounting. BOMs, work orders, production planning, quality checks and stock by batch end up in Excel sheets around Tally, and nobody has one view of the plant.
ERPNext covers accounts and GST as well, but it also runs manufacturing, stock, purchase and sales in the same system. If you are still deciding, our ERPNext vs Tally comparison sets out where each one fits. This guide assumes you have decided to move, and covers how to migrate from Tally without losing control of your numbers.
You are probably ready to migrate from Tally if:
None of these are Tally's fault. It was never meant to run a plant.
The cut-over date is the day ERPNext's opening balances are taken from. The cleanest choice is the start of a financial year, 1 April, because the old year stays entirely in Tally and ERPNext starts with a clean year. If audit adjustments to the old year come in later, post them in Tally and update the opening entry in ERPNext to match. The start of a quarter or month also works. Mid-month cut-overs make reconciliation harder and are best avoided.
Most manufacturers do not need years of Tally vouchers inside ERPNext. A common approach is:
Moving full history is possible, but it adds time and cost, and old data often needs the most cleaning.
| In Tally | In ERPNext |
|---|---|
| Ledgers and groups | Chart of accounts |
| Sundry debtors | Customers, linked to a receivable account |
| Sundry creditors | Suppliers, linked to a payable account |
| Stock groups | Item groups |
| Stock items | Items |
| Units of measure | UOMs |
| Godowns | Warehouses |
| Cost centres | Cost centres |
One change catches people out. In Tally, every customer and supplier is its own ledger. In ERPNext, customers and suppliers are parties, and they all post to a shared Debtors or Creditors account. Your balances by party are still there, in the receivable and payable reports.
Addresses, GSTINs and states come across with each party, because ERPNext needs them to work out GST on invoices.
Opening balances are set up as at the cut-over date:
The stock value in ERPNext should match the stock value in Tally's balance sheet on the cut-over date. If it does not, find out why before go-live.
Sales orders and purchase orders that are still open on the cut-over date are entered in ERPNext with their pending quantities. This lets deliveries and receipts after go-live link back to an order.
For a manufacturer, the biggest part of the job is not migration at all. It is building what Tally never held:
This is where the process walkthrough matters. Someone has to sit with production and stores and write down how each product is actually made. Our guide to ERPNext for manufacturing covers this setup step by step.
Tally data built up over years usually has:
Export masters and reports from Tally to Excel, clean them there, and agree on item codes before you import. Deleting duplicates in ERPNext after go-live is much harder, because transactions will already point at them.
ERPNext's Data Import tool takes Excel or CSV files. Import first into a test site, check the result, fix the source file and import again. Only import into the live site once the test run is clean.
Before go-live, compare these between Tally and ERPNext as at the cut-over date:
Have your accountant sign off on each. A migration is finished when the numbers match, not when the import runs without errors.
Running both systems in parallel for a short period, around a month, lets you compare results while the team learns. During that time:
Parallel running doubles the data entry, so keep it short and give it a clear end date. Some businesses run parallel only for accounts, while stores and production move to ERPNext straight away.
Accounts staff who know Tally well are often the most uneasy about the change. Show them where their familiar reports live in ERPNext: the general ledger, trial balance, receivables, payables and GST reports. Train them on their own company's data, not a demo.
Train each department on its own screens. Stores learn purchase receipts, stock entries and transfers. Production learns work orders and job cards. Purchase learns material requests and purchase orders. A short written guide for each role, with screenshots from your own system, saves many phone calls in the first month.
At CSE India, more than 25 users across production, quality and accounts were trained by role before switch-over, and five years of history came across from Excel.
A typical migration takes 4 to 8 weeks, plus around a month of parallel running. More history to move, more sites or heavy manufacturing setup will add time.
It is possible, but it means entering or syncing data twice and reconciling two systems. Most manufacturers find one system for both accounts and operations simpler to run.
No. Keep Tally available in read-only use for past years and audits. You can also bring summarised history into ERPNext if you need it for reports.
Yes. Opening balances are taken at the start of the month you choose. Year-end is cleaner, but a month or quarter start works well too.
Yes. Current ERPNext handles GST, e-invoicing and e-way bills through the India Compliance app, so invoices and GST reports come from the same system as stock and production.
Book a walkthrough and we will plan your move from Tally with you.
In a free 30-minute call we map your process and tell you plainly what would change, whether that is Tanush LIMS, ERPNext or something built for you. We reply within 24 hours.