Our accounts are in Tally, everything else is in Excel.
ERPNext runs sales, purchase, stock, production and accounts in one place; Excel stops being the system of record.
For companies moving off Tally
Move from Tally to ERPNext without losing a month-end
Masters and opening balances migrated, history left where it is, the books reconciled before cutover, and GST, e-invoicing and e-way bills set up in ERPNext. Where accounts need to stay in Tally for a while, ERPNext can keep it updated.
Bizmap started out implementing ERPNext for companies that had outgrown Tally and spreadsheets. Tally keeps the books well. What it does not do is run orders, production, stock by location, approvals and service in the same system. ERPNext does, and the move is mostly a question of what you bring across, on which date, and how you prove the numbers match.
Problems we hear
We are afraid of losing years of history.
History stays in Tally, read-only, for reference and audit. We migrate masters and opening balances, and history only where a regulator needs it in the new system.
Our accountant does not want to leave Tally yet.
ERPNext can run operations first while a scheduled sync keeps Tally up to date for accounting, as it does every day at JAT Metal Pressing. Accounts move when you are ready.
GST, e-invoicing and e-way bills must keep working on day one.
India Compliance is set up in ERPNext for GST, e-invoicing and e-way bills, and tested on your own transactions before cutover.
What is included
- What we migrate
- Detail
- Masters
- Chart of accounts, customers and suppliers with GSTINs and addresses, items with HSN codes and units, warehouses, cost centres.
- Opening balances
- Trial balance on the cutover date, open receivables and payables bill by bill, bank balances, and stock by warehouse with its value.
- What stays in Tally
- Past vouchers and history, kept read-only, unless a regulator needs them in the new system.
- Compliance
- GST, e-invoicing and e-way bills through India Compliance, checked on real invoices.
- Transition
- A parallel run where the risk warrants it, or a scheduled sync to Tally while accounts stay there.
How it works
- Pick the cutover date
Usually the start of a month or quarter, so each period closes in one system.
- Templates and cleansing
Migration templates issued in the first week; your team cleans the masters with our validators.
- Two dry runs
Each one reconciled: trial balance, stock, open receivables and payables, and bank must match Tally.
- Test with your users
Your accounts and operations teams run their own transactions, including GST invoices, on a staging copy.
- Cut over
Final balances loaded on the date you chose, a parallel run where risk warrants it, and Tally kept read-only afterwards.
- First month-end
We stay with your accounts team until the first month-end closes in ERPNext.
Case studies in ERPNext alongside Tally
JAT Metal PressingMoved a Mumbai automotive components maker from Excel and manual planning to ERPNext manufacturing, with a daily Tally sync for accounting. · Sales order to dispatch in one linked flow, with stage-wise QC and PDILiving LiquidzInvoice-to-payment on ERPNext for a 100+ outlet retail chain: goods receipt sync, a store app, multi-level approvals and bulk payments, with Tally integrated for accounting. · Invoices processed a day up from 1,000 to 1,500–2,000
Read next
Tally to ERPNext: what to migrate, what to leave behindOur stance in one line: migrate masters and opening balances, leave history in Tally unless a regulator needs it.ERP and business platformsERPNext implementation, migration and upgrades, and the support that follows.Integrations and APIsConnecting ERPNext to Tally, banks, payment gateways and marketplaces.
Why Bizmap here
FAQ
No. We migrate masters and opening balances on the cutover date. History stays in Tally, read-only, unless a regulator needs it in the new system.
Yes. ERPNext can run operations while a scheduled sync keeps Tally up to date. JAT Metal Pressing runs orders, production, quality and dispatch in ERPNext with a daily Tally sync for accounting.
That is part of the cutover plan. India Compliance is set up in ERPNext and tested on your own invoices in the dry runs, before any live transaction.
At the start of a period, usually a month or a quarter, so each period closes in one system. The date is yours to choose; we plan the dry runs back from it.
Before cutover we reconcile the trial balance, stock, open receivables and payables, and bank against Tally, in two dry runs and again at the final load.