Tally to ERPNext migration: a step-by-step guide

Tally is fast, familiar and understood by almost every accountant in India. Many businesses should stay on it. A move to ERPNext, an open-source ERP built on the Frappe framework, makes sense when the business has outgrown what an accounting package does well, not because a new system is fashionable.

The usual signs: several people need to work on the same books from different places at once; sales, purchasing, stock and manufacturing live in spreadsheets around the ledger; you need approvals and workflows, not only entries; you want your own reports and integrations through an API; or you want AI agents to draft work in the system, with permissions and a record. If none of these applies, the cost and disruption of a migration may not be worth it.

Stay put, or delay, if you are in the middle of an audit, a GST notice or a funding round, or if nobody in the business has time to own the project for a few weeks. Migrations fail for lack of an owner more often than for technical reasons.

Bringing every historical voucher across is tempting and rarely worth it. It multiplies the reconciliation work, and the history is already final, filed and audited in Tally. Move balances and open items; keep history where it was created, preserved and readable.

Choose the cut-over date first; everything else follows from it. The cleanest is the first day of a financial year, after the previous year is closed, because opening balances are then the audited closing balances. A quarter or month end works too, but you will reconcile a part-year in two systems.

Then set a freeze: a date after which nobody posts to the old period in Tally except agreed closing adjustments, each one logged. Name an owner in the business and an owner on the accounting side, usually your chartered accountant, and agree in writing what “reconciled” means before you start. Plan for a short parallel period in which new transactions go into ERPNext while late adjustments to the old period still go into Tally.

Mapping is where most of the real work happens. Tally's groups and ledgers do not map one-to-one to ERPNext's account tree, and a migration is the best chance you will get to clean up duplicates, dormant ledgers and accounts used inconsistently.

• Chart of accounts. Map every Tally ledger to an ERPNext account, merging duplicates and retiring dormant ones. Keep a mapping sheet; your auditor will want it.
• Parties. Customers and suppliers need clean names, GSTINs, state codes and billing addresses, because GST place-of-supply logic depends on them.
• Items. Codes, units, HSN or SAC codes and tax categories. Merge items that differ only in spelling.
• Tax templates. Set up GST sales and purchase templates in ERPNext, typically with the India Compliance app, and map each Tally tax ledger to them.
• Cost centres and dimensions. Decide what you will track, rather than copying every Tally cost centre.

Keep a mapping sheet

Record every decision in one sheet with four columns: the Tally ledger or master, the ERPNext record it maps to, the reason for any merge or change, and who agreed it. A few illustrative rows for a fictional company, Kolam Components*: “Freight Inward” and “Freight Charges” both map to “Freight and Forwarding Charges” because they were used interchangeably; “Suspense A/c” is cleared before cut-over rather than migrated; each GST ledger maps to a tax template account. Illustrative specimen. Not customer data.

Frappe's guide to preparing and mapping legacy data is a good checklist for this stage.

TallyPrime can export masters, vouchers and reports in formats including Excel and XML. Export the masters, the trial balance at the cut-over date, the outstanding receivables and payables with invoice detail, and the stock summary by item and warehouse.

In ERPNext, import in dependency order: the chart of accounts first, then parties and items, then tax templates, then opening balances, opening invoices and opening stock. Use the Data Import tool's preview to catch errors before records are created, and import in batches you can check. Scripts can automate the transformation between Tally's export and ERPNext's import templates, but every script output should still be reviewed against the source.

Do the whole import first into a copy of ERPNext that nobody uses for real work. Then reconcile, and do not move on until every figure ties.

• Trial balance: every account in ERPNext equals its mapped Tally ledger(s) at the cut-over date.
• Receivables and payables: party-wise balances and invoice-wise ageing match.
• Stock: quantities by item and warehouse match, and the stock value equals the stock ledger balance.
• GST: input tax credit balances in the electronic credit ledger agree with the books; open invoices carry the right GSTINs and place of supply.
• Spot checks: a sample of parties, items and invoices opened and compared field by field.

Keep the reconciliation workpapers. They are the evidence that the opening position in ERPNext is the closing position in Tally, and your auditor will ask for them in the first audit after the move.

When the dry run ties, your chartered accountant reviews the tie-out and signs it. That sign-off is not a formality: the CA will audit or review the first year in ERPNext, and the opening balances are part of that work.

Then repeat the import in production, using the same files and scripts, and run the same reconciliation again. Set a lock date in Tally so the old period cannot change, export Tally's data and its edit log in a readable form, and store them for the statutory retention period: eight years for books of account under the Companies Act, and for GST, until 72 months after the due date of the annual return for the year, under section 36 of the CGST Act.

• E-invoicing. Businesses whose aggregate annual turnover has exceeded ₹5 crore in any year since 2017-18 must issue e-invoices for B2B supplies. Since 1 April 2025, taxpayers with turnover of ₹10 crore or more cannot report an e-invoice to the IRP more than 30 days after its date, per the GSTN advisory. Configure and test e-invoice generation before the first live invoice.
• Edit log. Companies must keep an audit trail that cannot be disabled under the MCA audit trail rule. In ERPNext, enable the India Compliance audit trail setting from day one; once on, it cannot be switched off.
• User roles. Give each person, integration and AI agent its own user with the narrowest role that works. Shared logins defeat the edit log.
• First close. Run the first month-end close with your CA watching, and fix the process before habits form.

• Duplicate parties. The same customer appears twice in Tally under slightly different names, sometimes with different GSTINs for different states. Decide whether they are one party with several addresses or genuinely separate before import.
• Negative stock. Tally often allows stock to go negative; ERPNext, by default, does not. Fix negative balances in Tally, or post the missing entries, before you take the stock snapshot.
• The opening balance difference. Opening invoices are posted against a temporary opening account in ERPNext. After all opening entries, that account must net to zero. If it does not, something is missing or counted twice.
• Unreconciled bank accounts. Reconcile every bank account in Tally to the cut-over date first. Otherwise old uncleared cheques become a mystery in the new system.
• Round-off and suspense ledgers. Clear them before cut-over rather than carrying unexplained balances into a clean chart.
• Users who learn on go-live day. Train the people who will post entries on the dry-run copy, with real examples, before production opens.

There is no honest single figure for what a Tally to ERPNext migration costs or how long it takes in general. It depends on the number of ledgers, parties and items, how clean they are, whether stock and manufacturing are involved, and how quickly the business can answer mapping questions. Be wary of anyone who quotes a market average without seeing your data.

What we can give is our own list price: elan1's Tally to ERPNext migration is ₹24,999 one-time, exclusive of GST, and includes a dry run, reconciliation and CA sign-off. The time it takes is mostly the time your team needs to clean and confirm the masters; the import itself is the quick part.

elan1 Work runs governed AI agents for ERP on ERPNext, hosted by elan1 or attached to your own instance. The migration follows the steps in this guide, with a dry run, a reconciliation and your CA's sign-off before go-live, at the same price whether hosted or attached.

After the move, ERPNext AI agents can draft entries, invoices and reconciliations, and each change passes a rule check, a named approver where your rules ask, and leaves a proof record. Plans are set by turnover band; see elan1 Work plans by turnover. Most small firms come to us through your CA, whose seat is always free.