Tally to ERPNext migration: a CFO checklist for a clean FY 2027-28 start
The cleanest day to leave Tally is 1 April. Your books close on 31 March, the new year starts empty, and nobody has to explain why October invoices live in two systems. If you want FY 2027-28 to start in ERPNext, the work begins now, not in March. This is a CFO checklist for a Tally to ERPNext migration timed to the financial year boundary: what to bring across, what to leave behind, how to reconcile it, and how to keep your auditor comfortable.

Why 1 April 2027 is the right Tally to ERPNext migration date
A mid-year move is possible. We have done them. But a mid-year cut forces you to carry half a year of transactions, split GST returns across systems and prepare a statutory audit from two sources. A year-boundary move avoids all three.
There is one catch. Your Tally books for 31 March 2027 will not be final on 1 April. Provisions, depreciation, stock valuation and audit adjustments arrive weeks or months later. So a good Tally to ERPNext migration plans for two opening balance loads: a provisional one so business can run from day one, and a true-up once the FY 2026-27 books are closed. Teams that expect a single perfect load end up delaying go-live waiting for the auditor.
If you are still deciding whether to move at all, our ERPNext vs Tally guide covers that question. This article assumes the decision is made.
Tally to ERPNext migration: what to move and what to leave
The biggest mistake we see is trying to bring every voucher since 2015 into ERPNext. It is slow, it rarely reconciles, and nobody looks at it. Bring across what you need to run the business and close the year. Leave history where it already sits, readable and audited.
| Data | Migrate to ERPNext | How | Leave in Tally |
|---|---|---|---|
| Chart of accounts | Yes, redesigned | Map Tally groups to an ERPNext account tree, cut dead ledgers | Old ledger structure |
| Customers and suppliers | Active parties only | Data Import with GSTIN, addresses, credit terms | Dormant parties |
| Items | Active items with HSN, UOM, valuation method | Data Import, item groups cleaned first | Discontinued stock items |
| Open receivables and payables | Yes, invoice-wise | Opening Invoice Creation Tool | Settled bills |
| Ledger balances | Yes, as at 31 March | Journal Entry with Is Opening set to Yes | Monthly ledger detail |
| Stock | Quantity and value by warehouse, batch, serial | Stock Reconciliation for opening stock | Stock movement history |
| Fixed assets | Yes, with gross block and accumulated depreciation | Asset records marked as existing assets | Depreciation postings of past years |
| Open sales and purchase orders | Pending quantities only | Fresh Sales Order and Purchase Order | Fully executed orders |
| GST registrations | All GSTINs | Company addresses with GSTIN and state | Filed returns |
| Vouchers of past years | No | Not applicable | Yes, kept accessible for audit and assessment |
Frappe’s own documentation on opening balances in ERPNext describes this pattern, including a Temporary Opening account that must come back to zero once everything is posted.
The countdown: a timeline back from 1 April 2027
Here is how we plan a Tally to ERPNext migration for a ₹50 crore to ₹300 crore manufacturer. Shorten it if you are a pure trader with one warehouse. Do not shorten the parallel run.
- November and December 2026: scope and design. Agree modules, warehouses, cost centres and approval flows. Redesign the chart of accounts. This is the time to retire ledgers nobody has posted to in years.
- December 2026: master data clean-up in Tally. Merge duplicate parties, fix GSTINs, standardise item names and UOMs. Clean data at source, before export.
- January 2027: build and configure. Set up companies, GST settings, tax templates, BOMs and workflows on a test site.
- Late January 2027: trial migration one. Load masters plus opening balances as at 31 December. Reconcile the trial balance. Expect it not to match the first time.
- February 2027: user training and trial migration two. Fix mapping issues. Users run real December or January transactions on the test site.
- March 2027: parallel run. Key users enter live March transactions in both systems for two to three weeks.
- 1 April 2027: go-live. Provisional opening balances, open items and stock loaded. Tally becomes read-only for new transactions.
- After audit: true-up. Post final adjustments as an opening Journal Entry and re-reconcile.
Our ERPNext go-live cutover playbook covers the weekend itself in more detail.
Reconciliation steps a CFO should sign off
A Tally to ERPNext migration is finished when the numbers agree and someone senior has signed that they agree. Not before. These are the checks we put in front of the CFO.
First, the trial balance in ERPNext as at 1 April must equal Tally’s closing trial balance at 31 March, ledger by ledger after mapping. Second, the receivables and payables ageing in ERPNext must match Tally’s bill-wise outstanding, party by party. Third, stock value by warehouse must match the Tally stock summary, and quantities must match a physical count taken close to 31 March. Fourth, the Temporary Opening account must be zero. Fifth, bank balances must match bank statements, with unreconciled items listed and carried as open entries rather than buried.
For a Coimbatore foundry, stock is usually where it breaks: scrap, returnable patterns and work in progress at furnaces are valued differently in practice than on paper. Settle valuation rules before the physical count, not after.
Running Tally and ERPNext in parallel without doubling the work
A full parallel run of every transaction for a month exhausts teams, and it is the step most often cut short in a Tally to ERPNext migration. A focused one works better. Pick the transactions that carry risk: sales invoices with e-invoice and e-way bill, purchase invoices with GST, a full production cycle from Work Order to Stock Entry, payroll postings if relevant, and bank entries. Run those in both systems for two to three weeks in March.
Compare outputs daily: invoice totals, tax amounts, stock balances. Differences point to configuration problems, and March is the cheapest month to find them. One practical rule: March GST returns, filed in April, still come out of Tally. Your first ERPNext GSTR-1 is for April 2027. Do not try to mix.
Audit trail: what the Companies Act asks of both systems
Since financial years starting 1 April 2023, Rule 3(1) of the Companies (Accounts) Rules, 2014 requires companies to use accounting software that records an audit trail of each transaction, creates an edit log of every change with the date, and cannot have the audit trail disabled. Under Rule 11(g) of the Companies (Audit and Auditors) Rules, your statutory auditor reports on whether this was done and whether the audit trail was preserved. India Briefing notes the retention period follows Section 128(5), which is eight years.
That has two consequences for a Tally to ERPNext migration. In ERPNext, confirm with your partner and auditor that change tracking is active and cannot be switched off by users for accounting documents, and that submitted documents are corrected by cancel and amend, never edited. In Tally, keep the data files with edit log intact, backed up and accessible in India for the retention period. Do not “clean up” the old company in Tally after go-live. Your auditor will ask for it.
Who should do what
| Role | Owns | Signs off |
|---|---|---|
| CFO | Cut-off date, chart of accounts, valuation rules | Opening trial balance and true-up |
| Accounts head | Party balances, bank reconciliation, GST set-up | Ageing reports and tax templates |
| Stores and production | Physical count, item clean-up, BOMs | Stock by warehouse |
| Statutory auditor | Audit trail and retention review | Comfort on the new system before year end audit |
| ERP partner | Mapping, import templates, trial loads, training | Technical reconciliation reports |
The auditor row is the one teams tend to skip in a Tally to ERPNext migration. Bring them in during January, show them the set-up and the plan, and ask what they need. It costs one meeting and saves a difficult conversation in September.
How this differs from a generic data migration
Our ERPNext data migration playbook covers the mechanics for any source system. A Tally to ERPNext migration has its own quirks. Tally groups do not map one to one with ERPNext account types. Tally stock items often mix trading and manufactured goods without BOMs. Bill-wise details may be switched off for some parties, which makes invoice-wise receivables hard to rebuild. And Tally cost centres are rarely set up the way ERPNext expects. Spend time in December on these, and January goes faster. If you would rather hand the extraction and mapping to a team that has done it, see our ERP data migration service.
If you are still deciding when to start, our 20-week ERPNext implementation timeline for a 1 April 2027 go-live works backwards from the year-end cutover.
Planning a 1 April 2027 go-live? November is the right time to scope it. Book a free 30-minute ERPNext consultation and we will walk through your Tally data, timeline and likely effort.
Frequently asked questions
How long does a Tally to ERPNext migration take?
For a typical mid-sized manufacturer, plan four to five months from scoping to go-live, including two trial migrations and a parallel run. A small trading business with clean data can move faster. The calendar is driven more by data clean-up and user readiness than by the import itself.
Can I import all my old Tally vouchers into ERPNext?
You can, but we rarely recommend it. Past-year vouchers are already audited and remain available in Tally. Bring across opening balances, open invoices, stock and active masters, and keep Tally readable for history.
What if my 31 March balances change after the audit?
Load provisional balances at go-live so the business can run. Once the FY 2026-27 audit is complete, post the adjustments as an opening Journal Entry and reconcile the trial balance again.
Do I need to keep Tally after moving to ERPNext?
Yes, at least in read-only form. The audit trail and books of earlier years must be preserved and accessible for the statutory retention period. Keep the data and a working licence or a verified export.
Which GST returns should come from ERPNext after go-live?
Returns for April 2027 onwards. March 2027 returns, filed in April, should come from Tally because the March invoices live there.
Is ERPNext compliant with the Companies Act audit trail rule?
ERPNext records document versions and enforces cancel and amend on submitted transactions. Confirm with your implementation partner that tracking is configured so users cannot disable it, and walk your auditor through the set-up before year end.
Tally to ERPNext migration: key takeaways
A Tally to ERPNext migration timed for 1 April 2027 avoids split GST returns and a two-system audit. Migrate masters, open items, opening balances, stock with valuation, fixed assets and GSTINs, and leave past-year vouchers in Tally. Plan two trial loads, a focused March parallel run and a post-audit true-up, and keep Tally data with its edit log preserved for the retention period required under the Companies Act audit trail rules.